diff options
Diffstat (limited to 'static/netbsd/man8/man8.vax/boot.8 3.html')
| -rw-r--r-- | static/netbsd/man8/man8.vax/boot.8 3.html | 190 |
1 files changed, 0 insertions, 190 deletions
diff --git a/static/netbsd/man8/man8.vax/boot.8 3.html b/static/netbsd/man8/man8.vax/boot.8 3.html deleted file mode 100644 index 4b27750d..00000000 --- a/static/netbsd/man8/man8.vax/boot.8 3.html +++ /dev/null @@ -1,190 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">BOOT(8)</td> - <td class="head-vol">System Manager's Manual (vax)</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. Provided the auto-restart is enabled on the machine front panel, 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">These are processor-type dependent. On an 11/780, there are two - floppy files for each disk controller, both of which cause boots from unit 0 - of the root file system of a controller located on mba0 or uba0. One gives a - single user shell, while the other invokes the multi-user automatic reboot. - Thus these files are HPS and HPM for the single and multi-user boot from - MASSBUS RP06/RM03/RM05 disks, UPS and UPM for UNIBUS storage module - controller and disks such as the EMULEX SC-21 and AMPEX 9300 pair, RAS and - RAM to boot from MSCP controllers and disks such as the RA81, or HKS and HKM - for RK07 disks. There is also a script for booting from the default device, - which is normally a copy of one of the standard multi-user boot scripts, but - which may be modified to perform other actions or to boot from a different - unit. The situation on the 8600 is similar, with scripts loaded from the - console RL02.</p> -<p class="Pp">Giving the command</p> -<p class="Pp"></p> -<div class="Bd Bd-indent"><code class="Li">>>>BOOT HPM</code></div> -<p class="Pp">would boot the system from (e.g.) an RP06 and run the automatic - consistency check as described in <a class="Xr">fsck(8)</a>. (Note that it - may be necessary to type control-P and halt the processor to gain the - attention of the LSI-11 before getting the >>> prompt.) The - command</p> -<p class="Pp"></p> -<div class="Bd Bd-indent"><code class="Li">>>>BOOT ANY</code></div> -<p class="Pp">invokes a version of the boot program in a way which allows you to - specify any system as the system to be booted. It reads from the console a - device specification (see below) followed immediately by a pathname.</p> -<p class="Pp">The scripts may be modified for local configuration if necessary. - The flags are placed in register 11 (as defined in - <code class="In"><<a class="In">sys/reboot.h</a>></code>). The boot - device is specified in register 10. The encoding of this register is also - defined in <code class="In"><<a class="In">sys/reboot.h</a>></code>. - The current encoding has a historical basis, and is shown in the following - table:</p> -<p class="Pp"></p> -<div class="Bd Bd-indent"> -<pre>bits usage -0-7 boot device type (the device major number) -8-15 disk partition -16-19 drive unit -20-23 controller number -24-27 adaptor number (UNIBUS or MASSBUS as appropriate)</pre> -</div> -<p class="Pp">The adaptor number corresponds to the normal configuration on the - 11/750, and to the order in which adaptors are found on the 11/780 and 8600 - (generally the same as the numbers used by - <span class="Ux">UNIX</span>).</p> -<p class="Pp">On an 11/750, the reset button will boot from the device selected - by the front panel boot device switch. In systems with RK07's, position B - normally selects the RK07 for boot. This will boot multi-user. To boot from - RK07 with boot flags you may specify</p> -<p class="Pp"></p> -<div class="Bd Bd-indent"> -<pre><code class="Li">>>>B/</code><code class="Fl">-n</code> <span class="No">DMA0</span></pre> -</div> -<p class="Pp">where, giving a <var class="Ar">n</var> of 1 causes the boot - program to ask for the name of the system to be bootstrapped, giving a - <var class="Ar">n</var> of 2 causes the boot program to come up single user, - and a <var class="Ar">n</var> of 3 causes both of these actions to occur. - The ``DM'' specifies RK07, the ``A'' represents the adaptor number (UNIBUS - or MASSBUS), and the ``0'' is the drive unit number. Other disk types which - may be used are DB (MASSBUS), DD (TU58), and DU (UDA-50/RA disk). A non-zero - disk partition can be used by adding (partition times 1000 hex) to - <var class="Ar">n</var>.</p> -<p class="Pp">The boot procedure on the Micro VAX II is similar. A switch on the - back panel sets the power-up action to autoboot or to halt. When halted, the - processor may be booted using the same syntax as on the 11/750.</p> -<p class="Pp">The 11/750 boot procedure uses the boot ROMs to load block 0 off - of the specified device. The <span class="Pa">/usr/mdec</span> directory - contains a number of bootstrap programs for the various disks which should - be placed in a new pack by <a class="Xr">disklabel(8)</a>. Similarly, the - Micro VAX II boot procedure loads a boot parameter block from block 0 of the - disk. The <code class="Ic">rdboot</code> “bootstrap” contains - the correct parameters for an MSCP disk such as the RD53.</p> -<p class="Pp">On any processor, the <i class="Em">boot</i> program finds the - corresponding file on the given device (<span class="Pa">netbsd</span> by - default), loads that file into memory location zero, and starts the program - at the entry address specified in the program header (after clearing off the - high bit of the specified entry address).</p> -<p class="Pp">The file specifications used with “BOOT ANY” or - “B/3” are of the form:</p> -<p class="Pp"></p> -<div class="Bd - Bd-indent"><code class="Li">device(adaptor,controller,unit,minor)</code></div> -<p class="Pp">where <var class="Ar">device</var> is the type of the device to be - searched, <var class="Ar">adaptor</var> is the UNIBUS or MASSBUS number of - the adaptor to which the device is attached, - <var class="Ar">controller</var> is the unit number of the controller or - MASSBUS tape formatter on that adaptor, <var class="Ar">unit</var> is the - unit number of the disk or transport slave unit of the tape, and - <var class="Ar">minor</var> is the disk partition or tape file number. - Leading adaptor or controller numbers default to 0. Normal line editing - characters can be used when typing the file specification. The following - list of supported devices may vary from installation to installation:</p> -<p class="Pp"></p> -<div class="Bd Bd-indent"> -<pre>hp MASSBUS disk drive -up UNIBUS storage module drive -ht TE16,TU45,TU77 on MASSBUS -kra storage module on a KDB50 -mt TU78 on MASSBUS -hk RK07 on UNIBUS -ra storage module on a MSCP-compatible UNIBUS controller -rb storage module on a 730 IDC -rl RL02 on UNIBUS -tm TM11 emulation tape drives on UNIBUS -tms TMSCP-compatible tape -ts TS11 on UNIBUS -ut UNIBUS TU45 emulator</pre> -</div> -<p class="Pp">For example, to boot from a file system which starts at cylinder 0 - of unit 0 of a MASSBUS disk, type - ‘<code class="Li">hp(0,0)netbsd</code>’ to the boot prompt; - ‘<code class="Li">hp(2,0,1,0)netbsd</code>’ would specify - drive 1 on MASSBUS adaptor 2; - ‘<code class="Li">up(0,0)netbsd</code>’ would specify a UNIBUS - drive, ‘<code class="Li">hk(0,0)netbsd</code>’ would specify - an RK07 disk drive, - ‘<code class="Li">ra(1,0,0,0)netbsd</code>’ would specify a - UDA50 disk drive on a second UNIBUS, and - ‘<code class="Li">rb(0,0)netbsd</code>’ would specify a disk - on a 730 IDC. For tapes, the minor device number gives a file offset; - ‘<code class="Li">mt(1,2,3,4)</code>’ would specify the fifth - file on slave 3 of the formatter at - ‘<code class="Li">drive</code>’ 2 on mba 1.</p> -<p class="Pp">On an 11/750 with patchable control store, microcode patches will - be installed by <i class="Em">boot</i> if the file - <span class="Pa">pcs750.bin</span> exists in the root of the filesystem from - which the system is booted.</p> -<p class="Pp">In an emergency, the bootstrap methods described in the paper - <span class="RsT">Installing and Operating 4.3bsd</span> can be used to boot - from a distribution tape.</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">/boot</span></dt> - <dd>system bootstrap</dd> - <dt><span class="Pa">/usr/mdec/xxboot</span></dt> - <dd>sector 0-15 boot block</dd> - <dt><span class="Pa">/pcs750.bin</span></dt> - <dd>microcode patch file on 750</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">arff(8)</a>, <a class="Xr">halt(8)</a>, - <a class="Xr">reboot(8)</a>, <a class="Xr">shutdown(8)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1> -<p class="Pp">The <code class="Nm">boot</code> command appeared in - <span class="Ux">4.0BSD</span>.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">April 19, 1994</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> |