article.xml revision 118789
176082Sbmah<!-- 
276082Sbmah	FreeBSD errata document.  Unlike some of the other RELNOTESng
376082Sbmah	files, this file should remain as a single SGML file, so that
476082Sbmah	the dollar FreeBSD dollar header has a meaningful modification
576082Sbmah	time.  This file is all but useless without a datestamp on it,
676082Sbmah	so we'll take some extra care to make sure it has one.
776082Sbmah
876082Sbmah	(If we didn't do this, then the file with the datestamp might
976082Sbmah	not be the one that received the last change in the document.)
1076082Sbmah
1176082Sbmah-->
1276082Sbmah
1376082Sbmah<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
1476082Sbmah<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN">
1576082Sbmah%man;
1676082Sbmah<!ENTITY % authors PUBLIC  "-//FreeBSD//ENTITIES DocBook Author Entities//EN">
1776082Sbmah%authors;
1876082Sbmah<!ENTITY % mlists PUBLIC "-//FreeBSD//ENTITIES DocBook Mailing List Entities//EN">
1976082Sbmah%mlists;
2076082Sbmah<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN">
2176082Sbmah%release;
2276082Sbmah]>
2376082Sbmah
2476082Sbmah<article>
2576082Sbmah  <articleinfo>
26109307Sbmah    <title>&os;
27109543Sbmah<![ %release.type.snapshot [
28109543Sbmah    &release.prev;
29109543Sbmah]]>
30109543Sbmah<![ %release.type.release [
31109543Sbmah    &release.current;
32109543Sbmah]]>
33109307Sbmah    Errata</title>
3477914Sbmah
3576082Sbmah    <corpauthor>
3676082Sbmah    The &os; Project
3776082Sbmah    </corpauthor>
3876082Sbmah
3976082Sbmah    <pubdate>$FreeBSD: head/release/doc/en_US.ISO8859-1/errata/article.sgml 118789 2003-08-11 15:54:29Z bmah $</pubdate>
4076082Sbmah
4176082Sbmah    <copyright>
4276082Sbmah      <year>2000</year>
4376082Sbmah      <year>2001</year>
4488820Sbmah      <year>2002</year>
45108829Sbmah      <year>2003</year>
4676082Sbmah      <holder role="mailto:doc@FreeBSD.org">The FreeBSD Documentation Project</holder>
4776082Sbmah    </copyright>
4876082Sbmah  </articleinfo>
4976082Sbmah
5077914Sbmah  <abstract>
5179807Sbmah    <para>This document lists errata items for &os; 
52109543Sbmah<![ %release.type.snapshot [
53109543Sbmah      &release.prev;,
54109543Sbmah]]>
55109543Sbmah<![ %release.type.release [
56109543Sbmah      &release.current;,
57109543Sbmah]]>
58112874Sbmah      containing significant information discovered after the release
59112874Sbmah      or too late in the release cycle to be otherwise included in the
60112874Sbmah      release documentation.
6192295Sbmah      This information includes security advisories, as well as news
6292295Sbmah      relating to the software or documentation that could affect its
6392295Sbmah      operation or usability.  An up-to-date version of this document
6492295Sbmah      should always be consulted before installing this version of
6592295Sbmah      &os;.</para>
6677914Sbmah
67109307Sbmah    <para>This errata document for &os; 
68109543Sbmah<![ %release.type.snapshot [
69109543Sbmah      &release.prev;
70109543Sbmah]]>
71109543Sbmah<![ %release.type.release [
72109543Sbmah      &release.current;
73109543Sbmah]]>
74116130Sbmah      will be maintained until the release of &os; &release.next;.</para>
7577914Sbmah  </abstract>
7677914Sbmah
77109143Sroam  <sect1 id="intro">
7876082Sbmah    <title>Introduction</title>
7976082Sbmah
8079807Sbmah    <para>This errata document contains <quote>late-breaking news</quote>
8192295Sbmah      about &os;
82109543Sbmah<![ %release.type.snapshot [
83109543Sbmah      &release.prev;.
84109543Sbmah]]>
85109543Sbmah<![ %release.type.release [
86109543Sbmah      &release.current;.
87109543Sbmah]]>
8892295Sbmah      Before installing this version, it is important to consult this
8992295Sbmah      document to learn about any post-release discoveries or problems
9092295Sbmah      that may already have been found and fixed.</para>
9179807Sbmah
9292295Sbmah    <para>Any version of this errata document actually distributed
9392295Sbmah      with the release (for example, on a CDROM distribution) will be
9492295Sbmah      out of date by definition, but other copies are kept updated on
9592295Sbmah      the Internet and should be consulted as the <quote>current
9692295Sbmah      errata</quote> for this release.  These other copies of the
9792295Sbmah      errata are located at <ulink
9892295Sbmah      url="http://www.FreeBSD.org/releases/"></ulink>, plus any sites
9992295Sbmah      which keep up-to-date mirrors of this location.</para>
10076082Sbmah
10179807Sbmah    <para>Source and binary snapshots of &os; &release.branch; also
10292295Sbmah      contain up-to-date copies of this document (as of the time of
10392295Sbmah      the snapshot).</para>
10476082Sbmah
10577914Sbmah    <para>For a list of all &os; CERT security advisories, see <ulink
10692295Sbmah      url="http://www.FreeBSD.org/security/"></ulink> or <ulink
10792295Sbmah      url="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/"></ulink>.</para>
10892295Sbmah
10976082Sbmah  </sect1>
11076082Sbmah
111109143Sroam  <sect1 id="security">
11276082Sbmah    <title>Security Advisories</title>
113109309Sbmah
114115963Sbmah<![ %release.type.release [
115115963Sbmah    <para>No advisories.</para>
116115963Sbmah]]>
117109309Sbmah
118115963Sbmah<![ %release.type.snapshot [
119118789Sbmah    <para>The implementation of the &man.realpath.3; function contained
120118789Sbmah      a single-byte buffer overflow bug.  This had various
121118405Sbmah      impacts, depending on the application using &man.realpath.3; and
122118426Srushani      other factors.  This bug was fixed on the &release.branch; development
123118429Sbmah      branch before &release.prev;; &os; &release.prev; is therefore not affected.  However, this change
124118429Sbmah      was not noted in the release documentation.  For
125118405Sbmah      more information, see security advisory
126118405Sbmah      <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:08.realpath.asc">FreeBSD-SA-03:08</ulink>.</para>
127118789Sbmah
128118789Sbmah    <para>The kernel contains a bug that could allow it to attempt
129118789Sbmah      delivery of invalid signals, leading to a kernel panic or, under
130118789Sbmah      some circumstances, unauthorized modification of kernel memory.
131118789Sbmah      This bug has been fixed on the &release.branch; development
132118789Sbmah      branch and the &release.prev; security fix branch.  For more
133118789Sbmah      information, see security advisory
134118789Sbmah      <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:09.signal.asc">FreeBSD-SA-03:09</ulink>.</para>
135118789Sbmah
136118789Sbmah    <para>A bug in the iBCS2 emulation module could result in
137118789Sbmah      disclosing the contents of kernel memory.  (Note that this
138118789Sbmah      module is not enabled in &os; by default.)  This bug has been
139118789Sbmah      fixed on the &release.branch; development branch and the
140118789Sbmah      &release.prev; security fix branch.  More information can be
141118789Sbmah      found in security advisory
142118789Sbmah      <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:10.ibcs2.asc">FreeBSD-SA-03:10</ulink>.</para>
143115963Sbmah]]>
144111435Sbmah
145115963Sbmah  </sect1>
146111435Sbmah
147115963Sbmah  <sect1 id="open-issues">
148115963Sbmah    <title>Open Issues</title>
149111834Sbmah
150115963Sbmah<![ %release.type.release [
151115963Sbmah    <para>No open issues.</para>
152115963Sbmah]]>
153112435Sbmah
154115963Sbmah<![ %release.type.snapshot [
155115965Sbmah    <para>The RAIDframe disk driver described in &man.raid.4; is
156115965Sbmah      non-functional for this release.</para>
157115965Sbmah
158115965Sbmah    <para>ACPI seems to make some i386 machines unstable.  Turning off
159115965Sbmah      ACPI support may help solve some of these problems; see an item
160115965Sbmah      in <xref linkend="late-news">.</para>
161116787Sbmah
162116787Sbmah    <para>An integer overflow could cause kernel panics on PAE-using
163116787Sbmah      machines with certain memory sizes.  This bug has been corrected
164116787Sbmah      on both the <literal>RELENG_5_1</literal> and
165116787Sbmah      <literal>HEAD</literal> branches.  A workaround for this problem
166116787Sbmah      is to remove some memory, update the system in question, and
167116787Sbmah      reinstall the memory.</para>
168116787Sbmah
169116787Sbmah    <para>Attempting to write to an &man.msdosfs.5; file system that
170116787Sbmah      has been upgraded from read-only to read-write via
171116787Sbmah      <command>mount -u</command> will cause the system to lock up.
172116787Sbmah      To work around this problem, unmount the file system first, then
173116787Sbmah      mount it again with the appropriate options instead of using
174116787Sbmah      <command>mount -u</command>.</para>
175115963Sbmah]]>
176112477Sbmah
17776082Sbmah  </sect1>
17876082Sbmah
179109309Sbmah  <sect1 id="late-news">
180109309Sbmah    <title>Late-Breaking News</title>
181109309Sbmah
182115963Sbmah<![ %release.type.release [
183115963Sbmah    <para>No news.</para>
184115963Sbmah]]>
185109583Schris
186115963Sbmah<![ %release.type.snapshot [
187115965Sbmah    <para>&man.ipfw.4; should work correctly on strict-alignment
188115965Sbmah      64-bit architectures such as alpha and sparc64.</para>
189115965Sbmah
190115965Sbmah    <para>The release notes should have stated that the
191115965Sbmah      <filename>libthr</filename> library is built by default for the
192115965Sbmah      i386 platform.</para>
193115965Sbmah
194115965Sbmah    <para>&os; &release.prev; includes some new boot loader scripts
195115965Sbmah      designed to make booting &os; with different options easier.
196115965Sbmah      This may help diagnose bootstrapping problems.  These scripts
197115965Sbmah      build on the existing Forth-based boot loader scripts (thus,
198115965Sbmah      <filename>/boot/loader.conf</filename> and other existing loader
199115965Sbmah      configuration files still apply).  They are only installed by
200115965Sbmah      default for new binary installs on i386 machines.  The new
201115965Sbmah      scripts present a boot-time menu that controls how &os; is
202115965Sbmah      booted, and include options to turn off ACPI, a <quote>safe
203115965Sbmah      mode</quote> boot, single-user booting, and verbose booting.
204115965Sbmah      <quote>Safe mode</quote> booting can be particularly useful when
205115965Sbmah      compatibility with a system's hardware is uncertain, and sets
206115965Sbmah      the following kernel tunable variables:</para>
207115965Sbmah
208115965Sbmah      <programlisting>hint.acpi.0.disabled=1 # disable ACPI (i386 only)
209115965Sbmahhw.ata.ata_dma=0       # disable IDE DMA
210115965Sbmahhw.ata.atapi_dma=0     # disable ATAPI/IDE DMA
211115965Sbmahhw.ata.wc=0            # disable IDE disk write cache
212115965Sbmahhw.eisa_slots=0        # disable probing for EISA devices</programlisting>
213115965Sbmah
214115965Sbmah    <para>For new installs on i386 architecture machines,
215115965Sbmah      &man.sysinstall.8; will try to determine if ACPI was disabled
216115965Sbmah      via the new boot loader scripts mentioned above, and if so,
217115965Sbmah      ask if this change should be made permanent.</para>
218115965Sbmah
219115965Sbmah    <para>The release notes should have mentioned that work on the
220115965Sbmah      following features was sponsored by the Defense Advanced
221115965Sbmah      Research Projects Agency (DARPA): OpenPAM, NSS support, PAE
222115965Sbmah      support, various MAC framework updates, the GEOM disk geometry
223115965Sbmah      system.</para>
224116630Sbmah
225115963Sbmah]]>
226109309Sbmah
227115963Sbmah  </sect1>
228109583Schris
22976082Sbmah</article>
230