| blob | 87978df136405e5bcc6fec88145ac141455e3859 |
1 .\" $NetBSD: boot.8,v 1.11 2008/09/24 20:07:05 reed Exp $
2 .\"
3 .\" Copyright (c) 1980, 1991, 1993
4 .\" The Regents of the University of California. All rights reserved.
5 .\"
6 .\" Redistribution and use in source and binary forms, with or without
7 .\" modification, are permitted provided that the following conditions
8 .\" are met:
9 .\" 1. Redistributions of source code must retain the above copyright
10 .\" notice, this list of conditions and the following disclaimer.
11 .\" 2. Redistributions in binary form must reproduce the above copyright
12 .\" notice, this list of conditions and the following disclaimer in the
13 .\" documentation and/or other materials provided with the distribution.
14 .\" 3. Neither the name of the University nor the names of its contributors
15 .\" may be used to endorse or promote products derived from this software
16 .\" without specific prior written permission.
17 .\"
18 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
19 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
20 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
21 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
22 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
23 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
24 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
25 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
26 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
27 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
28 .\" SUCH DAMAGE.
29 .\"
30 .\" @(#)boot_vax.8 8.2 (Berkeley) 4/19/94
31 .\"
32 .Dd April 19, 1994
33 .Dt BOOT 8 vax
34 .Os
35 .Sh NAME
36 .Nm boot
37 .Nd
38 system bootstrapping procedures
39 .Sh DESCRIPTION
40 .Ss Power fail and crash recovery
41 Normally, the system will reboot itself at power-up or after crashes.
42 Provided the auto-restart is enabled on the machine front panel,
43 an automatic consistency check of the file systems will be performed,
44 and unless this fails, the system will resume multi-user operations.
45 .Pp
46 .Ss Cold starts
47 These are processor-type dependent.
48 On an 11/780, there are two floppy files for each disk controller,
49 both of which cause boots from unit 0 of the root file system
50 of a controller located on mba0 or uba0.
51 One gives a single user shell, while the other invokes the multi-user
52 automatic reboot.
53 Thus these files are
54 .Tn HPS
55 and
56 .Tn HPM
57 for the single
58 and multi-user boot from
59 .Tn MASSBUS
60 RP06/RM03/RM05 disks,
61 .Tn UPS
62 and
63 .Tn UPM
64 for
65 .Tn UNIBUS
66 storage module controller and disks
67 such as the
68 .Tn EMULEX
69 SC-21
70 and
71 .Tn AMPEX
72 9300 pair,
73 .Tn RAS
74 and
75 .Tn RAM
76 to boot from
77 .Tn MSCP
78 controllers and disks such as the RA81,
79 or
80 .Tn HKS
81 and
82 .Tn HKM
83 for RK07 disks.
84 There is also a script for booting from the default device,
85 which is normally a copy of one of the standard multi-user boot scripts,
86 but which may be modified to perform other actions
87 or to boot from a different unit.
88 The situation on the 8600 is similar, with scripts loaded from the console RL02.
89 .Pp
90 Giving the command
91 .Pp
92 .Dl \*[Gt]\*[Gt]\*[Gt]BOOT HPM
93 .Pp
94 would boot the system from (e.g.) an RP06 and run the automatic consistency
95 check as described in
96 .Xr fsck 8 .
97 (Note that it may
98 be necessary to type control-P
99 and halt the processor
100 to gain the attention of the
101 .Tn LSI-11
102 before getting the \*[Gt]\*[Gt]\*[Gt] prompt.)
103 The command
104 .Pp
105 .Dl \*[Gt]\*[Gt]\*[Gt]BOOT ANY
106 .Pp
107 invokes a version of the boot program in a way which allows you to
108 specify any system as the system to be booted.
109 It reads from the console a device specification (see below) followed
110 immediately by a pathname.
111 .Pp
112 The scripts may be modified for local configuration if necessary.
113 The flags are placed in register 11 (as defined in
114 .Aq Pa sys/reboot.h ) .
115 The boot device is specified in register 10.
116 The encoding of this register is also defined in
117 .Aq Pa sys/reboot.h .
118 The current encoding has a historical basis, and is shown in the following
119 table:
120 .Pp
121 .Bd -unfilled -offset indent -compact
122 bits usage
123 0-7 boot device type (the device major number)
124 8-15 disk partition
125 16-19 drive unit
126 20-23 controller number
127 24-27 adaptor number (UNIBUS or MASSBUS as appropriate)
128 .Ed
129 .Pp
130 The adaptor number corresponds to the normal configuration on the 11/750,
131 and to the order in which adaptors are found on the 11/780 and 8600
132 (generally the same as the numbers used by
133 .Ux ) .
134 .Pp
135 On an 11/750, the reset button will boot from the device
136 selected by the front panel boot device switch.
137 In systems with RK07's, position B normally selects the RK07 for boot.
138 This will boot multi-user.
139 To boot from RK07 with boot flags you may specify
140 .Pp
141 .Bd -unfilled -offset indent -compact
142 .Li \&\*[Gt]\*[Gt]\*[Gt]B/ Ns Fl n No DMA0
143 .Ed
144 .Pp
145 where, giving a
146 .Ar n
147 of 1 causes the boot program
148 to ask for the name of the system to be bootstrapped,
149 giving a
150 .Ar n
151 of 2 causes the boot program to come up single
152 user, and a
153 .Ar n
154 of 3 causes both of these actions to occur.
155 The ``DM'' specifies RK07, the ``A'' represents the adaptor number
156 .Pf ( Tn UNIBUS
157 or
158 .Tn MASSBUS ) ,
159 and the ``0'' is the drive unit number.
160 Other disk types which may be used are DB
161 .Pq Tn MASSBUS ,
162 DD (TU58),
163 and DU
164 .Pf ( Tn UDA-50/RA
165 disk).
166 A non-zero disk partition can be used by adding (partition times 1000 hex)
167 to
168 .Ar n .
169 .Pp
170 The boot procedure on the Micro
171 .Tn VAX
172 II
173 is similar.
174 A switch on the back panel sets the power-up action
175 to autoboot or to halt.
176 When halted, the processor may be booted using the same syntax
177 as on the 11/750.
178 .Pp
179 The 11/750 boot procedure uses the boot ROMs to load block 0 off of
180 the specified device.
181 The
182 .Pa /usr/mdec
183 directory contains a number
184 of bootstrap programs for the various disks which should be placed
185 in a new pack by
186 .Xr disklabel 8 .
187 Similarly, the Micro
188 .Tn VAX
189 II boot procedure loads a boot parameter block
190 from block 0 of the disk.
191 The
192 .Ic rdboot
193 .Dq bootstrap
194 contains the correct parameters for an
195 .Tn MSCP
196 disk such
197 as the RD53.
198 .Pp
199 On any processor, the
200 .Em boot
201 program
202 finds the corresponding file on the given device
203 .Pf ( Pa netbsd
204 by default), loads that file
205 into memory location zero, and starts the program at the entry address
206 specified in the program header (after clearing off the high bit
207 of the specified entry address).
208 .Pp
209 The file specifications used with
210 .Dq BOOT ANY
211 or
212 .Dq \&B/3
213 are of the form:
214 .Pp
215 .Dl device(adaptor,controller,unit,minor)
216 .Pp
217 where
218 .Ar device
219 is the type of the device to be searched,
220 .Ar adaptor
221 is the
222 .Tn UNIBUS
223 or
224 .Tn MASSBUS
225 number of the adaptor to which the device is attached,
226 .Ar controller
227 is the unit number of the controller or
228 .Tn MASSBUS
229 tape formatter on that adaptor,
230 .Ar unit
231 is the unit number of the disk or transport slave unit of the tape,
232 and
233 .Ar minor
234 is the disk partition or tape file number.
235 Leading adaptor or controller numbers default to 0.
236 Normal line editing characters can be used when typing the file specification.
237 The following list of supported devices may vary from installation to
238 installation:
239 .Pp
240 .Bd -unfilled -offset indent -compact
241 hp MASSBUS disk drive
242 up UNIBUS storage module drive
243 ht TE16,TU45,TU77 on MASSBUS
244 kra storage module on a KDB50
245 mt TU78 on MASSBUS
246 hk RK07 on UNIBUS
247 ra storage module on a MSCP-compatible UNIBUS controller
248 rb storage module on a 730 IDC
249 rl RL02 on UNIBUS
250 tm TM11 emulation tape drives on UNIBUS
251 tms TMSCP-compatible tape
252 ts TS11 on UNIBUS
253 ut UNIBUS TU45 emulator
254 .Ed
255 .Pp
256 For example,
257 to boot from a file system which starts at cylinder 0
258 of unit 0 of a
259 .Tn MASSBUS
260 disk, type
261 .Ql hp(0,0)netbsd
262 to the boot prompt;
263 .Ql hp(2,0,1,0)netbsd
264 would specify drive 1 on
265 .Tn MASSBUS
266 adaptor 2;
267 .Ql up(0,0)netbsd
268 would specify a
269 .Tn UNIBUS
270 drive,
271 .Ql hk(0,0)netbsd
272 would specify
273 an RK07 disk drive,
274 .Ql ra(1,0,0,0)netbsd
275 would specify a
276 .Tn UDA50
277 disk drive on a second
278 .Tn UNIBUS ,
279 and
280 .Ql rb(0,0)netbsd
281 would specify a
282 disk on a 730
283 .Tn IDC .
284 For tapes, the minor device number gives a file offset;
285 .Ql mt(1,2,3,4)
286 would specify the fifth file on slave 3 of the formatter
287 at
288 .Ql drive
289 2 on mba 1.
290 .Pp
291 On an 11/750 with patchable control store,
292 microcode patches will be installed by
293 .Em boot
294 if the file
295 .Pa psc750.bin
296 exists in the root of the filesystem from which the system is booted.
297 .Pp
298 In an emergency, the bootstrap methods described in the paper
299 .%T Installing and Operating 4.3bsd
300 can be used to boot from a distribution tape.
301 .Sh FILES
302 .Bl -tag -width /usr/mdec/xxboot -compact
303 .It Pa /netbsd
304 system code
305 .It Pa /boot
306 system bootstrap
307 .It Pa /usr/mdec/xxboot
308 sector-0 boot block for 750, xx is disk type
309 .It Pa /usr/mdec/bootxx
310 second-stage boot for 750, xx is disk type
311 .It Pa /pcs750.bin
312 microcode patch file on 750
313 .El
314 .Sh SEE ALSO
315 .Xr arff 8 ,
316 .Xr halt 8 ,
317 .Xr reboot 8 ,
318 .Xr shutdown 8
319 .Sh HISTORY
320 The
321 .Nm
322 command appeared in
323 .Bx 4.0 .