Annotation of htdocs/docs/bootcd.html, revision 1.78
1.72 nia 1: <!DOCTYPE html>
1.1 dsieger 2: <html>
3: <head>
4: <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
5: <meta name="generator" content="Website XSL Stylesheet V2.6.0">
6: <link rel="home" href="../." title="Welcome to The NetBSD Project: Of course it runs NetBSD.">
7: <link rel="up" href="../docs/." title="NetBSD Documentation">
8: <link rel="previous" href="../docs/books.html" title="Recommended reading">
9: <link rel="next" href="../docs/bsd/." title="Historic BSD information">
10: <link rel="first" href="../docs/Hardware/." title="Hardware Documentation">
11: <link rel="last" href="../docs/x/." title="NetBSD Documentation: The X Window System">
1.10 dsieger 12: <link rel="stylesheet" href="../global.css" type="text/css">
1.61 maya 13: <link rel="stylesheet" href="../donations/thermo/fundraiser.css" type="text/css">
1.1 dsieger 14:
15: <title>NetBSD Bootable CD ROM HOWTO</title>
16: </head>
1.62 maya 17: <meta name="viewport" content="width=device-width, initial-scale=1.0, minimum-scale=1.0">
1.1 dsieger 18: <body class="website"><div class="webpage">
1.53 maya 19: <a name="docs-bootcd"></a><div id="top"><a href="#mainContent" id="skiplink" tabindex="1">Skip to main content.</a></div>
1.62 maya 20: <input id="hamburger" type="checkbox"><label class="menuicon" for="hamburger"><span></span><span></span><span></span></label><div id="navBar" role="navigation">
1.36 maya 21: <div id="centralHeader"><div id="logo">
1.63 maya 22: <a href="../"><img id="projectLogo" alt="" height="120" src="../images/NetBSD-smaller-tb.png"></a><a href="/"><div id="fundraiser">
1.61 maya 23: <br><div id="fundraiser-amount"><div id="fundraiser-raised"></div></div>
24: </div></a>
1.36 maya 25: </div></div>
1.6 dsieger 26: <span class="doNotDisplay">
27: Navigation:
1.18 jym 28: </span><ul>
29: <li>
30: <a href="../">
1.64 maya 31: Home</a><ul>
1.18 jym 32: <li><a href="../changes/">
33: Recent changes</a></li>
1.39 maya 34: <li><a href="//blog.NetBSD.org/">
1.18 jym 35: NetBSD blog</a></li>
1.59 maya 36: <li><a href="../gallery/presentations/">
37: Presentations</a></li>
1.18 jym 38: </ul>
39: </li>
40: <li>
41: <a href="../about/">
42: About</a><ul>
1.48 maya 43: <li><a href="../people/developers.html">
1.64 maya 44: Developers</a></li>
1.18 jym 45: <li><a href="../gallery/">
1.56 leot 46: Gallery</a></li>
1.64 maya 47: <li><a href="//wiki.NetBSD.org/ports/">
48: Ports</a></li>
1.71 nia 49: <li><a href="//www.pkgsrc.org/">
1.64 maya 50: Packages</a></li>
1.18 jym 51: </ul>
52: </li>
53: <li>
54: <a href="../docs/">
55: Documentation</a><ul>
56: <li><a href="../docs/misc/index.html">
57: FAQ & HOWTOs</a></li>
58: <li><a href="../docs/guide/en/">
59: The Guide</a></li>
1.68 nia 60: <li><a href="//man.NetBSD.org/">
1.18 jym 61: Manual pages</a></li>
1.39 maya 62: <li><a href="//wiki.NetBSD.org/">
1.18 jym 63: Wiki</a></li>
64: </ul>
65: </li>
66: <li>
67: <a href="../support/">
68: Support</a><ul>
1.65 leot 69: <li><a href="/community/">
1.64 maya 70: Community</a></li>
1.65 leot 71: <li><a href="/mailinglists/">
72: Mailing lists</a></li>
1.18 jym 73: <li><a href="../support/send-pr.html">
1.64 maya 74: Bug reports</a></li>
1.18 jym 75: <li><a href="../support/security/">
76: Security</a></li>
77: </ul>
78: </li>
79: <li>
80: <a href="../developers/">
81: Developers</a><ul>
1.42 maya 82: <li><a href="http://cvsweb.NetBSD.org/">
1.64 maya 83: CVSWeb</a></li>
84: <li><a href="//anonhg.NetBSD.org/">
85: Mercurial</a></li>
1.39 maya 86: <li><a href="//nxr.NetBSD.org/">
1.18 jym 87: Cross-reference</a></li>
1.39 maya 88: <li><a href="//releng.NetBSD.org/">
1.18 jym 89: Release engineering</a></li>
1.39 maya 90: <li><a href="//wiki.NetBSD.org/projects/">
1.18 jym 91: Projects list</a></li>
92: </ul>
93: </li>
94: </ul>
1.3 dsieger 95: </div>
1.52 maya 96: <div id="content"><div id="mainContent" class="fullWidth"><div class="rowOfBoxes">
1.3 dsieger 97: <h1>NetBSD Bootable CD ROM HOWTO</h1>
1.14 spz 98: <div class="sect1">
1.1 dsieger 99: <div class="titlepage"></div>
100: <p>
101: This document attempts to explain how to make bootable NetBSD
102: CD ROMs.
103: </p>
104: </div>
105: <h3 class="title"><a name="overview">Overview</a></h3>
106: <ul><li><a href="#creating-the-image">Creating the CD image</a></li></ul>
107: <h3 class="title"><a name="platforms">Platform specific instructions</a></h3>
108: <ul>
109: <li><a href="#alphaimage">NetBSD/alpha</a></li>
110: <li><a href="#i386image">NetBSD/i386</a></li>
111: <li><a href="#macppcimage">NetBSD/macppc</a></li>
112: <li><a href="#pmaximage">NetBSD/pmax</a></li>
113: <li><a href="#sgimips">NetBSD/sgimips</a></li>
114: <li><a href="#sparcimage">NetBSD/sparc</a></li>
115: <li><a href="#sparc64image">NetBSD/sparc64</a></li>
116: <li><a href="#sun2image">NetBSD/sun2</a></li>
117: <li><a href="#sun3image">NetBSD/sun3</a></li>
118: <li><a href="#vaximage">NetBSD/vax</a></li>
119: <li><a href="#multiimage">Multiple Machine</a></li>
120: </ul>
121: <h3 class="title"><a name="examining-the-image">Examining the CD image</a></h3>
122: <ul>
123: <li><a href="#netbsd_mountimage">Under NetBSD</a></li>
124: <li><a href="#linux_mountimage">Under Linux</a></li>
125: <li><a href="#solaris_mountimage">Under Solaris</a></li>
126: </ul>
127: <h3 class="title"><a name="burning-the-cd">Burning the CD</a></h3>
128: <ul>
129: <li><a href="#cdrecord">Using cdrecord (U*nix)</a></li>
130: <li><a href="#winrecord">Under Windows</a></li>
131: <li><a href="#macrecord">Under Mac OS</a></li>
132: </ul>
133: <hr>
134: <h3 class="title">Overview</h3>
135: <h4 class="title">
1.49 maya 136: <a name="creating-the-image"></a>Creating the CD image</h4>
1.1 dsieger 137: <p>
138: The first step in making a CD ROM is to create an image of the CD.
139: This image will initially be stored as a (rather large, up to 650 Mb)
140: file on your hard drive and then later written to the CD.
141: </p>
142: <p>
143: This section assumes you have access to the program
144: <code class="code">mkisofs</code>. If you are making the CD image on a NetBSD
145: machine, you can install <code class="code">mkisofs</code> from the
1.70 nia 146: <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/sysutils/cdrtools/index.html" target="_top"><code class="filename">sysutils/cdrtools</code></a>
1.1 dsieger 147: package.
148: </p>
149: <p>
150: It is assumed the directory <code class="code">/cdsources</code> exists on your system
151: and contains all the files which you want to end up on the CD ROM.
152: One suggested layout for making an install CD is to follow the
1.10 dsieger 153: directory structure on <a class="ulink" href="ftp://ftp.NetBSD.org/pub/NetBSD/NetBSD-3.0/" target="_top">ftp.NetBSD.org</a>. For example:
1.1 dsieger 154: </p>
155: <pre class="programlisting">
156: /cdsources/i386/.....
157: /cdsources/sparc/.....</pre>
158: <p>
159: </p>
160: <hr>
161: <h3 class="title">Platform specific instructions</h3>
162: <h4 class="title">
1.49 maya 163: <a name="alphaimage"></a>NetBSD/alpha</h4>
1.1 dsieger 164: <p>
165: There are 2 steps involved in making a NetBSD/alpha bootable CD ROM.
166: The first is to create an ISO 9660 image of whatever you want
167: to put on the CD. This image must have the secondary boot program and
168: kernel in its root directory. In addition, the primary boot program
169: will be needed for the second step. To put the boot programs and
170: kernel in the right places, do the following:
171: </p>
172:
173: <pre class="programlisting">
174: cd /cdsources/alpha/binary/sets
175: tar -zxvf base.tgz ./usr/mdec/boot ./usr/mdec/bootxx_cd9660
176: mv -f ./usr/mdec/boot /cdsources/boot
177: mkdir /tmp/mdec.alpha
178: mv -f ./usr/mdec/bootxx_cd9660 /tmp/mdec.alpha/bootxx_cd9660
179: rm -rf ./usr
180: cd /cdsources/alpha/installation/instkernel
181: cp -f netbsd.gz /cdsources/netbsd.gz</pre>
182:
183: <p>
184: Now create the ISO 9660 image.
185: </p>
186: <pre class="programlisting">mkisofs -o output.iso -l -J -R -allow-leading-dots /cdsources</pre>
187:
188: <p>
189: The second step is to install NetBSD/alpha disk and CD ROM bootstrap
1.78 ! martin 190: software using <a href="//man.NetBSD.org/NetBSD-10.0/installboot.8">installboot(8)</a>. This is done with the
1.1 dsieger 191: following command:
192: </p>
193:
194: <pre class="programlisting">installboot -m alpha -v output.iso /tmp/mdec.alpha/bootxx_cd9660</pre>
195:
196:
197: <h4 class="title">
1.49 maya 198: <a name="i386image"></a>NetBSD/i386</h4>
1.1 dsieger 199: <p>
200: This section shows how to make a NetBSD/i386 bootable CD ROM. The
201: particular example is how to make a NetBSD-3.0/i386 install CD. It
202: is assumed that the directory <code class="code">/cdsources/</code> exists on your system
203: and contains all the files and the directory structure from the
1.10 dsieger 204: <a class="ulink" href="ftp://ftp.NetBSD.org/pub/NetBSD/NetBSD-3.0/i386/" target="_top">NetBSD-3.0/i386</a>
1.1 dsieger 205: distribution.
206: The exact contents depend on what you want on your CD. The
207: important part is that
208: <code class="code">/cdsources/i386/installation/floppy/boot-big.fs</code> exists as that will
209: be used as the bootable image.
210: </p>
211: <p>
212: To create the CD image use the following command:
213: </p>
214:
215: <pre class="programlisting">
216: mkisofs -o output.iso -b i386/installation/floppy/boot-big.fs \
217: -c boot.catalog -l -J -R -allow-leading-dots /cdsources</pre>
218:
219: <p>
220: This will create a file, <code class="code">output.iso</code>, which is the CD image.
221: The options are:
222: </p>
1.24 tron 223: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.14 spz 224: <li class="listitem">
1.1 dsieger 225: <p>
226: <code class="code">-b i386/installation/floppy/boot-big.fs</code>
227: -- specifies the boot image to be used
228: </p>
229: </li>
1.14 spz 230: <li class="listitem">
1.1 dsieger 231: <p>
232: <code class="code">-c boot.catalog</code>
233: -- creates a boot catalog
234: </p>
235: </li>
1.14 spz 236: <li class="listitem">
1.1 dsieger 237: <p>
238: <code class="code">-l</code> -- Allow long (32 character) file names
239: </p>
240: </li>
1.14 spz 241: <li class="listitem">
1.1 dsieger 242: <p><code class="code">-J</code> -- Includes Joliet extensions</p>
243: </li>
1.14 spz 244: <li class="listitem">
1.1 dsieger 245: <p><code class="code">-R</code> -- Sets file permissions including setuid</p>
246: </li>
1.14 spz 247: <li class="listitem">
1.1 dsieger 248: <p>
249: <code class="code">-allow-leading-dots</code> -- Allows filenames to begin with
1.14 spz 250: <span class="quote">“<span class="quote">.</span>”</span>, was <code class="code">-L</code> in older versions
1.1 dsieger 251: of mkisofs.
252: </p>
253: </li>
1.14 spz 254: <li class="listitem">
1.1 dsieger 255: <p>
256: <code class="code">/cdsources</code> -- Specifies that the directory
257: <code class="code">/cdsources</code> is the root of the CD image
258: </p>
259: </li>
260: </ul></div>
261: <p>
262: </p>
263:
264: <h4 class="title">
1.49 maya 265: <a name="macppcimage"></a>NetBSD/macppc</h4>
1.1 dsieger 266: <p>
267: All supported macppc models can boot from the first session of a CD ROM.
268: The procedure for making a CD bootable depends on what version of Open
1.10 dsieger 269: Firmware your model has. Refer to the <a class="ulink" href="../ports/macppc/models.html" target="_top">NetBSD/macppc Model Support Page</a> to
1.1 dsieger 270: determine your system's Open Firmware version and its support status.
271: </p>
272:
273: <p>
274: It is assumed that the directory <code class="code">/cdsources/</code> exists on your
1.10 dsieger 275: system and contains all the files and the directory structure from the <a class="ulink" href="ftp://ftp.NetBSD.org/pub/NetBSD/NetBSD-3.0/macppc/" target="_top">NetBSD-3.0/macppc</a>
1.1 dsieger 276: distribution. The exact contents depend on what you want on your CD.
277: </p>
278:
279: <p>
280: Make sure your <code class="code">/cdsources/</code> has <code class="code">ofwboot.xcf</code> (the macppc
281: bootloader) and a kernel (we suggest <code class="code">netbsd.GENERIC_MD</code>, the
282: ramdisk-based install kernel that supports all models).
283: </p>
284:
285: <pre class="programlisting">
286: cd /cdsources
287: cp macppc/binary/kernel/netbsd-GENERIC_MD.gz netbsd.macppc
288: cp macppc/installation/ofwboot.xcf .</pre>
289:
290: <p>
291: The NetBSD/macppc official ISO image is bootable on all supported models
292: because it does some special magic. The CD is created as an HFS
293: hybrid CD with an Apple Disk Partition Table using the <code class="code">-hfs -part</code>
294: options in mkisofs. The Partition Table is then modified to map (or point to)
295: a driver file which makes the CD bootable on the PPC Macintosh and the
296: driver file is appended to the end of the iso image.
297: </p>
298:
299: <p>
300: The CD won't be bootable via the
1.14 spz 301: <span class="quote">“<span class="quote"><code class="code">C</code></span>”</span> snag key though. However
1.1 dsieger 302: this can be added with the following, although it may not
303: work on all Macppc systems. (Adding the option will not
304: impair the use of booting via OpenFirmware commands.) To
305: do this, create a CHRP bootscript in a top-level
306: directory, tag the bootscript file with the proper Mac OS
307: Type and Creator, and "bless" the directory which contains
308: the file. Mkisofs will attach the proper Mac OS Type and
309: Creator codes while generating the ISO image file if the
310: following line is added to the file
311: <code class="code">/usr/src/distrib/cdrom/hfsmap.lst</code>:
312: </p>
313:
314: <pre class="programlisting">.chrp - 'chrp' 'tbxi'</pre>
315:
316: <p>
317: Then place the following file named <code class="code">bootscript</code> in the (top-level)
318: <code class="code">macppc</code> directory:
319: </p>
320:
321: <pre class="programlisting">
322: <CHRP-BOOT>
323: <COMPATIBLE>MacRISC</COMPATIBLE>
324: <DESCRIPTION>
325: NetBSD/macppc bootable CD script
326: </DESCRIPTION>
327: <BOOT-SCRIPT>
328: boot cd:,ofwboot.xcf netbsd.macppc
329: </BOOT-SCRIPT>
330: </CHRP-BOOT></pre>
331:
332: <p>Create the macppc bootable CD image using the following commands:</p>
333:
334: <pre class="programlisting">
335: cdrom_util="/usr/src/distrib/cdrom"
336: snag_boot="-map ${cdrom_util}/hfsmap.lst -hfs-bless ./macppc"
337: ofw_boot="-boot-hfs-file ${cdrom_util}/macppc_installboot/macppcboot.raw"
338: mkisofs -o output.iso -hfs -part ${snag_boot} ${ofw_boot} -l -J -r -allow-leading-dots /cdsources
339: blknum=`ls -l output.iso | awk '{print $5}'`
340: blknum=`expr ${blknum} / 512`
341: ${cdrom_util}/macppc_installboot/macppc_installboot output.iso ${blknum} 756
342: dd if=/usr/mdec/ofwboot bs=64k count=1 conv=sync >> output.iso</pre>
343:
344: <p>
345: Once you have burnt the CD, make sure Open Firmware can find the
346: bootloader on your new CD ROM (see
1.10 dsieger 347: <a class="ulink" href="../ports/macppc/faq.html#ofw-dir-listing" target="_top">How do I get a listing (in
1.1 dsieger 348: Open Firmware) of the files on my disk?</a> in the FAQ). This is
349: important, since Open Firmware treats the boot file name as case
350: sensitive. Most (if not all) Open Firmware 1.0.5, 1.1.22, and 2.0.x systems
351: will think the bootloader is <code class="code">OFWBOOT.XCF</code> and Open Firmware 3 should
352: properly see it as <code class="code">ofwboot.xcf</code>.
353: </p>
354:
355: <h4 class="title">
1.49 maya 356: <a name="pmaximage"></a>NetBSD/pmax</h4>
1.1 dsieger 357: <p>
358: NetBSD/pmax can boot from either a FFS or ISO 9660 CD ROM. This
359: section assumes you are making an ISO 9660 CD ROM. Please note that
360: the bootxx_cd9660 program was not added until <span class="emphasis"><em>after</em></span> NetBSD-1.4.x.
361: If you're running NetBSD-1.4.x, you can obtain <code class="code">boot.pmax</code>,
362: <code class="code">installboot</code>, and <code class="code">bootxx_cd9660</code> from a -current snapshot.
363: Make sure the sources are from <span class="emphasis"><em>after</em></span> late November, 1999.
364: </p>
365: <p>
366: There are 2 steps involved in making a NetBSD/pmax bootable CD ROM.
367: The first is to create an ISO 9660 image of whatever you want
368: to put on the CD. This image must have the secondary boot program
369: and kernel in its root directory.
370: In addition, the primary boot program
371: will be needed for the second step. To put the boot programs and
372: kernel in the right places, do the following:
373: </p>
374:
375: <pre class="programlisting">
376: cd /cdsources/pmax/binary/sets
377: tar -zxvf base.tgz ./usr/mdec/boot.pmax ./usr/mdec/bootxx_cd9660
378: mv -f ./usr/mdec/boot.pmax /cdsources/boot.pmax
379: mkdir /tmp/mdec.pmax
380: mv -f ./usr/mdec/bootxx_cd9660 /tmp/mdec.pmax/bootxx_cd9660
381: rmdir ./usr/mdec
382:
383: cd /cdsources/pmax/binary/kernel
384: cp -f install.gz /cdsources/netbsd.pmax.gz
385: gunzip /cdsources/netbsd.pmax.gz</pre>
386:
387: <p>
388: Now create the ISO 9660 image.
389: </p>
390:
391: <pre class="programlisting">mkisofs -o output.iso -l -J -r -allow-leading-dots /cdsources</pre>
392:
393: <p>
394: The second step is to install NetBSD/pmax disk and CD ROM bootstrap
1.78 ! martin 395: software using <a href="//man.NetBSD.org/NetBSD-10.0/installboot.8">installboot(8)</a>. The
! 396: <a href="//man.NetBSD.org/NetBSD-10.0/installboot.8">installboot(8)</a> command is used in the following way:
1.1 dsieger 397: </p>
398:
399: <pre class="programlisting">installboot -m pmax -v output.iso /usr/mdec/bootxx_cd9660</pre>
400:
401:
402: <h4 class="title">
1.49 maya 403: <a name="sgimips"></a>NetBSD/sgimips</h4>
1.1 dsieger 404: <p>
1.10 dsieger 405: Please see <a class="ulink" href="http://mail-index.NetBSD.org/port-sgimips/2003/06/29/0000.html" target="_top">this
406: posting</a> to the <a class="ulink" href="../mailinglists/#port-sgimips" target="_top">port-sgimips
1.1 dsieger 407: MailingList</a> for instructions on how to create a bootable CD ROM. Note
408: that these instructions have not been verified by the NetBSD developers (yet).
409: </p>
410:
411: <h4 class="title">
1.49 maya 412: <a name="sparcimage"></a>NetBSD/sparc</h4>
1.1 dsieger 413: <p>
414: There are three steps involved in making a NetBSD/sparc bootable CD ROM.
415: Step 1 is to create an "almost" full ISO 9660 image of whatever you want
416: to put on the CD. For example:
417: </p>
418:
419: <pre class="programlisting">mkisofs -o output.iso -l -J -r -allow-leading-dots /cdsources</pre>
420:
421: <p>
422: Now get a bootable floppy image. For NetBSD-3.0/sparc, this image
423: may be found at
1.10 dsieger 424: <a class="ulink" href="ftp://ftp.NetBSD.org/pub/NetBSD/NetBSD-3.0/sparc/installation/bootfs/boot.fs.gz" target="_top">ftp://ftp.NetBSD.org/pub/NetBSD/NetBSD-3.0/sparc/installation/bootfs/boot.fs.gz</a>
1.1 dsieger 425: </p>
426:
427: <p>
428: The final step is to rewrite the ISO image with (a) a sun disklabel at
429: the start, (b) the original image at the end, and (c) with the right
430: offset/size values in the disklabel for the bootloader. The program
431: <code class="code">mksunbootcd</code> will perform this task. If <code class="code">mksunbootcd</code>
432: is not installed on your system, it can be installed from the
1.70 nia 433: <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/sysutils/mksunbootcd/index.html" target="_top"><code class="filename">sysutils/mksunbootcd</code></a>
1.1 dsieger 434: package. If you're creating the image on a non-NetBSD system, you
435: can try compiling <code class="code">mksunbootcd</code> on your system. The sources
436: are available at
1.10 dsieger 437: <a class="ulink" href="ftp://ftp.NetBSD.org/pub/NetBSD/misc/mksunbootcd/" target="_top">ftp://ftp.NetBSD.org/pub/NetBSD/misc/mksunbootcd/</a>.
1.1 dsieger 438: </p>
439:
440: <p>
441: To use <code class="code">mksunbootcd</code> use the following:
442: </p>
443:
444: <pre class="programlisting">mksunbootcd output.iso boot.fs boot.fs boot.fs</pre>
445:
446: <p>
447: The bootable image is listed three times corresponding to what will get
448: booted by a sun4, sun4c and sun4m system respectively. If you have
449: different bootable images for the three machines, or if you also have
450: a bootable image for sun2, sun3, and sun3x systems, you can do something
451: like:
452: </p>
453:
454: <pre class="programlisting">mksunbootcd output.iso boot-sun4.fs boot-sun4c.fs boot-sun4m.fs boot-sun3.fs</pre>
455:
456: <p>
457: Note that <code class="code">mksunbootcd</code> rewrites the <code class="code">output.iso</code> file, so
458: don't run it multiple times.
459: </p>
460:
461: <p>
462: As a note, this step is fine to perform on a NFS mounted directory. Ie,
463: if your ISO image is on a remote machine, it can be mounted on a NetBSD
464: machine for running <code class="code">mksunbootcd</code> without requiring extreme amounts
465: of data to be transferred over the network.
466: </p>
467:
468: <h4 class="title">
1.49 maya 469: <a name="sparc64image"></a>NetBSD/sparc64</h4>
1.1 dsieger 470: <p>
471: There are three steps involved in making a NetBSD/sparc64 bootable CD ROM.
472: Step 1 is to create an "almost" full ISO 9660 image of whatever you want to
473: put on the CD. For example:
474: </p>
475:
476: <pre class="programlisting">mkisofs -o output.iso -l -J -r -allow-leading-dots /cdsources</pre>
477:
478: <p>
479: Now get a bootable floppy image. For NetBSD-3.0/sparc64, this image
1.10 dsieger 480: may be found at <a class="ulink" href="ftp://ftp.NetBSD.org/pub/NetBSD/NetBSD-3.0/sparc64/installation/misc/boot.fs.gz" target="_top">ftp://ftp.NetBSD.org/pub/NetBSD/NetBSD-3.0/sparc64/installation/misc/boot.fs.gz</a>.
1.1 dsieger 481: </p>
482:
483: <p>
484: The final step is to rewrite the ISO image with (a) a sun disklabel at
485: the start, (b) the original image at the end, and (c) with the right
486: offset/size values in the disklabel for the bootloader. The program
487: <code class="code">sunbootcd.sh</code> will perform this task. If <code class="code">sunbootcd.sh</code>
1.10 dsieger 488: is not installed on your system, it can be obtained from <a class="ulink" href="ftp://ftp.NetBSD.org/pub/NetBSD/NetBSD-current/src/distrib/common/sunbootcd.sh" target="_top">ftp://ftp.NetBSD.org/pub/NetBSD/NetBSD-current/src/distrib/common/sunbootcd.sh</a>.
1.1 dsieger 489: </p>
490:
491: <p>
492: To use <code class="code">sunbootcd.sh</code> use the following:
493: </p>
494:
495: <pre class="programlisting">sunbootcd.sh output.iso - - - - boot.fs</pre>
496:
497: <p>
498: The arguments are for bootable images for sun4, sun4c, sun4m, sun4d, and
499: sun4u. Specifying a dash instead of a boot image means the CD will not be
500: bootable for that platform. In the above example the only platform given
501: a boot image is sun4u.
502: </p>
503:
504: <p>
505: Note that <code class="code">sunbootcd.sh</code> rewrites the <code class="code">output.iso</code> file, so
506: don't run it multiple times.
507: </p>
508:
509: <p>
510: As a note, this step is fine to perform on a NFS mounted directory. Ie,
511: if your ISO image is on a remote machine, it can be mounted on a NetBSD
512: machine for running <code class="code">sunbootcd.sh</code> without requiring extreme amounts
513: of data to be transferred over the network.
514: </p>
515:
516: <p>
517: Be aware that <code class="code">sunbootcd.sh</code> will produce a CD that is not
518: recognized by vold under Solaris 10. If you want to mount the NetBSD
519: install CD under Solaris, you will first need to stop vold.
520: </p>
521:
522: <pre class="programlisting">/etc/init.d/volmgt stop</pre>
523:
524:
525: <h4 class="title">
1.49 maya 526: <a name="sun2image"></a>NetBSD/sun2</h4>
1.1 dsieger 527: <p>
528: To make a NetBSD/sun2 bootable CD ROM, follow the procedure below for
529: making a NetBSD/sun3 bootable CD ROM. This procedure makes a single
530: CD ROM that will boot on both sun2 and sun3 systems.
531: </p>
532:
533: <p>
534: <span class="emphasis"><em>Optional:</em></span> When following the procedure below, it is beneficial
535: to uncompress the sun2 miniroot
536: (<code class="code">/cdsources/sun2/installation/miniroot.fs.gz</code>) and binary sets
537: (<code class="code">/cdsources/sun2/binary/sets/*.tgz</code>)
538: before writing the ISO 9660 image. This is entirely optional, and consumes
539: a lot of space on the ISO 9660 image, but saves time during installation
540: because decompression is very slow on the sun2.
541: </p>
542:
543: <h4 class="title">
1.49 maya 544: <a name="sun3image"></a>NetBSD/sun3</h4>
1.1 dsieger 545: <p>
546: There are three steps involved in making a NetBSD/sun3 bootable CD ROM, and
547: this will result in a CD ROM that can also boot NetBSD/sun2.
548: </p>
549:
550: <p>
551: Step 1 is to create an "almost" full ISO 9660 image of whatever you want
552: to put on the CD. For example:
553: </p>
554:
555: <pre class="programlisting">mkisofs -o output.iso -l -J -r -allow-leading-dots /cdsources</pre>
556:
557: <p>
558: Now build a bootable ffs image. This image is currently not included in
559: the release, so you have to put it together yourself.
560: </p>
561:
562: <pre class="programlisting">
563: mkdir /tmp/boot-sun3
564: cd /tmp/boot-sun3
565: gzip -cd < /cdsources/sun2/binary/kernel/netbsd.RAMDISK.gz > netbsd.sun2
566: ln netbsd.sun2 vmunix
567: gzip -cd < /cdsources/sun3/binary/kernel/netbsd.RAMDISK.gz > netbsd.sun3
568: gzip -cd < /cdsources/sun3/binary/kernel/netbsd.RAMDISK3X.gz > netbsd.sun3x
569: tar xzvf /cdsources/sun3/binary/sets/base.tgz ./usr/mdec
570: mv usr/mdec/ufsboot .
571: mv usr/mdec/bootxx /tmp/bootxx.sun3
572: rm -rf /tmp/boot-sun3/usr
573:
574: echo /set type=file uname=root gname=wheel mode=0755 > /tmp/boot-sun3.spec
575: echo . type=dir >> /tmp/boot-sun3.spec
576: echo ufsboot mode=0644 >> /tmp/boot-sun3.spec
577: /bin/ls netbsd* vmunix >> /tmp/boot-sun3.spec
578:
579: makefs -t ffs -B be -F /tmp/boot-sun3.spec /tmp/boot-sun3.fs /tmp/boot-sun3
580:
581: installboot -m sun3 -v /tmp/boot-sun3.fs /tmp/bootxx.sun3 ufsboot</pre>
582:
583: <p>
584: The final step is to rewrite the ISO image with (a) a sun disklabel at
585: the start, (b) the original image at the end, and (c) with the right
586: offset/size values in the disklabel for the bootloader. The program
587: <code class="code">mksunbootcd</code> will perform this task. If <code class="code">mksunbootcd</code>
588: is not installed on your system, it can be installed from the
1.70 nia 589: <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/sysutils/mksunbootcd/index.html" target="_top"><code class="filename">sysutils/mksunbootcd</code></a>
1.1 dsieger 590: package. If you're creating the image on a non-NetBSD system, you
591: can try compiling <code class="code">mksunbootcd</code> on your system. The sources
592: are available at
1.10 dsieger 593: <a class="ulink" href="ftp://ftp.NetBSD.org/pub/NetBSD/misc/mksunbootcd/" target="_top">ftp://ftp.NetBSD.org/pub/NetBSD/misc/mksunbootcd/</a>.
1.1 dsieger 594: </p>
595:
596: <p>
597: To use <code class="code">mksunbootcd</code> use the following:
598: </p>
599:
600: <pre class="programlisting">mksunbootcd output.iso /tmp/boot-sun3.fs </pre>
601:
602: <p>
603: Note that <code class="code">mksunbootcd</code> is also used to make a bootable CD ROM
604: for sparc systems. It is possible to make a bootable CD ROM that will
605: boot on sparc, sun2, sun3, and sun3x by doing something like:
606: </p>
607:
608: <pre class="programlisting">mksunbootcd output.iso boot-sun4.fs boot-sun4c.fs boot-sun4m.fs boot-sun3.fs</pre>
609:
610: <p>
611: You can rearrange the ordering of the bootable filesystems in any way
612: you want; this only changes the partition numbers that the different
613: filesystems end up with, thus changing the partition number you need
614: to give to the PROM <code class="code">b</code> or <code class="code">boot</code> command to boot the
615: right filesystem for a given architecture.
616: </p>
617:
618: <p>
619: Note that <code class="code">mksunbootcd</code> rewrites the <code class="code">output.iso</code> file, so
620: don't run it multiple times.
621: </p>
622:
623: <p>
624: As a note, this step is fine to perform on a NFS mounted directory. Ie,
625: if your ISO image is on a remote machine, it can be mounted on a NetBSD
626: machine for running <code class="code">mksunbootcd</code> without requiring extreme amounts
627: of data to be transferred over the network.
628: </p>
629:
630: <h4 class="title">
1.49 maya 631: <a name="vaximage"></a>NetBSD/vax</h4>
1.1 dsieger 632: <p>
633: NetBSD/vax can boot from either a FFS or ISO 9660 CD ROM. This
634: section assumes you are making an ISO 9660 CD ROM. Please note that
635: this capability was not added until NetBSD-1.5
636: </p>
637:
638: <p>
639: There are 2 steps involved in making a NetBSD/vax bootable CD ROM.
640: The first is to create an ISO 9660 image of whatever you want
641: to put on the CD. This image must have the secondary boot program
642: and kernel in its root directory.
643: In addition, the primary boot program
644: will be needed for the second step. To put the boot programs and
645: kernel in the right places, do the following:
646: </p>
647:
648: <pre class="programlisting">
649: cd /cdsources/vax/binary/sets
650: tar -zxvf base.tgz ./usr/mdec/boot ./usr/mdec/xxboot
651: mv -f ./usr/mdec/boot /cdsources/boot.vax
652: mkdir /tmp/mdec.vax
653: mv -f ./usr/mdec/xxboot /tmp/mdec.vax/xxboot
654: rmdir ./usr/mdec
655:
656: cd /cdsources/vax/installation/netboot
657: cp -f install.ram.gz /cdsources/netbsd.vax.gz
658: gunzip -f /cdsources/netbsd.vax.gz</pre>
659:
660: <p>
661: Now create the ISO 9660 image.
662: </p>
663:
664: <pre class="programlisting">mkisofs -o output.iso -l -J -r -allow-leading-dots /cdsources</pre>
665:
666: <p>
667: The second step is to install NetBSD/vax disk and CD ROM bootstrap
1.78 ! martin 668: software using <a href="//man.NetBSD.org/NetBSD-10.0/installboot.8">installboot(8)</a>. The
! 669: <a href="//man.NetBSD.org/NetBSD-10.0/installboot.8">installboot(8)</a> command is used in the following way:
1.1 dsieger 670: </p>
671:
672: <pre class="programlisting">installboot -m vax -v output.iso /usr/mdec/xxboot</pre>
673:
674:
675: <h4 class="title">
1.49 maya 676: <a name="multiimage"></a>Multiple Machine</h4>
1.1 dsieger 677: <p>
678: NetBSD-current has infrastructure in
1.10 dsieger 679: <code class="code"><a class="ulink" href="http://cvsweb.NetBSD.org/bsdweb.cgi/src/distrib/cdrom?rev=HEAD&content-type=text/x-cvsweb-markup" target="_top">src/distrib/cdrom</a></code>
1.1 dsieger 680: to build CDs which can boot multiple machines.
681: This has been used to build a four CD set containing thirty-nine platforms,
682: with eight platforms able to boot off the CDs.
683: This technique requires <code class="code">mkisofs</code> version 1.15a34 or newer.
684: </p>
685:
686: <p>
687: Alternatively, multiple machine boot CDs can be created with the
688: following manual procedure.
689: This procedure
690: has been successfully used to create a single CD which is bootable on
691: alpha, i386, pmax, and sparc. It should be possible to also make the
692: CD bootable on macppc, vax and on sun2, sun3 and sun3x.
693: To create a CD which is bootable by multiple architectures, use the
694: following steps in this order. Please note that the order is critical.
695:
696: </p>
1.24 tron 697: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.14 spz 698: <li class="listitem">
1.1 dsieger 699: <p>
700: Make sure you have all the required files including the various
701: kernels and boot programs listed in the individual machine
702: sections.
703: </p>
704: </li>
1.14 spz 705: <li class="listitem">
1.1 dsieger 706: <p>
707: Include a directory somewhere in the <code class="code">cdsources</code>
708: directory called <code class="code">mdec.pmax</code>
709: and include the pmax <code class="code">bootxx_cd9660</code> file there. For example,
710: <code class="code">/cdsources/usr/mdec.pmax/bootxx_cd9660</code>.
711: </p>
712: </li>
1.14 spz 713: <li class="listitem">
1.1 dsieger 714: <p>
715: Include a directory somewhere in the <code class="code">cdsources</code>
716: directory called <code class="code">mdec.vax</code>
717: and include the vax <code class="code">xxboot</code> file there. For example,
718: <code class="code">/cdsources/usr/mdec.vax/xxboot</code>.
719: </p>
720: </li>
1.14 spz 721: <li class="listitem">
1.1 dsieger 722: <p>
723: Include the macppc <code class="code">ofwboot.xcf</code> bootloader in <code class="code">/cdsources</code>.
724: </p>
725: </li>
1.14 spz 726: <li class="listitem">
1.1 dsieger 727: <p>
728: Create an i386 bootable image.
729:
730: </p>
731: <pre class="programlisting">
732: sh
733: mkisofs -v -v -o output.iso -b i386/installation/floppy/boot-big.fs \
734: -c boot.catalog -l -J -r -allow-leading-dots /cdsources 2>&1 | tee /tmp/mkisofs.log
735: exit</pre>
736: <p>
737:
738: Note that the appearance of the <code class="code">-v</code> flag twice is required. If you are
739: making a bootable CD for an Open Firmware 3 macppc model, make sure to include
740: <code class="code">-hfs -part</code> in the parameters for <code class="code">mkisofs</code>.
741: </p>
742: </li>
1.14 spz 743: <li class="listitem">
1.1 dsieger 744: <p>
745: Run <code class="code">mksunbootcd</code> on a NetBSD/sparc machine to install sparc
746: and sun2/sun3 bootblocks. Alternatively, install the
1.70 nia 747: <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/sysutils/mksunbootcd/index.html" target="_top"><code class="filename">sysutils/mksunbootcd</code></a>
1.1 dsieger 748: package on your favorite NetBSD machine.
749:
750: </p>
751: <pre class="programlisting">mksunbootcd output.iso boot-sun4.fs boot-sun4c.fs boot-sun4m.fs boot-sun3.fs</pre>
752: <p>
753: </p>
754: </li>
1.14 spz 755: <li class="listitem">
1.1 dsieger 756: <p>
1.78 ! martin 757: Run the <a href="//man.NetBSD.org/NetBSD-10.0/installboot.8">installboot(8)</a> program targeted for
1.1 dsieger 758: NetBSD/pmax to install the pmax bootblocks.
759: Note that in order to coexist with other NetBSD boot blocks, the pmax
760: boot block is appended to the end of the ISO file system.
761:
762: </p>
763: <pre class="programlisting">installboot -m pmax -v -o append,sunsum output.iso /tmp/mdec.pmax/bootxx_cd9660</pre>
764: <p>
765:
766: The <code class="code">-o append,sunsum</code> option appends the first stage boot block to
767: the end of the ISO file system, and restores the checksum used when booting
768: on a sun.
769: </p>
770: </li>
1.14 spz 771: <li class="listitem">
1.1 dsieger 772: <p>
1.78 ! martin 773: Run the <a href="//man.NetBSD.org/NetBSD-10.0/installboot.8">installboot(8)</a> program targeted for
1.1 dsieger 774: NetBSD/vax to install the vax bootblocks.
775: Note that in order to coexist with other NetBSD boot blocks, the vax
776: boot block is appended to the end of the ISO file system.
777:
778: </p>
779: <pre class="programlisting">installboot -m vax -v -o append,sunsum output.iso /tmp/mdec.vax/xxboot</pre>
780: <p>
781:
782: (See the pmax entry above for an explanation of the flags).
783: </p>
784: </li>
1.14 spz 785: <li class="listitem">
1.1 dsieger 786: <p>
1.78 ! martin 787: Run the <a href="//man.NetBSD.org/NetBSD-10.0/installboot.8">installboot(8)</a> program targeted for
1.1 dsieger 788: NetBSD/alpha to install the alpha bootblocks.
789:
790: </p>
791: <pre class="programlisting">installboot -m alpha -v -o append,sunsum output.iso /tmp/mdec.alpha/bootxx_cd9660</pre>
792: <p>
793:
794: Note that the alpha installboot must occur after the others, because
795: currently it's the only machine dependent back-end for
796: <code class="code">installboot(8)</code> that can calculate the alpha checksum.
797: (See the pmax entry above for an explanation of the flags).
798: </p>
799: </li>
800: </ul></div>
801: <p>
802: </p>
803: <hr>
804: <h3 class="title">Examining the CD image</h3>
1.15 reed 805: <p>
806: It is possible to mount the cd image to examine the filesystem you
807: just created.
808: </p>
1.1 dsieger 809: <h4 class="title">
1.49 maya 810: <a name="netbsd_mountimage"></a>Under NetBSD</h4>
1.1 dsieger 811: <p>
812: Mount the CD image using the following:
813: </p>
814:
815: <pre class="programlisting">
816: vnconfig -c vnd0 output.iso
817: mount -t cd9660 /dev/vnd0c /mnt</pre>
818:
819: <p>
820: Please note that on i386 systems, you should use <code class="code">/dev/vnd0d</code> instead
821: of <code class="code">/dev/vnd0c</code>.
822: Now you can cd to /mnt and explore your newly created CD image.
823: To unmount the image, do the following:
824: </p>
825:
826: <pre class="programlisting">
827: umount /mnt
828: vnconfig -u vnd0</pre>
829:
830:
831: <h4 class="title">
1.49 maya 832: <a name="linux_mountimage"></a>Under Linux</h4>
1.1 dsieger 833: <p>
834: Linux has a similar capability. To mount the CD image:
835: </p>
836:
837: <pre class="programlisting">mount -t iso9660 -o ro,loop=/dev/loop0 output.iso /mnt</pre>
838:
839: <p>
840: and to unmount the CD image:
841: </p>
842:
843: <pre class="programlisting">umount /mnt</pre>
844:
845:
846: <h4 class="title">
1.49 maya 847: <a name="solaris_mountimage"></a>Under Solaris</h4>
1.1 dsieger 848: <p>
849: Solaris-8 and newer is reported to be able to also mount
850: the CD image. See the <code class="code">lofiadm</code> manpage on solaris
851: for more details on how to do this.
852: </p>
853:
854: <p>
855: For older versions of Solaris, you might want to try the
856: <code class="code">fbk</code> driver written by Joerg Schilling. The <code class="code">fbk</code> driver
857: is available from
1.10 dsieger 858: <a class="ulink" href="ftp://ftp.berlios.de/pub/schily/kernel/fbk/" target="_top">ftp://ftp.berlios.de/pub/schily/kernel/fbk/</a>.
1.1 dsieger 859: Please refer to the <code class="code">fbk</code> documentation for installation instructions.
860: Once the <code class="code">fbk</code> driver is installed on your system, you can mount the ISO 9660 image
861: with the following command:
862: </p>
863:
864: <pre class="programlisting">mount -F fbk -o ro,type=hsfs /dev/fbk0:output.iso /mnt</pre>
865:
866: <p>
867: and to unmount the CD image:
868: </p>
869:
870: <pre class="programlisting">umount /mnt</pre>
871:
872: <hr>
873: <h3 class="title">Burning the CD</h3>
874: <h4 class="title">
1.49 maya 875: <a name="cdrecord"></a>Using cdrecord (U*nix)</h4>
1.1 dsieger 876: <p>
877: The program <code class="code">cdrecord</code> may be used to burn the CD image to the
878: CD. <code class="code">cdrecord</code> is included in the
1.70 nia 879: <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/sysutils/cdrtools/index.html" target="_top"><code class="filename">sysutils/cdrtools</code></a>
1.1 dsieger 880: package.
881: </p>
882:
883: <p>
884: An example of the use of <code class="code">cdrecord</code> is the following:
885: </p>
886:
887: <pre class="programlisting">cdrecord -v speed=4 dev=/dev/cd1c output.iso</pre>
888:
889: <p>
890: You will need to substitute the correct speed for your CD writer and
891: the correct device for your system (for i386 it would be
892: <code class="code">/dev/cd1d</code>).
893: </p>
894:
895: <h4 class="title">
1.49 maya 896: <a name="winrecord"></a>Under Windows</h4>
1.1 dsieger 897: <p>
898: There are several programs available for Windows which will write an
899: ISO 9660 image to a CD. This section is not an endorsement for any of
900: these programs in particular, but is intended to at least mention some
901: of the alternatives.
902:
903: </p>
1.24 tron 904: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.14 spz 905: <li class="listitem">
1.1 dsieger 906: <p>
1.10 dsieger 907: <a class="ulink" href="http://www.goldenhawk.com/cdrwin.htm" target="_top">CDRWIN</a>.
1.1 dsieger 908: Commercial software that can create bootable (by i386) ISO 9660 images
909: and write them to CD.
910: </p>
911: </li>
1.14 spz 912: <li class="listitem">
1.1 dsieger 913: <p>
1.10 dsieger 914: <a class="ulink" href="http://www.goldenhawk.com/freeware.htm" target="_top">FILE2CD</a>.
1.1 dsieger 915: Freeware program which can write an ISO 9660 image to CD.
916: </p>
917: </li>
1.14 spz 918: <li class="listitem">
1.1 dsieger 919: <p>
1.10 dsieger 920: <a class="ulink" href="http://www.roxio.com/en/products/ecdc/index.jhtml" target="_top">
1.1 dsieger 921: Roxio Easy CD Creator</a>. Commercial software.
922: </p>
923: </li>
1.14 spz 924: <li class="listitem">
1.1 dsieger 925: <p>
1.10 dsieger 926: <a class="ulink" href="http://www.ahead.de/en/index.html" target="_top">Ahead Nero
1.1 dsieger 927: Burning ROM</a>. Commercial software.
928: </p>
929: </li>
1.14 spz 930: <li class="listitem">
1.1 dsieger 931: <p>
1.10 dsieger 932: <a class="ulink" href="ftp://ftp.berlios.de/pub/cdrecord/alpha/win32/" target="_top">CDRECORD</a>.
1.1 dsieger 933: Free software that can create bootable ISO 9660 images and write them to CD.
934: This does not include a graphical interface, it is command line only.
935: This depends on an ASPI driver, which is available
1.10 dsieger 936: <a class="ulink" href="http://www.adaptec.com/worldwide/support/driverdetail.jsp?cat=%2fProduct%2fASPI-4.70&filekey=aspi_v470.exe" target="_top">here</a>.
1.1 dsieger 937: For IDE drives you will need to modify your registry:
938: </p>
939:
940: <pre class="programlisting">
941: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ASPI32]
942: "ErrorControl"=dword:00000001
943: "Start"=dword:00000001
944: "Type"=dword:00000001
945: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ASPI32\Parameters]
946: "ExcludeMiniports"=""</pre>
947:
948: </li>
949: </ul></div>
950: <p>
951: </p>
952:
953: <h4 class="title">
1.49 maya 954: <a name="macrecord"></a>Under Mac OS</h4>
1.1 dsieger 955: <p>
1.10 dsieger 956: On Mac OS X, the program <span class="command"><strong>hdiutil</strong></span> may be used to burn the
1.1 dsieger 957: ISO image to the CD.
958: </p>
959:
960: <p>
1.10 dsieger 961: An example of the use of <span class="command"><strong>hdiutil</strong></span> is the following:
1.1 dsieger 962: </p>
963:
964: <pre class="programlisting">hdiutil burn output.iso -verbose -noverifyburn</pre>
965:
966: <p>
967: You may need to use additional options which are documented in the
1.10 dsieger 968: hdiutil <a class="ulink" href="http://developer.apple.com/documentation/Darwin/Reference/ManPages/man1/hdiutil.1.html" target="_top">documentation</a>.
1.1 dsieger 969: </p>
970:
971: <p>
972: There are also several other programs available for Mac OS which will write an
973: ISO 9660 image to a CD. This section is not an endorsement for any of
974: these programs in particular, but is intended to at least mention some
975: of the alternatives.
976: </p>
977:
1.24 tron 978: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
1.1 dsieger 979: <p>
1.10 dsieger 980: <a class="ulink" href="http://www.roxio.com/en/products/toast/index.jhtml" target="_top">Roxio
1.1 dsieger 981: Toast</a>. Commercial software.
982: </p>
983: </li></ul></div>
1.3 dsieger 984: </div></div></div>
985: <div class="navfoot"></div>
1.12 mishka 986: <div id="footer"><div id="footerContent"><center>
1.39 maya 987: <span class="footfeed"><a href="//www.NetBSD.org/cgi-bin/feedback.cgi">
1.3 dsieger 988: Contact</a> |
1.9 kano 989: </span><span class="footcopy"><a href="../about/disclaimer.html">
1.3 dsieger 990: Disclaimer</a> |
991:
1.77 martin 992: <span class="copyright">Copyright © 1994-2024 The NetBSD Foundation, Inc. </span>ALL RIGHTS RESERVED.<br>NetBSD<sup>®</sup> is a registered trademark of The NetBSD
1.3 dsieger 993: Foundation, Inc.</span>
1.12 mishka 994: </center></div></div>
1.1 dsieger 995: </div></body>
996: </html>
CVSweb <webmaster@jp.NetBSD.org>