| article.xml (109400) | article.xml (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 --- 10 unchanged lines hidden (view full) --- 19%mlists; 20<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN"> 21%release; 22]> 23 24<article> 25 <articleinfo> 26 <title>&os; | 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 --- 10 unchanged lines hidden (view full) --- 19%mlists; 20<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN"> 21%release; 22]> 23 24<article> 25 <articleinfo> 26 <title>&os; |
| 27 &release.next; | 27<![ %release.type.snapshot [ 28 &release.prev; 29]]> 30<![ %release.type.release [ 31 &release.current; 32]]> |
| 28 Errata</title> 29 30 <corpauthor> 31 The &os; Project 32 </corpauthor> 33 | 33 Errata</title> 34 35 <corpauthor> 36 The &os; Project 37 </corpauthor> 38 |
| 34 <pubdate>$FreeBSD: head/release/doc/en_US.ISO8859-1/errata/article.sgml 109400 2003-01-16 23:58:28Z bmah $</pubdate> | 39 <pubdate>$FreeBSD: head/release/doc/en_US.ISO8859-1/errata/article.sgml 109543 2003-01-19 23:32:07Z bmah $</pubdate> |
| 35 36 <copyright> 37 <year>2000</year> 38 <year>2001</year> 39 <year>2002</year> 40 <year>2003</year> 41 <holder role="mailto:doc@FreeBSD.org">The FreeBSD Documentation Project</holder> 42 </copyright> 43 </articleinfo> 44 45 <abstract> 46 <para>This document lists errata items for &os; | 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; |
| 47 &release.next;, | 52<![ %release.type.snapshot [ 53 &release.prev;, 54]]> 55<![ %release.type.release [ 56 &release.current;, 57]]> |
| 48 containing significant information discovered after the release. 49 This information includes security advisories, as well as news 50 relating to the software or documentation that could affect its 51 operation or usability. An up-to-date version of this document 52 should always be consulted before installing this version of 53 &os;.</para> 54 55 <para>This errata document for &os; | 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; |
| 56 &release.next; | 66<![ %release.type.snapshot [ 67 &release.prev; 68]]> 69<![ %release.type.release [ 70 &release.current; 71]]> |
| 57 will be maintained until the release of &os; 5.1-RELEASE.</para> 58 </abstract> 59 60 <sect1 id="intro"> 61 <title>Introduction</title> 62 63 <para>This errata document contains <quote>late-breaking news</quote> 64 about &os; | 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; |
| 65 &release.next;. | 80<![ %release.type.snapshot [ 81 &release.prev;. 82]]> 83<![ %release.type.release [ 84 &release.current;. 85]]> |
| 66 Before installing this version, it is important to consult this 67 document to learn about any post-release discoveries or problems 68 that may already have been found and fixed.</para> 69 70 <para>Any version of this errata document actually distributed 71 with the release (for example, on a CDROM distribution) will be 72 out of date by definition, but other copies are kept updated on 73 the Internet and should be consulted as the <quote>current --- 68 unchanged lines hidden (view full) --- 142 has been deferred until after 5.0.</para> 143 144 <para>Some bugs have been reported in &man.sysinstall.8; disk 145 partitioning. One observed problem on the i386 is that 146 &man.sysinstall.8; cannot recalculate the free space left on a 147 disk after changing the type of an FDISK-type partition.</para> 148 149 <para>In some case, documentation (such as the FAQ or Handbook) | 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 --- 68 unchanged lines hidden (view full) --- 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) |
| 150 has not been updated to take into account &os; &release.current; | 170 has not been updated to take into account &os; &release.prev; |
| 151 features. Examples of areas where documentation is still 152 needed include &man.gbde.8; and the new <quote>fast 153 IPsec</quote> implementation.</para> 154 155 <para>Attempting to unmount smbfs shares may fail with 156 <errorname>Device busy</errorname> errors even when the 157 mount-point is not really busy. A workaround is to keep trying 158 to unmount the share until it eventually succeeds. This bug has | 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 |
| 159 been fixed in 5.0-CURRENT.</para> | 179 been fixed in &release.current;.</para> |
| 160 161 <para>Forcefully unmounting (<command>umount -f</command>) smbfs 162 shares may cause a kernel panic. This bug has been fixed in | 180 181 <para>Forcefully unmounting (<command>umount -f</command>) smbfs 182 shares may cause a kernel panic. This bug has been fixed in |
| 163 5.0-CURRENT.</para> | 183 &release.current;.</para> |
| 164 165 <para>When called on a connected socket file descriptor, 166 &man.fstat.2; is supposed to return the number of bytes 167 available to read in the <varname>st_size</varname> member of 168 <varname>struct stat</varname>. However, 169 <varname>st_size</varname> is always erroneously reported as 170 <literal>0</literal> on TCP sockets. This bug has been fixed in | 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 |
| 171 5.0-CURRENT.</para> | 191 &release.current;.</para> |
| 172 173 <para>The &man.kqueue.2; <literal>EVFILT_READ</literal> filter 174 erroneously indicates that <literal>0</literal> bytes are 175 available to be read on TCP sockets, regardless of the number of 176 bytes that are actually available. The 177 <literal>NOTE_LOWAT</literal> flag for 178 <literal>EVFILT_READ</literal> is also broken on TCP sockets. | 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. |
| 179 This bug has been fixed in 5.0-CURRENT.</para> | 199 This bug has been fixed in &release.current;.</para> |
| 180 | 200 |
| 181 <para>&os; 5.0-RELEASE introduced support for POSIX named semaphores | 201 <para>&os; &release.prev; introduced support for POSIX named semaphores |
| 182 but the implementation contains a critical bug that causes 183 &man.sem.open.3; to incorrectly handle the opening of the same 184 semaphore multiple times by the same process, and that causes 185 &man.sem.close.3; to crash calling programs. This bug has been | 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 |
| 186 fixed in 5.0-CURRENT.</para> | 206 fixed in &release.current;.</para> |
| 187 | 207 |
| 188 <para>&os; 5.0-RELEASE has a minor bug in how the permissions of | 208 <para>&os; &release.prev; has a minor bug in how the permissions of |
| 189 <filename>/dev/tty</filename> are handled. This can be 190 triggered by logging in as a non-<username>root</username>, 191 non-<groupname>tty</groupname> group user, and using &man.su.1; 192 to switch to a second non-<username>root</username>, 193 non-<groupname>tty</groupname> group user. &man.ssh.1; will 194 fail because it cannot open <filename>/dev/tty</filename>. This | 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 |
| 195 bug has been fixed in 5.0-CURRENT.</para> | 215 bug has been fixed in &release.current;.</para> |
| 196 197 <para>&man.growfs.8; no longer works on &man.vinum.4; volumes (and 198 presumably, on &man.geom.4; entities) since these subsystems no 199 longer fake disklabels, but &man.growfs.8; insists on examining 200 a label.</para> 201 202 </sect1> 203</article> | 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> |