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