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

Annotation of www/errata.html, Revision 1.61

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