Regen from article.sgml 1.50.

This commit is contained in:
Bruce A. Mah 2003-09-20 00:21:52 +00:00
parent 99a6588c0b
commit 11f2eba086
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/www/; revision=18180

View file

@ -4,104 +4,80 @@
<head> <head>
<meta name="generator" content="HTML Tidy, see www.w3.org" /> <meta name="generator" content="HTML Tidy, see www.w3.org" />
<title>FreeBSD 5.1-RELEASE Errata</title> <title>FreeBSD 5.1-RELEASE Errata</title>
<meta name="GENERATOR" <meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.73 " />
content="Modular DocBook HTML Stylesheet Version 1.73 " />
<link rel="STYLESHEET" type="text/css" href="docbook.css" /> <link rel="STYLESHEET" type="text/css" href="docbook.css" />
</head> </head>
<body class="ARTICLE" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#840084"
<body class="ARTICLE" bgcolor="#FFFFFF" text="#000000" alink="#0000FF">
link="#0000FF" vlink="#840084" alink="#0000FF">
<div class="ARTICLE"> <div class="ARTICLE">
<div class="TITLEPAGE"> <div class="TITLEPAGE">
<h1 class="TITLE"><a id="AEN2" name="AEN2">FreeBSD <h1 class="TITLE"><a id="AEN2" name="AEN2">FreeBSD 5.1-RELEASE Errata</a></h1>
5.1-RELEASE Errata</a></h1>
<h3 class="CORPAUTHOR">The FreeBSD Project</h3> <h3 class="CORPAUTHOR">The FreeBSD Project</h3>
<p class="COPYRIGHT">Copyright &copy; 2000, 2001, 2002, <p class="COPYRIGHT">Copyright &copy; 2000, 2001, 2002, 2003 by The FreeBSD Documentation
2003 by The FreeBSD Documentation Project</p> Project</p>
<p class="PUBDATE">$FreeBSD: <p class="PUBDATE">$FreeBSD: src/release/doc/en_US.ISO8859-1/errata/article.sgml,v 1.50
src/release/doc/en_US.ISO8859-1/errata/article.sgml,v 1.49 2003/09/20 00:17:52 bmah Exp $<br />
2003/09/16 23:25:48 bmah Exp $<br />
</p> </p>
<div class="LEGALNOTICE"> <div class="LEGALNOTICE"><a id="TRADEMARKS" name="TRADEMARKS"></a>
<a id="TRADEMARKS" name="TRADEMARKS"></a> <p>FreeBSD is a registered trademark of Wind River Systems, Inc. This is expected to
change soon.</p>
<p>FreeBSD is a registered trademark of Wind River <p>Intel, Celeron, EtherExpress, i386, i486, Itanium, Pentium, and Xeon are trademarks or
Systems, Inc. This is expected to change soon.</p> registered trademarks of Intel Corporation or its subsidiaries in the United States and
other countries.</p>
<p>Intel, Celeron, EtherExpress, i386, i486, Itanium, <p>Sparc, Sparc64, SPARCEngine, and UltraSPARC are trademarks of SPARC International, Inc
Pentium, and Xeon are trademarks or registered trademarks in the United States and other countries. Products bearing SPARC trademarks are based
of Intel Corporation or its subsidiaries in the United upon architecture developed by Sun Microsystems, Inc.</p>
States and other countries.</p>
<p>Sparc, Sparc64, SPARCEngine, and UltraSPARC are <p>Many of the designations used by manufacturers and sellers to distinguish their
trademarks of SPARC International, Inc in the United products are claimed as trademarks. Where those designations appear in this document, and
States and other countries. Products bearing SPARC the FreeBSD Project was aware of the trademark claim, the designations have been followed
trademarks are based upon architecture developed by Sun by the ``&trade;'' or the ``&reg;'' symbol.</p>
Microsystems, Inc.</p>
<p>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 ``&trade;'' or the ``&reg;'' symbol.</p>
</div> </div>
<hr /> <hr />
</div> </div>
<blockquote class="ABSTRACT"> <blockquote class="ABSTRACT">
<div class="ABSTRACT"> <div class="ABSTRACT"><a id="AEN19" name="AEN19"></a>
<a id="AEN19" name="AEN19"></a> <p>This document lists errata items for FreeBSD 5.1-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.</p>
<p>This document lists errata items for FreeBSD <p>This errata document for FreeBSD 5.1-RELEASE will be maintained until the release of
5.1-RELEASE, containing significant information FreeBSD 5.2-RELEASE.</p>
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.</p>
<p>This errata document for FreeBSD 5.1-RELEASE will be
maintained until the release of FreeBSD 5.2-RELEASE.</p>
</div> </div>
</blockquote> </blockquote>
<div class="SECT1"> <div class="SECT1">
<hr /> <hr />
<h1 class="SECT1"><a id="INTRO" name="INTRO">1 Introduction</a></h1>
<h1 class="SECT1"><a id="INTRO" name="INTRO">1 <p>This errata document contains ``late-breaking news'' about FreeBSD 5.1-RELEASE. Before
Introduction</a></h1> 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.</p>
<p>This errata document contains ``late-breaking news'' <p>Any version of this errata document actually distributed with the release (for
about FreeBSD 5.1-RELEASE. Before installing this version, example, on a CDROM distribution) will be out of date by definition, but other copies are
it is important to consult this document to learn about any kept updated on the Internet and should be consulted as the ``current errata'' for this
post-release discoveries or problems that may already have release. These other copies of the errata are located at <a
been found and fixed.</p>
<p>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 <a
href="http://www.FreeBSD.org/releases/" href="http://www.FreeBSD.org/releases/"
target="_top">http://www.FreeBSD.org/releases/</a>, plus target="_top">http://www.FreeBSD.org/releases/</a>, plus any sites which keep up-to-date
any sites which keep up-to-date mirrors of this mirrors of this location.</p>
location.</p>
<p>Source and binary snapshots of FreeBSD 5-CURRENT also <p>Source and binary snapshots of FreeBSD 5-CURRENT also contain up-to-date copies of
contain up-to-date copies of this document (as of the time this document (as of the time of the snapshot).</p>
of the snapshot).</p>
<p>For a list of all FreeBSD CERT security advisories, see <p>For a list of all FreeBSD CERT security advisories, see <a
<a href="http://www.FreeBSD.org/security/" href="http://www.FreeBSD.org/security/"
target="_top">http://www.FreeBSD.org/security/</a> or <a target="_top">http://www.FreeBSD.org/security/</a> or <a
href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/" href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/"
target="_top">ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/</a>.</p> target="_top">ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/</a>.</p>
@ -109,125 +85,101 @@
<div class="SECT1"> <div class="SECT1">
<hr /> <hr />
<h1 class="SECT1"><a id="SECURITY" name="SECURITY">2 Security Advisories</a></h1>
<h1 class="SECT1"><a id="SECURITY" name="SECURITY">2
Security Advisories</a></h1>
<p>The implementation of the <a <p>The implementation of the <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=realpath&amp;sektion=3&amp;manpath=FreeBSD+5.1-current"> href="http://www.FreeBSD.org/cgi/man.cgi?query=realpath&amp;sektion=3&amp;manpath=FreeBSD+5.1-current">
<span class="CITEREFENTRY"><span <span class="CITEREFENTRY"><span class="REFENTRYTITLE">realpath</span>(3)</span></a>
class="REFENTRYTITLE">realpath</span>(3)</span></a> function contained a single-byte buffer overflow bug. This had various impacts, depending
function contained a single-byte buffer overflow bug. This on the application using <a
had various impacts, depending on the application using <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=realpath&amp;sektion=3&amp;manpath=FreeBSD+5.1-current"> href="http://www.FreeBSD.org/cgi/man.cgi?query=realpath&amp;sektion=3&amp;manpath=FreeBSD+5.1-current">
<span class="CITEREFENTRY"><span <span class="CITEREFENTRY"><span class="REFENTRYTITLE">realpath</span>(3)</span></a> and
class="REFENTRYTITLE">realpath</span>(3)</span></a> and other factors. This bug was fixed on the 5-CURRENT development branch before 5.1-RELEASE;
other factors. This bug was fixed on the 5-CURRENT FreeBSD 5.1-RELEASE is therefore not affected. However, this change was not noted in the
development branch before 5.1-RELEASE; FreeBSD 5.1-RELEASE release documentation. For more information, see security advisory <a
is therefore not affected. However, this change was not
noted in the release documentation. For more information,
see security advisory <a
href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:08.realpath.asc" href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:08.realpath.asc"
target="_top">FreeBSD-SA-03:08</a>.</p> target="_top">FreeBSD-SA-03:08</a>.</p>
<p>The kernel contains a bug that could allow it to attempt <p>The kernel contains a bug that could allow it to attempt delivery of invalid signals,
delivery of invalid signals, leading to a kernel panic or, leading to a kernel panic or, under some circumstances, unauthorized modification of
under some circumstances, unauthorized modification of kernel memory. This bug has been fixed on the 5-CURRENT development branch and the
kernel memory. This bug has been fixed on the 5-CURRENT 5.1-RELEASE security fix branch. For more information, see security advisory <a
development branch and the 5.1-RELEASE security fix branch.
For more information, see security advisory <a
href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:09.signal.asc" href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:09.signal.asc"
target="_top">FreeBSD-SA-03:09</a>.</p> target="_top">FreeBSD-SA-03:09</a>.</p>
<p>A bug in the iBCS2 emulation module could result in <p>A bug in the iBCS2 emulation module could result in disclosing the contents of kernel
disclosing the contents of kernel memory. (Note that this memory. (Note that this module is not enabled in FreeBSD by default.) This bug has been
module is not enabled in FreeBSD by default.) This bug has fixed on the 5-CURRENT development branch and the 5.1-RELEASE security fix branch. More
been fixed on the 5-CURRENT development branch and the information can be found in security advisory <a
5.1-RELEASE security fix branch. More information can be
found in security advisory <a
href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:10.ibcs2.asc" href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:10.ibcs2.asc"
target="_top">FreeBSD-SA-03:10</a>.</p> target="_top">FreeBSD-SA-03:10</a>.</p>
<p><b class="APPLICATION">OpenSSH</b> contains a bug in its <p><b class="APPLICATION">OpenSSH</b> contains a bug in its buffer management code that
buffer management code that could potentially cause it to could potentially cause it to crash. This bug has been fixed via a vendor-supplied patch
crash. This bug has been fixed via a vendor-supplied patch on the 5-CURRENT development branch and the 5.1-RELEASE security fix branch. For more
on the 5-CURRENT development branch and the 5.1-RELEASE details, refer to security advisory <a
security fix branch. For more details, refer to security
advisory <a
href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:12.openssh.asc" href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:12.openssh.asc"
target="_top">FreeBSD-SA-03:12</a>.</p> target="_top">FreeBSD-SA-03:12</a>.</p>
<p><b class="APPLICATION">sendmail</b> contains a remotely-exploitable buffer overflow.
This bug has been fixed via a new version import on the 5-CURRENT development branch and
via a vendor-supplied patch on the 5.1-RELEASE security fix branch. More details can be
found in security advisory <a
href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:13.sendmail.asc"
target="_top">FreeBSD-SA-03:13</a>.</p>
</div> </div>
<div class="SECT1"> <div class="SECT1">
<hr /> <hr />
<h1 class="SECT1"><a id="OPEN-ISSUES" name="OPEN-ISSUES">3 Open Issues</a></h1>
<h1 class="SECT1"><a id="OPEN-ISSUES" name="OPEN-ISSUES">3
Open Issues</a></h1>
<p>The RAIDframe disk driver described in <a <p>The RAIDframe disk driver described in <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=raid&amp;sektion=4&amp;manpath=FreeBSD+5.1-current"> href="http://www.FreeBSD.org/cgi/man.cgi?query=raid&amp;sektion=4&amp;manpath=FreeBSD+5.1-current">
<span class="CITEREFENTRY"><span <span class="CITEREFENTRY"><span class="REFENTRYTITLE">raid</span>(4)</span></a> is
class="REFENTRYTITLE">raid</span>(4)</span></a> is
non-functional for this release.</p> non-functional for this release.</p>
<p>ACPI seems to make some <span <p>ACPI seems to make some <span class="TRADEMARK">i386</span>&#8482; machines unstable.
class="TRADEMARK">i386</span>&#8482; machines unstable. Turning off ACPI support may help solve some of these problems; see an item in <a
Turning off ACPI support may help solve some of these href="#LATE-NEWS">Section 4</a>.</p>
problems; see an item in <a href="#LATE-NEWS">Section
4</a>.</p>
<p>An integer overflow could cause kernel panics on <p>An integer overflow could cause kernel panics on PAE-using machines with certain
PAE-using machines with certain memory sizes. This bug has memory sizes. This bug has been corrected on both the <tt class="LITERAL">RELENG_5_1</tt>
been corrected on both the <tt and <tt class="LITERAL">HEAD</tt> branches. A workaround for this problem is to remove
class="LITERAL">RELENG_5_1</tt> and <tt some memory, update the system in question, and reinstall the memory.</p>
class="LITERAL">HEAD</tt> branches. A workaround for this
problem is to remove some memory, update the system in
question, and reinstall the memory.</p>
<p>Attempting to write to an <a <p>Attempting to write to an <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=msdosfs&amp;sektion=5&amp;manpath=FreeBSD+5.1-current"> href="http://www.FreeBSD.org/cgi/man.cgi?query=msdosfs&amp;sektion=5&amp;manpath=FreeBSD+5.1-current">
<span class="CITEREFENTRY"><span <span class="CITEREFENTRY"><span class="REFENTRYTITLE">msdosfs</span>(5)</span></a> file
class="REFENTRYTITLE">msdosfs</span>(5)</span></a> file system that has been upgraded from read-only to read-write via <tt class="COMMAND">mount
system that has been upgraded from read-only to read-write -u</tt> will cause the system to lock up. To work around this problem, unmount the file
via <tt class="COMMAND">mount -u</tt> will cause the system system first, then mount it again with the appropriate options instead of using <tt
to lock up. To work around this problem, unmount the file class="COMMAND">mount -u</tt>.</p>
system first, then mount it again with the appropriate
options instead of using <tt class="COMMAND">mount
-u</tt>.</p>
</div> </div>
<div class="SECT1"> <div class="SECT1">
<hr /> <hr />
<h1 class="SECT1"><a id="LATE-NEWS" name="LATE-NEWS">4 Late-Breaking News</a></h1>
<h1 class="SECT1"><a id="LATE-NEWS" name="LATE-NEWS">4
Late-Breaking News</a></h1>
<p><a <p><a
href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&amp;sektion=4&amp;manpath=FreeBSD+5.1-current"> href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&amp;sektion=4&amp;manpath=FreeBSD+5.1-current">
<span class="CITEREFENTRY"><span <span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> should
class="REFENTRYTITLE">ipfw</span>(4)</span></a> should work work correctly on strict-alignment 64-bit architectures such as alpha and <span
correctly on strict-alignment 64-bit architectures such as class="TRADEMARK">Sparc64</span>&reg;.</p>
alpha and <span class="TRADEMARK">Sparc64</span>&reg;.</p>
<p>The release notes should have stated that the <tt <p>The release notes should have stated that the <tt class="FILENAME">libthr</tt> library
class="FILENAME">libthr</tt> library is built by default is built by default for the <span class="TRADEMARK">i386</span> platform.</p>
for the <span class="TRADEMARK">i386</span> platform.</p>
<p>FreeBSD 5.1-RELEASE includes some new boot loader scripts designed to make booting
FreeBSD with different options easier. This may help diagnose bootstrapping problems.
These scripts build on the existing Forth-based boot loader scripts (thus, <tt
class="FILENAME">/boot/loader.conf</tt> and other existing loader configuration files
still apply). They are only installed by default for new binary installs on <span
class="TRADEMARK">i386</span> machines. The new scripts present a boot-time menu that
controls how FreeBSD is booted, and include options to turn off ACPI, a ``safe mode''
boot, single-user booting, and verbose booting. ``Safe mode'' booting can be particularly
useful when compatibility with a system's hardware is uncertain, and sets the following
kernel tunable variables:</p>
<p>FreeBSD 5.1-RELEASE includes some new boot loader
scripts designed to make booting FreeBSD with different
options easier. This may help diagnose bootstrapping
problems. These scripts build on the existing Forth-based
boot loader scripts (thus, <tt
class="FILENAME">/boot/loader.conf</tt> and other existing
loader configuration files still apply). They are only
installed by default for new binary installs on <span
class="TRADEMARK">i386</span> machines. The new scripts
present a boot-time menu that controls how FreeBSD is
booted, and include options to turn off ACPI, a ``safe
mode'' boot, single-user booting, and verbose booting.
``Safe mode'' booting can be particularly useful when
compatibility with a system's hardware is uncertain, and
sets the following kernel tunable variables:</p>
<pre class="PROGRAMLISTING"> <pre class="PROGRAMLISTING">
hint.acpi.0.disabled=1 # disable ACPI (i386 only) hint.acpi.0.disabled=1 # disable ACPI (i386 only)
hw.ata.ata_dma=0 # disable IDE DMA hw.ata.ata_dma=0 # disable IDE DMA
@ -236,41 +188,34 @@ hw.ata.wc=0 # disable IDE disk write cache
hw.eisa_slots=0 # disable probing for EISA devices hw.eisa_slots=0 # disable probing for EISA devices
</pre> </pre>
<p>For new installs on <span class="TRADEMARK">i386</span> <p>For new installs on <span class="TRADEMARK">i386</span> architecture machines, <a
architecture machines, <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&amp;sektion=8&amp;manpath=FreeBSD+5.1-current"> href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&amp;sektion=8&amp;manpath=FreeBSD+5.1-current">
<span class="CITEREFENTRY"><span <span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a>
class="REFENTRYTITLE">sysinstall</span>(8)</span></a> will will try to determine if ACPI was disabled via the new boot loader scripts mentioned
try to determine if ACPI was disabled via the new boot above, and if so, ask if this change should be made permanent.</p>
loader scripts mentioned above, and if so, ask if this
change should be made permanent.</p>
<p>The release notes should have mentioned that work on the <p>The release notes should have mentioned that work on the following features was
following features was sponsored by the Defense Advanced sponsored by the Defense Advanced Research Projects Agency (DARPA): OpenPAM, NSS support,
Research Projects Agency (DARPA): OpenPAM, NSS support, PAE PAE support, various MAC framework updates, the GEOM disk geometry system.</p>
support, various MAC framework updates, the GEOM disk
geometry system.</p>
</div> </div>
</div> </div>
<hr /> <hr />
<p align="center"><small>This file, and other release-related documents, can be
<p align="center"><small>This file, and other release-related downloaded from <a
documents, can be downloaded from <a
href="http://snapshots.jp.FreeBSD.org/">http://snapshots.jp.FreeBSD.org/</a>.</small></p> href="http://snapshots.jp.FreeBSD.org/">http://snapshots.jp.FreeBSD.org/</a>.</small></p>
<p align="center"><small>For questions about FreeBSD, read the <p align="center"><small>For questions about FreeBSD, read the <a
<a href="http://www.FreeBSD.org/docs.html">documentation</a> href="http://www.FreeBSD.org/docs.html">documentation</a> before contacting &#60;<a
before contacting &#60;<a
href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>&#62;.</small></p> href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>&#62;.</small></p>
<p align="center"><small><small>All users of FreeBSD 5-CURRENT <p align="center"><small><small>All users of FreeBSD 5-CURRENT should subscribe to the
should subscribe to the &#60;<a &#60;<a href="mailto:current@FreeBSD.org">current@FreeBSD.org</a>&#62; mailing
href="mailto:current@FreeBSD.org">current@FreeBSD.org</a>&#62; list.</small></small></p>
mailing list.</small></small></p>
<p align="center">For questions about this documentation, <p align="center">For questions about this documentation, e-mail &#60;<a
e-mail &#60;<a
href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>&#62;.</p> href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>&#62;.</p>
<br /> <br />
<br /> <br />
</body> </body>