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