diff options
Diffstat (limited to 'static/netbsd/man8/man8.x68k/boot.8 3.html')
| -rw-r--r-- | static/netbsd/man8/man8.x68k/boot.8 3.html | 193 |
1 files changed, 0 insertions, 193 deletions
diff --git a/static/netbsd/man8/man8.x68k/boot.8 3.html b/static/netbsd/man8/man8.x68k/boot.8 3.html deleted file mode 100644 index f069b3f4..00000000 --- a/static/netbsd/man8/man8.x68k/boot.8 3.html +++ /dev/null @@ -1,193 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">BOOT(8)</td> - <td class="head-vol">System Manager's Manual (x68k)</td> - <td class="head-rtitle">BOOT(8)</td> - </tr> -</table> -<div class="manual-text"> -<section class="Sh"> -<h1 class="Sh" id="NAME"><a class="permalink" href="#NAME">NAME</a></h1> -<p class="Pp"><code class="Nm">boot</code> — <span class="Nd">system - bootstrapping procedures</span></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<section class="Ss"> -<h2 class="Ss" id="Power_fail_and_crash_recovery"><a class="permalink" href="#Power_fail_and_crash_recovery">Power - fail and crash recovery</a></h2> -<p class="Pp">Normally, the system will reboot itself at power-up or after - crashes. An automatic consistency check of the file systems will be - performed, and unless this fails, the system will resume multi-user - operations.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Cold_starts"><a class="permalink" href="#Cold_starts">Cold - starts</a></h2> -<p class="Pp">The X68000/X68030 system boots from the device which is determined - by the configuration of battery-backuped SRAM. By default, the boot ROM - attempts to boot from floppy disk drives (from 0 to 3) first, and then - attempts to boot from hard disk (SASI or SCSI). On the - <span class="Ux">NetBSD</span>/x68k, booting from SCSI disks (sd??) and 2HD - floppy disks (fd?a, fd?c) is currently supported.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Bootstrapping_from_a_floppy"><a class="permalink" href="#Bootstrapping_from_a_floppy">Bootstrapping - from a floppy</a></h2> -<p class="Pp">When the floppy disk is selected as the boot device, the initial - program loader of the IOCS (firmware) reads the - <span class="Pa">fdboot_ufs</span> program at the top of the disk, and then - the fdboot_ufs program loads the <span class="Pa">/boot</span> program from - the FFS or LFS file system. Normally, the <span class="Pa">/boot</span> - program then loads the <span class="Ux">NetBSD</span> kernel - <span class="Pa">/netbsd</span> from the same floppy. In addition, the - <span class="Pa">/boot</span> program has abilities to uncompress gzip'ed - kernels, to read the kernel from other disks of other file systems etc (see - below).</p> -<p class="Pp">For floppy disks, <span class="Pa">fdboot_ustar</span> is also - provided to read large kernels which do not fit one a single floppy.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Bootstrapping_from_a_SCSI_hard_disk"><a class="permalink" href="#Bootstrapping_from_a_SCSI_hard_disk">Bootstrapping - from a SCSI hard disk</a></h2> -<p class="Pp">When a SCSI hard disk is selected as the boot device, the initial - program loader on the SCSI host adapter's ROM reads the operating - system-independent IPL menu program at the top of the disk. The IPL menu - program recognizes the partition table, and selects the partition to read - the operating system kernel. During this phase, when the HELP key on the - keyboard is pressed, the IPL menu program displays the partition menu of - that disk to prompt the user to select the boot partition (although the - <span class="Ux">NetBSD</span> implementation of the IPL menu, - <span class="Pa">/usr/mdec/mboot</span>, does not have this - functionality).</p> -<p class="Pp">Next, the IPL menu reads the OS-dependent boot program from the - top of the selected partition. For <span class="Ux">NetBSD</span> FFS/LFS - file systems <span class="Pa">sdboot_ufs</span> is used. The - <span class="Pa">sdboot_ufs</span> program then loads the - <span class="Pa">/boot</span> program from that partition.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Normal_Operation"><a class="permalink" href="#Normal_Operation">Normal - Operation</a></h2> -<p class="Pp">Once running, a banner similar to the following will appear:</p> -<div class="Bd Pp Bd-indent Li"> -<pre>NetBSD Multi-boot, Revision 1.1 -(user@buildhost, builddate) -Press return to boot now, any other key for boot menu -booting sd0a:netbsd - starting in 5</pre> -</div> -<p class="Pp">After a countdown, the system image listed will be loaded. (In the - example above, it will be - “<code class="Li">sd0a:netbsd</code>” which is the file - <code class="Nm">netbsd</code> on partition “a” of the - <span class="Ux">NetBSD</span> SCSI hard disk of ID 0. Pressing a key within - the time limit will enter interactive mode.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Interactive_mode"><a class="permalink" href="#Interactive_mode">Interactive - mode</a></h2> -<p class="Pp">In interactive mode, the boot loader will present a prompt, - allowing input of these commands:</p> -<div class="Bd-indent"> -<dl class="Bl-tag"> - <dt id="boot"><a class="permalink" href="#boot"><code class="Ic">boot</code></a> - [<var class="Ar">device</var>:][<var class="Ar">filename</var>] - [<code class="Fl">-adqsv</code>]</dt> - <dd>The default <var class="Ar">device</var> will be set to the disk that the - boot loader was loaded from. To boot from an alternate disk, the full name - of the device should be given at the prompt. <var class="Ar">device</var> - is of the form - <var class="Ar">xd</var>[<var class="Ar">N</var>[<var class="Ar">x</var>]] - where <var class="Ar">xd</var> is the device from which to boot, - <var class="Ar">N</var> is the unit number, and <var class="Ar">x</var> is - the partition letter. - <p class="Pp">The following list of supported devices may vary from - installation to installation:</p> - <p class="Pp"></p> - <dl class="Bl-hang Bl-compact"> - <dt>sd</dt> - <dd>SCSI disks on a controller recognized by the IOCS. The unit number is - the SCSI ID.</dd> - <dt>fd</dt> - <dd>Floppy drives as numbered by the IOCS.</dd> - </dl> - <p class="Pp">The default <var class="Ar">filename</var> is - <span class="Pa">netbsd</span>; if the boot loader fails to successfully - open that image, it then tries <span class="Pa">netbsd.gz</span> - (expected to be a kernel image compressed by <a class="Xr">gzip(1)</a>). - Alternate system images can be loaded by just specifying the name of the - image.</p> - <p class="Pp">Options are:</p> - <dl class="Bl-tag"> - <dt id="a"><a class="permalink" href="#a"><code class="Fl">-a</code></a></dt> - <dd>Prompt for the root file system device, the system crash dump device, - and the path to <a class="Xr">init(8)</a>.</dd> - <dt id="d"><a class="permalink" href="#d"><code class="Fl">-d</code></a></dt> - <dd>Bring the system up in debug mode. Here it waits for a kernel debugger - connect; see <a class="Xr">ddb(4)</a>.</dd> - <dt id="q"><a class="permalink" href="#q"><code class="Fl">-q</code></a></dt> - <dd>Boot the system in quiet mode.</dd> - <dt id="s"><a class="permalink" href="#s"><code class="Fl">-s</code></a></dt> - <dd>Bring the system up in single-user mode.</dd> - <dt id="v"><a class="permalink" href="#v"><code class="Fl">-v</code></a></dt> - <dd>Boot the system in verbose mode.</dd> - </dl> - </dd> - <dt id="help"><a class="permalink" href="#help"><code class="Ic">help</code></a></dt> - <dd>Print an overview about commands and arguments.</dd> - <dt id="ls"><a class="permalink" href="#ls"><code class="Ic">ls</code></a> - [<span class="Pa">path</span>]</dt> - <dd>Print a directory listing of <span class="Pa">path</span>, containing - inode number, filename and file type. <span class="Pa">path</span> can - contain a device specification.</dd> - <dt id="halt"><a class="permalink" href="#halt"><code class="Ic">halt</code></a></dt> - <dd>Reboot the system.</dd> -</dl> -</div> -</section> -<section class="Ss"> -<h2 class="Ss" id="Model-specific_notes"><a class="permalink" href="#Model-specific_notes">Model-specific - notes</a></h2> -<p class="Pp">Note for X68030+MC68030 systems: Nothing special to be attended - to; you can boot <span class="Ux">NetBSD</span> just like as other operating - systems such as Human68k and OS-9.</p> -<p class="Pp">Note for X68030/040turbo(68040 accelerator by BEEPs) systems: - <span class="Ux">NetBSD</span> can boot under 040 mode. It can also boot - under 030 mode if you have MC68030 on the board.</p> -<p class="Pp">Note for X68000/Xellent30(68030 accelerator by TSR)+MC68030 - systems: In order to boot <span class="Ux">NetBSD</span>, you must choose - 030 mode by using <span class="Pa">CH30.SYS</span>, which must reside in the - battery-backuped SRAM.</p> -<p class="Pp">Note for X68000/Jupiter-X(68040/060 accelerator by FTZ-net) - systems: The system must be in 040/060 processor mode.</p> -</section> -</section> -<section class="Sh"> -<h1 class="Sh" id="FILES"><a class="permalink" href="#FILES">FILES</a></h1> -<dl class="Bl-tag Bl-compact"> - <dt><span class="Pa">/netbsd</span></dt> - <dd>system code</dd> - <dt><span class="Pa">/netbsd.gz</span></dt> - <dd>gzip-compressed system code</dd> - <dt><span class="Pa">/usr/mdec/xxboot_ufs</span></dt> - <dd>boot block (read by installboot), xx is disktype</dd> - <dt><span class="Pa">/usr/mdec/boot</span></dt> - <dd>source of /boot (can be just copied to the root directory)</dd> - <dt><span class="Pa">/boot</span></dt> - <dd>main part of the boot program</dd> -</dl> -</section> -<section class="Sh"> -<h1 class="Sh" id="SEE_ALSO"><a class="permalink" href="#SEE_ALSO">SEE - ALSO</a></h1> -<p class="Pp"><a class="Xr">reboot(2)</a>, <a class="Xr">disklabel(8)</a>, - <a class="Xr">halt(8)</a>, <a class="Xr">reboot(8)</a>, - <a class="Xr">shutdown(8)</a></p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">August 16, 2014</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> |