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