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

Diff for /www/errata.html between version 1.38 and 1.39

version 1.38, 1997/12/09 11:18:40 version 1.39, 1997/12/09 11:30:02
Line 17 
Line 17 
 <ul>  <ul>
 <li><strong>All architectures</strong>  <li><strong>All architectures</strong>
 <ul>  <ul>
 <li>Building an object tree from a readonly source tree may fail under certain  <li>Building an object tree from a read-only source tree (such as off a CDROM)
 circumstances (e.g. when creating a symlink on sparc whose target name is  may fail under certain circumstances (e.g. when creating a symlink on sparc
 exactly 33 characters).  As a workaround you have to either provide the  whose target name is exactly 33 characters).  As a workaround you have to
 source tree read/write, or install a /usr/bin/readlink based on  either provide the source tree read/write, or install a newer version of
   /usr/bin/readlink.  You wish to use
 <a href=http://www.openbsd.org/cgi-bin/cvsweb/src/usr.bin/readlink/readlink.c?rev=1.13>  <a href=http://www.openbsd.org/cgi-bin/cvsweb/src/usr.bin/readlink/readlink.c?rev=1.13>
 revision 1.13 of usr.bin/readlink/readlink.c</a>.  revision 1.13 of usr.bin/readlink/readlink.c</a>.
   <p>
 </ul>  </ul>
 <li><strong>alpha</strong>  
 <ul>  
 <li>No problems so far.  
 </ul>  
 <li><strong>amiga</strong>  
 <ul>  
 <li>No problems so far.  
 </ul>  
 <li><strong>hp300</strong>  
 <ul>  
 <li>No problems so far.  
 </ul>  
 <li><strong>i386</strong>  <li><strong>i386</strong>
 <ul>  <ul>
 <li>The i386 F00F bug was discovered after the CDR's had already been sent to  <li>The Intel P5 F00F bug was discovered after the CDR's had already been
 the manufacturer.  sent to the manufacturer.  This problem permits any user who has an account
   to lock your machine up using a 4-line program.  The problem only affects
   Intel P5 processors (the i386, i486, P-Pro, and P-II are not vulnerable,
   nor are processors by other manufacturers).
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/i386/patch.f00f>  <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/i386/patch.f00f>
 A patch is available</a>.  A kernel source-code patch is available</a>.
   <p>
 <li>Some Linux binaries will execute in SVR4 emulation mode, which is  <li>Some Linux binaries will execute in SVR4 emulation mode, which is
 definately a problem for people who need Linux emulation to work correctly.  definately a problem for people who need Linux emulation to work correctly.
 To solve this,  To solve this mis-identification problem,
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/i386/compat_linux.patch>  <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/i386/compat_linux.patch>
 a patch file is provided.</a>  (This patch works on OpenBSD current.  It has  a patch file is provided.</a>  (This patch works on OpenBSD current.  It has
 not been tested on 2.2 yet, please test this and mail deraadt@openbsd.org  not been tested on 2.2 yet, please test this and mail deraadt@openbsd.org
 so that I can remove this message).  so that I can remove this bracketed warning).
 <li>If after installation on an IDE machine, your kernel fails to mount the root  <p>
 filesystem because it thinks that it should be opening sd0 (0x400), this means  <li>A few people are running into this problem, particularily if they had some
 you have incorrectly setup your disklabel.  other *BSD operating system on their machine before trying OpenBSD: if after
 Use the floppy to run "disklabel -E wd0", then using the "edit" command ensure  installation onto an IDE-based machine, the kernel fails to mount the root
 the type is set to "ST506".  partition because it thinks that it should be opening sd0 (0x400), this means
   you have incorrectly setup your disklabel for the IDE drive -- the disklabel
   is indicating that the drive is SCSI.
   To repair this, use the floppy to run "disklabel -E wd0", then using the
   "edit" command ensure the type field is set to "ST506".
   <p>
 </ul>  </ul>
 <li><strong>sparc</strong>  
 <ul>  
 <li>No problems so far.  
 </ul>  
 <li><strong>mac68k</strong>  <li><strong>mac68k</strong>
 <ul>  <ul>
 <li>mac68k X11 did not manage to make it onto the CDROM -- it will be  <li>Working X11 binaries for the mac68k did not manage to make it onto the
 forthcoming. Send mail to bother  CDROM -- a pointer to these binaries will be provided here as soon as the
   binaries are available.
   Send mail to bother
 <a href="mailto:gene@openbsd.org">the maintainer</a>  <a href="mailto:gene@openbsd.org">the maintainer</a>
 so that it shows up soon!  so that it shows up soon!
   <p>
 </ul>  </ul>
   <li><strong>sparc</strong>
   <ul>
   <li>No problems identified yet.
   <p>
   </ul>
   <li><strong>alpha</strong>
   <p>
   <ul>
   <li>No problems identified yet.
   <p>
   </ul>
   <li><strong>amiga</strong>
   <p>
   <ul>
   <li>No problems identified yet.
   </ul>
   <li><strong>hp300</strong>
   <p>
   <ul>
   <li>No problems identified yet.
   <p>
   </ul>
 <li><strong>pmax</strong>  <li><strong>pmax</strong>
 <ul>  <ul>
 <li>No problems so far.  <li>No problems identified yet.
   <p>
 </ul>  </ul>
 <li><strong>arc</strong>  <li><strong>arc</strong>
 <ul>  <ul>
 <li>No problems so far.  <li>No problems identified yet.
   <p>
 </ul>  </ul>
 <li><strong>mvme68k</strong>  <li><strong>mvme68k</strong>
 <ul>  <ul>
 <li>No problems so far.  <li>No problems identified yet.
   <p>
 </ul>  </ul>
 </ul>  </ul>
 <br>  <br>
Legend:
Removed from v.1.38  
changed lines
  Added in v.1.39