1.\" $NetBSD: boot.8,v 1.10 2003/08/07 10:31:28 agc Exp $ 2.\" 3.\" Copyright (c) 1980, 1991, 1993 4.\" The Regents of the University of California. All rights reserved. 5.\" 6.\" Redistribution and use in source and binary forms, with or without 7.\" modification, are permitted provided that the following conditions 8.\" are met: 9.\" 1. Redistributions of source code must retain the above copyright 10.\" notice, this list of conditions and the following disclaimer. 11.\" 2. Redistributions in binary form must reproduce the above copyright 12.\" notice, this list of conditions and the following disclaimer in the 13.\" documentation and/or other materials provided with the distribution. 14.\" 3. Neither the name of the University nor the names of its contributors 15.\" may be used to endorse or promote products derived from this software 16.\" without specific prior written permission. 17.\" 18.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND 19.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 20.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 21.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE 22.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 23.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 24.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 25.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 26.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 27.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 28.\" SUCH DAMAGE. 29.\" 30.\" @(#)boot_vax.8 8.2 (Berkeley) 4/19/94 31.\" 32.Dd April 19, 1994 33.Dt BOOT 8 vax 34.Os 35.Sh NAME 36.Nm boot 37.Nd 38system bootstrapping procedures 39.Sh DESCRIPTION 40.Sy Power fail and crash recovery 41Normally, the system will reboot itself at power-up or after crashes. 42Provided the auto-restart is enabled on the machine front panel, 43an automatic consistency check of the file systems will be performed, 44and unless this fails, the system will resume multi-user operations. 45.Pp 46.Sy Cold starts 47These are processor-type dependent. 48On an 11/780, there are two floppy files for each disk controller, 49both of which cause boots from unit 0 of the root file system 50of a controller located on mba0 or uba0. 51One gives a single user shell, while the other invokes the multi-user 52automatic reboot. 53Thus these files are 54.Tn HPS 55and 56.Tn HPM 57for the single 58and multi-user boot from 59.Tn MASSBUS 60RP06/RM03/RM05 disks, 61.Tn UPS 62and 63.Tn UPM 64for 65.Tn UNIBUS 66storage module controller and disks 67such as the 68.Tn EMULEX 69SC-21 70and 71.Tn AMPEX 729300 pair, 73.Tn RAS 74and 75.Tn RAM 76to boot from 77.Tn MSCP 78controllers and disks such as the RA81, 79or 80.Tn HKS 81and 82.Tn HKM 83for RK07 disks. 84There is also a script for booting from the default device, 85which is normally a copy of one of the standard multi-user boot scripts, 86but which may be modified to perform other actions 87or to boot from a different unit. 88The situation on the 8600 is similar, with scripts loaded from the console RL02. 89.Pp 90Giving the command 91.Pp 92.Dl \*[Gt]\*[Gt]\*[Gt]BOOT HPM 93.Pp 94would boot the system from (e.g.) an RP06 and run the automatic consistency 95check as described in 96.Xr fsck 8 . 97(Note that it may 98be necessary to type control-P 99and halt the processor 100to gain the attention of the 101.Tn LSI-11 102before getting the \*[Gt]\*[Gt]\*[Gt] prompt.) 103The command 104.Pp 105.Dl \*[Gt]\*[Gt]\*[Gt]BOOT ANY 106.Pp 107invokes a version of the boot program in a way which allows you to 108specify any system as the system to be booted. 109It reads from the console a device specification (see below) followed 110immediately by a pathname. 111.Pp 112The scripts may be modified for local configuration if necessary. 113The flags are placed in register 11 (as defined in 114.Aq Pa sys/reboot.h ) . 115The boot device is specified in register 10. 116The encoding of this register is also defined in 117.Aq Pa sys/reboot.h . 118The current encoding has a historical basis, and is shown in the following 119table: 120.Pp 121.Bd -unfilled -offset indent -compact 122bits usage 1230-7 boot device type (the device major number) 1248-15 disk partition 12516-19 drive unit 12620-23 controller number 12724-27 adaptor number (UNIBUS or MASSBUS as appropriate) 128.Ed 129.Pp 130The adaptor number corresponds to the normal configuration on the 11/750, 131and to the order in which adaptors are found on the 11/780 and 8600 132(generally the same as the numbers used by 133.Ux ) . 134.Pp 135On an 11/750, the reset button will boot from the device 136selected by the front panel boot device switch. 137In systems with RK07's, position B normally selects the RK07 for boot. 138This will boot multi-user. 139To boot from RK07 with boot flags you may specify 140.Pp 141.Bd -unfilled -offset indent -compact 142.Li \&\*[Gt]\*[Gt]\*[Gt]B/ Ns Fl n No DMA0 143.Ed 144.Pp 145where, giving a 146.Ar n 147of 1 causes the boot program 148to ask for the name of the system to be bootstrapped, 149giving a 150.Ar n 151of 2 causes the boot program to come up single 152user, and a 153.Ar n 154of 3 causes both of these actions to occur. 155The ``DM'' specifies RK07, the ``A'' represents the adaptor number 156.Pf ( Tn UNIBUS 157or 158.Tn MASSBUS ) , 159and the ``0'' is the drive unit number. 160Other disk types which may be used are DB 161.Pq Tn MASSBUS , 162DD (TU58), 163and DU 164.Pf ( Tn UDA-50/RA 165disk). 166A non-zero disk partition can be used by adding (partition times 1000 hex) 167to 168.Ar n . 169.Pp 170The boot procedure on the Micro 171.Tn VAX 172II 173is similar. 174A switch on the back panel sets the power-up action 175to autoboot or to halt. 176When halted, the processor may be booted using the same syntax 177as on the 11/750. 178.Pp 179The 11/750 boot procedure uses the boot ROMs to load block 0 off of 180the specified device. The /usr/mdec directory contains a number 181of bootstrap programs for the various disks which should be placed 182in a new pack by 183.Xr disklabel 8 . 184Similarly, the Micro 185.Tn VAX 186II boot procedure loads a boot parameter block 187from block 0 of the disk. 188The 189.Ic rdboot 190.Dq bootstrap 191contains the correct parameters for an 192.Tn MSCP 193disk such 194as the RD53. 195.Pp 196On any processor, the 197.Em boot 198program 199finds the corresponding file on the given device 200.Pf ( Pa netbsd 201by default), loads that file 202into memory location zero, and starts the program at the entry address 203specified in the program header (after clearing off the high bit 204of the specified entry address). 205.Pp 206The file specifications used with 207.Dq BOOT ANY 208or 209.Dq \&B/3 210are of the form: 211.Pp 212.Dl device(adaptor,controller,unit,minor) 213.Pp 214where 215.Ar device 216is the type of the device to be searched, 217.Ar adaptor 218is the 219.Tn UNIBUS 220or 221.Tn MASSBUS 222number of the adaptor to which the device is attached, 223.Ar controller 224is the unit number of the controller or 225.Tn MASSBUS 226tape formatter on that adaptor, 227.Ar unit 228is the unit number of the disk or transport slave unit of the tape, 229and 230.Ar minor 231is the disk partition or tape file number. 232Leading adaptor or controller numbers default to 0. 233Normal line editing characters can be used when typing the file specification. 234The following list of supported devices may vary from installation to 235installation: 236.Pp 237.Bd -unfilled -offset indent -compact 238hp MASSBUS disk drive 239up UNIBUS storage module drive 240ht TE16,TU45,TU77 on MASSBUS 241kra storage module on a KDB50 242mt TU78 on MASSBUS 243hk RK07 on UNIBUS 244ra storage module on a MSCP-compatible UNIBUS controller 245rb storage module on a 730 IDC 246rl RL02 on UNIBUS 247tm TM11 emulation tape drives on UNIBUS 248tms TMSCP-compatible tape 249ts TS11 on UNIBUS 250ut UNIBUS TU45 emulator 251.Ed 252.Pp 253For example, 254to boot from a file system which starts at cylinder 0 255of unit 0 of a 256.Tn MASSBUS 257disk, type 258.Ql hp(0,0)netbsd 259to the boot prompt; 260.Ql hp(2,0,1,0)netbsd 261would specify drive 1 on 262.Tn MASSBUS 263adaptor 2; 264.Ql up(0,0)netbsd 265would specify a 266.Tn UNIBUS 267drive, 268.Ql hk(0,0)netbsd 269would specify 270an RK07 disk drive, 271.Ql ra(1,0,0,0)netbsd 272would specify a 273.Tn UDA50 274disk drive on a second 275.Tn UNIBUS , 276and 277.Ql rb(0,0)netbsd 278would specify a 279disk on a 730 280.Tn IDC . 281For tapes, the minor device number gives a file offset; 282.Ql mt(1,2,3,4) 283would specify the fifth file on slave 3 of the formatter 284at 285.Ql drive 2862 on mba 1. 287.Pp 288On an 11/750 with patchable control store, 289microcode patches will be installed by 290.Em boot 291if the file 292.Pa psc750.bin 293exists in the root of the filesystem from which the system is booted. 294.Pp 295In an emergency, the bootstrap methods described in the paper 296.%T Installing and Operating 4.3bsd 297can be used to boot from a distribution tape. 298.Sh FILES 299.Bl -tag -width /usr/mdec/xxboot -compact 300.It Pa /netbsd 301system code 302.It Pa /boot 303system bootstrap 304.It Pa /usr/mdec/xxboot 305sector-0 boot block for 750, xx is disk type 306.It Pa /usr/mdec/bootxx 307second-stage boot for 750, xx is disk type 308.It Pa /pcs750.bin 309microcode patch file on 750 310.El 311.Sh SEE ALSO 312.Xr arff 8 , 313.Xr halt 8 , 314.Xr reboot 8 , 315.Xr shutdown 8 316.Sh HISTORY 317The 318.Nm 319command appeared in 320.Bx 4.0 . 321