First, sorry for the long dry spell on information about 6.2-RELEASE. I
should have been sending out periodic status reports when we started to
hit a few delays.
Since RC1 we have been working out a few more bugs in device drivers, a
few device drivers were updated, BIND was updated, and bugs in several
other areas of the kernel have been worked out. We also wound up having
hardware problems with the primary distribution machine that took some
time to resolve.
All problems we felt needed to be addressed before 6.2 could be released
have been taken care of. Unless further testing turns up something new
RC2, which is available now for dowloading, will be the last of the
Release Candidates and 6.2-RELEASE should be ready in about 2 weeks.
Your continued help with testing would be greatly appreciated. If you
notice any problems with RC2 you can submit a PR or send mail to this
list.
Checksums for ISOs:
MD5 (6.2-RC2-alpha-bootonly.iso) = e6ea204d3e3b0e20ebc561c7b1d52150
MD5 (6.2-RC2-alpha-disc1.iso) = a3578cfd41bf9fb0fb258ea0da64a085
MD5 (6.2-RC2-amd64-bootonly.iso) = 11cbf691c78322f9a0d2a14e0651df19
MD5 (6.2-RC2-amd64-disc1.iso) = f1477df9bc3ba45a3ea6521708b09b35
MD5 (6.2-RC2-amd64-disc2.iso) = 0420385ee1617b807ca304efef815d97
MD5 (6.2-RC2-amd64-docs.iso) = e5312592494c0a2d8c9dff37c4ceab5d
MD5 (6.2-RC2-i386-bootonly.iso) = 3438ecae6bd8b8c5fd832bbf1e4b87e2
MD5 (6.2-RC2-i386-disc1.iso) = 1703e562f4e265debc56712165b1c32f
MD5 (6.2-RC2-i386-disc2.iso) = b2a80388bf05b637a9d8a5ed6a030454
MD5 (6.2-RC2-i386-docs.iso) = f0e796a1e66f982f337dcbca48daf513
MD5 (6.2-RC2-ia64-bootonly.iso) = 490f249e24e640e74e2b5d7f2f5f7043
MD5 (6.2-RC2-ia64-disc1.iso) = fb594f597af2b266ed541e80f500012b
MD5 (6.2-RC2-ia64-disc2.iso) = e0721e4bf39043198a8764ec7ef16508
MD5 (6.2-RC2-ia64-docs.iso) = 199b62b4d388689766fced2ca320f0e2
MD5 (6.2-RC2-ia64-livefs.iso) = e499b3fc6fdbb54129a77c9b603c6ae3
MD5 (6.2-RC1-pc98-bootonly.iso) = 43df2d851438b5212faa81e456190ae5
MD5 (6.2-RC1-pc98-disc1.iso) = ba33bc96d1c416f16e123d43c88110da
MD5 (6.2-RC2-sparc64-bootonly.iso) = b978eb34fd5862a50332a0cb3bb880fa
MD5 (6.2-RC2-sparc64-disc1.iso) = 04cff1890eb3b798ade0e2d0f64753a9
MD5 (6.2-RC2-sparc64-disc2.iso) = 2775c4325fc14a16226228969ff4221d
MD5 (6.2-RC2-sparc64-docs.iso) = 54e2a7ed7efd4f985bc9ae1d0e7fc369
SHA256 (6.2-RC2-alpha-bootonly.iso) =
19321abedf91c58972c43319281f0786c10ad8d17c3d43fca6d1abd1967af7df
SHA256 (6.2-RC2-alpha-disc1.iso) =
497f1b96960b1025f0100cbfcee1c714bdf7f6e9960646f59dbff3abdd779026
SHA256 (6.2-RC2-amd64-bootonly.iso) =
28650201578ad75ff09d2e4b61794a08e46e65076c6f794c1b8688c69d37ec21
SHA256 (6.2-RC2-amd64-disc1.iso) =
43c934950d65c8b2412ed4b367ef3ec08eb46ab103620165bad093ef90d478a6
SHA256 (6.2-RC2-amd64-disc2.iso) =
2e370e2d5c637a18ff0413c12f72b3c8a6332a164b033683387e8513bdd96831
SHA256 (6.2-RC2-amd64-docs.iso) =
605a045b5b44677f0a717310f871dd6988e0cd8d1edc82a52180210d3696d027
SHA256 (6.2-RC2-i386-bootonly.iso) =
1e3aefc186d37b2813b0d6e00ad6879f4906de8a4f4c0c156e0c30d0ece9cf9f
SHA256 (6.2-RC2-i386-disc1.iso) =
900561ee5b32ef5dd5c68444f759c941f59f7dea310dd08d09d3c233fad61618
SHA256 (6.2-RC2-i386-disc2.iso) =
01e586f5eb834de9eadde2ab6d3cb8e498a0ec4d6012963eb8cdbc2f652fc4bb
SHA256 (6.2-RC2-i386-docs.iso) =
8f7f40922c4cd254e419c674a7441e9f15c3f4a017c93dbf5c7011b5a584c400
SHA256 (6.2-RC2-ia64-bootonly.iso) =
c4c567856768e72273f40d8d6a2871df1b8e740e074415842d8a709b736a5023
SHA256 (6.2-RC2-ia64-disc1.iso) =
194797ed6e8617af1614f400c8f08f6614e20a2734e24bdfa05d2ba0e67503e2
SHA256 (6.2-RC2-ia64-disc2.iso) =
cc74718f913e7d8e6626429cd618f064fe00dd2559f43d2e2c7f289b9d87e8ad
SHA256 (6.2-RC2-ia64-docs.iso) =
954bac255cc799a885d1035bd65add6a5e0fda7f8645fcb44873459ed82fa26f
SHA256 (6.2-RC2-ia64-livefs.iso) =
4f4f4693792b185359f11609b71ef6e2f23b5509576d0a616fe10a67a6f6f8bf
SHA256 (6.2-RC1-pc98-bootonly.iso) =
66d30a5a3ca1b296cf9370a9116a1cce282d5f25d1843be36c21d731b4225bf6
SHA256 (6.2-RC1-pc98-disc1.iso) =
1a1ff42156d8e201feb54c6a1e36c3b07a682b22fc7ba8a13fee0ebef2316c26
SHA256 (6.2-RC2-sparc64-bootonly.iso) =
8415d46707c881fca685ebc044cf8dc450a30c51eb049f37a7a4ec8054914ea1
SHA256 (6.2-RC2-sparc64-disc1.iso) =
7c6a9fde09e99bfcc44308ce02c2e3b1cfb7b558da7b48f3685e8ed4e9ea7748
SHA256 (6.2-RC2-sparc64-disc2.iso) =
545f6952590c3642ccdee0ac292bd20647cf26bd2f9499a1e7f9d430d4ec06d0
SHA256 (6.2-RC2-sparc64-docs.iso) =
a2ee235f2dcb9e8695dbd77c71084a5f92165feb9d1fd1f260758ec7882aa5dc
--
Ken Smith
- From there to here, from here to | kensmith@cse.buffalo.edu
there, funny things are everywhere. |
- Theodore Geisel |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: This is a digitally signed message part
Url :
http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20061227/8b8578c6/attachment.pgp
Would someone please please please publicly document what all the various 6.x ISO images are, which of them are (or might be) needed for a fresh installation (assuming poor or nonexistent network connectivity), and which have overlapping bits. If this is actually explained anywhere that's supposed to be obvious, I have yet to find it. For anyone who's new to FreeBSD, it's challenging enough to try to figure out where to start. For someone who's been part of the FreeBSD community for a number of years, it's even more confusing, since there have been some fairly radical changes. (BTW, what's this "docs" ISO? That wasn't around in previous releases...) Also, as 64-bit CPUs become more commonplace, "which discs do I need" probably requires a more in-depth explanation. -=EPS=-
>http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install-diff-media.html#AEN3220Let me try to explain what's wrong here... This URL corresponds to "Preparing Your Own Installation Media," which appears after "Advanced Installation Guide." That's sure not the first place I'd look. Titles like "Choosing What to Install" or "Choosing Your Installation Media" are what are going to catch my eye. In a reasonably organized document, "Troubleshooting" would typically follow the last section with any content of interest to most readers--and I wouldn't look there unless I already had everything I thought I'd needed, actually attempted an installation, and then it failed somehow. Everything following this section should be applicable to even fewer situations. I'd expect "Advanced Installation Guide" to cover truly unusual ("special purpose" as opposed to "common installation") situations, and "Preparing Your Own Installation Media" to pertain to "remastering" (to borrow a term from Those Other Guys)--something I would never, ever be interested in doing (at least not any time in the foreseeable future). Basically, the titles are deceptive, and the Handbook is structured in such a way that it doesn't present information in any sort of logical order. That aside, the Handbook is hardly the first place anyone is going to start. I'd probably begin with the Hardware Notes for the -RELEASE to determine whether I should be bothering trying to install FreeBSD at all. Then I'd look at the Release Notes to see if there are any "gotchas" I should be aware of. After that, the Installation Instructions for my architecture. That's where I'd expect these questions to be answered. What's the first "meaningful" section in that document? How to install from Floppy Disks. Heck, most computers sold today don't even have floppy drives. That's followed by a section that mentions CDROM installation, but then starts babbling about boot floppies again. The first bullet point refers to "_the_ FreeBSD installation CD" but if I don't have something in my hot little hands that clearly says "Hi! I'm the FreeBSD installation CD you're looking for," that instruction isn't immediately helpful. Skipping past a number of sections that are clearly irrelevant, I come upon, e.g. "Question and Answer Section for i386 Architecture Users." My question isn't addressed here. That's followed by "Distribution Format"--a title that sounds promising. But it quickly becomes apparent this isn't going to answer my question, either. The subsequent sections increasingly smack of "not applicable," and finally I arrive at the "Troubleshooting" section, which tells me it's time to stop reading this document. Oh, there's a README file, which advises potential users to purchase commercially published media: "This is frequently the most convenient way to obtain FreeBSD for new installations." Why is that convenient? Because the discs are presumably labeled in a meaningful way, and they're likely accompanied by a piece of paper, slightly smaller than the front of a jewel box, that provides a concise "quick start guide." Having given up on the -RELEASE documentation, my next stop is going to be to the www.freebsd.org home page. Look, there's a FAQ link there. The FAQ page has a Table of Contents that begins Introduction, Documentation and Support, Installation. So, of course, I'm going to head straight to Installation. The very first item is "Which file do I download to get FreeBSD?" Hey, that sounds like my question. *click* The answer says I need floppy images?!? No! No! That's not what I want! You need to try to put yourself in an end user's frame of reference. It's easy to understand why even fairly experienced folks can find FreeBSD documentation baffling. I'm sure a fair number give up in disgust, and fall prey to the next evangelist who hands them an Ubuntu CD... P.S. The URL you gave makes no mention of "docs" or "livefs" images. -=EPS=-
Thomas Herrlin
2006-Dec-28 07:27 UTC
FreeBSD 6.2-RC2 Available - networking zoneli freeze problem still exist.
Ken Smith wrote: <snip>> All problems we felt needed to be addressed before 6.2 could be released > have been taken care of.It still runs networking daemons into a frozen zoneli state on heavy/(D)DOS network loads. Such processes cant be kill-9ed so there is no way to recover from it. (think frozen sshd and a very remote/headless server). See the stress test panic called 'Ran out of "128 Bucket" <http://people.FreeBSD.org/%7Epho/stress/log/cons210.html>' on the 6.2 todo list and my own latest test here: http://www.maniacs.se/~junics/temp/vmstat-z.txt This test was on a new 6.2-RC2 install with no zone limit tweaks nor any sbsize limits in /etc/login.conf. I just made a vm disk image with replication instructions, however Peter Holm have replicated it with his own tools so i have not bothered with it until now.> Unless further testing turns up something new > RC2, which is available now for dowloading, will be the last of the > Release Candidates and 6.2-RELEASE should be ready in about 2 weeks. > Your continued help with testing would be greatly appreciated. If you > notice any problems with RC2 you can submit a PR or send mail to this > list. ><snip> /Thomas Herrlin
Abdullah Al-Marrie
2007-Jan-08 01:22 UTC
FreeBSD 6.2-RC2 Available - networking zoneli freeze problem still exist.
On 12/28/06, Thomas Herrlin <junics-fbsdstable@atlantis.maniacs.se> wrote:> Ken Smith wrote: > > <snip> > > All problems we felt needed to be addressed before 6.2 could be released > > have been taken care of. > It still runs networking daemons into a frozen zoneli state on > heavy/(D)DOS network loads. Such processes cant be kill-9ed so there is > no way to recover from it. (think frozen sshd and a very remote/headless > server). > See the stress test panic called 'Ran out of "128 Bucket" > <http://people.FreeBSD.org/%7Epho/stress/log/cons210.html>' on the 6.2 > todo list and my own latest test here: > http://www.maniacs.se/~junics/temp/vmstat-z.txt > This test was on a new 6.2-RC2 install with no zone limit tweaks nor any > sbsize limits in /etc/login.conf. > I just made a vm disk image with replication instructions, however Peter > Holm have replicated it with his own tools so i have not bothered with > it until now. > > > Unless further testing turns up something new > > RC2, which is available now for dowloading, will be the last of the > > Release Candidates and 6.2-RELEASE should be ready in about 2 weeks. > > Your continued help with testing would be greatly appreciated. If you > > notice any problems with RC2 you can submit a PR or send mail to this > > list. > > > <snip> > > /Thomas HerrlinHave you tried these options in kernel? options DEVICE_POLLING options HZ=1000 add this line to the end of your /etc/sysctl.conf: kern.polling.enable=1 DEVICE_POLLING changes the method through which data gets from your network card to the kernel. Traditionally, each time the network card needs attention (for example when it receives a packet), it generates an interrupt request. The request causes a context switch and a call to an interrupt handler. A context switch is when the CPU and kernel have to switch from user land (the user's programs or daemons), and kernel land (dealing with device drivers, hardware, and other kernel-bound tasks). The last few years have seen significant improvements in the efficiency of context switching but it is still an extremely expensive operation. Furthermore, the amount of time the system can have to spend when dealing with an interrupt can be almost limitless. It is completely possible for an interrupt to never free the kernel, leaving your machine unresponsive. Those of us unfortunate enough to be on the wrong side of certain Denial of Service attacks will know about this. More info in here A guide to server and workstation optimization, by Avleen Vig http://silverwraith.com/papers/freebsd-tuning.php -- Regards, -Abdullah Ibn Hamad Al-Marri Arab Portal http://www.WeArab.Net/