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

Diff for /www/errata21.html between version 1.80 and 1.81

version 1.80, 2019/04/02 12:46:56 version 1.81, 2019/05/27 22:55:19
Line 1 
Line 1 
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">  <!doctype html>
 <html>  <html lang=en id=errata>
 <head>  <meta charset=utf-8>
   
 <title>OpenBSD 2.1 Errata</title>  <title>OpenBSD 2.1 Errata</title>
 <meta name="description" content="the OpenBSD CD errata page">  <meta name="description" content="the OpenBSD CD errata page">
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">  
 <meta name="viewport" content="width=device-width, initial-scale=1">  <meta name="viewport" content="width=device-width, initial-scale=1">
 <link rel="stylesheet" type="text/css" href="openbsd.css">  <link rel="stylesheet" type="text/css" href="openbsd.css">
 <link rel="canonical" href="https://www.openbsd.org/errata21.html">  <link rel="canonical" href="https://www.openbsd.org/errata21.html">
 </head>  
   
 <!--  <!--
                         IMPORTANT REMINDER                          IMPORTANT REMINDER
         IF YOU ADD A NEW ERRATUM, MAIL THE PATCH TO TECH AND ANNOUNCE          IF YOU ADD A NEW ERRATUM, MAIL THE PATCH TO TECH AND ANNOUNCE
 -->  -->
   
 <body bgcolor="#ffffff" text="#000000" link="#23238E">  
   
 <h2>  <h2 id=OpenBSD>
 <a href="index.html">  <a href="index.html">
 <font color="#0000ff"><i>Open</i></font><font color="#000084">BSD</font></a>  <i>Open</i><b>BSD</b></a>
 <font color="#e00000">2.1 Errata</font>  2.1 Errata
 </h2>  </h2>
 <hr>  <hr>
   
Line 87 
Line 85 
   
 <ul>  <ul>
 <li>  <li>
 <font color="#009000"><strong>CD RELEASE WORKAROUND</strong></font>  <strong>CD RELEASE WORKAROUND</strong>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 One of the install scripts has a flaw that makes the CD-ROM mount fail  One of the install scripts has a flaw that makes the CD-ROM mount fail
 when using the CD-ROM as the install source media.  when using the CD-ROM as the install source media.
Line 108 
Line 106 
 </pre>  </pre>
 <p>  <p>
 <li>  <li>
 <font color="#009000"><strong>CD RELEASE WORKAROUND</strong></font>  <strong>CD RELEASE WORKAROUND</strong>
 &nbsp; <i>alpha only</i><br>  &nbsp; <i>alpha only</i><br>
 CD2 does not boot on the alpha, as had been planned. Instead, you  CD2 does not boot on the alpha, as had been planned. Instead, you
 must use the floppy install method.  This is not significantly  must use the floppy install method.  This is not significantly
 harder..  harder..
 <p>  <p>
 <li>  <li>
 <font color="#009000"><strong>BOOT BLOCK BUG</strong></font>  <strong>BOOT BLOCK BUG</strong>
 &nbsp; <i>i386 only</i><br>  &nbsp; <i>i386 only</i><br>
 Some rarer PC BIOSs do not like the hardrive bootblocks when used  Some rarer PC BIOSs do not like the hardrive bootblocks when used
 as a MBR.  The symptom is that the BIOS says "READ ERROR" when booting,  as a MBR.  The symptom is that the BIOS says "READ ERROR" when booting,
Line 125 
Line 123 
 non-zero offset.  For instance, start OpenBSD at next track boundary or so.  non-zero offset.  For instance, start OpenBSD at next track boundary or so.
 <p>  <p>
 <li>  <li>
 <font color="#009000"><strong>WRONG CHECKSUMS</strong></font>  <strong>WRONG CHECKSUMS</strong>
 &nbsp; <i>i386 only</i><br>  &nbsp; <i>i386 only</i><br>
 The i386/X11/SUMS.md5 file contains 4 incorrect MD5 checksums.  The i386/X11/SUMS.md5 file contains 4 incorrect MD5 checksums.
 These have been corrected on the ftp mirrors. The correct lines are:<br>  These have been corrected on the ftp mirrors. The correct lines are:<br>
Line 139 
Line 137 
 problems.  Read the document, please.  problems.  Read the document, please.
 <p>  <p>
 <li>  <li>
 <font color="#009000"><strong>RELEASE BUG</strong></font>  <strong>RELEASE BUG</strong>
 &nbsp; <i>amiga only</i><br>  &nbsp; <i>amiga only</i><br>
 The amiga install has a flaw wrt Tseng based graphic cards: when entering  The amiga install has a flaw wrt Tseng based graphic cards: when entering
 multiuser mode the console won't get a login prompt.  This is due to  multiuser mode the console won't get a login prompt.  This is due to
