article.xml revision 109543
1<!-- 2 FreeBSD errata document. Unlike some of the other RELNOTESng 3 files, this file should remain as a single SGML file, so that 4 the dollar FreeBSD dollar header has a meaningful modification 5 time. This file is all but useless without a datestamp on it, 6 so we'll take some extra care to make sure it has one. 7 8 (If we didn't do this, then the file with the datestamp might 9 not be the one that received the last change in the document.) 10 11--> 12 13<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [ 14<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN"> 15%man; 16<!ENTITY % authors PUBLIC "-//FreeBSD//ENTITIES DocBook Author Entities//EN"> 17%authors; 18<!ENTITY % mlists PUBLIC "-//FreeBSD//ENTITIES DocBook Mailing List Entities//EN"> 19%mlists; 20<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN"> 21%release; 22]> 23 24<article> 25 <articleinfo> 26 <title>&os; 27<![ %release.type.snapshot [ 28 &release.prev; 29]]> 30<![ %release.type.release [ 31 &release.current; 32]]> 33 Errata</title> 34 35 <corpauthor> 36 The &os; Project 37 </corpauthor> 38 39 <pubdate>$FreeBSD: head/release/doc/en_US.ISO8859-1/errata/article.sgml 109543 2003-01-19 23:32:07Z bmah $</pubdate> 40 41 <copyright> 42 <year>2000</year> 43 <year>2001</year> 44 <year>2002</year> 45 <year>2003</year> 46 <holder role="mailto:doc@FreeBSD.org">The FreeBSD Documentation Project</holder> 47 </copyright> 48 </articleinfo> 49 50 <abstract> 51 <para>This document lists errata items for &os; 52<![ %release.type.snapshot [ 53 &release.prev;, 54]]> 55<![ %release.type.release [ 56 &release.current;, 57]]> 58 containing significant information discovered after the release. 59 This information includes security advisories, as well as news 60 relating to the software or documentation that could affect its 61 operation or usability. An up-to-date version of this document 62 should always be consulted before installing this version of 63 &os;.</para> 64 65 <para>This errata document for &os; 66<![ %release.type.snapshot [ 67 &release.prev; 68]]> 69<![ %release.type.release [ 70 &release.current; 71]]> 72 will be maintained until the release of &os; 5.1-RELEASE.</para> 73 </abstract> 74 75 <sect1 id="intro"> 76 <title>Introduction</title> 77 78 <para>This errata document contains <quote>late-breaking news</quote> 79 about &os; 80<![ %release.type.snapshot [ 81 &release.prev;. 82]]> 83<![ %release.type.release [ 84 &release.current;. 85]]> 86 Before installing this version, it is important to consult this 87 document to learn about any post-release discoveries or problems 88 that may already have been found and fixed.</para> 89 90 <para>Any version of this errata document actually distributed 91 with the release (for example, on a CDROM distribution) will be 92 out of date by definition, but other copies are kept updated on 93 the Internet and should be consulted as the <quote>current 94 errata</quote> for this release. These other copies of the 95 errata are located at <ulink 96 url="http://www.FreeBSD.org/releases/"></ulink>, plus any sites 97 which keep up-to-date mirrors of this location.</para> 98 99 <para>Source and binary snapshots of &os; &release.branch; also 100 contain up-to-date copies of this document (as of the time of 101 the snapshot).</para> 102 103 <para>For a list of all &os; CERT security advisories, see <ulink 104 url="http://www.FreeBSD.org/security/"></ulink> or <ulink 105 url="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/"></ulink>.</para> 106 107 </sect1> 108 109 <sect1 id="security"> 110 <title>Security Advisories</title> 111 112 <para>No active security advisories.</para> 113 114 </sect1> 115 116 <sect1 id="late-news"> 117 <title>Late-Breaking News</title> 118 119 <para>The &man.geom.4;-based disk partitioning code in the kernel 120 will not allow an open partition to be overwritten. This 121 usually prevents the use of <command>disklabel -B</command> to 122 update the boot blocks on a disk because the 123 <literal>a</literal> partition overlaps the space where the boot 124 blocks are stored. A suggested workaround is to boot from an 125 alternate disk, a CDROM, or a fixit floppy.</para> 126 127 <para>When using disk media with sector sizes larger than 512 128 bytes (for instance, &man.gbde.4; encrypted disks), the 129 &man.dump.8; program fails to respect the larger sector size and 130 cannot dump the partition. One possible workaround is to copy 131 the entire file system in raw format and dump the copy. It is, 132 for instance, possible to dump a file system stored in a regular 133 file:</para> 134 135 <screen>&prompt.root; <userinput>dd if=/dev/ad0s1d.bde of=/junk/ad0.dd bs=1m</userinput> 136&prompt.root; <userinput>dump 0f - /junk/ad0.dd | ...</userinput></screen> 137 138 <para>A simpler workaround is to use &man.tar.1; or &man.cpio.1; 139 to make backup copies.</para> 140 141 <para>Hangs have been reported during &os; 5.0 snapshot 142 installations when installing to &man.mly.4;-supported RAID 143 arrays, in hardware configurations that appear to work fine 144 under &os; 4.7-RELEASE.</para> 145 146 <para>NETNCP and nwfs appear to be as-yet unadapted for KSE, and 147 hence not working.</para> 148 149 <para>During installation, the &man.iir.4; controller appears to 150 probe correctly, but finds no disk devices.</para> 151 152 <para>&man.truss.1; appears to contain a race condition during the 153 start-up of debugging, which can result in &man.truss.1; failing 154 to attach to the process before it exists. The symptom is that 155 &man.truss.1; reports that it cannot open the &man.procfs.5; 156 node supporting the process being debugged. A bug also appears 157 to exist wherein &man.truss.1; will hang if &man.execve.2; 158 returns <literal>ENOENT</literal> A further race appears to 159 exist in which &man.truss.1; will return <errorname>PIOCWAIT: 160 Input/output error</errorname> occasionally on startup. The fix 161 for this sufficiently changes process execution handling that it 162 has been deferred until after 5.0.</para> 163 164 <para>Some bugs have been reported in &man.sysinstall.8; disk 165 partitioning. One observed problem on the i386 is that 166 &man.sysinstall.8; cannot recalculate the free space left on a 167 disk after changing the type of an FDISK-type partition.</para> 168 169 <para>In some case, documentation (such as the FAQ or Handbook) 170 has not been updated to take into account &os; &release.prev; 171 features. Examples of areas where documentation is still 172 needed include &man.gbde.8; and the new <quote>fast 173 IPsec</quote> implementation.</para> 174 175 <para>Attempting to unmount smbfs shares may fail with 176 <errorname>Device busy</errorname> errors even when the 177 mount-point is not really busy. A workaround is to keep trying 178 to unmount the share until it eventually succeeds. This bug has 179 been fixed in &release.current;.</para> 180 181 <para>Forcefully unmounting (<command>umount -f</command>) smbfs 182 shares may cause a kernel panic. This bug has been fixed in 183 &release.current;.</para> 184 185 <para>When called on a connected socket file descriptor, 186 &man.fstat.2; is supposed to return the number of bytes 187 available to read in the <varname>st_size</varname> member of 188 <varname>struct stat</varname>. However, 189 <varname>st_size</varname> is always erroneously reported as 190 <literal>0</literal> on TCP sockets. This bug has been fixed in 191 &release.current;.</para> 192 193 <para>The &man.kqueue.2; <literal>EVFILT_READ</literal> filter 194 erroneously indicates that <literal>0</literal> bytes are 195 available to be read on TCP sockets, regardless of the number of 196 bytes that are actually available. The 197 <literal>NOTE_LOWAT</literal> flag for 198 <literal>EVFILT_READ</literal> is also broken on TCP sockets. 199 This bug has been fixed in &release.current;.</para> 200 201 <para>&os; &release.prev; introduced support for POSIX named semaphores 202 but the implementation contains a critical bug that causes 203 &man.sem.open.3; to incorrectly handle the opening of the same 204 semaphore multiple times by the same process, and that causes 205 &man.sem.close.3; to crash calling programs. This bug has been 206 fixed in &release.current;.</para> 207 208 <para>&os; &release.prev; has a minor bug in how the permissions of 209 <filename>/dev/tty</filename> are handled. This can be 210 triggered by logging in as a non-<username>root</username>, 211 non-<groupname>tty</groupname> group user, and using &man.su.1; 212 to switch to a second non-<username>root</username>, 213 non-<groupname>tty</groupname> group user. &man.ssh.1; will 214 fail because it cannot open <filename>/dev/tty</filename>. This 215 bug has been fixed in &release.current;.</para> 216 217 <para>&man.growfs.8; no longer works on &man.vinum.4; volumes (and 218 presumably, on &man.geom.4; entities) since these subsystems no 219 longer fake disklabels, but &man.growfs.8; insists on examining 220 a label.</para> 221 222 </sect1> 223</article> 224