Regen from article.sgml 1.18.
This commit is contained in:
Bruce A. Mah
parent
c8610293d2
commit
c3bc650a1c
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/www/; revision=15687
1 changed files with 110 additions and 24 deletions
|
|
@ -22,8 +22,8 @@
|
|||
2003 by The FreeBSD Documentation Project</p>
|
||||
|
||||
<p class="PUBDATE">$FreeBSD:
|
||||
src/release/doc/en_US.ISO8859-1/errata/article.sgml,v
|
||||
1.9.2.4 2003/01/14 18:12:50 roam Exp $<br />
|
||||
src/release/doc/en_US.ISO8859-1/errata/article.sgml,v 1.18
|
||||
2003/01/16 23:58:28 bmah Exp $<br />
|
||||
</p>
|
||||
<hr />
|
||||
</div>
|
||||
|
|
@ -96,7 +96,7 @@
|
|||
Late-Breaking News</a></h1>
|
||||
|
||||
<p>The <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=geom&sektion=4&manpath=FreeBSD+5.0-RELEASE">
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=geom&sektion=4&manpath=FreeBSD+5.0-current">
|
||||
<span class="CITEREFENTRY"><span
|
||||
class="REFENTRYTITLE">geom</span>(4)</span></a>-based disk
|
||||
partitioning code in the kernel will not allow an open
|
||||
|
|
@ -109,11 +109,11 @@
|
|||
|
||||
<p>When using disk media with sector sizes larger than 512
|
||||
bytes (for instance, <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=gbde&sektion=4&manpath=FreeBSD+5.0-RELEASE">
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=gbde&sektion=4&manpath=FreeBSD+5.0-current">
|
||||
<span class="CITEREFENTRY"><span
|
||||
class="REFENTRYTITLE">gbde</span>(4)</span></a> encrypted
|
||||
disks), the <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=dump&sektion=8&manpath=FreeBSD+5.0-RELEASE">
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=dump&sektion=8&manpath=FreeBSD+5.0-current">
|
||||
<span class="CITEREFENTRY"><span
|
||||
class="REFENTRYTITLE">dump</span>(8)</span></a> program
|
||||
fails to respect the larger sector size and cannot dump the
|
||||
|
|
@ -129,17 +129,17 @@ class="USERINPUT"><b>dump 0f - /junk/ad0.dd | ...</b></tt>
|
|||
</pre>
|
||||
|
||||
<p>A simpler workaround is to use <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=tar&sektion=1&manpath=FreeBSD+5.0-RELEASE">
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=tar&sektion=1&manpath=FreeBSD+5.0-current">
|
||||
<span class="CITEREFENTRY"><span
|
||||
class="REFENTRYTITLE">tar</span>(1)</span></a> or <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=cpio&sektion=1&manpath=FreeBSD+5.0-RELEASE">
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=cpio&sektion=1&manpath=FreeBSD+5.0-current">
|
||||
<span class="CITEREFENTRY"><span
|
||||
class="REFENTRYTITLE">cpio</span>(1)</span></a> to make
|
||||
backup copies.</p>
|
||||
|
||||
<p>Hangs have been reported during FreeBSD 5.0 snapshot
|
||||
installations when installing to <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=mly&sektion=4&manpath=FreeBSD+5.0-RELEASE">
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=mly&sektion=4&manpath=FreeBSD+5.0-current">
|
||||
<span class="CITEREFENTRY"><span
|
||||
class="REFENTRYTITLE">mly</span>(4)</span></a>-supported
|
||||
RAID arrays, in hardware configurations that appear to work
|
||||
|
|
@ -149,41 +149,41 @@ class="USERINPUT"><b>dump 0f - /junk/ad0.dd | ...</b></tt>
|
|||
and hence not working.</p>
|
||||
|
||||
<p>During installation, the <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=iir&sektion=4&manpath=FreeBSD+5.0-RELEASE">
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=iir&sektion=4&manpath=FreeBSD+5.0-current">
|
||||
<span class="CITEREFENTRY"><span
|
||||
class="REFENTRYTITLE">iir</span>(4)</span></a> controller
|
||||
appears to probe correctly, but finds no disk devices.</p>
|
||||
|
||||
<p><a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=truss&sektion=1&manpath=FreeBSD+5.0-RELEASE">
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=truss&sektion=1&manpath=FreeBSD+5.0-current">
|
||||
<span class="CITEREFENTRY"><span
|
||||
class="REFENTRYTITLE">truss</span>(1)</span></a> appears to
|
||||
contain a race condition during the start-up of debugging,
|
||||
which can result in <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=truss&sektion=1&manpath=FreeBSD+5.0-RELEASE">
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=truss&sektion=1&manpath=FreeBSD+5.0-current">
|
||||
<span class="CITEREFENTRY"><span
|
||||
class="REFENTRYTITLE">truss</span>(1)</span></a> failing to
|
||||
attach to the process before it exists. The symptom is that
|
||||
<a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=truss&sektion=1&manpath=FreeBSD+5.0-RELEASE">
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=truss&sektion=1&manpath=FreeBSD+5.0-current">
|
||||
<span class="CITEREFENTRY"><span
|
||||
class="REFENTRYTITLE">truss</span>(1)</span></a> reports
|
||||
that it cannot open the <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=procfs&sektion=5&manpath=FreeBSD+5.0-RELEASE">
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=procfs&sektion=5&manpath=FreeBSD+5.0-current">
|
||||
<span class="CITEREFENTRY"><span
|
||||
class="REFENTRYTITLE">procfs</span>(5)</span></a> node
|
||||
supporting the process being debugged. A bug also appears
|
||||
to exist wherein <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=truss&sektion=1&manpath=FreeBSD+5.0-RELEASE">
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=truss&sektion=1&manpath=FreeBSD+5.0-current">
|
||||
<span class="CITEREFENTRY"><span
|
||||
class="REFENTRYTITLE">truss</span>(1)</span></a> will hang
|
||||
if <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=execve&sektion=2&manpath=FreeBSD+5.0-RELEASE">
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=execve&sektion=2&manpath=FreeBSD+5.0-current">
|
||||
<span class="CITEREFENTRY"><span
|
||||
class="REFENTRYTITLE">execve</span>(2)</span></a> returns
|
||||
<tt class="LITERAL">ENOENT</tt> A further race appears to
|
||||
exist in which <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=truss&sektion=1&manpath=FreeBSD+5.0-RELEASE">
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=truss&sektion=1&manpath=FreeBSD+5.0-current">
|
||||
<span class="CITEREFENTRY"><span
|
||||
class="REFENTRYTITLE">truss</span>(1)</span></a> will
|
||||
return ``<tt class="ERRORNAME">PIOCWAIT: Input/output
|
||||
|
|
@ -192,11 +192,11 @@ class="USERINPUT"><b>dump 0f - /junk/ad0.dd | ...</b></tt>
|
|||
been deferred until after 5.0.</p>
|
||||
|
||||
<p>Some bugs have been reported in <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+5.0-RELEASE">
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+5.0-current">
|
||||
<span class="CITEREFENTRY"><span
|
||||
class="REFENTRYTITLE">sysinstall</span>(8)</span></a> disk
|
||||
partitioning. One observed problem on the i386 is that <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+5.0-RELEASE">
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+5.0-current">
|
||||
<span class="CITEREFENTRY"><span
|
||||
class="REFENTRYTITLE">sysinstall</span>(8)</span></a>
|
||||
cannot recalculate the free space left on a disk after
|
||||
|
|
@ -204,28 +204,114 @@ class="USERINPUT"><b>dump 0f - /junk/ad0.dd | ...</b></tt>
|
|||
|
||||
<p>In some case, documentation (such as the FAQ or
|
||||
Handbook) has not been updated to take into account FreeBSD
|
||||
5.0-RELEASE features. Examples of areas where documentation
|
||||
5.0-CURRENT features. Examples of areas where documentation
|
||||
is still needed include <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=gbde&sektion=8&manpath=FreeBSD+5.0-RELEASE">
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=gbde&sektion=8&manpath=FreeBSD+5.0-current">
|
||||
<span class="CITEREFENTRY"><span
|
||||
class="REFENTRYTITLE">gbde</span>(8)</span></a> and the new
|
||||
``fast IPsec'' implementation.</p>
|
||||
|
||||
<p>Attempting to unmount smbfs shares may fail with ``<tt
|
||||
class="ERRORNAME">Device busy</tt>'' errors even when the
|
||||
mount-point is not really busy. A workaround is to keep
|
||||
trying to unmount the share until it eventually succeeds.
|
||||
This bug has been fixed in 5.0-CURRENT.</p>
|
||||
|
||||
<p>Forcefully unmounting (<tt class="COMMAND">umount
|
||||
-f</tt>) smbfs shares may cause a kernel panic. This bug
|
||||
has been fixed in 5.0-CURRENT.</p>
|
||||
|
||||
<p>When called on a connected socket file descriptor, <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=fstat&sektion=2&manpath=FreeBSD+5.0-current">
|
||||
<span class="CITEREFENTRY"><span
|
||||
class="REFENTRYTITLE">fstat</span>(2)</span></a> is
|
||||
supposed to return the number of bytes available to read in
|
||||
the <tt class="VARNAME">st_size</tt> member of <tt
|
||||
class="VARNAME">struct stat</tt>. However, <tt
|
||||
class="VARNAME">st_size</tt> is always erroneously reported
|
||||
as <tt class="LITERAL">0</tt> on TCP sockets. This bug has
|
||||
been fixed in 5.0-CURRENT.</p>
|
||||
|
||||
<p>The <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=kqueue&sektion=2&manpath=FreeBSD+5.0-current">
|
||||
<span class="CITEREFENTRY"><span
|
||||
class="REFENTRYTITLE">kqueue</span>(2)</span></a> <tt
|
||||
class="LITERAL">EVFILT_READ</tt> filter erroneously
|
||||
indicates that <tt class="LITERAL">0</tt> bytes are
|
||||
available to be read on TCP sockets, regardless of the
|
||||
number of bytes that are actually available. The <tt
|
||||
class="LITERAL">NOTE_LOWAT</tt> flag for <tt
|
||||
class="LITERAL">EVFILT_READ</tt> is also broken on TCP
|
||||
sockets. This bug has been fixed in 5.0-CURRENT.</p>
|
||||
|
||||
<p>FreeBSD 5.0-RELEASE introduced support for POSIX named
|
||||
semaphores but the implementation contains a critical bug
|
||||
that causes <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=sem_open&sektion=3&manpath=FreeBSD+5.0-current">
|
||||
<span class="CITEREFENTRY"><span
|
||||
class="REFENTRYTITLE">sem_open</span>(3)</span></a> to
|
||||
incorrectly handle the opening of the same semaphore
|
||||
multiple times by the same process, and that causes <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=sem_close&sektion=3&manpath=FreeBSD+5.0-current">
|
||||
<span class="CITEREFENTRY"><span
|
||||
class="REFENTRYTITLE">sem_close</span>(3)</span></a> to
|
||||
crash calling programs. This bug has been fixed in
|
||||
5.0-CURRENT.</p>
|
||||
|
||||
<p>FreeBSD 5.0-RELEASE has a minor bug in how the
|
||||
permissions of <tt class="FILENAME">/dev/tty</tt> are
|
||||
handled. This can be triggered by logging in as a non-<tt
|
||||
class="USERNAME">root</tt>, non-<tt
|
||||
class="GROUPNAME">tty</tt> group user, and using <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=su&sektion=1&manpath=FreeBSD+5.0-current">
|
||||
<span class="CITEREFENTRY"><span
|
||||
class="REFENTRYTITLE">su</span>(1)</span></a> to switch to
|
||||
a second non-<tt class="USERNAME">root</tt>, non-<tt
|
||||
class="GROUPNAME">tty</tt> group user. <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=ssh&sektion=1&manpath=FreeBSD+5.0-current">
|
||||
<span class="CITEREFENTRY"><span
|
||||
class="REFENTRYTITLE">ssh</span>(1)</span></a> will fail
|
||||
because it cannot open <tt class="FILENAME">/dev/tty</tt>.
|
||||
This bug has been fixed in 5.0-CURRENT.</p>
|
||||
|
||||
<p><a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=growfs&sektion=8&manpath=FreeBSD+5.0-current">
|
||||
<span class="CITEREFENTRY"><span
|
||||
class="REFENTRYTITLE">growfs</span>(8)</span></a> no longer
|
||||
works on <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=vinum&sektion=4&manpath=FreeBSD+5.0-current">
|
||||
<span class="CITEREFENTRY"><span
|
||||
class="REFENTRYTITLE">vinum</span>(4)</span></a> volumes
|
||||
(and presumably, on <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=geom&sektion=4&manpath=FreeBSD+5.0-current">
|
||||
<span class="CITEREFENTRY"><span
|
||||
class="REFENTRYTITLE">geom</span>(4)</span></a> entities)
|
||||
since these subsystems no longer fake disklabels, but <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=growfs&sektion=8&manpath=FreeBSD+5.0-current">
|
||||
<span class="CITEREFENTRY"><span
|
||||
class="REFENTRYTITLE">growfs</span>(8)</span></a> insists
|
||||
on examining a label.</p>
|
||||
</div>
|
||||
</div>
|
||||
<hr />
|
||||
|
||||
<p align="center"><small>This file, and other release-related
|
||||
documents, can be downloaded from <a
|
||||
href="ftp://ftp.FreeBSD.org/">ftp://ftp.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
|
||||
<a href="http://www.FreeBSD.org/docs.html">documentation</a>
|
||||
before contacting <<a
|
||||
href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p>
|
||||
|
||||
<p align="center"><small>For questions about this
|
||||
documentation, e-mail <<a
|
||||
href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</small></p>
|
||||
<p align="center"><small><small>All users of FreeBSD 5-CURRENT
|
||||
should subscribe to the <<a
|
||||
href="mailto:current@FreeBSD.org">current@FreeBSD.org</a>>
|
||||
mailing list.</small></small></p>
|
||||
|
||||
<p align="center">For questions about this documentation,
|
||||
e-mail <<a
|
||||
href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</p>
|
||||
<br />
|
||||
<br />
|
||||
</body>
|
||||
|
|
|
|||
Loading…
Reference in a new issue