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

Annotation of www/errata.html, Revision 1.64

1.1       deraadt     1: <!DOCTYPE HTML PUBLIC  "-//IETF//DTD HTML Strict//EN">
                      2: <html>
                      3: <head>
1.64    ! deraadt     4: <title>OpenBSD release errata</title>
1.1       deraadt     5: <link rev=made href=mailto:www@openbsd.org>
                      6: <meta name="resource-type" content="document">
                      7: <meta name="description" content="the OpenBSD CD errata page">
                      8: <meta name="keywords" content="openbsd,cd,errata">
                      9: <meta name="distribution" content="global">
                     10: <meta name="copyright" content="This document copyright 1997 by OpenBSD.">
                     11: </head>
                     12:
                     13: <BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#23238E">
                     14:
1.37      deraadt    15: <img alt="[OpenBSD]" SRC="images/smalltitle.gif">
1.50      deraadt    16: <h3><font color=#0000e0>This is the OpenBSD 2.2 CD errata list:</font></h3>
1.25      deraadt    17: <ul>
1.43      deraadt    18: <a name=all></a>
1.50      deraadt    19: <li><font color=#e00000>All architectures</font>
1.25      deraadt    20: <ul>
1.39      deraadt    21: <li>Building an object tree from a read-only source tree (such as off a CDROM)
                     22: may fail under certain circumstances (e.g. when creating a symlink on sparc
                     23: whose target name is exactly 33 characters).  As a workaround you have to
                     24: either provide the source tree read/write, or install a newer version of
                     25: /usr/bin/readlink.  You wish to use
1.34      deraadt    26: <a href=http://www.openbsd.org/cgi-bin/cvsweb/src/usr.bin/readlink/readlink.c?rev=1.13>
                     27: revision 1.13 of usr.bin/readlink/readlink.c</a>.
1.39      deraadt    28: <p>
1.62      deraadt    29: <a name=ruserok></a>
1.61      deraadt    30: <li><strong>IMPORTANT</strong>
                     31: A combination localhost+remote host security problem exists if a
                     32: local user running a setuid binary causes a non-existant root .rhosts
                     33: file to be created via a symbolic link with a specific kind of corefile,
                     34: and then subsequently uses rsh/rlogin to enter the machine from remote.
                     35: A similar exploit might also be possible using sshd which lacks any code
                     36: for checking for deviations from the expected format in the .rhosts or
                     37: .shosts files, but we have not confirmed this yet.  The following two
                     38: fixes are recommended:
                     39: <p>
                     40: <ul>
                     41: <li>
                     42: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/nosuidcoredump.patch>
                     43: (1) Adds a new sysctl option which permits the adminstrator to decide
                     44: whether setuid corefiles should be written or not.</a>
                     45: <p>
                     46: <li><a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/rcmd.patch>
                     47: (2) Replaces the ruserok() function in libc with a much more paranoid
                     48: version which can detect these bogus looking .rhosts files better.  If the
                     49: previous patch is used to stop setuid coredumps, then this patch is not
                     50: as important.</a>
                     51: </ul>
                     52: <p>
                     53: This problem is fixed much better in OpenBSD-current, where the kernel's
                     54: symbolic link handling has been improved such that coredumping will not
                     55: create a file on the other side of a symbolic link.  Such a patch is not
                     56: possible for the 4.4lite1 VFS layer in the OpenBSD 2.2 kernel.
                     57: <p>
1.25      deraadt    58: </ul>
1.42      deraadt    59: <a name=i386></a>
1.50      deraadt    60: <li><font color=#e00000>i386</font>
1.25      deraadt    61: <ul>
1.39      deraadt    62: <li>The Intel P5 F00F bug was discovered after the CDR's had already been
                     63: sent to the manufacturer.  This problem permits any user who has an account
                     64: to lock your machine up using a 4-line program.  The problem only affects
                     65: Intel P5 processors (the i386, i486, P-Pro, and P-II are not vulnerable,
                     66: nor are processors by other manufacturers).
1.44      deraadt    67: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/i386/f00f.patch>
1.39      deraadt    68: A kernel source-code patch is available</a>.
                     69: <p>
1.33      deraadt    70: <li>Some Linux binaries will execute in SVR4 emulation mode, which is
                     71: definately a problem for people who need Linux emulation to work correctly.
