|
|
1.1 ! root 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: .\" @(#)reboot.8 6.6 (Berkeley) 7/12/88 ! 6: .\" ! 7: .TH REBOOT 8 "July 12, 1988" ! 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 allows the system ! 34: to perform other shutdown activities such as resynchronizing ! 35: hardware time-of-day clocks. ! 36: A multi-user reboot (as described below) is then initiated. ! 37: This causes a system to be ! 38: booted and an automatic disk check to be performed. If all this succeeds ! 39: without incident, the system is then brought up for many users. ! 40: .PP ! 41: Options to reboot are: ! 42: .TP ! 43: .B \-n ! 44: option avoids the sync. It can be used if a disk or the processor ! 45: is on fire. ! 46: .TP ! 47: .B \-q ! 48: reboots quickly and ungracefully, without shutting down running ! 49: processes first. ! 50: .PP ! 51: .I Reboot ! 52: normally logs the reboot using ! 53: .IR syslog (8) ! 54: and places a shutdown record in the login accounting file ! 55: /usr/adm/wtmp. ! 56: These actions are inhibited if the ! 57: .B \-n ! 58: or ! 59: .B \-q ! 60: options are present. ! 61: .PP ! 62: .B "Power fail and crash recovery." ! 63: Normally, the system will reboot itself at power-up or after crashes. ! 64: Provided the auto-restart is enabled on the machine front panel, ! 65: an automatic consistency check of the file systems will be performed, ! 66: and unless this fails, the system will resume multi-user operations. ! 67: .PP ! 68: .B Cold starts. ! 69: These are processor-type dependent. ! 70: On an 11/780, there are two floppy files for each disk controller, ! 71: both of which cause boots from unit 0 of the root file system ! 72: of a controller located on mba0 or uba0. ! 73: One gives a single user shell, while the other invokes the multi-user ! 74: automatic reboot. Thus these files are HPS and HPM for the single ! 75: and multi-user boot from MASSBUS RP06/RM03/RM05 disks, ! 76: UPS and UPM for UNIBUS storage module controller and disks ! 77: such as the EMULEX SC-21 ! 78: and AMPEX 9300 pair, ! 79: RAS and RAM to boot from MSCP controllers and disks such as the RA81, ! 80: or HKS and HKM for RK07 disks. ! 81: There is also a script for booting from the default device, ! 82: which is normally a copy of one of the standard multi-user boot scripts, ! 83: but which may be modified to perform other actions ! 84: or to boot from a different unit. ! 85: The situation on the 8600 is similar, with scripts loaded from the console RL02. ! 86: .PP ! 87: Giving the command ! 88: .IP ! 89: >>>BOOT HPM ! 90: .LP ! 91: would boot the system from (e.g.) an RP06 and run the automatic consistency ! 92: check as described in ! 93: .IR fsck (8). ! 94: (Note that it may ! 95: be necessary to type control-P ! 96: and halt the processor ! 97: to gain the attention of the LSI-11 before getting the >>> prompt.) ! 98: The command ! 99: .IP ! 100: >>>BOOT ANY ! 101: .LP ! 102: invokes a version of the boot program in a way which allows you to ! 103: specify any system as the system to be booted. ! 104: It reads from the console a device specification (see below) followed ! 105: immediately by a pathname. ! 106: .PP ! 107: The scripts may be modified for local configuration if necessary. ! 108: The flags are placed in register 11 (as defined in ! 109: .IR <sys/reboot.h> ). ! 110: The boot device is specified in register 10. ! 111: The encoding of this register is also defined in ! 112: .IR <sys/reboot.h> . ! 113: The current encoding has a historical basis, and is shown in the following ! 114: table: ! 115: .LP ! 116: .ta 5 10 ! 117: .nf ! 118: bits usage ! 119: 0-7 boot device type (the device major number) ! 120: 8-15 disk partition ! 121: 16-19 drive unit ! 122: 20-23 controller number ! 123: 24-27 adaptor number (UNIBUS or MASSBUS as appropriate) ! 124: .fi ! 125: .LP ! 126: The adaptor number corresponds to the normal configuration on the 11/750, ! 127: and to the order in which adaptors are found on the 11/780 and 8600 ! 128: (generally the same as the numbers used by UNIX). ! 129: .PP ! 130: On an 11/750, the reset button will boot from the device ! 131: selected by the front panel boot device switch. In systems ! 132: with RK07's, position B normally selects the RK07 for boot. ! 133: This will boot multi-user. To boot from RK07 with boot flags you ! 134: may specify ! 135: .IP ! 136: >>>B/\fIn\fR DMA0 ! 137: .LP ! 138: where, giving a \fIn\fR of 1 causes the boot program ! 139: to ask for the name of the system to be bootstrapped, ! 140: giving a \fIn\fR of 2 causes the boot program to come up single ! 141: user, and a \fIn\fR of 3 causes both of these actions to occur. ! 142: The ``DM'' specifies RK07, the ``A'' represents the adaptor number (UNIBUS ! 143: or MASSBUS), and the ``0'' is the drive unit number. ! 144: Other disk types which may be used are DB (MASSBUS), DD (TU58), ! 145: and DU (UDA-50/RA disk). ! 146: A non-zero disk partition can be used by adding (partition times 1000 hex) ! 147: to \fIn\fR. ! 148: .PP ! 149: The boot procedure on the MicroVAX II is similar. ! 150: A switch on the back panel sets the power-up action ! 151: to autoboot or to halt. ! 152: When halted, the processor may be booted using the same syntax ! 153: as on the 11/750. ! 154: .PP ! 155: The 11/750 boot procedure uses the boot roms to load block 0 off of ! 156: the specified device. The /usr/mdec directory contains a number ! 157: of bootstrap programs for the various disks which should be placed ! 158: in a new pack by ! 159: .IR disklabel (8). ! 160: Similarly, the MicroVAX II boot procedure loads a boot parameter block ! 161: from block 0 of the disk. ! 162: The ! 163: .I rdboot ! 164: ``bootstrap'' contains the correct parameters for an MSCP disk such ! 165: as the RD53. ! 166: .PP ! 167: On any processor, the ! 168: .I boot ! 169: program ! 170: finds the corresponding file on the given device ! 171: .RI ( vmunix ! 172: by default), loads that file ! 173: into memory location zero, and starts the program at the entry address ! 174: specified in the program header (after clearing off the high bit ! 175: of the specified entry address). ! 176: .PP ! 177: The file specifications used with \*(lqBOOT ANY\*(rq or \*(lqB/3\*(rq ! 178: are of the form: ! 179: .IP ! 180: device(adaptor,controller,unit,minor) ! 181: .PP ! 182: where ! 183: .I device ! 184: is the type of the device to be searched, ! 185: .I adaptor ! 186: is the UNIBUS or MASSBUS number of the adaptor to which the device is attached, ! 187: .I controller ! 188: is the unit number of the controller or MASSBUS tape formatter on that adaptor, ! 189: .I unit ! 190: is the unit number of the disk or transport slave unit of the tape, ! 191: and ! 192: .I minor ! 193: is the disk partition or tape file number. ! 194: Leading adaptor or controller numbers default to 0. ! 195: Normal line editing characters can be used when typing the file specification. ! 196: The following list of supported devices may vary from installation to ! 197: installation: ! 198: .LP ! 199: .ta 5 10 ! 200: .nf ! 201: hp MASSBUS disk drive ! 202: up UNIBUS storage module drive ! 203: ht TE16,TU45,TU77 on MASSBUS ! 204: kra storage module on a KDB50 ! 205: mt TU78 on MASSBUS ! 206: hk RK07 on UNIBUS ! 207: ra storage module on a MSCP-compatible UNIBUS controller ! 208: rb storage module on a 730 IDC ! 209: rl RL02 on UNIBUS ! 210: tm TM11 emulation tape drives on UNIBUS ! 211: tms TMSCP-compatible tape ! 212: ts TS11 on UNIBUS ! 213: ut UNIBUS TU45 emulator ! 214: .fi ! 215: .PP ! 216: For example, ! 217: to boot from a file system which starts at cylinder 0 ! 218: of unit 0 of a MASSBUS disk, type \*(lqhp(0,0)vmunix\*(rq ! 219: to the boot prompt; \*(lqhp(2,0,1,0)vmunix\*(rq ! 220: would specify drive 1 on MASSBUS adaptor 2; ! 221: \*(lqup(0,0)vmunix\*(rq would specify ! 222: a UNIBUS drive, \*(lqhk(0,0)vmunix\*(rq would specify ! 223: an RK07 disk drive, \*(lqra(1,0,0,0)vmunix\*(rq would specify a ! 224: UDA50 disk drive on a second UNIBUS, and \*(lqrb(0,0)vmunix\*(rq would specify a ! 225: disk on a 730 IDC. ! 226: For tapes, the minor device number gives a file offset; ! 227: \*(lqmt(1,2,3,4)\*(rq would specify the fifth file on slave 3 of the formatter ! 228: at \*(lqdrive\*(rq 2 on mba 1. ! 229: .PP ! 230: On an 11/750 with patchable control store, ! 231: microcode patches will be installed by ! 232: .I boot ! 233: if the file ! 234: .I psc750.bin ! 235: exists in the root of the filesystem from which the system is booted. ! 236: .PP ! 237: In an emergency, the bootstrap methods described in the paper ! 238: ``Installing and Operating 4.3bsd'' can be used ! 239: to boot from a distribution tape. ! 240: .SH FILES ! 241: .ta \w'/usr/mdec/bootxx 'u ! 242: /vmunix system code ! 243: .br ! 244: /boot system bootstrap ! 245: .br ! 246: /usr/mdec/xxboot sector-0 boot block for 750, xx is disk type ! 247: .br ! 248: /usr/mdec/bootxx second-stage boot for 750, xx is disk type ! 249: .br ! 250: /pcs750.bin microcode patch file on 750 ! 251: .SH "SEE ALSO" ! 252: arff(8V), ! 253: crash(8V), ! 254: disklabel(8), ! 255: fsck(8), ! 256: halt(8), ! 257: init(8), ! 258: rc(8), ! 259: shutdown(8), ! 260: syslogd(8)
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.