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