os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Regen from errata/article.sgml r1.73.2.23.

Browse source
This commit is contained in:
Bruce A. Mah 2006-06-01 17:50:36 +00:00
parent cbb422aafa
commit 1e0edb06d5
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=27997
1 changed files with 67 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

74
en/releases/6.1R/errata.html
View file

@ -20,7 +20,7 @@ alink="#0000FF">
FreeBSD Documentation Project</p>
<p class="PUBDATE">$FreeBSD: src/release/doc/en_US.ISO8859-1/errata/article.sgml,v
1.73.2.22 2006/06/01 04:57:58 bmah Exp $<br />
1.73.2.23 2006/06/01 17:49:26 bmah Exp $<br />
</p>
<div class="LEGALNOTICE"><a id="TRADEMARKS" name="TRADEMARKS"></a>
@ -167,12 +167,24 @@ One known example is <tt class="FILENAME">smartd</tt> from the <a
href="http://www.FreeBSD.org/cgi/url.cgi?ports/sysutils/smartmontools/pkg-descr"><tt
class="FILENAME">sysutils/smartmontools</tt></a> port.</p>
<p>(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
<p>(2006/05/27, updated 2006/06/01) On FreeBSD/alpha, <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.0-stable">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a>
sometimes does not allow a disk to be labeled. The disk is presented in <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.0-stable">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a>
but actions like <span class="GUIMENUITEM">Auto</span> do not result in a disklabel being
presented. One workaround is to boot the install CD, then select <span
class="GUIMENUITEM">Fixit</span>. From the <samp class="PROMPT">Fixit#</samp> prompt, run
<a
href="http://www.FreeBSD.org/cgi/man.cgi?query=disklabel&sektion=8&manpath=FreeBSD+6.0-stable">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">disklabel</span>(8)</span></a>
manually. For example: <tt class="COMMAND">disklabel -rw da1 auto</tt> ensures a valid
disklabel is written onto <tt class="DEVICENAME">da1</tt>. Reboot from the install media.
<a
href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.0-stable">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a>
will now detect a valid disklabel on the disk and allow it to be partitioned to your
preference.</p>
<p>(2006/05/27) FreeBSD 6.1-RELEASE includes a change to some definitions in <tt
@ -180,6 +192,54 @@ class="FILENAME">src/sys/net/if_media.h</tt> (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.</p>
<p>(2006/06/01) A bug in the <tt class="FILENAME">rc.d/jail</tt> startup script could
cause various problems for users attempting to configure <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=jail&sektion=2&manpath=FreeBSD+6.0-stable">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">jail</span>(2)</span></a>
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.</p>
<p>(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.</p>
<p>(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.</p>
<p>(2006/06/01) Problems have been observed when trying to load packages from multiple
CDROMs inside the <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.0-stable">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a>
environment. Specifically, the disk-switching functionality in <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.0-stable">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a>
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 <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.0-stable">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a> 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.</p>
<p>(2006/06/01) An error in the statistics-keeping logic in the UMA kernel memory
allocator has led to the number of <tt class="LITERAL">requests for mbufs denied</tt> (as
reported by <tt class="COMMAND">netstat -m</tt>) 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.</p>
<p>(2006/06/01) A longstanding bug in the i386 bootloader can cause root file system
corruption when the <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=nextboot&sektion=8&manpath=FreeBSD+6.0-stable">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">nextboot</span>(8)</span></a>
utility is used and the <tt class="FILENAME">/boot/nextboot.conf</tt> 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.</p>
</div>
</div>