Commit | Line | Data |
---|---|---|
021014a6 KM |
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 4.1 (Berkeley) %G% | |
6 | .\" | |
7 | .TH REBOOT 8 5/10/81 | |
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 zero. | |
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. (It is no longer necessary to reboot after rebuilding | |
43 | the root file system.) | |
44 | .TP | |
45 | .B \-q | |
46 | reboots quickly and ungracefully, without shutting down running | |
47 | processes first. | |
48 | .PP | |
49 | .B "Power fail and crash recovery." | |
50 | Normally, the system will reboot itself at power-up or after crashes. | |
51 | Provided the auto-restart is enabled on the machine front panel, | |
52 | an automatic consistency check of the file systems will be performed | |
53 | then and unless this fails the system will resume multi-user operations. | |
54 | .PP | |
55 | .B Cold starts. | |
56 | These are processor type dependent. | |
57 | On an 11/780, there are two floppy files for each disk controller, | |
58 | both of which cause boots from unit 0 of the root file system | |
59 | of a controller located on mba0 or uba0. | |
60 | One gives a single user shell, while the other invokes the multi-user | |
61 | automatic reboot. Thus these files are HPS and HPM for the single | |
62 | and multi-user boot from MASSBUS RP06/RM03/RM05 disks, | |
63 | UPS and UPM for UNIBUS storage module controller and disks | |
64 | such as the EMULEX SC-21 | |
65 | and AMPEX 9300 pair, or HKS and HKM for RK07 disks. | |
66 | .PP | |
67 | Giving the command | |
68 | .IP | |
69 | >>>BOOT HPM | |
70 | .LP | |
71 | Would boot the system from (e.g.) an RP06 and run the automatic consistency | |
72 | check as described in | |
73 | .IR fsck (8). | |
74 | (Note that it may | |
75 | be necessary to type control-P | |
76 | to gain the attention of the LSI-11 before getting the >>> prompt.) | |
77 | The command | |
78 | .IP | |
79 | >>>BOOT ANY | |
80 | .LP | |
81 | invokes a version of the boot program in a way which allows you to | |
82 | specify any system as the system to be booted. | |
83 | It reads from the console a device specification (see below) followed | |
84 | immediately by a pathname. | |
85 | .PP | |
86 | On an 11/750, the reset button will boot from the device | |
87 | selected by the front panel boot device switch. In systems | |
88 | with RK07's, position B normally selects the RK07 for boot. | |
89 | This will boot multi-user. To boot from RK07 with boot flags you | |
90 | may specify | |
91 | .IP | |
92 | >>>B/\fIn\fR DMA0 | |
93 | .LP | |
94 | where, giving a \fIn\fR of 1 causes the boot program | |
95 | to ask for the name of the system to be bootstrapped, | |
96 | giving a \fIn\fR of 2 causes the boot program to come up single | |
97 | user, and a \fIn\fR of 3 causes both of these actions to occur. | |
98 | .PP | |
99 | The 11/750 boot procedure uses the boot roms to load block 0 off of | |
100 | the specified device. The /usr/mdec directory contains a number | |
101 | of bootstrap programs for the various disks which should be placed | |
102 | in a new pack via | |
103 | .IP | |
104 | cp /usr/mdec/\fIxx\fRboot /dev/\fIxx\fR?a | |
105 | .PP | |
106 | whenever a new bootable pack is to be created. | |
107 | .PP | |
108 | On both processors, the | |
109 | .I boot | |
110 | program | |
111 | finds the corresponding file on the given device, loads that file | |
112 | into memory location zero, and starts the program at the entry address | |
113 | specified in the program header (after clearing off the high bit | |
114 | of the specified entry address.) | |
115 | Normal line editing characters can be used in specifying the pathname. | |
116 | .PP | |
117 | If you have an rp06, rm05 or rm03 disk and wish to boot off of a file | |
118 | system which starts at cylinder 0 of unit 0, you can type \*(lqhp(0,0)vmunix\*(rq | |
119 | to the boot prompt; \*(lqup(0,0)vmunix\*(rq would specify | |
120 | a UNIBUS ampex 9300 drive, ``rk(0,0)vmunix'' would specify | |
121 | a RK-07 disk drive. | |
122 | .PP | |
123 | A device specification has the following form: | |
124 | .IP | |
125 | device(unit, minor) | |
126 | .PP | |
127 | where | |
128 | .I device | |
129 | is the type of the device to be searched, | |
130 | .I unit | |
131 | is 8* the mba or uba number plus | |
132 | the unit number of the device, | |
133 | and | |
134 | .I minor | |
135 | is the minor device index. | |
136 | The following list of supported devices may vary from installation to | |
137 | installation: | |
138 | .ta 5 10 | |
139 | .nf | |
140 | hp RP06, RM03, RM05, RP07 or RM80 on MASSBUS | |
141 | up storage module drive on UNIBUS | |
142 | ht TE16,TU45,TU77 on MASSBUS | |
143 | hk RK07 on UNIBUS | |
144 | tm TM11 emulation tape drives on UNIBUS | |
145 | ts TS11 on UNIBUS | |
146 | .fi | |
147 | .PP | |
148 | For tapes, the minor device number gives a file offset. | |
149 | .PP | |
150 | In an emergency, the bootstrap methods described in the paper | |
151 | ``Setting up the Fourth Berkeley Software Tape'' can be used | |
152 | to boot from a distribution tape. | |
153 | .SH FILES | |
154 | .ta \w'/usr/mdec/mboot 'u | |
155 | /vmunix system code | |
156 | .br | |
157 | /boot system bootstrap | |
158 | .SH "SEE ALSO" | |
159 | crash(8), fsck(8), init(8), rc(8), shutdown(8), halt(8) |