===================================================================
RCS file: /cvsrepo/anoncvs/cvs/www/errata21.html,v
retrieving revision 1.82
retrieving revision 1.83
diff -c -r1.82 -r1.83
*** www/errata21.html	2019/05/28 16:32:41	1.82
--- www/errata21.html	2019/05/28 16:52:04	1.83
***************
*** 85,91 ****
  
  <ul>
  
! <li>
  <strong>001: CD RELEASE WORKAROUND</strong>
  &nbsp; <i>All architectures</i><br>
  One of the install scripts has a flaw that makes the CD-ROM mount fail
--- 85,91 ----
  
  <ul>
  
! <li id="cdrelease1">
  <strong>001: CD RELEASE WORKAROUND</strong>
  &nbsp; <i>All architectures</i><br>
  One of the install scripts has a flaw that makes the CD-ROM mount fail
***************
*** 107,113 ****
  </pre>
  <p>
  
! <li>
  <strong>002: CD RELEASE WORKAROUND</strong>
  &nbsp; <i>alpha only</i><br>
  CD2 does not boot on the alpha, as had been planned. Instead, you
--- 107,113 ----
  </pre>
  <p>
  
! <li id="cdrelease2">
  <strong>002: CD RELEASE WORKAROUND</strong>
  &nbsp; <i>alpha only</i><br>
  CD2 does not boot on the alpha, as had been planned. Instead, you
***************
*** 115,121 ****
  harder..
  <p>
  
! <li>
  <strong>003: BOOT BLOCK BUG</strong>
  &nbsp; <i>i386 only</i><br>
  Some rarer PC BIOSs do not like the hardrive bootblocks when used
--- 115,121 ----
  harder..
  <p>
  
! <li id="bootblock">
  <strong>003: BOOT BLOCK BUG</strong>
  &nbsp; <i>i386 only</i><br>
  Some rarer PC BIOSs do not like the hardrive bootblocks when used
***************
*** 126,132 ****
  non-zero offset.  For instance, start OpenBSD at next track boundary or so.
  <p>
  
! <li>
  <strong>004: WRONG CHECKSUMS</strong>
  &nbsp; <i>i386 only</i><br>
  The i386/X11/SUMS.md5 file contains 4 incorrect MD5 checksums.
--- 126,132 ----
  non-zero offset.  For instance, start OpenBSD at next track boundary or so.
  <p>
  
! <li id="checksums">
  <strong>004: WRONG CHECKSUMS</strong>
  &nbsp; <i>i386 only</i><br>
  The i386/X11/SUMS.md5 file contains 4 incorrect MD5 checksums.
***************
*** 141,147 ****
  problems.  Read the document, please.
  <p>
  
! <li>
  <strong>005: RELEASE BUG</strong>
  &nbsp; <i>amiga only</i><br>
  The amiga install has a flaw wrt Tseng based graphic cards: when entering
--- 141,147 ----
  problems.  Read the document, please.
  <p>
  
! <li id="tseng">
  <strong>005: RELEASE BUG</strong>
  &nbsp; <i>amiga only</i><br>
  The amiga install has a flaw wrt Tseng based graphic cards: when entering
***************
*** 153,159 ****
  </pre>
  <p>
  
! <li>
  <strong>006: RELEASE BUG</strong>
  &nbsp; <i>sparc only</i><br>
  The sparc X11R6.3 xdm-config files reference /usr/X11R6.3/... This is
--- 153,159 ----
  </pre>
  <p>
  
! <li id="sparcx">
  <strong>006: RELEASE BUG</strong>
  &nbsp; <i>sparc only</i><br>
  The sparc X11R6.3 xdm-config files reference /usr/X11R6.3/... This is
***************
*** 163,169 ****
  <b>#</b> ln -s X11R6 X11R6.3
  </pre>
  <p>
! <li>
  <strong>007: RELEASE BUG</strong>
  &nbsp; <i>sparc only</i><br>
  The sparc "single floppy install disk" has a problem when you specify
--- 163,170 ----
  <b>#</b> ln -s X11R6 X11R6.3
  </pre>
  <p>
! 
! <li id="sparcfd">
  <strong>007: RELEASE BUG</strong>
  &nbsp; <i>sparc only</i><br>
  The sparc "single floppy install disk" has a problem when you specify
***************
*** 172,178 ****
  again for a terminal type, enter "dumb" and it will work correctly.
  <p>
  
! <li>
  <strong>008: RELEASE BUG</strong>
  &nbsp; <i>sparc only</i><br>
  When netbooting an older sparc system such as a Sun4 or Sun4c, the boot
--- 173,179 ----
  again for a terminal type, enter "dumb" and it will work correctly.
  <p>
  
! <li id="sparctftp">
  <strong>008: RELEASE BUG</strong>
  &nbsp; <i>sparc only</i><br>
  When netbooting an older sparc system such as a Sun4 or Sun4c, the boot
***************
*** 185,192 ****
  </pre>
  <p>
  
! <li>
! <strong>RELEASE BUG</strong>
  &nbsp; <i>sparc only</i><br>
  The sparc install script has two flaws that make the kernel copy
  and the bootblock install fail. The kernel copy only fails
--- 186,193 ----
  </pre>
  <p>
  
! <li id="sparcboot">
! <strong>009: RELEASE BUG</strong>
  &nbsp; <i>sparc only</i><br>
  The sparc install script has two flaws that make the kernel copy
  and the bootblock install fail. The kernel copy only fails
***************
*** 219,226 ****
  </pre>
  <p>
  
! <li>
! <strong>009: RELEASE BUG</strong>
  &nbsp; <i>pmax only</i><br>
  When using the X11R6 binaries from the 2.1 release you will get
  errors like:
--- 220,227 ----
  </pre>
  <p>
  
! <li id="mkfont">
! <strong>010: RELEASE BUG</strong>
  &nbsp; <i>pmax only</i><br>
  When using the X11R6 binaries from the 2.1 release you will get
  errors like:
***************
*** 244,251 ****
  after the next reboot if everything is working fine.
  <p>
  
! <li>
! <strong>010: RELEASE BUG</strong>
  &nbsp; <i>mac68k only</i><br>
  The installer generates incorrect /etc/fstab files causing messages such
  as "file system read-only" on bootup.  To correct, boot to single-user
--- 245,252 ----
  after the next reboot if everything is working fine.
  <p>
  
! <li id="fstab">
! <strong>011: RELEASE BUG</strong>
  &nbsp; <i>mac68k only</i><br>
  The installer generates incorrect /etc/fstab files causing messages such
  as "file system read-only" on bootup.  To correct, boot to single-user
***************
*** 267,274 ****
  "ufs" type; the "ffs" type is more correct.
  <p>
  
! <li>
! <strong>011: RELEASE BUG</strong>
  &nbsp; <i>mac68k only</i><br>
  The installer forgets to install the kernel onto the filesystem.
  This is because the installer expects all packages including the kernel to
--- 268,275 ----
  "ufs" type; the "ffs" type is more correct.
  <p>
  
! <li id="mac68kzip">
! <strong>012: RELEASE BUG</strong>
  &nbsp; <i>mac68k only</i><br>
  The installer forgets to install the kernel onto the filesystem.
  This is because the installer expects all packages including the kernel to