1.39      deraadt    72: To solve this mis-identification problem,
1.32      deraadt    73: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/i386/compat_linux.patch>
1.56      deraadt    74: a patch file is provided.</a>
1.39      deraadt    75: <p>
1.45      deraadt    76: <li>APM can crash on machines without it.
                     77: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/i386/apm.patch>
                     78: A kernel source-code patch is available</a>.
                     79: <p>
1.39      deraadt    80: <li>A few people are running into this problem, particularily if they had some
                     81: other *BSD operating system on their machine before trying OpenBSD: if after
                     82: installation onto an IDE-based machine, the kernel fails to mount the root
                     83: partition because it thinks that it should be opening sd0 (0x400), this means
                     84: you have incorrectly setup your disklabel for the IDE drive -- the disklabel
                     85: is indicating that the drive is SCSI.
                     86: To repair this, use the floppy to run "disklabel -E wd0", then using the
                     87: "edit" command ensure the type field is set to "ST506".
                     88: <p>
                     89: </ul>
1.47      deraadt    90: <a name=mac68k></a>
1.50      deraadt    91: <li><font color=#e00000>mac68k</font>
1.39      deraadt    92: <ul>
1.46      gene       93: <li>Unfortunately, X11 binaries for the mac68k did not manage to make it onto the
                     94: CDROM.  However, X Windows for the mac68k is immediately available from
                     95: <a href="ftp://ftp.openbsd.org/pub/OpenBSD/2.2/mac68k/X11/X11R6.tar.gz">
                     96: ftp://ftp.OpenBSD.org/pub/OpenBSD/2.2/mac68k/X11/X11R6.tar.gz</a>.  Please
                     97: be sure to read the <a href="ftp://ftp.openbsd.org/pub/OpenBSD/2.2/mac68k/X11/README.X11">README file</a> also in that directory for instructions on installing
                     98: and setting up X.
