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