molotov
September 27th, 2004, 14:25
>>IMPORTANT:
>>BIND9 is being imported and will be in the next and likely final beta,
>>BETA7. Users of the named daemon should visit the ISC website for
>>information about migrating to BIND9.
>
>
> BETA6 still has some critical and/or serious bugs open apparently
> (according to the PR data base):
>
> 1. /bin/sh "unset" is still in violation of IEEE Std 1003.1, 2004
> edition. FIX IS AVAILABLE, bug has been open for many months, has
> persisted in BETA4 and 5.
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=standards/45738
> http://lists.freebsd.org/pipermail/freebsd-current/2004-September/037819.html

I'll defer this to the standards folks.

>
> 2. tcpdump IPv6CP segfaults are still open as of BETA5, FIX IS AVAILABLE:
> http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/71453
>

Looks pretty straight-forward. Anyone want to import the fix from the
tcpdump CVS tree?
4
> 3. data corruption on unaligned block access bug, kern/60313,
> is still open and unpatched AFAICS

Is this actually an issue in FreeBSD 5? In the audit trail of the PR,
Bruce Evans seems to concede that GEOM checks block alignment properly.

>
> 4. NIS is still faulty in pretending users aren't there when in fact NIS
> cannot tell if an account exists; bin/46866 is still open and unpatched

While it's a compelling argument to follow the Solaris behavior, it's
also a compelling argument to have a reasonable timeout on password lookups.

>
> 5. default inetd configuration denial of service bug, conf/33670, is still
> open and unpatched AND A LAST CHANCE TO FIX NOW

inetd is not turned on by default. What do OpenBSD and NetBSD do?
What does Linux do with xinetd?

>
> 6. (portsmgr issue) no "yes or no" or whatsoever for my inquires whether
> ports/72017 can be committed in spite of the freeze. It's a
> bugfix-only update.
>
> Please state which of these will be fixed before 5.3-RELEASE and what
> further help is needed with these.

looks like one more planned beta before we see RC1

bumbler
September 28th, 2004, 09:59
I've read a few reports on Usenet that some stuff is newly broken on Beta6, and it makes me reluctant to update. My Beta5 is working quite well. I think I'll wait for the RCs. At least the Mozilla bugs are patched, and I rebuilt it overnight.

Bumbler

molotov
September 28th, 2004, 15:37
Yea, I get that impression from the mailing lists. Probablly a good call there Bumbler. Beta7 may offer a smoother transition.

molotov
September 28th, 2004, 15:42
Here we go:
The FreeBSD Release Engineering Team is proud to announce the
availability of FreeBSD 5.3-BETA6. This is the sixth BETA of the 5.3
release cycle. It is intended for early adopters and those wishing to
help find and/or fix bugs. The 5.3 release cycle will continue with
weekly BETA builds while bugs are being fixed and features finalized.
The schedule is at http://www.freebsd.org/releases/5.3R/schedule.html.
Be sure to check the "Known issues" below, there are known problems
still being worked on at this time.

IMPORTANT:
BIND9 is being imported and will be in the next and likely final beta,
BETA7. Users of the named daemon should visit the ISC website for
information about migrating to BIND9.

Fixes and Enhancements made since BETA5:

- Many USB device updates
- Fix a panic when unloading the if_tap module
- Fix a lock order reversal in the network ioctl code
- Fix a panic with PF
- Fix large UID and GID handling in libarchive
- The PFIL_HOOKS kernel option is now silently enabled by default.
- Various locking fixes to the network stack
- The net.inet.ip.check_interface sysctl is off by default now
- Fix a long-standing panic on i386 and amd64 SMP under extreme load
- Many fixes to gvinum
- The README.html files that are generated for each port are no longer
installed. They can be found on the disc2 live filesystem.
- Fix a rare panic on startup on i386 SMP
- Fix problem with multiple floppy drives all having the name
"/dev/fd0"

Known issues in this release

