article.xml revision 109339
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; 27109308Sbmah &release.next; 28109307Sbmah Errata</title> 2977914Sbmah 3076082Sbmah <corpauthor> 3176082Sbmah The &os; Project 3276082Sbmah </corpauthor> 3376082Sbmah 3476082Sbmah <pubdate>$FreeBSD: head/release/doc/en_US.ISO8859-1/errata/article.sgml 109339 2003-01-15 23:35:46Z bmah $</pubdate> 3576082Sbmah 3676082Sbmah <copyright> 3776082Sbmah <year>2000</year> 3876082Sbmah <year>2001</year> 3988820Sbmah <year>2002</year> 40108829Sbmah <year>2003</year> 4176082Sbmah <holder role="mailto:doc@FreeBSD.org">The FreeBSD Documentation Project</holder> 4276082Sbmah </copyright> 4376082Sbmah </articleinfo> 4476082Sbmah 4577914Sbmah <abstract> 4679807Sbmah <para>This document lists errata items for &os; 47109308Sbmah &release.next;, 4892295Sbmah containing significant information discovered after the release. 4992295Sbmah This information includes security advisories, as well as news 5092295Sbmah relating to the software or documentation that could affect its 5192295Sbmah operation or usability. An up-to-date version of this document 5292295Sbmah should always be consulted before installing this version of 5392295Sbmah &os;.</para> 5477914Sbmah 55109307Sbmah <para>This errata document for &os; 56109308Sbmah &release.next; 57109308Sbmah will be maintained until the release of &os; 5.1-RELEASE.</para> 5877914Sbmah </abstract> 5977914Sbmah 60109143Sroam <sect1 id="intro"> 6176082Sbmah <title>Introduction</title> 6276082Sbmah 6379807Sbmah <para>This errata document contains <quote>late-breaking news</quote> 6492295Sbmah about &os; 65109308Sbmah &release.next;. 6692295Sbmah Before installing this version, it is important to consult this 6792295Sbmah document to learn about any post-release discoveries or problems 6892295Sbmah that may already have been found and fixed.</para> 6979807Sbmah 7092295Sbmah <para>Any version of this errata document actually distributed 7192295Sbmah with the release (for example, on a CDROM distribution) will be 7292295Sbmah out of date by definition, but other copies are kept updated on 7392295Sbmah the Internet and should be consulted as the <quote>current 7492295Sbmah errata</quote> for this release. These other copies of the 7592295Sbmah errata are located at <ulink 7692295Sbmah url="http://www.FreeBSD.org/releases/"></ulink>, plus any sites 7792295Sbmah which keep up-to-date mirrors of this location.</para> 7876082Sbmah 7979807Sbmah <para>Source and binary snapshots of &os; &release.branch; also 8092295Sbmah contain up-to-date copies of this document (as of the time of 8192295Sbmah the snapshot).</para> 8276082Sbmah 8377914Sbmah <para>For a list of all &os; CERT security advisories, see <ulink 8492295Sbmah url="http://www.FreeBSD.org/security/"></ulink> or <ulink 8592295Sbmah url="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/"></ulink>.</para> 8692295Sbmah 8776082Sbmah </sect1> 8876082Sbmah 89109143Sroam <sect1 id="security"> 9076082Sbmah <title>Security Advisories</title> 91109309Sbmah 92109309Sbmah <para>No active security advisories.</para> 93109309Sbmah 9476082Sbmah </sect1> 9576082Sbmah 96109309Sbmah <sect1 id="late-news"> 97109309Sbmah <title>Late-Breaking News</title> 98109309Sbmah 99109309Sbmah <para>The &man.geom.4;-based disk partitioning code in the kernel 100109309Sbmah will not allow an open partition to be overwritten. This 101109309Sbmah usually prevents the use of <command>disklabel -B</command> to 102109309Sbmah update the boot blocks on a disk because the 103109309Sbmah <literal>a</literal> partition overlaps the space where the boot 104109309Sbmah blocks are stored. A suggested workaround is to boot from an 105109309Sbmah alternate disk, a CDROM, or a fixit floppy.</para> 106109309Sbmah 107109309Sbmah <para>When using disk media with sector sizes larger than 512 108109309Sbmah bytes (for instance, &man.gbde.4; encrypted disks), the 109109309Sbmah &man.dump.8; program fails to respect the larger sector size and 110109309Sbmah cannot dump the partition. One possible workaround is to copy 111109309Sbmah the entire file system in raw format and dump the copy. It is, 112109309Sbmah for instance, possible to dump a file system stored in a regular 113109309Sbmah file:</para> 114109309Sbmah 115109309Sbmah <screen>&prompt.root; <userinput>dd if=/dev/ad0s1d.bde of=/junk/ad0.dd bs=1m</userinput> 116109309Sbmah&prompt.root; <userinput>dump 0f - /junk/ad0.dd | ...</userinput></screen> 117109309Sbmah 118109309Sbmah <para>A simpler workaround is to use &man.tar.1; or &man.cpio.1; 119109309Sbmah to make backup copies.</para> 120109309Sbmah 121109309Sbmah <para>Hangs have been reported during &os; 5.0 snapshot 122109309Sbmah installations when installing to &man.mly.4;-supported RAID 123109309Sbmah arrays, in hardware configurations that appear to work fine 124109309Sbmah under &os; 4.7-RELEASE.</para> 125109309Sbmah 126109309Sbmah <para>NETNCP and nwfs appear to be as-yet unadapted for KSE, and 127109309Sbmah hence not working.</para> 128109309Sbmah 129109309Sbmah <para>During installation, the &man.iir.4; controller appears to 130109309Sbmah probe correctly, but finds no disk devices.</para> 131109309Sbmah 132109309Sbmah <para>&man.truss.1; appears to contain a race condition during the 133109309Sbmah start-up of debugging, which can result in &man.truss.1; failing 134109309Sbmah to attach to the process before it exists. The symptom is that 135109309Sbmah &man.truss.1; reports that it cannot open the &man.procfs.5; 136109309Sbmah node supporting the process being debugged. A bug also appears 137109309Sbmah to exist wherein &man.truss.1; will hang if &man.execve.2; 138109309Sbmah returns <literal>ENOENT</literal> A further race appears to 139109309Sbmah exist in which &man.truss.1; will return <errorname>PIOCWAIT: 140109309Sbmah Input/output error</errorname> occasionally on startup. The fix 141109309Sbmah for this sufficiently changes process execution handling that it 142109309Sbmah has been deferred until after 5.0.</para> 143109309Sbmah 144109309Sbmah <para>Some bugs have been reported in &man.sysinstall.8; disk 145109309Sbmah partitioning. One observed problem on the i386 is that 146109309Sbmah &man.sysinstall.8; cannot recalculate the free space left on a 147109309Sbmah disk after changing the type of an FDISK-type partition.</para> 148109309Sbmah 149109309Sbmah <para>In some case, documentation (such as the FAQ or Handbook) 150109309Sbmah has not been updated to take into account &os; &release.current; 151109309Sbmah features. Examples of areas where documentation is still 152109309Sbmah needed include &man.gbde.8; and the new <quote>fast 153109309Sbmah IPsec</quote> implementation.</para> 154109309Sbmah 155109338Sbmah <para>Attempting to unmount smbfs shares may fail with 156109338Sbmah <errorname>Device busy</errorname> errors even when the 157109338Sbmah mount-point is not really busy. A workaround is to keep trying 158109338Sbmah to unmount the share until it eventually succeeds. This bug has 159109338Sbmah been fixed in 5.0-CURRENT.</para> 160109338Sbmah 161109338Sbmah <para>Forcefully unmounting (<command>umount -f</command>) smbfs 162109338Sbmah shares may cause a kernel panic. This bug has been fixed in 163109338Sbmah 5.0-CURRENT.</para> 164109338Sbmah 165109338Sbmah <para>When called on a connected socket file descriptor, 166109338Sbmah &man.fstat.2; is supposed to return the number of bytes 167109338Sbmah available to read in the <varname>st_size</varname> member of 168109338Sbmah <varname>struct stat</varname>. However, 169109338Sbmah <varname>st_size</varname> is always erroneously reported as 170109338Sbmah <literal>0</literal> on TCP sockets. This bug has been fixed in 171109338Sbmah 5.0-CURRENT.</para> 172109338Sbmah 173109338Sbmah <para>The &man.kqueue.2; <literal>EVFILT_READ</literal> filter 174109338Sbmah erroneously indicates that <literal>0</literal> bytes are 175109338Sbmah available to be read on TCP sockets, regardless of the number of 176109338Sbmah bytes that are actually available. The 177109338Sbmah <literal>NOTE_LOWAT</literal> flag for 178109338Sbmah <literal>EVFILT_READ</literal> is also broken on TCP sockets. 179109338Sbmah This bug has been fixed in 5.0-CURRENT.</para> 180109338Sbmah 181109338Sbmah <para>&os; 5.0-RELEASE introduced support for POSIX named semaphores 182109338Sbmah but the implementation contains a critical bug that causes 183109338Sbmah &man.sem.open.3; to incorrectly handle the opening of the same 184109338Sbmah semaphore multiple times by the same process, and that causes 185109338Sbmah &man.sem.close.3; to crash calling programs. This bug has been 186109338Sbmah fixed in 5.0-CURRENT.</para> 187109338Sbmah 188109339Sbmah <para>&os; 5.0-RELEASE has a minor bug in how the permissions of 189109339Sbmah <filename>/dev/tty</filename> are handled. This can be 190109339Sbmah triggered by logging in as a non-<username>root</username>, 191109339Sbmah non-<groupname>tty</groupname> group user, and using &man.su.1; 192109339Sbmah to switch to a second non-<username>root</username>, 193109339Sbmah non-<groupname>tty</groupname> group user. &man.ssh.1; will 194109339Sbmah fail because it cannot open <filename>/dev/tty</filename>. This 195109339Sbmah bug has been fixed in 5.0-CURRENT.</para> 196109339Sbmah 19776082Sbmah </sect1> 19876082Sbmah</article> 199