| 1 | .\" Copyright (c) 1980 Regents of the University of California. |
| 2 | .\" All rights reserved. The Berkeley software License Agreement |
| 3 | .\" specifies the terms and conditions for redistribution. |
| 4 | .\" |
| 5 | .\" @(#)boot_vax.8 6.2 (Berkeley) %G% |
| 6 | .\" |
| 7 | .TH REBOOT 8 "" |
| 8 | .UC 4 |
| 9 | .SH NAME |
| 10 | reboot \- UNIX bootstrapping procedures |
| 11 | .SH SYNOPSIS |
| 12 | .B /etc/reboot |
| 13 | [ |
| 14 | .B \-n |
| 15 | ] [ |
| 16 | .B \-q |
| 17 | ] |
| 18 | .SH DESCRIPTION |
| 19 | .PP |
| 20 | UNIX is started by placing it in memory |
| 21 | at location zero and transferring to the entry point. |
| 22 | Since the system is not reenterable, |
| 23 | it is necessary to read it in from disk or tape |
| 24 | each time it is to be bootstrapped. |
| 25 | .PP |
| 26 | .B Rebooting a running system. |
| 27 | When a UNIX is running and a reboot is desired, |
| 28 | .IR shutdown (8) |
| 29 | is normally used. |
| 30 | If there are no users then |
| 31 | .B /etc/reboot |
| 32 | can be used. |
| 33 | Reboot causes the disks to be synced, and then a multi-user |
| 34 | reboot (as described below) is initiated. This causes a system to be |
| 35 | booted and an automatic disk check to be performed. If all this succeeds |
| 36 | without incident, the system is then brought up for many users. |
| 37 | .PP |
| 38 | Options to reboot are: |
| 39 | .TP |
| 40 | .B \-n |
| 41 | option avoids the sync. It can be used if a disk or the processor |
| 42 | is on fire. |
| 43 | .TP |
| 44 | .B \-q |
| 45 | reboots quickly and ungracefully, without shutting down running |
| 46 | processes first. |
| 47 | .PP |
| 48 | .B "Power fail and crash recovery." |
| 49 | Normally, the system will reboot itself at power-up or after crashes. |
| 50 | Provided the auto-restart is enabled on the machine front panel, |
| 51 | an automatic consistency check of the file systems will be performed, |
| 52 | and unless this fails, the system will resume multi-user operations. |
| 53 | .PP |
| 54 | .B Cold starts. |
| 55 | These are processor type dependent. |
| 56 | On an 11/780, there are two floppy files for each disk controller, |
| 57 | both of which cause boots from unit 0 of the root file system |
| 58 | of a controller located on mba0 or uba0. |
| 59 | One gives a single user shell, while the other invokes the multi-user |
| 60 | automatic reboot. Thus these files are HPS and HPM for the single |
| 61 | and multi-user boot from MASSBUS RP06/RM03/RM05 disks, |
| 62 | UPS and UPM for UNIBUS storage module controller and disks |
| 63 | such as the EMULEX SC-21 |
| 64 | and AMPEX 9300 pair, or HKS and HKM for RK07 disks. |
| 65 | There is also a script for booting from the default device, |
| 66 | which is normally a copy of one of the standard multi-user boot scripts, |
| 67 | but which may be modified to perform other actions |
| 68 | or to boot from a different unit. |
| 69 | The situation on the 8600 is similar, with scripts loaded from the console RL02. |
| 70 | .PP |
| 71 | Giving the command |
| 72 | .IP |
| 73 | >>>BOOT HPM |
| 74 | .LP |
| 75 | Would boot the system from (e.g.) an RP06 and run the automatic consistency |
| 76 | check as described in |
| 77 | .IR fsck (8). |
| 78 | (Note that it may |
| 79 | be necessary to type control-P |
| 80 | and halt the processor |
| 81 | to gain the attention of the LSI-11 before getting the >>> prompt.) |
| 82 | The command |
| 83 | .IP |
| 84 | >>>BOOT ANY |
| 85 | .LP |
| 86 | invokes a version of the boot program in a way which allows you to |
| 87 | specify any system as the system to be booted. |
| 88 | It reads from the console a device specification (see below) followed |
| 89 | immediately by a pathname. |
| 90 | .PP |
| 91 | The scripts may be modified for local configuration if necessary. |
| 92 | The boot device type is set in register 10 as the device major number. |
| 93 | The flags and minor device are placed in register 11. |
| 94 | The register is used in four one-byte fields; from least to most significant, |
| 95 | they are boot flags (as defined in |
| 96 | .IR <sys/reboot.h> ), |
| 97 | disk partition, drive unit, and adaptor number (UNIBUS or MASSBUS as |
| 98 | appropriate). |
| 99 | .PP |
| 100 | On an 11/750, the reset button will boot from the device |
| 101 | selected by the front panel boot device switch. In systems |
| 102 | with RK07's, position B normally selects the RK07 for boot. |
| 103 | This will boot multi-user. To boot from RK07 with boot flags you |
| 104 | may specify |
| 105 | .IP |
| 106 | >>>B/\fIn\fR DMA0 |
| 107 | .LP |
| 108 | where, giving a \fIn\fR of 1 causes the boot program |
| 109 | to ask for the name of the system to be bootstrapped, |
| 110 | giving a \fIn\fR of 2 causes the boot program to come up single |
| 111 | user, and a \fIn\fR of 3 causes both of these actions to occur. |
| 112 | The ``DM'' specifies RK07, the ``A'' represents the adaptor number (UNIBUS |
| 113 | or MASSBUS), and the ``0'' is the drive unit number. |
| 114 | Other disk types which may be used are DB (MASSBUS), DD (TU58), |
| 115 | and DU (UDA-50/RA disk). |
| 116 | A non-zero disk partition can be used by adding (partition times 1000 hex) |
| 117 | to \fIn\fR. |
| 118 | .PP |
| 119 | The 11/750 boot procedure uses the boot roms to load block 0 off of |
| 120 | the specified device. The /usr/mdec directory contains a number |
| 121 | of bootstrap programs for the various disks which should be placed |
| 122 | in a new pack automatically by |
| 123 | .IR newfs (8) |
| 124 | when the ``a'' partition file system on the pack is created. |
| 125 | .PP |
| 126 | On any processor, the |
| 127 | .I boot |
| 128 | program |
| 129 | finds the corresponding file on the given device |
| 130 | .RI ( vmunix |
| 131 | by default), loads that file |
| 132 | into memory location zero, and starts the program at the entry address |
| 133 | specified in the program header (after clearing off the high bit |
| 134 | of the specified entry address). |
| 135 | .PP |
| 136 | The file specifications used with \*(lqBOOT ANY\*(rq or \*(lqB/3\*(rq |
| 137 | are of the form: |
| 138 | .IP |
| 139 | device(unit,minor) |
| 140 | .PP |
| 141 | where |
| 142 | .I device |
| 143 | is the type of the device to be searched, |
| 144 | .I unit |
| 145 | is 8 * the mba or uba number plus |
| 146 | the unit number of the disk or tape, |
| 147 | and |
| 148 | .I minor |
| 149 | is the disk partition or tape file number. |
| 150 | Normal line editing characters can be used when typing the file specification. |
| 151 | The following list of supported devices may vary from installation to |
| 152 | installation: |
| 153 | .ta 5 10 |
| 154 | .nf |
| 155 | hp MASSBUS disk drive |
| 156 | up UNIBUS storage module drive |
| 157 | ht TE16,TU45,TU77 on MASSBUS |
| 158 | mt TU78 on MASSBUS |
| 159 | hk RK07 on UNIBUS |
| 160 | ra storage module on a UDA50 |
| 161 | rb storage module on a 730 IDC |
| 162 | rl RL02 on UNIBUS |
| 163 | tm TM11 emulation tape drives on UNIBUS |
| 164 | ts TS11 on UNIBUS |
| 165 | ut UNIBUS TU45 emulator |
| 166 | .fi |
| 167 | .PP |
| 168 | For example, |
| 169 | to boot from a file system which starts at cylinder 0 |
| 170 | of unit 0 of a MASSBUS disk, type \*(lqhp(0,0)vmunix\*(rq |
| 171 | to the boot prompt; \*(lqup(0,0)vmunix\*(rq would specify |
| 172 | a UNIBUS drive, \*(lqhk(0,0)vmunix\*(rq would specify |
| 173 | an RK07 disk drive, \*(lqra(0,0)vmunix\*(rq would specify a |
| 174 | UDA50 disk drive, and \*(lqrb(0,0)vmunix\*(rq would specify a |
| 175 | disk on a 730 IDC. |
| 176 | For tapes, the minor device number gives a file offset. |
| 177 | .PP |
| 178 | In an emergency, the bootstrap methods described in the paper |
| 179 | ``Installing and Operating 4.3bsd'' can be used |
| 180 | to boot from a distribution tape. |
| 181 | .SH FILES |
| 182 | .ta \w'/usr/mdec/installboot 'u |
| 183 | /vmunix system code |
| 184 | .br |
| 185 | /boot system bootstrap |
| 186 | .br |
| 187 | /usr/mdec/xxboot sector-0 boot block for 750, xx is disk type |
| 188 | .br |
| 189 | /usr/mdec/bootxx second-stage boot for 750, xx is disk type |
| 190 | .br |
| 191 | /usr/mdec/installboot program to install boot blocks on 750 |
| 192 | .SH "SEE ALSO" |
| 193 | arff(8V), |
| 194 | crash(8V), |
| 195 | fsck(8), |
| 196 | halt(8), |
| 197 | init(8), |
| 198 | newfs(8), |
| 199 | rc(8), |
| 200 | shutdown(8) |