1.\" Copyright (c) 1980, 1991, 1993 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" %sccs.include.redist.man% 5.\" 6.\" @(#)boot_vax.8 8.2 (Berkeley) 04/19/94 7.\" 8.Dd 9.Dt BOOT 8 vax 10.Os 11.Sh NAME 12.Nm boot 13.Nd 14system bootstrapping procedures 15.Sh DESCRIPTION 16.Sy Power fail and crash recovery. 17Normally, the system will reboot itself at power-up or after crashes. 18Provided the auto-restart is enabled on the machine front panel, 19an automatic consistency check of the file systems will be performed, 20and unless this fails, the system will resume multi-user operations. 21.Pp 22.Sy Cold starts. 23These are processor-type dependent. 24On an 11/780, there are two floppy files for each disk controller, 25both of which cause boots from unit 0 of the root file system 26of a controller located on mba0 or uba0. 27One gives a single user shell, while the other invokes the multi-user 28automatic reboot. 29Thus these files are 30.Tn HPS 31and 32.Tn HPM 33for the single 34and multi-user boot from 35.Tn MASSBUS 36RP06/RM03/RM05 disks, 37.Tn UPS 38and 39.Tn UPM 40for 41.Tn UNIBUS 42storage module controller and disks 43such as the 44.Tn EMULEX 45SC-21 46and 47.Tn AMPEX 489300 pair, 49.Tn RAS 50and 51.Tn RAM 52to boot from 53.Tn MSCP 54controllers and disks such as the RA81, 55or 56.Tn HKS 57and 58.Tn HKM 59for RK07 disks. 60There is also a script for booting from the default device, 61which is normally a copy of one of the standard multi-user boot scripts, 62but which may be modified to perform other actions 63or to boot from a different unit. 64The situation on the 8600 is similar, with scripts loaded from the console RL02. 65.Pp 66Giving the command 67.Pp 68.Dl >>>BOOT HPM 69.Pp 70would boot the system from (e.g.) an RP06 and run the automatic consistency 71check as described in 72.Xr fsck 8 . 73(Note that it may 74be necessary to type control-P 75and halt the processor 76to gain the attention of the 77.Tn LSI-11 78before getting the >>> prompt.) 79The command 80.Pp 81.Dl >>>BOOT ANY 82.Pp 83invokes a version of the boot program in a way which allows you to 84specify any system as the system to be booted. 85It reads from the console a device specification (see below) followed 86immediately by a pathname. 87.Pp 88The scripts may be modified for local configuration if necessary. 89The flags are placed in register 11 (as defined in 90.Aq Pa sys/reboot.h ) . 91The boot device is specified in register 10. 92The encoding of this register is also defined in 93.Aq Pa sys/reboot.h . 94The current encoding has a historical basis, and is shown in the following 95table: 96.Pp 97.Bd -unfilled -offset indent -compact 98bits usage 990-7 boot device type (the device major number) 1008-15 disk partition 10116-19 drive unit 10220-23 controller number 10324-27 adaptor number (UNIBUS or MASSBUS as appropriate) 104.Ed 105.Pp 106The adaptor number corresponds to the normal configuration on the 11/750, 107and to the order in which adaptors are found on the 11/780 and 8600 108(generally the same as the numbers used by 109.Tn UNIX ) . 110.Pp 111On an 11/750, the reset button will boot from the device 112selected by the front panel boot device switch. In systems 113with RK07's, position B normally selects the RK07 for boot. 114This will boot multi-user. To boot from RK07 with boot flags you 115may specify 116.Pp 117.Bd -unfilled -offset indent -compact 118.Li \&>>>B/ Ns Fl n No DMA0 119.Ed 120.Pp 121where, giving a 122.Ar n 123of 1 causes the boot program 124to ask for the name of the system to be bootstrapped, 125giving a 126.Ar n 127of 2 causes the boot program to come up single 128user, and a 129.Ar n 130of 3 causes both of these actions to occur. 131The ``DM'' specifies RK07, the ``A'' represents the adaptor number 132.Pf ( Tn UNIBUS 133or 134.Tn MASSBUS ) , 135and the ``0'' is the drive unit number. 136Other disk types which may be used are DB 137.Pq Tn MASSBUS , 138DD (TU58), 139and DU 140.Pf ( Tn UDA-50/RA 141disk). 142A non-zero disk partition can be used by adding (partition times 1000 hex) 143to 144.Ar n . 145.Pp 146The boot procedure on the Micro 147.Tn VAX 148II 149is similar. 150A switch on the back panel sets the power-up action 151to autoboot or to halt. 152When halted, the processor may be booted using the same syntax 153as on the 11/750. 154.Pp 155The 11/750 boot procedure uses the boot roms to load block 0 off of 156the specified device. The /usr/mdec directory contains a number 157of bootstrap programs for the various disks which should be placed 158in a new pack by 159.Xr disklabel 8 . 160Similarly, the Micro 161.Tn VAX 162II boot procedure loads a boot parameter block 163from block 0 of the disk. 164The 165.Xr rdboot 166.Dq bootstrap 167contains the correct parameters for an 168.Tn MSCP 169disk such 170as the RD53. 171.Pp 172On any processor, the 173.Em boot 174program 175finds the corresponding file on the given device 176.Pf ( Pa vmunix 177by default), loads that file 178into memory location zero, and starts the program at the entry address 179specified in the program header (after clearing off the high bit 180of the specified entry address). 181.Pp 182The file specifications used with 183.Dq BOOT ANY 184or 185.Dq \&B/3 186are of the form: 187.Pp 188.Dl device(adaptor,controller,unit,minor) 189.Pp 190where 191.Ar device 192is the type of the device to be searched, 193.Ar adaptor 194is the 195.Tn UNIBUS 196or 197.Tn MASSBUS 198number of the adaptor to which the device is attached, 199.Ar controller 200is the unit number of the controller or 201.Tn MASSBUS 202tape formatter on that adaptor, 203.Ar unit 204is the unit number of the disk or transport slave unit of the tape, 205and 206.Ar minor 207is the disk partition or tape file number. 208Leading adaptor or controller numbers default to 0. 209Normal line editing characters can be used when typing the file specification. 210The following list of supported devices may vary from installation to 211installation: 212.Pp 213.Bd -unfilled -offset indent -compact 214hp MASSBUS disk drive 215up UNIBUS storage module drive 216ht TE16,TU45,TU77 on MASSBUS 217kra storage module on a KDB50 218mt TU78 on MASSBUS 219hk RK07 on UNIBUS 220ra storage module on a MSCP-compatible UNIBUS controller 221rb storage module on a 730 IDC 222rl RL02 on UNIBUS 223tm TM11 emulation tape drives on UNIBUS 224tms TMSCP-compatible tape 225ts TS11 on UNIBUS 226ut UNIBUS TU45 emulator 227.Ed 228.Pp 229For example, 230to boot from a file system which starts at cylinder 0 231of unit 0 of a 232.Tn MASSBUS 233disk, type 234.Ql hp(0,0)vmunix 235to the boot prompt; 236.Ql hp(2,0,1,0)vmunix 237would specify drive 1 on 238.Tn MASSBUS 239adaptor 2; 240.Ql up(0,0)vmunix 241would specify a 242.Tn UNIBUS 243drive, 244.Ql hk(0,0)vmunix 245would specify 246an RK07 disk drive, 247.Ql ra(1,0,0,0)vmunix 248would specify a 249.Tn UDA50 250disk drive on a second 251.Tn UNIBUS , 252and 253.Ql rb(0,0)vmunix 254would specify a 255disk on a 730 256.Tn IDC . 257For tapes, the minor device number gives a file offset; 258.Ql mt(1,2,3,4) 259would specify the fifth file on slave 3 of the formatter 260at 261.Ql drive 2622 on mba 1. 263.Pp 264On an 11/750 with patchable control store, 265microcode patches will be installed by 266.Em boot 267if the file 268.Pa psc750.bin 269exists in the root of the filesystem from which the system is booted. 270.Pp 271In an emergency, the bootstrap methods described in the paper 272.%T Installing and Operating 4.3bsd 273can be used to boot from a distribution tape. 274.Sh FILES 275.Bl -tag -width /usr/mdec/xxboot -compact 276.It Pa /vmunix 277system code 278.It Pa /boot 279system bootstrap 280.It Pa /usr/mdec/xxboot 281sector-0 boot block for 750, xx is disk type 282.It Pa /usr/mdec/bootxx 283second-stage boot for 750, xx is disk type 284.It Pa /pcs750.bin 285microcode patch file on 750 286.El 287.Sh SEE ALSO 288.Xr arff 8 , 289.Xr halt 8 , 290.Xr reboot 8 , 291.Xr shutdown 8 292.Sh HISTORY 293The 294.Nm 295command appeared in 296.Bx 4.0 . 297