- There are known data corruption issues with gvinum. Fixes are being
tested now.
- There are several problems with the ATA driver that can result in
system hangs at boot and erroneous disk failures. Fixes for these
are being tested now and will be in the next BETA.
- Detaching a USB Hub device, including many keyboards and monitors,
will trigger a panic. The fix for this is being tested and will be
in the next BETA.
- The Synaptics Touchpad mouse support is known to have issues with
responsiveness. It can be disabled with 'hint.psm.0.flags="0x200"'
in "/boot/device.hints". This will be resolved for the release.
- There are reports of packet corruption with the nge(1) driver when
the network stack is run without Giant. A fix is being tested.

A complete list of defects that will be fixed for the release can be
found at http://www.freebsd.org/releases/5.3R/todo.html.

Availability:

For people wishing to upgrade older systems using cvsup(1) and the
procedure described in src/UPDATING the CVS tag to use is RELENG_5
at this point. Note that like all RELENG_X branches this is an
active development branch. We do not recommend those branches for
normal use (for normal use RELENG_X_Y branches are more appropriate,
e.g. RELENG_4_10 is the current stable branch).

As of this writing the following are available on ftp.freebsd.org
along with some of the mirror sites:

alpha: all images available
amd64: all images available
i386: all images available
ia64: miniinst available
pc98: miniinst available
sparc64: all images available

MD5s for the builds that are complete at this time are:

MD5 (5.3-BETA6-alpha-bootonly.iso) = d466a7f804784fad845bb9c5c2f69d9c
MD5 (5.3-BETA6-alpha-disc1.iso) = bf3dc22140abe43c564f44c2b8d22a58
MD5 (5.3-BETA6-alpha-disc2.iso) = 814e2e1dc02bcde8e00b230a5734e36c
MD5 (5.3-BETA6-alpha-miniinst.iso) = f50bc98fc56c295e56ac59e50833ed3c

MD5 (5.3-BETA6-amd64-bootonly.iso) = a6fdd46c64f32ab154c50934255f1316
MD5 (5.3-BETA6-amd64-disc2.iso) = 9f15d66b13ccbfe1a3bd9dede08dfeff
MD5 (5.3-BETA6-amd64-miniinst.iso) = 864ad066ea17aa5e724b216a594a0aec
MD5 (5.3-BETA6-amd64-disc1.iso) = 52a17e83f4c0f3121a4db0e5d208a4e5

MD5 (5.3-BETA6-i386-bootonly.iso) = 17a194ba9beccd5075514d94b87c9035
MD5 (5.3-BETA6-i386-disc1.iso) = d6b2da7b6134da2e4beb7f09d658df2c
MD5 (5.3-BETA6-i386-disc2.iso) = 243af47dff5b3bd0e06fd37f529d642a
MD5 (5.3-BETA6-i386-miniinst.iso) = 31e0ded04415e337054c32a1d95db8d5

MD5 (5.3-BETA6-ia64-bootonly.iso) = 53b95d1e940e2f55ac1e6f883a63f557
MD5 (5.3-BETA6-ia64-disc2.iso) = ce10109f514a1bcf231d40b57405e4b3
MD5 (5.3-BETA6-ia64-miniinst.iso) = 4410203b8b8b01600b86c3b3ece7f619

MD5 (5.3-BETA6-pc98-disc2.iso) = 4c3a24517ef20c081aab47e87d5382cf
MD5 (5.3-BETA6-pc98-miniinst.iso) = 6b745905e68af92e0b6825759f8a89d4

MD5 (5.3-BETA6-sparc64-bootonly.iso) = 6bdfadcc97ee1fcb86717ce301f3af65
MD5 (5.3-BETA6-sparc64-disc1.iso) = 32635c99e5db0d22f5bdb8d73f74c045
MD5 (5.3-BETA6-sparc64-disc2.iso) = 5b84f646968d363410dd06c51a681a3a
MD5 (5.3-BETA6-sparc64-miniinst.iso) = 0839853f14cb2866740babc09ba511c7