$FreeBSD: src/release/doc/en_US.ISO8859-1/errata/article.sgml,v
-1.73.2.25 2006/06/14 16:29:06 hrs Exp $
+1.73.2.26 2006/06/16 21:30:41 bmah Exp $
Inoperative access controls in +href="http://www.FreeBSD.org/cgi/man.cgi?query=ypserv&sektion=8&manpath=FreeBSD+6.0-stable"> ypserv(8)
(2006/05/13) A change in the ata(4) driver in +href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+6.0-stable"> +ata(4) driver in FreeBSD 6.1-RELEASE modified a software interface visible from userland programs. Programs that use the IOCATAREQUEST +href="http://www.FreeBSD.org/cgi/man.cgi?query=ioctl&sektion=2&manpath=FreeBSD+6.0-stable"> ioctl(2) interface will need to be recompiled. Typically, these programs communicate directly with ATA and ATAPI drives, such as CDROM burning or ripping tools, or monitoring utilities. @@ -177,21 +177,21 @@ href="http://www.FreeBSD.org/cgi/url.cgi?ports/sysutils/smartmontools/pkg-descr" class="FILENAME">sysutils/smartmontools port.
(2006/05/27, updated 2006/06/01) On FreeBSD/alpha, +href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.0-stable"> sysinstall(8) sometimes does not allow a disk to be labeled. The disk is presented in +href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.0-stable"> sysinstall(8) but actions like Auto do not result in a disklabel being presented. One workaround is to boot the install CD, then select Fixit. From the Fixit# prompt, run +href="http://www.FreeBSD.org/cgi/man.cgi?query=disklabel&sektion=8&manpath=FreeBSD+6.0-stable"> disklabel(8) manually. For example: disklabel -rw da1 auto ensures a valid disklabel is written onto da1. Reboot from the install media. +href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.0-stable"> sysinstall(8) will now detect a valid disklabel on the disk and allow it to be partitioned to your preference.
@@ -204,7 +204,7 @@ notes.(2006/06/01, updated 2006/06/07) A bug in the rc.d/jail startup script could cause various problems for users attempting to configure +href="http://www.FreeBSD.org/cgi/man.cgi?query=jail&sektion=2&manpath=FreeBSD+6.0-stable"> jail(2) environments at system startup time. A fix has been committed to HEAD and RELENG_6; it will be merged to the RELENG_6_1 errata fix branch after more testing.
@@ -214,22 +214,22 @@ snapshots and quotas are both being used on a file system. This problem has been the HEAD and RELENG_6 branches; more testing is planned before a merge to the RELENG_6_1 errata fix branch. -(2006/06/01) A bug in the Neighbor Discovery Protocol (NDP) implementation causes -spurious error messages for point-to-point IPv6 links on FreeBSD 6.1-RELEASE. This -behavior is a regression from FreeBSD 6.0-RELEASE. A solution for this problem is being -analyzed and tested.
+(2006/06/01, updated 2006/06/16) A bug in the Neighbor Discovery Protocol (NDP) +implementation causes spurious error messages for point-to-point IPv6 links on FreeBSD +6.1-RELEASE. This behavior is a regression from FreeBSD 6.0-RELEASE. A solution for this +problem has been committed to HEAD and is planned for merging to RELENG_6.
(2006/06/01) Problems have been observed when trying to load packages from multiple CDROMs inside the +href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.0-stable"> sysinstall(8) environment. Specifically, the disk-switching functionality in +href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.0-stable"> sysinstall(8) seems to become confused about the contents of a disk that has just been requested. This situation has been seen primarily when installing the base system without Xorg (which lives on the first CDROM of a multi-disk set), and then later using +href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.0-stable"> sysinstall(8) to load some packages (such as the GNOME or KDE desktop environments) from a subsequent CDROM that depend on Xorg. As a workaround during a new install, one should try to @@ -240,11 +240,11 @@ depend on it.
kernel memory allocator has led to the number of requests for mbufs denied (as reported by netstat -m) to increase erroneously. A fix for this problem has been committed to HEAD and RELENG_6 and will be merged to the -RELENG_6_1 branche after additional testing. +RELENG_6_1 branch after additional testing.(2006/06/01) A longstanding bug in the i386 bootloader can cause root file system corruption when the +href="http://www.FreeBSD.org/cgi/man.cgi?query=nextboot&sektion=8&manpath=FreeBSD+6.0-stable"> nextboot(8) utility is used and the /boot/nextboot.conf configuration file happens to be located after cylinder 1023 on the boot disk. A bugfix has been committed