article.xml revision 110514
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 110514 2003-02-07 20:09:30Z 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 112110463Sbmah <para>Remotely exploitable vulnerabilities in 113110463Sbmah <application>CVS</application> could allow an attacker to 114110463Sbmah execute arbitrary comands on a CVS server. More details can be 115110463Sbmah found in security advisory <ulink 116110463Sbmah url="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:01.cvs.asc">FreeBSD-SA-03:01</ulink>.</para> 117109309Sbmah 11876082Sbmah </sect1> 11976082Sbmah 120109309Sbmah <sect1 id="late-news"> 121109309Sbmah <title>Late-Breaking News</title> 122109309Sbmah 123109583Schris <bridgehead renderas="sect3">GEOM</bridgehead> 124109583Schris 125109309Sbmah <para>The &man.geom.4;-based disk partitioning code in the kernel 126109309Sbmah will not allow an open partition to be overwritten. This 127109309Sbmah usually prevents the use of <command>disklabel -B</command> to 128109309Sbmah update the boot blocks on a disk because the 129109309Sbmah <literal>a</literal> partition overlaps the space where the boot 130109309Sbmah blocks are stored. A suggested workaround is to boot from an 131109309Sbmah alternate disk, a CDROM, or a fixit floppy.</para> 132109309Sbmah 133109583Schris <bridgehead renderas="sect3">&man.dump.8;</bridgehead> 134109583Schris 135109309Sbmah <para>When using disk media with sector sizes larger than 512 136109309Sbmah bytes (for instance, &man.gbde.4; encrypted disks), the 137109309Sbmah &man.dump.8; program fails to respect the larger sector size and 138109309Sbmah cannot dump the partition. One possible workaround is to copy 139109309Sbmah the entire file system in raw format and dump the copy. It is, 140109309Sbmah for instance, possible to dump a file system stored in a regular 141109309Sbmah file:</para> 142109309Sbmah 143109309Sbmah <screen>&prompt.root; <userinput>dd if=/dev/ad0s1d.bde of=/junk/ad0.dd bs=1m</userinput> 144109309Sbmah&prompt.root; <userinput>dump 0f - /junk/ad0.dd | ...</userinput></screen> 145109309Sbmah 146109309Sbmah <para>A simpler workaround is to use &man.tar.1; or &man.cpio.1; 147109309Sbmah to make backup copies.</para> 148109309Sbmah 149109583Schris <bridgehead renderas="sect3">&man.mly.4;</bridgehead> 150109583Schris 151110514Sbmah <para>Hangs were reported during &os; 5.0 snapshot 152109309Sbmah installations when installing to &man.mly.4;-supported RAID 153109309Sbmah arrays, in hardware configurations that appear to work fine 154110514Sbmah under &os; 4.7-RELEASE. These problems have been corrected 155110514Sbmah in &os; &release.current;.</para> 156109309Sbmah 157109583Schris <bridgehead renderas="sect3">NETNCP/Netware File System 158109583Schris Support</bridgehead> 159109583Schris 160109309Sbmah <para>NETNCP and nwfs appear to be as-yet unadapted for KSE, and 161109309Sbmah hence not working.</para> 162109309Sbmah 163109583Schris <bridgehead renderas="sect3">&man.iir.4; controller</bridgehead> 164109583Schris 165109309Sbmah <para>During installation, the &man.iir.4; controller appears to 166109309Sbmah probe correctly, but finds no disk devices.</para> 167109309Sbmah 168109583Schris <bridgehead renderas="sect3">&man.truss.1; race condition</bridgehead> 169109583Schris 170109309Sbmah <para>&man.truss.1; appears to contain a race condition during the 171109309Sbmah start-up of debugging, which can result in &man.truss.1; failing 172109309Sbmah to attach to the process before it exists. The symptom is that 173109309Sbmah &man.truss.1; reports that it cannot open the &man.procfs.5; 174109309Sbmah node supporting the process being debugged. A bug also appears 175109309Sbmah to exist wherein &man.truss.1; will hang if &man.execve.2; 176109309Sbmah returns <literal>ENOENT</literal> A further race appears to 177109309Sbmah exist in which &man.truss.1; will return <errorname>PIOCWAIT: 178109309Sbmah Input/output error</errorname> occasionally on startup. The fix 179109309Sbmah for this sufficiently changes process execution handling that it 180109309Sbmah has been deferred until after 5.0.</para> 181109309Sbmah 182109583Schris <bridgehead renderas="sect3">Disk Partitioning in Installer</bridgehead> 183109583Schris 184109309Sbmah <para>Some bugs have been reported in &man.sysinstall.8; disk 185109309Sbmah partitioning. One observed problem on the i386 is that 186109309Sbmah &man.sysinstall.8; cannot recalculate the free space left on a 187109309Sbmah disk after changing the type of an FDISK-type partition.</para> 188109309Sbmah 189109583Schris <bridgehead renderas="sect3">Stale Documentation</bridgehead> 190109583Schris 191109309Sbmah <para>In some case, documentation (such as the FAQ or Handbook) 192109543Sbmah has not been updated to take into account &os; &release.prev; 193109309Sbmah features. Examples of areas where documentation is still 194109309Sbmah needed include &man.gbde.8; and the new <quote>fast 195109309Sbmah IPsec</quote> implementation.</para> 196109309Sbmah 197109583Schris <bridgehead renderas="sect3">SMB File System</bridgehead> 198109583Schris 199109338Sbmah <para>Attempting to unmount smbfs shares may fail with 200109338Sbmah <errorname>Device busy</errorname> errors even when the 201109338Sbmah mount-point is not really busy. A workaround is to keep trying 202109338Sbmah to unmount the share until it eventually succeeds. This bug has 203109543Sbmah been fixed in &release.current;.</para> 204109338Sbmah 205109338Sbmah <para>Forcefully unmounting (<command>umount -f</command>) smbfs 206109338Sbmah shares may cause a kernel panic. This bug has been fixed in 207109543Sbmah &release.current;.</para> 208109338Sbmah 209109583Schris <bridgehead renderas="sect3">&man.fstat.2;</bridgehead> 210109583Schris 211109338Sbmah <para>When called on a connected socket file descriptor, 212109338Sbmah &man.fstat.2; is supposed to return the number of bytes 213109338Sbmah available to read in the <varname>st_size</varname> member of 214109338Sbmah <varname>struct stat</varname>. However, 215109338Sbmah <varname>st_size</varname> is always erroneously reported as 216109338Sbmah <literal>0</literal> on TCP sockets. This bug has been fixed in 217109543Sbmah &release.current;.</para> 218109338Sbmah 219109583Schris <bridgehead renderas="sect3">Kernel Event Queues</bridgehead> 220109583Schris 221109338Sbmah <para>The &man.kqueue.2; <literal>EVFILT_READ</literal> filter 222109338Sbmah erroneously indicates that <literal>0</literal> bytes are 223109338Sbmah available to be read on TCP sockets, regardless of the number of 224109338Sbmah bytes that are actually available. The 225109338Sbmah <literal>NOTE_LOWAT</literal> flag for 226109338Sbmah <literal>EVFILT_READ</literal> is also broken on TCP sockets. 227109543Sbmah This bug has been fixed in &release.current;.</para> 228109338Sbmah 229109583Schris <bridgehead renderas="sect3">POSIX Named Semaphores</bridgehead> 230109583Schris 231109543Sbmah <para>&os; &release.prev; introduced support for POSIX named semaphores 232109338Sbmah but the implementation contains a critical bug that causes 233109338Sbmah &man.sem.open.3; to incorrectly handle the opening of the same 234109338Sbmah semaphore multiple times by the same process, and that causes 235109338Sbmah &man.sem.close.3; to crash calling programs. This bug has been 236109543Sbmah fixed in &release.current;.</para> 237109338Sbmah 238109583Schris <bridgehead renderas="sect3"><filename>/dev/tty</filename> 239109583Schris Permissions</bridgehead> 240109583Schris 241109543Sbmah <para>&os; &release.prev; has a minor bug in how the permissions of 242109339Sbmah <filename>/dev/tty</filename> are handled. This can be 243109339Sbmah triggered by logging in as a non-<username>root</username>, 244109339Sbmah non-<groupname>tty</groupname> group user, and using &man.su.1; 245109339Sbmah to switch to a second non-<username>root</username>, 246109339Sbmah non-<groupname>tty</groupname> group user. &man.ssh.1; will 247109339Sbmah fail because it cannot open <filename>/dev/tty</filename>. This 248109543Sbmah bug has been fixed in &release.current;.</para> 249109339Sbmah 250109583Schris <bridgehead renderas="sect3">&man.growfs.8;</bridgehead> 251109583Schris 252109400Sbmah <para>&man.growfs.8; no longer works on &man.vinum.4; volumes (and 253109400Sbmah presumably, on &man.geom.4; entities) since these subsystems no 254109400Sbmah longer fake disklabels, but &man.growfs.8; insists on examining 255109400Sbmah a label.</para> 256109400Sbmah 257109612Sbmah <bridgehead renderas="sect3">IPFW</bridgehead> 258109612Sbmah 259109612Sbmah <para>&man.ipfw.4; <literal>skipto</literal> rules do not work 260109612Sbmah when coupled with the <literal>log</literal> keyword. This bug 261109612Sbmah has been fixed in &release.current;.</para> 262109689Sbmah 263109689Sbmah <bridgehead renderas="sect3">Passwords and &man.adduser.8;</bridgehead> 264109689Sbmah 265109689Sbmah <para>&man.adduser.8; does not correctly handle setting user 266109689Sbmah passwords containing special shell characters. This problem has 267109689Sbmah been corrected in &release.current;.</para> 268109689Sbmah 269109692Sbmah <bridgehead renderas="sect3">&man.xl.4;</bridgehead> 270109692Sbmah 271109692Sbmah <para>The &man.xl.4; driver has a timing bug that may cause a 272109692Sbmah kernel panic (or other problems) when attempting to configure an 273109692Sbmah interface. This bug has been fixed in &release.current;.</para> 274109692Sbmah 275109791Sbmah <bridgehead renderas="sect3">ISC DHCP</bridgehead> 276109791Sbmah 277109791Sbmah <para><application>ISC DHCP</application> was updated to 278109791Sbmah 3.0.1rc11. This update was actually a part of &os; 279109791Sbmah &release.prev;, but was not documented in the release 280109791Sbmah notes.</para> 281109791Sbmah 282110124Sbmah <bridgehead renderas="sect3">&man.amd.8; 283110124Sbmah Interoperability</bridgehead> 284110124Sbmah 285110124Sbmah <para>&release.prev; contains some bugs in its non-blocking RPC 286110124Sbmah code. The most noticeable side-effect of these bugs was that 287110124Sbmah &man.amd.8; users were not able to mount volumes from a 288110124Sbmah &release.prev; server. This bug has been fixed in 289110124Sbmah &release.current;.</para> 290110124Sbmah 29176082Sbmah </sect1> 29276082Sbmah</article> 293