article.xml revision 109612
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 109612 2003-01-21 05:30:41Z 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]]> 5892295Sbmah containing significant information discovered after the release. 5992295Sbmah This information includes security advisories, as well as news 6092295Sbmah relating to the software or documentation that could affect its 6192295Sbmah operation or usability. An up-to-date version of this document 6292295Sbmah should always be consulted before installing this version of 6392295Sbmah &os;.</para> 6477914Sbmah 65109307Sbmah <para>This errata document for &os; 66109543Sbmah<![ %release.type.snapshot [ 67109543Sbmah &release.prev; 68109543Sbmah]]> 69109543Sbmah<![ %release.type.release [ 70109543Sbmah &release.current; 71109543Sbmah]]> 72109308Sbmah will be maintained until the release of &os; 5.1-RELEASE.</para> 7377914Sbmah </abstract> 7477914Sbmah 75109143Sroam <sect1 id="intro"> 7676082Sbmah <title>Introduction</title> 7776082Sbmah 7879807Sbmah <para>This errata document contains <quote>late-breaking news</quote> 7992295Sbmah about &os; 80109543Sbmah<![ %release.type.snapshot [ 81109543Sbmah &release.prev;. 82109543Sbmah]]> 83109543Sbmah<![ %release.type.release [ 84109543Sbmah &release.current;. 85109543Sbmah]]> 8692295Sbmah Before installing this version, it is important to consult this 8792295Sbmah document to learn about any post-release discoveries or problems 8892295Sbmah that may already have been found and fixed.</para> 8979807Sbmah 9092295Sbmah <para>Any version of this errata document actually distributed 9192295Sbmah with the release (for example, on a CDROM distribution) will be 9292295Sbmah out of date by definition, but other copies are kept updated on 9392295Sbmah the Internet and should be consulted as the <quote>current 9492295Sbmah errata</quote> for this release. These other copies of the 9592295Sbmah errata are located at <ulink 9692295Sbmah url="http://www.FreeBSD.org/releases/"></ulink>, plus any sites 9792295Sbmah which keep up-to-date mirrors of this location.</para> 9876082Sbmah 9979807Sbmah <para>Source and binary snapshots of &os; &release.branch; also 10092295Sbmah contain up-to-date copies of this document (as of the time of 10192295Sbmah the snapshot).</para> 10276082Sbmah 10377914Sbmah <para>For a list of all &os; CERT security advisories, see <ulink 10492295Sbmah url="http://www.FreeBSD.org/security/"></ulink> or <ulink 10592295Sbmah url="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/"></ulink>.</para> 10692295Sbmah 10776082Sbmah </sect1> 10876082Sbmah 109109143Sroam <sect1 id="security"> 11076082Sbmah <title>Security Advisories</title> 111109309Sbmah 112109309Sbmah <para>No active security advisories.</para> 113109309Sbmah 11476082Sbmah </sect1> 11576082Sbmah 116109309Sbmah <sect1 id="late-news"> 117109309Sbmah <title>Late-Breaking News</title> 118109309Sbmah 119109583Schris <bridgehead renderas="sect3">GEOM</bridgehead> 120109583Schris 121109309Sbmah <para>The &man.geom.4;-based disk partitioning code in the kernel 122109309Sbmah will not allow an open partition to be overwritten. This 123109309Sbmah usually prevents the use of <command>disklabel -B</command> to 124109309Sbmah update the boot blocks on a disk because the 125109309Sbmah <literal>a</literal> partition overlaps the space where the boot 126109309Sbmah blocks are stored. A suggested workaround is to boot from an 127109309Sbmah alternate disk, a CDROM, or a fixit floppy.</para> 128109309Sbmah 129109583Schris <bridgehead renderas="sect3">&man.dump.8;</bridgehead> 130109583Schris 131109309Sbmah <para>When using disk media with sector sizes larger than 512 132109309Sbmah bytes (for instance, &man.gbde.4; encrypted disks), the 133109309Sbmah &man.dump.8; program fails to respect the larger sector size and 134109309Sbmah cannot dump the partition. One possible workaround is to copy 135109309Sbmah the entire file system in raw format and dump the copy. It is, 136109309Sbmah for instance, possible to dump a file system stored in a regular 137109309Sbmah file:</para> 138109309Sbmah 139109309Sbmah <screen>&prompt.root; <userinput>dd if=/dev/ad0s1d.bde of=/junk/ad0.dd bs=1m</userinput> 140109309Sbmah&prompt.root; <userinput>dump 0f - /junk/ad0.dd | ...</userinput></screen> 141109309Sbmah 142109309Sbmah <para>A simpler workaround is to use &man.tar.1; or &man.cpio.1; 143109309Sbmah to make backup copies.</para> 144109309Sbmah 145109583Schris <bridgehead renderas="sect3">&man.mly.4;</bridgehead> 146109583Schris 147109309Sbmah <para>Hangs have been reported during &os; 5.0 snapshot 148109309Sbmah installations when installing to &man.mly.4;-supported RAID 149109309Sbmah arrays, in hardware configurations that appear to work fine 150109309Sbmah under &os; 4.7-RELEASE.</para> 151109309Sbmah 152109583Schris <bridgehead renderas="sect3">NETNCP/Netware File System 153109583Schris Support</bridgehead> 154109583Schris 155109309Sbmah <para>NETNCP and nwfs appear to be as-yet unadapted for KSE, and 156109309Sbmah hence not working.</para> 157109309Sbmah 158109583Schris <bridgehead renderas="sect3">&man.iir.4; controller</bridgehead> 159109583Schris 160109309Sbmah <para>During installation, the &man.iir.4; controller appears to 161109309Sbmah probe correctly, but finds no disk devices.</para> 162109309Sbmah 163109583Schris <bridgehead renderas="sect3">&man.truss.1; race condition</bridgehead> 164109583Schris 165109309Sbmah <para>&man.truss.1; appears to contain a race condition during the 166109309Sbmah start-up of debugging, which can result in &man.truss.1; failing 167109309Sbmah to attach to the process before it exists. The symptom is that 168109309Sbmah &man.truss.1; reports that it cannot open the &man.procfs.5; 169109309Sbmah node supporting the process being debugged. A bug also appears 170109309Sbmah to exist wherein &man.truss.1; will hang if &man.execve.2; 171109309Sbmah returns <literal>ENOENT</literal> A further race appears to 172109309Sbmah exist in which &man.truss.1; will return <errorname>PIOCWAIT: 173109309Sbmah Input/output error</errorname> occasionally on startup. The fix 174109309Sbmah for this sufficiently changes process execution handling that it 175109309Sbmah has been deferred until after 5.0.</para> 176109309Sbmah 177109583Schris <bridgehead renderas="sect3">Disk Partitioning in Installer</bridgehead> 178109583Schris 179109309Sbmah <para>Some bugs have been reported in &man.sysinstall.8; disk 180109309Sbmah partitioning. One observed problem on the i386 is that 181109309Sbmah &man.sysinstall.8; cannot recalculate the free space left on a 182109309Sbmah disk after changing the type of an FDISK-type partition.</para> 183109309Sbmah 184109583Schris <bridgehead renderas="sect3">Stale Documentation</bridgehead> 185109583Schris 186109309Sbmah <para>In some case, documentation (such as the FAQ or Handbook) 187109543Sbmah has not been updated to take into account &os; &release.prev; 188109309Sbmah features. Examples of areas where documentation is still 189109309Sbmah needed include &man.gbde.8; and the new <quote>fast 190109309Sbmah IPsec</quote> implementation.</para> 191109309Sbmah 192109583Schris <bridgehead renderas="sect3">SMB File System</bridgehead> 193109583Schris 194109338Sbmah <para>Attempting to unmount smbfs shares may fail with 195109338Sbmah <errorname>Device busy</errorname> errors even when the 196109338Sbmah mount-point is not really busy. A workaround is to keep trying 197109338Sbmah to unmount the share until it eventually succeeds. This bug has 198109543Sbmah been fixed in &release.current;.</para> 199109338Sbmah 200109338Sbmah <para>Forcefully unmounting (<command>umount -f</command>) smbfs 201109338Sbmah shares may cause a kernel panic. This bug has been fixed in 202109543Sbmah &release.current;.</para> 203109338Sbmah 204109583Schris <bridgehead renderas="sect3">&man.fstat.2;</bridgehead> 205109583Schris 206109338Sbmah <para>When called on a connected socket file descriptor, 207109338Sbmah &man.fstat.2; is supposed to return the number of bytes 208109338Sbmah available to read in the <varname>st_size</varname> member of 209109338Sbmah <varname>struct stat</varname>. However, 210109338Sbmah <varname>st_size</varname> is always erroneously reported as 211109338Sbmah <literal>0</literal> on TCP sockets. This bug has been fixed in 212109543Sbmah &release.current;.</para> 213109338Sbmah 214109583Schris <bridgehead renderas="sect3">Kernel Event Queues</bridgehead> 215109583Schris 216109338Sbmah <para>The &man.kqueue.2; <literal>EVFILT_READ</literal> filter 217109338Sbmah erroneously indicates that <literal>0</literal> bytes are 218109338Sbmah available to be read on TCP sockets, regardless of the number of 219109338Sbmah bytes that are actually available. The 220109338Sbmah <literal>NOTE_LOWAT</literal> flag for 221109338Sbmah <literal>EVFILT_READ</literal> is also broken on TCP sockets. 222109543Sbmah This bug has been fixed in &release.current;.</para> 223109338Sbmah 224109583Schris <bridgehead renderas="sect3">POSIX Named Semaphores</bridgehead> 225109583Schris 226109543Sbmah <para>&os; &release.prev; introduced support for POSIX named semaphores 227109338Sbmah but the implementation contains a critical bug that causes 228109338Sbmah &man.sem.open.3; to incorrectly handle the opening of the same 229109338Sbmah semaphore multiple times by the same process, and that causes 230109338Sbmah &man.sem.close.3; to crash calling programs. This bug has been 231109543Sbmah fixed in &release.current;.</para> 232109338Sbmah 233109583Schris <bridgehead renderas="sect3"><filename>/dev/tty</filename> 234109583Schris Permissions</bridgehead> 235109583Schris 236109543Sbmah <para>&os; &release.prev; has a minor bug in how the permissions of 237109339Sbmah <filename>/dev/tty</filename> are handled. This can be 238109339Sbmah triggered by logging in as a non-<username>root</username>, 239109339Sbmah non-<groupname>tty</groupname> group user, and using &man.su.1; 240109339Sbmah to switch to a second non-<username>root</username>, 241109339Sbmah non-<groupname>tty</groupname> group user. &man.ssh.1; will 242109339Sbmah fail because it cannot open <filename>/dev/tty</filename>. This 243109543Sbmah bug has been fixed in &release.current;.</para> 244109339Sbmah 245109583Schris <bridgehead renderas="sect3">&man.growfs.8;</bridgehead> 246109583Schris 247109400Sbmah <para>&man.growfs.8; no longer works on &man.vinum.4; volumes (and 248109400Sbmah presumably, on &man.geom.4; entities) since these subsystems no 249109400Sbmah longer fake disklabels, but &man.growfs.8; insists on examining 250109400Sbmah a label.</para> 251109400Sbmah 252109612Sbmah <bridgehead renderas="sect3">IPFW</bridgehead> 253109612Sbmah 254109612Sbmah <para>&man.ipfw.4; <literal>skipto</literal> rules do not work 255109612Sbmah when coupled with the <literal>log</literal> keyword. This bug 256109612Sbmah has been fixed in &release.current;.</para> 25776082Sbmah </sect1> 25876082Sbmah</article> 259