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

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