Line 150 
Line 148 
 </pre>  </pre>
 <p>  <p>
 <li>  <li>
 <font color="#009000"><strong>RELEASE BUG</strong></font>  <strong>RELEASE BUG</strong>
 &nbsp; <i>sparc only</i><br>  &nbsp; <i>sparc only</i><br>
 The sparc X11R6.3 xdm-config files reference /usr/X11R6.3/... This is  The sparc X11R6.3 xdm-config files reference /usr/X11R6.3/... This is
  to X11R6.3's default config file contents.  To fix, su and   to X11R6.3's default config file contents.  To fix, su and
Line 160 
Line 158 
 </pre>  </pre>
 <p>  <p>
 <li>  <li>
 <font color="#009000"><strong>RELEASE BUG</strong></font>  <strong>RELEASE BUG</strong>
 &nbsp; <i>sparc only</i><br>  &nbsp; <i>sparc only</i><br>
 The sparc "single floppy install disk" has a problem when you specify  The sparc "single floppy install disk" has a problem when you specify
 "dumb" in response to the terminal type query.  As a work-around  "dumb" in response to the terminal type query.  As a work-around
Line 168 
Line 166 
 again for a terminal type, enter "dumb" and it will work correctly.  again for a terminal type, enter "dumb" and it will work correctly.
 <p>  <p>
 <li>  <li>
 <font color="#009000"><strong>RELEASE BUG</strong></font>  <strong>RELEASE BUG</strong>
 &nbsp; <i>sparc only</i><br>  &nbsp; <i>sparc only</i><br>
 When netbooting an older sparc system such as a Sun4 or Sun4c, the boot  When netbooting an older sparc system such as a Sun4 or Sun4c, the boot
 may hang up at the end of the tftp transfer of the bootstrap due  may hang up at the end of the tftp transfer of the bootstrap due
Line 180 
Line 178 
 </pre>  </pre>
 <p>  <p>
 <li>  <li>
 <font color="#009000"><strong>RELEASE BUG</strong></font>  <strong>RELEASE BUG</strong>
 &nbsp; <i>sparc only</i><br>  &nbsp; <i>sparc only</i><br>
 The sparc install script has two flaws that make the kernel copy  The sparc install script has two flaws that make the kernel copy
 and the bootblock install fail. The kernel copy only fails  and the bootblock install fail. The kernel copy only fails
Line 213 
Line 211 
 </pre>  </pre>
 <p>  <p>
 <li>  <li>
 <font color="#009000"><strong>RELEASE BUG</strong></font>  <strong>RELEASE BUG</strong>
 &nbsp; <i>pmax only</i><br>  &nbsp; <i>pmax only</i><br>
 When using the X11R6 binaries from the 2.1 release you will get  When using the X11R6 binaries from the 2.1 release you will get
 errors like:  errors like:
Line 237 
Line 235 
 after the next reboot if everything is working fine.  after the next reboot if everything is working fine.
 <p>  <p>
 <li>  <li>
 <font color="#009000"><strong>RELEASE BUG</strong></font>  <strong>RELEASE BUG</strong>
 &nbsp; <i>mac68k only</i><br>  &nbsp; <i>mac68k only</i><br>
 The installer generates incorrect /etc/fstab files causing messages such  The installer generates incorrect /etc/fstab files causing messages such
 as "file system read-only" on bootup.  To correct, boot to single-user  as "file system read-only" on bootup.  To correct, boot to single-user
Line 259 
Line 257 
 "ufs" type; the "ffs" type is more correct.  "ufs" type; the "ffs" type is more correct.
 <p>  <p>
 <li>  <li>
 <font color="#009000"><strong>RELEASE BUG</strong></font>  <strong>RELEASE BUG</strong>
 &nbsp; <i>mac68k only</i><br>  &nbsp; <i>mac68k only</i><br>
 The installer forgets to install the kernel onto the filesystem.  The installer forgets to install the kernel onto the filesystem.
 This is because the installer expects all packages including the kernel to  This is because the installer expects all packages including the kernel to
Line 282 
Line 280 
 </ul>  </ul>
   
 <hr>  <hr>
   
 </body>  
 </html>  

Legend:
Removed from v.1.80  
changed lines
  Added in v.1.81