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