From 1e0edb06d5d980a9a534db6dc830e59342404f53 Mon Sep 17 00:00:00 2001 From: "Bruce A. Mah" Date: Thu, 1 Jun 2006 17:50:36 +0000 Subject: [PATCH] Regen from errata/article.sgml r1.73.2.23. --- en/releases/6.1R/errata.html | 74 ++++++++++++++++++++++++++++++++---- 1 file changed, 67 insertions(+), 7 deletions(-) diff --git a/en/releases/6.1R/errata.html b/en/releases/6.1R/errata.html index b494083a48..7f452c6213 100644 --- a/en/releases/6.1R/errata.html +++ b/en/releases/6.1R/errata.html @@ -20,7 +20,7 @@ alink="#0000FF"> FreeBSD Documentation Project

$FreeBSD: src/release/doc/en_US.ISO8859-1/errata/article.sgml,v -1.73.2.22 2006/06/01 04:57:58 bmah Exp $
+1.73.2.23 2006/06/01 17:49:26 bmah Exp $

@@ -167,12 +167,24 @@ One known example is smartd from the sysutils/smartmontools port.

-

(2006/05/27) On FreeBSD/alpha, sysinstall sometimes does not allow a disk to be -labeled. The disk is presented in sysinstall but actions like 'A'auto do not result in a -disklabel being presented. Workaround is to boot the install CD, then select Fixit. From -the Fixit prompt run disklabel manually. For example: "disklabel -rw da1 auto" ensures a -valid disklabel is written onto da1. Reboot from the install media. sysinstall will now -detect a valid disklabel on the disk and allow it to be partitioned to your +

(2006/05/27, updated 2006/06/01) On FreeBSD/alpha, +sysinstall(8) +sometimes does not allow a disk to be labeled. The disk is presented in +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 + +disklabel(8) +manually. For example: disklabel -rw da1 auto ensures a valid +disklabel is written onto da1. Reboot from the install media. + +sysinstall(8) +will now detect a valid disklabel on the disk and allow it to be partitioned to your preference.

(2006/05/27) FreeBSD 6.1-RELEASE includes a change to some definitions in src/sys/net/if_media.h (revision 1.30.2.1). This could bre source-level compatibility with externally-maintained 10Gb Ethernet network drivers written for FreeBSD 6.0-RELEASE. This change should have been documented in the release notes.

+ +

(2006/06/01) A bug in the rc.d/jail startup script could +cause various problems for users attempting to configure +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.

+ +

(2006/06/01) Deadlocks have been observed (and can be reproduced) in some cases where +snapshots and quotas are both being used on a file system. This problem has been fixed on +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) Problems have been observed when trying to load packages from multiple +CDROMs inside the +sysinstall(8) +environment. Specifically, the disk-switching functionality in +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 +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 +install Xorg along with the base system, or at least before any other packages that +depend on it.

+ +

(2006/06/01) An error in the statistics-keeping logic in the UMA 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 will be merged to the RELENG_6 and RELENG_6_1 +branches after additional testing.

+ +

(2006/06/01) A longstanding bug in the i386 bootloader can cause root file system +corruption when the +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 +to HEAD and planned for merging after additional testing.