[BACK]Return to errata22.html CVS log [TXT][DIR] Up to [local] / www

Diff for /www/errata22.html between version 1.96 and 1.97

version 1.96, 2019/05/28 16:32:41 version 1.97, 2019/05/28 17:03:19
Line 211 
Line 211 
 A kernel patch is available which corrects this behaviour (this is  A kernel patch is available which corrects this behaviour (this is
 revision 3 of this patch)</a>.  revision 3 of this patch)</a>.
 <p>  <p>
 <li><strong>010: BUILD PROCESS FIX</strong>  
   <li id="build1">
   <strong>010: BUILD PROCESS FIX</strong>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 Building an object tree from a read-only source tree (such as off a CDROM)  Building an object tree from a read-only source tree (such as off a CDROM)
 may fail under certain circumstances (e.g. when creating a symlink on sparc  may fail under certain circumstances (e.g. when creating a symlink on sparc
Line 231 
Line 233 
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/mountd.patch">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/mountd.patch">
 A patch is available which corrects this behaviour</a>.  A patch is available which corrects this behaviour</a>.
 <p>  <p>
 <li><strong>012: RELIABILITY FIX</strong>  
   <li id="eor">
   <strong>012: RELIABILITY FIX</strong>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 Setting the MSG_EOR flag on a tcp packet in the send(2) family of  Setting the MSG_EOR flag on a tcp packet in the send(2) family of
 system calls could cause a kernel panic.  system calls could cause a kernel panic.
Line 249 
Line 253 
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/i386/f00f.patch">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/i386/f00f.patch">
 A kernel source-code patch is available</a>.  A kernel source-code patch is available</a>.
 <p>  <p>
 <li><strong>014: FUNCTIONALITY FIX</strong><br>  
   <li id="svr4">
   <strong>014: FUNCTIONALITY FIX</strong><br>
 Some Linux binaries will execute in SVR4 emulation mode, which is  Some Linux binaries will execute in SVR4 emulation mode, which is
 definitely a problem for people who need Linux emulation to work correctly.  definitely a problem for people who need Linux emulation to work correctly.
 To solve this mis-identification problem,  To solve this mis-identification problem,
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/i386/compat_linux.patch">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/i386/compat_linux.patch">
 a patch file is provided</a>.  a patch file is provided</a>.
 <p>  <p>
 <li><strong>015: RELIABILITY FIX</strong><br>  
   <li li="apm">
   <strong>015: RELIABILITY FIX</strong><br>
 APM can crash on machines without it.  APM can crash on machines without it.
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/i386/apm.patch">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/i386/apm.patch">
 A kernel source-code patch is available</a>.  A kernel source-code patch is available</a>.
 <p>  <p>
 <li><strong>016: INSTALLATION PROCESS FLAW</strong><br>  
   <li li="ide">
   <strong>016: INSTALLATION PROCESS FLAW</strong><br>
 A few people are running into this problem, particularly if they had some  A few people are running into this problem, particularly if they had some
 other *BSD operating system on their machine before trying OpenBSD: if after  other *BSD operating system on their machine before trying OpenBSD: if after
 installation onto an IDE-based machine, the kernel fails to mount the root  installation onto an IDE-based machine, the kernel fails to mount the root
Line 271 
Line 281 
 To repair this, use the floppy to run "disklabel -E wd0", then using the  To repair this, use the floppy to run "disklabel -E wd0", then using the
 "edit" command ensure the type field is set to "ST506".  "edit" command ensure the type field is set to "ST506".
 <p>  <p>
 <li><strong>017: NEW SOFTWARE</strong><br>  
   <li id="mac68kx">
   <strong>017: NEW SOFTWARE</strong><br>
 Unfortunately, X11 binaries for the mac68k did not manage to make it onto the  Unfortunately, X11 binaries for the mac68k did not manage to make it onto the
 CDROM.  However, X11 for the mac68k is immediately available from  CDROM.  However, X11 for the mac68k is immediately available from
 <a href="https://ftp.openbsd.org/pub/OpenBSD/2.2/mac68k/X11/X11R6.tar.gz">  <a href="https://ftp.openbsd.org/pub/OpenBSD/2.2/mac68k/X11/X11R6.tar.gz">
Line 279 
Line 291 
 be sure to read the <a href="https://ftp.openbsd.org/pub/OpenBSD/2.2/mac68k/X11/README.X11">README file</a> also in that directory for instructions on installing  be sure to read the <a href="https://ftp.openbsd.org/pub/OpenBSD/2.2/mac68k/X11/README.X11">README file</a> also in that directory for instructions on installing
 and setting up X.  and setting up X.
 <p>  <p>
 <li><strong>018: INSTALLATION PROCESS FLAW</strong><br>  
   <li id="mac68kpath">
   <strong>018: INSTALLATION PROCESS FLAW</strong><br>
 As shipped on the CDROM, both the  As shipped on the CDROM, both the
 <a href="https://ftp.openbsd.org/pub/OpenBSD/2.2/mac68k/bsd-generic.tar.gz">  <a href="https://ftp.openbsd.org/pub/OpenBSD/2.2/mac68k/bsd-generic.tar.gz">
 generic kernel</a>  generic kernel</a>
Line 301 
Line 315 
 mini-shell to "cpin" the kernel.  Alternately, you could install the kernel  mini-shell to "cpin" the kernel.  Alternately, you could install the kernel
 with the Installer and use the mini-shell to move the binary from <code>/usr/src/...</code> to <code>/bsd</code>.  with the Installer and use the mini-shell to move the binary from <code>/usr/src/...</code> to <code>/bsd</code>.
 <p>  <p>
 <li><strong>019: RELIABILITY FIX</strong><br>  
   <li id="4300">
   <strong>019: RELIABILITY FIX</strong><br>
 Older 4/xxx systems (particularly the 4/300's) cannot boot  Older 4/xxx systems (particularly the 4/300's) cannot boot
 with the 2.2 kernel due to bugs in the scsi device driver.  with the 2.2 kernel due to bugs in the scsi device driver.
 <a href="https://ftp.OpenBSD.org/pub/OpenBSD/patches/2.2/sparc/esp.patch">  <a href="https://ftp.OpenBSD.org/pub/OpenBSD/patches/2.2/sparc/esp.patch">
Line 320 
Line 336 
 A workaround (kernel source patch) is available</a>.  Apply the patch and  A workaround (kernel source patch) is available</a>.  Apply the patch and
 then re-build your kernel.  then re-build your kernel.
 <p>  <p>
 <li><strong>021: FUNCTIONALITY FIX</strong><br>  
   <li id="xamiga">
   <strong>021: FUNCTIONALITY FIX</strong><br>
 Missing Xamiga manual pages.  Get  Missing Xamiga manual pages.  Get
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/amiga/Xamiga-manual.tgz">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/amiga/Xamiga-manual.tgz">
 this package</a> and execute, <i>as root</i>:<br>  this package</a> and execute, <i>as root</i>:<br>
Line 328 
Line 346 
 The MD5 checksum of this package is:<br>  The MD5 checksum of this package is:<br>
 <b>MD5 (Xamiga-manual.tgz) = 2362a7857264b9d17f65cca258b42031</b>  <b>MD5 (Xamiga-manual.tgz) = 2362a7857264b9d17f65cca258b42031</b>
 <p>  <p>
 <li><strong>022: FUNCTIONALITY FIX</strong><br>  
   <li id="araidne">
   <strong>022: FUNCTIONALITY FIX</strong><br>
 The Ariadne ethernet support was broken, there will be both binary and  The Ariadne ethernet support was broken, there will be both binary and
 source level fixes available shortly.  If you are in a hurry mail  source level fixes available shortly.  If you are in a hurry mail
 <a href="mailto:niklas@openbsd.org">Niklas</a> for a test kernel.<p>  <a href="mailto:niklas@openbsd.org">Niklas</a> for a test kernel.<p>
 <p>  <p>
 <li><strong>023: FUNCTIONALITY FIX</strong><br>  
   <li id="pmax">
   <strong>023: FUNCTIONALITY FIX</strong><br>
 There is a Year-1998 problem in the time-setting code (which causes the  There is a Year-1998 problem in the time-setting code (which causes the
 date and time to be set incorrectly after a reboot in 1998).  date and time to be set incorrectly after a reboot in 1998).
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/clock.patch">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/clock.patch">
Line 343 
Line 365 
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/bsd">bsd</a>,  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/bsd">bsd</a>,
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/bsd.rz0">bsd.rz0</a>.  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/bsd.rz0">bsd.rz0</a>.
 <p>  <p>
 <li><strong>024: FUNCTIONALITY FIX</strong><br>  
   <li id="3min">
   <strong>024: FUNCTIONALITY FIX</strong><br>
 X11 support for the 3min and 3maxplus machines was broken  X11 support for the 3min and 3maxplus machines was broken
 due to a kernel bug.  due to a kernel bug.
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/fb.patch">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/fb.patch">
Line 358 
Line 382 
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/ld.so">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/ld.so">
 The replacement binary is here</a>.  The replacement binary is here</a>.
 <p>  <p>
 <li><strong>026: SECURITY FIX</strong><br>  
   <li id="ldso2">
   <strong>026: SECURITY FIX</strong><br>
 A security problem in the shared library linker <b>ld.so</b> requires  A security problem in the shared library linker <b>ld.so</b> requires
 that you replace it with a new binary.  The following binary  that you replace it with a new binary.  The following binary
 will work on both pmax and arc machines.  will work on both pmax and arc machines.
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/ld.so">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/ld.so">
 The replacement binary is here</a>.  The replacement binary is here</a>.
 <p>  <p>
 <li><strong>027: MISSING FUNCTIONALITY</strong><br>  
   <li id="nat">
   <strong>027: MISSING FUNCTIONALITY</strong><br>
 Network Address Translation and other parts of IP Filtering do not work  Network Address Translation and other parts of IP Filtering do not work
 on the alpha.  This will be fixed in the 2.3 release, and perhaps earlier  on the alpha.  This will be fixed in the 2.3 release, and perhaps earlier
 in a snapshot.  There is no patch for 2.2.  in a snapshot.  There is no patch for 2.2.
Legend:
Removed from v.1.96  
changed lines
  Added in v.1.97