Copyright © 2000, 2001, 2002, 2003, 2004 The FreeBSD Documentation Project
$FreeBSD: src/release/doc/en_US.ISO8859-1/errata/article.sgml,v
1.69.2.2 2004/10/24 12:10:37 hrs Exp $
FreeBSD is a registered trademark of Wind River Systems, Inc. This is expected to change soon.
Intel, Celeron, EtherExpress, i386, i486, Itanium, Pentium, and Xeon are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
Sparc, Sparc64, SPARCEngine, and UltraSPARC are trademarks of SPARC International, Inc in the United States and other countries. Products bearing SPARC trademarks are based upon architecture developed by Sun Microsystems, Inc.
Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this document, and the FreeBSD Project was aware of the trademark claim, the designations have been followed by the ``™'' or the ``®'' symbol.
This document lists errata items for FreeBSD 5.3-RELEASE, containing significant information discovered after the release or too late in the release cycle to be otherwise included in the release documentation. This information includes security advisories, as well as news relating to the software or documentation that could affect its operation or usability. An up-to-date version of this document should always be consulted before installing this version of FreeBSD.
This errata document for FreeBSD 5.3-RELEASE will be maintained until the release of FreeBSD 5.4-RELEASE.
This errata document contains ``late-breaking news'' about FreeBSD 5.3-RELEASE Before installing this version, it is important to consult this document to learn about any post-release discoveries or problems that may already have been found and fixed.
Any version of this errata document actually distributed with the release (for example, on a CDROM distribution) will be out of date by definition, but other copies are kept updated on the Internet and should be consulted as the ``current errata'' for this release. These other copies of the errata are located at http://www.FreeBSD.org/releases/, plus any sites which keep up-to-date mirrors of this location.
Source and binary snapshots of FreeBSD 5-STABLE also contain up-to-date copies of this document (as of the time of the snapshot).
For a list of all FreeBSD CERT security advisories, see http://www.FreeBSD.org/security/ or ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/.
(26 Oct 2004) /usr/share/examples/cvsup/standard-supfile, a sample supfile for CVSup incorrectly includes RELENG_5 as the target branch. The following line in the file:
*default release=cvs tag=RELENG_5
should be replaced with the following:
*default release=cvs tag=RELENG_5_3
(26 Oct 2004) Sometimes the performance of the re(4) and em(4) drivers can become poor under heavy load. Especially, there are reports of em(4) on the IBM ThinkPad T40 locking up under such conditions.
(26 Oct 2004) There are reports of the sk(4) driver locking up under heavy load. As a workaround, bring the interface down then back up, and it will clear the condition.
(26 Oct 2004) The vr(4) can cause a panic when it is detached (on shutdown, for example).
(26 Oct 2004) The burncd(8) utility is functional but may behave erratically on some systems. Reported symptoms include that burncd(8) can appear to hang up and never complete while the operation actually does complete, and the progress indicator does not show the correct value. Workarounds include:
Eject and re-insert a media after burning a CD.
Press Ctrl-C when burncd(8) appears to hang up in spite the access LED goes inactive.
(26 Oct 2004) When the user/group rule modificators in pf(4) and ipfw(4) are used, the loader tunable debug.mpsafenet must be set to 0 (this is 1 by default). For example, the following rules are affected:
for ipfw(4):
count ip from any to 192.168.2.1 uid root
for pf(4):
block log quick proto { tcp, udp } all user root
To set debug.mpsafenet to 0 in every boot time, add the following line into /boot/loader.conf:
debug.mpsafenet=0
More specifically, the group and user filter parameters in pf(4), and the gid, jail, and uid rule options in ipfw(4) are relevant. If debug.mpsafenet is set to 1, the system can hang up when the rule is evaluated due to a lock order reversal with the socket layer. More details can be found in the ipfw(8) and pf.conf(5) manual pages.
(26 Oct 2004) The classical vinum(4) subsystem has been replaced with the new geom(4)-based one. To activate the geom(4)-aware vinum on boot time, the following steps are needed:
Add start_vinum="YES" to /etc/rc.conf.
Change start_cmd="vinum start" to start_cmd="gvinum start" in /etc/rc.d/vinum.
Add geom_vinum_load="YES" to /boot/loader.conf.
Change /dev/vinum/* to /dev/gvinum/* in /etc/fstab
Reboot your system.
While it is basically backward compatible, note that the vinum(8) utility cannot be used any longer, and the userland control program for geom(4)-aware vinum, gvinum still lacks a few functionality. Since the classical vinum(4) subsystem is still included but has several problems, it is considered non-functional in this release.
This file, and other release-related documents, can be downloaded from http://snapshots.jp.FreeBSD.org/.
For questions about FreeBSD, read the documentation before contacting <questions@FreeBSD.org>.
All users of FreeBSD 5-STABLE should subscribe to the <stable@FreeBSD.org> mailing list.
For questions about this documentation, e-mail <doc@FreeBSD.org>.