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