Regen from article.sgml 1.28.
This commit is contained in:
parent
070db941c3
commit
0aebe8757f
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/www/; revision=16122
1 changed files with 88 additions and 67 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.26
|
||||
2003/02/06 17:06:57 bmah Exp $<br />
|
||||
src/release/doc/en_US.ISO8859-1/errata/article.sgml,v 1.28
|
||||
2003/02/24 17:50:27 bmah Exp $<br />
|
||||
</p>
|
||||
<hr />
|
||||
</div>
|
||||
|
@ -92,6 +92,26 @@
|
|||
be found in security advisory <a
|
||||
href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:01.cvs.asc"
|
||||
target="_top">FreeBSD-SA-03:01</a>.</p>
|
||||
|
||||
<p>A timing-based attack on <b
|
||||
class="APPLICATION">OpenSSL</b>, could allow a very
|
||||
powerful attacker access to plaintext under certain
|
||||
circumstances. This problem has been corrected in FreeBSD
|
||||
5.0-CURRENT with an upgrade to <b
|
||||
class="APPLICATION">OpenSSL</b> 0.9.7. On supported
|
||||
security fix branches, this problem has been corrected with
|
||||
the import of <b class="APPLICATION">OpenSSL</b> 0.9.6i.
|
||||
See security advisory <a
|
||||
href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:02.openssl.asc"
|
||||
target="_top">FreeBSD-SA-03:02</a> for more details.</p>
|
||||
|
||||
<p>It may be possible to recover the shared secret key used
|
||||
by the implementation of the ``syncookies'' feature. This
|
||||
reduces its effectiveness in dealing with TCP SYN flood
|
||||
denial-of-service attacks. Workaround information and fixes
|
||||
are given in security advisory <a
|
||||
href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:03.syncookies.asc"
|
||||
target="_top">FreeBSD-SA-03:03</a>.</p>
|
||||
</div>
|
||||
|
||||
<div class="SECT1">
|
||||
|
@ -100,11 +120,11 @@
|
|||
<h1 class="SECT1"><a id="LATE-NEWS" name="LATE-NEWS">3
|
||||
Late-Breaking News</a></h1>
|
||||
|
||||
<h4 class="BRIDGEHEAD"><a id="AEN33"
|
||||
name="AEN33">GEOM</a></h4>
|
||||
<h4 class="BRIDGEHEAD"><a id="AEN41"
|
||||
name="AEN41">GEOM</a></h4>
|
||||
|
||||
<p>The <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=geom&sektion=4&manpath=FreeBSD+5.0-current">
|
||||
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
|
||||
|
@ -115,18 +135,18 @@
|
|||
stored. A suggested workaround is to boot from an alternate
|
||||
disk, a CDROM, or a fixit floppy.</p>
|
||||
|
||||
<h4 class="BRIDGEHEAD"><a id="AEN40" name="AEN40"><a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=dump&sektion=8&manpath=FreeBSD+5.0-current">
|
||||
<h4 class="BRIDGEHEAD"><a id="AEN48" name="AEN48"><a
|
||||
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></a></h4>
|
||||
|
||||
<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-current">
|
||||
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-current">
|
||||
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
|
||||
|
@ -142,81 +162,82 @@ 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-current">
|
||||
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-current">
|
||||
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>
|
||||
|
||||
<h4 class="BRIDGEHEAD"><a id="AEN63" name="AEN63"><a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=mly&sektion=4&manpath=FreeBSD+5.0-current">
|
||||
<h4 class="BRIDGEHEAD"><a id="AEN71" name="AEN71"><a
|
||||
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></a></h4>
|
||||
|
||||
<p>Hangs have been reported during FreeBSD 5.0 snapshot
|
||||
<p>Hangs were 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-current">
|
||||
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
|
||||
fine under FreeBSD 4.7-RELEASE.</p>
|
||||
fine under FreeBSD 4.7-RELEASE. These problems have been
|
||||
corrected in FreeBSD 5.0-CURRENT.</p>
|
||||
|
||||
<h4 class="BRIDGEHEAD"><a id="AEN71"
|
||||
name="AEN71">NETNCP/Netware File System Support</a></h4>
|
||||
<h4 class="BRIDGEHEAD"><a id="AEN79"
|
||||
name="AEN79">NETNCP/Netware File System Support</a></h4>
|
||||
|
||||
<p>NETNCP and nwfs appear to be as-yet unadapted for KSE,
|
||||
and hence not working.</p>
|
||||
|
||||
<h4 class="BRIDGEHEAD"><a id="AEN73" name="AEN73"><a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=iir&sektion=4&manpath=FreeBSD+5.0-current">
|
||||
<h4 class="BRIDGEHEAD"><a id="AEN81" name="AEN81"><a
|
||||
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</a></h4>
|
||||
|
||||
<p>During installation, the <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=iir&sektion=4&manpath=FreeBSD+5.0-current">
|
||||
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>
|
||||
|
||||
<h4 class="BRIDGEHEAD"><a id="AEN81" name="AEN81"><a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=truss&sektion=1&manpath=FreeBSD+5.0-current">
|
||||
<h4 class="BRIDGEHEAD"><a id="AEN89" name="AEN89"><a
|
||||
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> race
|
||||
condition</a></h4>
|
||||
|
||||
<p><a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=truss&sektion=1&manpath=FreeBSD+5.0-current">
|
||||
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-current">
|
||||
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-current">
|
||||
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-current">
|
||||
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-current">
|
||||
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-current">
|
||||
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-current">
|
||||
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
|
||||
|
@ -224,33 +245,33 @@ class="USERINPUT"><b>dump 0f - /junk/ad0.dd | ...</b></tt>
|
|||
sufficiently changes process execution handling that it has
|
||||
been deferred until after 5.0.</p>
|
||||
|
||||
<h4 class="BRIDGEHEAD"><a id="AEN109" name="AEN109">Disk
|
||||
<h4 class="BRIDGEHEAD"><a id="AEN117" name="AEN117">Disk
|
||||
Partitioning in Installer</a></h4>
|
||||
|
||||
<p>Some bugs have been reported in <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+5.0-current">
|
||||
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-current">
|
||||
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
|
||||
changing the type of an FDISK-type partition.</p>
|
||||
|
||||
<h4 class="BRIDGEHEAD"><a id="AEN117" name="AEN117">Stale
|
||||
<h4 class="BRIDGEHEAD"><a id="AEN125" name="AEN125">Stale
|
||||
Documentation</a></h4>
|
||||
|
||||
<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
|
||||
is still needed include <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=gbde&sektion=8&manpath=FreeBSD+5.0-current">
|
||||
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>
|
||||
|
||||
<h4 class="BRIDGEHEAD"><a id="AEN123" name="AEN123">SMB
|
||||
<h4 class="BRIDGEHEAD"><a id="AEN131" name="AEN131">SMB
|
||||
File System</a></h4>
|
||||
|
||||
<p>Attempting to unmount smbfs shares may fail with ``<tt
|
||||
|
@ -263,13 +284,13 @@ class="USERINPUT"><b>dump 0f - /junk/ad0.dd | ...</b></tt>
|
|||
-f</tt>) smbfs shares may cause a kernel panic. This bug
|
||||
has been fixed in 5.0-CURRENT.</p>
|
||||
|
||||
<h4 class="BRIDGEHEAD"><a id="AEN128" name="AEN128"><a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=fstat&sektion=2&manpath=FreeBSD+5.0-current">
|
||||
<h4 class="BRIDGEHEAD"><a id="AEN136" name="AEN136"><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></a></h4>
|
||||
|
||||
<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">
|
||||
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
|
||||
|
@ -279,11 +300,11 @@ class="USERINPUT"><b>dump 0f - /junk/ad0.dd | ...</b></tt>
|
|||
as <tt class="LITERAL">0</tt> on TCP sockets. This bug has
|
||||
been fixed in 5.0-CURRENT.</p>
|
||||
|
||||
<h4 class="BRIDGEHEAD"><a id="AEN140" name="AEN140">Kernel
|
||||
<h4 class="BRIDGEHEAD"><a id="AEN148" name="AEN148">Kernel
|
||||
Event Queues</a></h4>
|
||||
|
||||
<p>The <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=kqueue&sektion=2&manpath=FreeBSD+5.0-current">
|
||||
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
|
||||
|
@ -294,24 +315,24 @@ class="USERINPUT"><b>dump 0f - /junk/ad0.dd | ...</b></tt>
|
|||
class="LITERAL">EVFILT_READ</tt> is also broken on TCP
|
||||
sockets. This bug has been fixed in 5.0-CURRENT.</p>
|
||||
|
||||
<h4 class="BRIDGEHEAD"><a id="AEN149" name="AEN149">POSIX
|
||||
<h4 class="BRIDGEHEAD"><a id="AEN157" name="AEN157">POSIX
|
||||
Named Semaphores</a></h4>
|
||||
|
||||
<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">
|
||||
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">
|
||||
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>
|
||||
|
||||
<h4 class="BRIDGEHEAD"><a id="AEN157" name="AEN157"><tt
|
||||
<h4 class="BRIDGEHEAD"><a id="AEN165" name="AEN165"><tt
|
||||
class="FILENAME">/dev/tty</tt> Permissions</a></h4>
|
||||
|
||||
<p>FreeBSD 5.0-RELEASE has a minor bug in how the
|
||||
|
@ -319,79 +340,79 @@ class="USERINPUT"><b>dump 0f - /junk/ad0.dd | ...</b></tt>
|
|||
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">
|
||||
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">
|
||||
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>
|
||||
|
||||
<h4 class="BRIDGEHEAD"><a id="AEN172" name="AEN172"><a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=growfs&sektion=8&manpath=FreeBSD+5.0-current">
|
||||
<h4 class="BRIDGEHEAD"><a id="AEN180" name="AEN180"><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></a></h4>
|
||||
|
||||
<p><a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=growfs&sektion=8&manpath=FreeBSD+5.0-current">
|
||||
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">
|
||||
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">
|
||||
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">
|
||||
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>
|
||||
|
||||
<h4 class="BRIDGEHEAD"><a id="AEN189"
|
||||
name="AEN189">IPFW</a></h4>
|
||||
<h4 class="BRIDGEHEAD"><a id="AEN197"
|
||||
name="AEN197">IPFW</a></h4>
|
||||
|
||||
<p><a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+5.0-current">
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+5.0-current">
|
||||
<span class="CITEREFENTRY"><span
|
||||
class="REFENTRYTITLE">ipfw</span>(4)</span></a> <tt
|
||||
class="LITERAL">skipto</tt> rules do not work when coupled
|
||||
with the <tt class="LITERAL">log</tt> keyword. This bug has
|
||||
been fixed in 5.0-CURRENT.</p>
|
||||
|
||||
<h4 class="BRIDGEHEAD"><a id="AEN196"
|
||||
name="AEN196">Passwords and <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=adduser&sektion=8&manpath=FreeBSD+5.0-current">
|
||||
<h4 class="BRIDGEHEAD"><a id="AEN204"
|
||||
name="AEN204">Passwords and <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=adduser&sektion=8&manpath=FreeBSD+5.0-current">
|
||||
<span class="CITEREFENTRY"><span
|
||||
class="REFENTRYTITLE">adduser</span>(8)</span></a></a></h4>
|
||||
|
||||
<p><a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=adduser&sektion=8&manpath=FreeBSD+5.0-current">
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=adduser&sektion=8&manpath=FreeBSD+5.0-current">
|
||||
<span class="CITEREFENTRY"><span
|
||||
class="REFENTRYTITLE">adduser</span>(8)</span></a> does not
|
||||
correctly handle setting user passwords containing special
|
||||
shell characters. This problem has been corrected in
|
||||
5.0-CURRENT.</p>
|
||||
|
||||
<h4 class="BRIDGEHEAD"><a id="AEN204" name="AEN204"><a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=xl&sektion=4&manpath=FreeBSD+5.0-current">
|
||||
<h4 class="BRIDGEHEAD"><a id="AEN212" name="AEN212"><a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=xl&sektion=4&manpath=FreeBSD+5.0-current">
|
||||
<span class="CITEREFENTRY"><span
|
||||
class="REFENTRYTITLE">xl</span>(4)</span></a></a></h4>
|
||||
|
||||
<p>The <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=xl&sektion=4&manpath=FreeBSD+5.0-current">
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=xl&sektion=4&manpath=FreeBSD+5.0-current">
|
||||
<span class="CITEREFENTRY"><span
|
||||
class="REFENTRYTITLE">xl</span>(4)</span></a> driver has a
|
||||
timing bug that may cause a kernel panic (or other
|
||||
problems) when attempting to configure an interface. This
|
||||
bug has been fixed in 5.0-CURRENT.</p>
|
||||
|
||||
<h4 class="BRIDGEHEAD"><a id="AEN212" name="AEN212">ISC
|
||||
<h4 class="BRIDGEHEAD"><a id="AEN220" name="AEN220">ISC
|
||||
DHCP</a></h4>
|
||||
|
||||
<p><b class="APPLICATION">ISC DHCP</b> was updated to
|
||||
|
@ -399,8 +420,8 @@ class="USERINPUT"><b>dump 0f - /junk/ad0.dd | ...</b></tt>
|
|||
5.0-RELEASE, but was not documented in the release
|
||||
notes.</p>
|
||||
|
||||
<h4 class="BRIDGEHEAD"><a id="AEN215" name="AEN215"><a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=amd&sektion=8&manpath=FreeBSD+5.0-current">
|
||||
<h4 class="BRIDGEHEAD"><a id="AEN223" name="AEN223"><a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=amd&sektion=8&manpath=FreeBSD+5.0-current">
|
||||
<span class="CITEREFENTRY"><span
|
||||
class="REFENTRYTITLE">amd</span>(8)</span></a>
|
||||
Interoperability</a></h4>
|
||||
|
@ -408,7 +429,7 @@ class="USERINPUT"><b>dump 0f - /junk/ad0.dd | ...</b></tt>
|
|||
<p>5.0-RELEASE contains some bugs in its non-blocking RPC
|
||||
code. The most noticeable side-effect of these bugs was
|
||||
that <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=amd&sektion=8&manpath=FreeBSD+5.0-current">
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=amd&sektion=8&manpath=FreeBSD+5.0-current">
|
||||
<span class="CITEREFENTRY"><span
|
||||
class="REFENTRYTITLE">amd</span>(8)</span></a> users were
|
||||
not able to mount volumes from a 5.0-RELEASE server. This
|
||||
|
|
Loading…
Reference in a new issue