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

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

version 1.81, 2019/05/27 22:55:19 version 1.82, 2019/05/28 16:32:41
Line 84 
Line 84 
 <hr>  <hr>
   
 <ul>  <ul>
   
 <li>  <li>
 <strong>CD RELEASE WORKAROUND</strong>  <strong>001: 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 105 
Line 106 
 <pre><b>#</b> install  <pre><b>#</b> install
 </pre>  </pre>
 <p>  <p>
   
 <li>  <li>
 <strong>CD RELEASE WORKAROUND</strong>  <strong>002: 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>
 <strong>BOOT BLOCK BUG</strong>  <strong>003: 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 122 
Line 125 
 MBR, then install OpenBSD in a partition all by itself starting at a  MBR, then install OpenBSD in a partition all by itself starting at a
 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>
 <strong>WRONG CHECKSUMS</strong>  <strong>004: 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 136 
Line 140 
 INSTALL.i386 document, and hence end up with geometry translation  INSTALL.i386 document, and hence end up with geometry translation
 problems.  Read the document, please.  problems.  Read the document, please.
 <p>  <p>
   
 <li>  <li>
 <strong>RELEASE BUG</strong>  <strong>005: 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 147 
Line 152 
 <b>#</b> sh MAKEDEV ttye6  <b>#</b> sh MAKEDEV ttye6
 </pre>  </pre>
 <p>  <p>
   
 <li>  <li>
 <strong>RELEASE BUG</strong>  <strong>006: 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 158 
Line 164 
 </pre>  </pre>
 <p>  <p>
 <li>  <li>
 <strong>RELEASE BUG</strong>  <strong>007: 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
 first specify an invalid terminal such as "bogus" and when prompted  first specify an invalid terminal such as "bogus" and when prompted
 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>
 <strong>RELEASE BUG</strong>  <strong>008: 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 177 
Line 184 
 <b>#</b> mv newboot boot  <b>#</b> mv newboot boot
 </pre>  </pre>
 <p>  <p>
   
 <li>  <li>
 <strong>RELEASE BUG</strong>  <strong>RELEASE BUG</strong>
 &nbsp; <i>sparc only</i><br>  &nbsp; <i>sparc only</i><br>
Line 210 
Line 218 
 <b>#</b>  <b>#</b>
 </pre>  </pre>
 <p>  <p>
   
 <li>  <li>
 <strong>RELEASE BUG</strong>  <strong>009: 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 234 
Line 243 
 sensitive part of the system. You can remove the original_libc.so.16.1  sensitive part of the system. You can remove the original_libc.so.16.1
 after the next reboot if everything is working fine.  after the next reboot if everything is working fine.
 <p>  <p>
   
 <li>  <li>
 <strong>RELEASE BUG</strong>  <strong>010: 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 256 
Line 266 
 The installer should not have specified the filesystem as the old  The installer should not have specified the filesystem as the old
 "ufs" type; the "ffs" type is more correct.  "ufs" type; the "ffs" type is more correct.
 <p>  <p>
   
 <li>  <li>
 <strong>RELEASE BUG</strong>  <strong>011: 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

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