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