1.39      deraadt    99: <p>
1.25      deraadt   100: </ul>
1.50      deraadt   101: <li><font color=#e00000>sparc</font>
1.25      deraadt   102: <ul>
1.58      deraadt   103: <li>Older 4/xxx systems (particularily the 4/300's) cannot boot
                    104: with the 2.2 kernel due to bugs in the scsi device driver.
1.57      jason     105: <a href=ftp://ftp.OpenBSD.org/pub/OpenBSD/patches/2.2/sparc/esp.patch>
                    106: A kernel source patch is available.</a>
1.60      jason     107: Replacement kernels are available for:
                    108: <a href=ftp://ftp.OpenBSD.org/pub/OpenBSD/patches/2.2/sparc/bsd>bsd</a>,
                    109: <a href=ftp://ftp.OpenBSD.org/pub/OpenBSD/patches/2.2/sparc/bsd.scsi3>bsd.scsi3</a>,
                    110: and a replacement for bsd.rd is coming soon.
1.39      deraadt   111: <p>
1.63      marc      112: <li>SPARCstation 4 and 5 (Microsparc 2) users may see kernel panics when
                    113: using a custom kernel configured for option sun4m only.
                    114: <a href=ftp://ftp.OpenBSD.org/pub/OpenBSD/patches/2.2/sparc/sun4m.patch>
                    115: A workaround (kernel source patch) is available.</a>  Apply the patch and
                    116: then re-build your kernel.
                    117: <p>
1.39      deraadt   118: </ul>
1.50      deraadt   119: <li><font color=#e00000>amiga</font>
1.39      deraadt   120: <p>
                    121: <ul>
1.48      niklas    122: <li>Missing Xamiga manual page.  Get
                    123: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/amiga/Xamiga-manual.tgz>
                    124: this package</a> and execute, <i>as root</i>:<br>
1.49      deraadt   125: <pre><b># </b>pkg_add Xamiga-manual.tgz</pre>
1.51      deraadt   126: The MD5 checksum of this package is:<br>
1.49      deraadt   127: <b>MD5 (Xamiga-manual.tgz) = 2362a7857264b9d17f65cca258b42031</b><p>
1.48      niklas    128: <li>The Ariadne ethernet support was broken, there will be both binary and
                    129: source level fixes available shortly.  If you are in a hurry mail
1.49      deraadt   130: <a href=mailto:niklas@openbsd.org>Niklas</a> for a test kernel.<p>
1.25      deraadt   131: </ul>
1.50      deraadt   132: <li><font color=#e00000>pmax</font>
1.25      deraadt   133: <ul>
1.53      deraadt   134: <li>There is a Year-1998 problem in the time-setting code (which causes the
                    135: date and time to be set incorrectly after a reboot in 1998).
                    136: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/clock.patch>
                    137: A source code patch file is available.</a> plus replacement installation
                    138: kernels for the 2.2 release at
                    139: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/bsd.NFS>bsd.NFS</a>,
                    140: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/bsd>bsd</a>,
                    141: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/bsd.rz0>bsd.rz0</a>.
                    142: <li>X11 support for the 3min and 3maxplus machines was broken
                    143: due to a kernel bug.
                    144: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/fb.patch>
                    145: A source code patch is available</a>.
1.59      deraadt   146: <li>A bug in the shared library linker <strong>ld.so</strong> requires that
                    147: you replace it with a new binary.
                    148: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2//pmax/ld.so>
                    149: The replacement binary is here.</a>
1.39      deraadt   150: <p>
1.25      deraadt   151: </ul>
1.59      deraadt   152: <li><font color=#e00000>arc</font>
                    153: <ul>
                    154: <li>A bug in the shared library linker <strong>ld.so</strong> requires that
                    155: you replace it with a new binary.
                    156: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2//pmax/ld.so>
                    157: The replacement binary is here.</a>
                    158: </ul>
1.56      deraadt   159: <li><font color=#e00000>alpha</font>
                    160: <p>
                    161: <ul>
                    162: <li>No problems identified yet.
                    163: <p>
                    164: </ul>
                    165: <li><font color=#e00000>hp300</font>
                    166: <p>
                    167: <ul>
                    168: <li>No problems identified yet.
                    169: <p>
                    170: </ul>
1.39      deraadt   171: <p>
1.25      deraadt   172: </ul>
1.50      deraadt   173: <li><font color=#e00000>mvme68k</font>
1.25      deraadt   174: <ul>
1.39      deraadt   175: <li>No problems identified yet.
                    176: <p>
1.25      deraadt   177: </ul>
                    178: </ul>
                    179: <br>
                    180: <hr>
1.50      deraadt   181: <h3><font color=#0000e0>This is the OpenBSD 2.1 CD errata list:</font></h3>
1.13      pefo      182: <br>
1.14      pefo      183: <ul>
1.50      deraadt   184: <li><font color=#e00000>All architectures</font>
1.13      pefo      185: <ul>
                    186: <li>One of the install scripts has a flaw that makes the CD-ROM mount fail
                    187:        when using the CD-ROM as the install source media.
                    188:        To workaround this use the following sequence of commands before
                    189:        starting the install script. This must be done each time the install
                    190:        kernel is booted if the install script is to be run and the CD-ROM
                    191:        is the media to install from. Do the following at the shell prompt:
1.16      pefo      192: <pre><b>#</b> ed install.sub
                    193: /{_filesystem/s//{_fstype/
                    194: wq
1.13      pefo      195: <b>#</b>
                    196: </pre>
1.22      niklas    197:        For architectures where the install scripts start automatically
                    198:        (like amiga), you need to abort it at the (I)nstall or (U)pdate
1.29      todd      199:        prompt by pressing Ctrl-C before doing the above command.  After
1.22      niklas    200:        that you can restart the install by:
                    201: <pre><b>#</b> install
                    202: </pre>
1.13      pefo      203: </ul>
1.1       deraadt   204: <br>
1.50      deraadt   205: <li><font color=#e00000>Alpha</font>
1.6       grr       206: <ul>
1.1       deraadt   207: <li>CD2 does not boot on the alpha, as had been planned. Instead, you
1.3       deraadt   208:        must use the floppy install method.  This is not significantly
                    209:        harder..
1.6       grr       210: </ul>
1.11      millert   211: <br>
1.50      deraadt   212: <li><font color=#e00000>i386</font>
1.7       deraadt   213: <ul>
                    214: <li>Some rarer PC BIOS's do not like the hardrive bootblocks when used
                    215: as a MBR.  The symptom is that the BIOS says "READ ERROR" when booting,
                    216: but everything suggests it should work fine. In those cases, it is
                    217: sufficient to install OS-BS or some other primary bootloader as the main
                    218: MBR, then install OpenBSD in a partition all by itself starting at a
1.24      mickey    219: non-zero offset.  For instance, start OpenBSD at next track boundary or so.
1.8       deraadt   220: <li>The i386/X11/SUMS.md5 file contains 4 incorrect MD5 checksums.
1.24      mickey    221: These have been corrected on the ftp mirrors. The correct lines are:<br>
1.8       deraadt   222: MD5 (X33doc.tgz) = 6aa0be7987f9a3cf32a63b5ea9a83b39<br>
                    223: MD5 (X33html.tgz) = 6ba39d41aef7c75c35a0533275c6f8c0<br>
                    224: MD5 (X33ps.tgz) = ea49fc1b12c17fc16ece7d0e4ad4ee06<br>
                    225: MD5 (RELNOTES) = 689fda20596a4eb82f86ded51efb01f4<br>
1.21      deraadt   226: <li>A lot of people with IDE disk drives fail to read the
                    227: INSTALL.i386 document, and hence end up with geometry translation
                    228: problems.  Read the document, please.
1.7       deraadt   229: </ul>
1.11      millert   230: <br>
1.50      deraadt   231: <li><font color=#e00000>Amiga</font>
1.6       grr       232: <ul>
1.4       niklas    233: <li>The amiga install has a flaw wrt Tseng based graphic cards: when entering
                    234:        multiuser mode the console won't get a login prompt.  This is due to
                    235:        a problem in the shipped /dev/MAKEDEV script.  To fix, enter single
                    236:        user mode and do:
1.5       todd      237: <pre><b>#</b> cd /dev
1.4       niklas    238: <b>#</b> sh MAKEDEV ttye6
                    239: </pre>
1.6       grr       240: </ul>
1.50      deraadt   241: <li><font color=#e00000>Sparc</font>
1.6       grr       242: <ul>
1.5       todd      243: <li>The sparc X11R6.3 xdm-config files reference /usr/X11R6.3/... This is
                    244:        due to X11R6.3's default config file contents.  To fix, su and
                    245:        type:
                    246: <pre><b>#</b> cd /usr
                    247: <b>#</b> ln -s X11R6 X11R6.3
                    248: </pre>
1.6       grr       249: <li>The sparc "single floppy install disk" has a problem when you specify
                    250:        "dumb" in response to the terminal type query.  As a work-around
                    251:        first specify an invalid terminal such as "bogus" and when prompted
                    252:        again for a terminal type, enter "dumb" and it will work correctly.
                    253: <li>When netbooting an older sparc system such as a Sun4 or Sun4c, the boot
                    254:        may hang up at the end of the tftp transfer of the bootstrap due
                    255:        to the tftp transfer working in 512-byte blocks.  If this occurs
                    256:        create a "padded" version of the bootstrap (boot or zboot) as follows:
                    257: <pre><b>#</b> cd /tftpboot
                    258: <b>#</b> dd if=boot of=newboot obs=512 conv=osync
                    259: <b>#</b> mv newboot boot
                    260: </pre>
1.19      graichen  261: <li>The sparc install script has two flaws that make the kernel copy
                    262:        and the bootblock install fail. The kernel copy only fails
                    263:        then installing from CD-ROM. To workaround this use the
                    264:        following sequence of commands before starting the install
                    265:        script. This must be done each time the install kernel is
                    266:        booted if the install script is to be run and the CD-ROM is
                    267:        the media to install from. Do the following at the shell
                    268:        prompt:
                    269:         if you install from CD-ROM do the following:
                    270: <pre><b>#</b> ed install.md
                    271: /\/bsd/s//\/mnt2\/2.1\/sparc\/bsd/
                    272: wq
                    273: <b>#</b>
                    274: </pre>
                    275:         ... or if you plan to use the bsd.scsi3 kernel you should use instead:
                    276: <pre><b>#</b> ed install.md
                    277: /\/bsd/s//\/mnt2\/2.1\/sparc\/bsd.scsi3/
                    278: wq
                    279: <b>#</b>
                    280: </pre>
                    281:         The following one you'll have to do always (not only then
                    282:        installing from from CD-ROM)
                    283: <pre><b>#</b> ed /usr/mdec/binstall
                    284: /getopt/,/getopt/+4d
                    285: wq
                    286: <b>#</b>
                    287: </pre>
1.6       grr       288: </ul>
1.50      deraadt   289: <li><font color=#e00000>Pmax</font>
1.9       graichen  290: <ul>
1.10      millert   291: <li> When using the X11R6 binaries from the 2.1 release you will get
1.9       graichen  292: errors like:
                    293: <pre><b>#</b> mkfontdir
                    294: mkfontdir: undefined symbol: 'astpending' 12
                    295: Segmentation fault (core dumped)
                    296: </pre>
                    297: this is due to a little problem affecting the compatibility between
                    298: the OpenBSD/arc port (on which the X11R6 clients were build) and
                    299: OpenBSD/pmax. You can work around this problem by using the arc
                    300: version of the shared libc instead of the pmax one. You may get a copy
                    301: of the OpenBSD/arc 2.1 libc.so.16.1 from <a
                    302: href=ftp://miranda.rz-berlin.mpg.de/pub/OpenBSD/pmax/fixes/libc.so.16.1>
                    303: here </a>. Simply download it and do the following:
                    304: <pre><b>#</b> cd /usr/lib
                    305: <b>#</b> mv libc.so.16.1 original_libc.so.16.1
                    306: <b>#</b> cp /where_you_have_downloaded_it_to/libc.so.16.1 .
                    307: <b>#</b> chown root.bin libc.so.16.1
                    308: <b>#</b> chmod 444 libc.so.16.1
                    309: </pre>
                    310: Please be careful while doing this - because the libc is a very
                    311: sensitive part of the system. You can remove the original_libc.so.16.1
                    312: after the next reboot if everything is working fine.
                    313: </ul>
1.18      deraadt   314: <p>
1.50      deraadt   315: <li><font color=#e00000>Mac68k</font>
1.17      deraadt   316: <ul>
1.20      gene      317: <li>The installer generates incorrect /etc/fstab files causing messages such as "file system read-only" on bootup.
                    318: To correct, boot to single-user mode (by clicking that checkbox in the Booter's Booting:Options dialog) and do the following:
1.17      deraadt   319: <pre>
1.18      deraadt   320: <b>#</b> mount /dev/sd0a /
                    321: <b>#</b> ed /etc/fstab
                    322: 1,$s/ ufs / ffs /
1.20      gene      323: 1,$s/ ro / rw /
1.18      deraadt   324: w
                    325: q
1.17      deraadt   326: </pre>
1.20      gene      327: Alternately, simply invoke vi or another editor and change the root filesystem
                    328: to be of type ffs rather than ufs and be rw (read-write) rather than ro
                    329: (read-only).  In either case, you'll need to reboot the system afterwards.
                    330: Make this correction as soon as possible after installing the system.
1.17      deraadt   331: The installer should not have specified the filesystem as the old
                    332: "ufs" type; the "ffs" type is more correct.
1.20      gene      333:
1.17      deraadt   334: <li>The installer forgets to install the kernel onto the filesystem.
1.20      gene      335: This is because the installer expects all packages including the kernel to
                    336: be tar'ed and gzip'ed.  The kernel was not shipped that way.  Therefore, you
                    337: must make this correction <em>before attempting to boot the system</em>.
1.17      deraadt   338: To correct, use the Installer mini-shell and do the following:
                    339: <pre>
1.20      gene      340: > cpin :[internal-macos-path]:bsd-generic bsd
                    341: </pre>
                    342: This should place the kernel as /bsd on the filesystem. You should
1.23      gene      343: replace the above string with the colon-delimited path from your desktop to
1.20      gene      344: wherever you have placed the kernel.  If possible, it is easiest to drag the
1.23      gene      345: kernel into the same folder as the Installer, so you can simply issue a
                    346: command without leading colon(s) like:
1.20      gene      347: <pre>
1.23      gene      348: > cpin bsd-generic bsd
1.17      deraadt   349: </pre>
1.20      gene      350: Good luck.
1.17      deraadt   351: </ul>
1.1       deraadt   352: </ul>
1.2       deraadt   353:
                    354: <hr>
                    355: <a href=orders.html><img src=back.gif border=0 alt=OpenBSD></a>
                    356: <a href=mailto:www@openbsd.org>www@openbsd.org</a>
1.64    ! deraadt   357: <br><small>$OpenBSD: errata.html,v 1.63 1998/02/14 07:24:02 marc Exp $</small>
1.2       deraadt   358:
                    359: </body>
                    360: </html>