1 .\" Copyright (c) 1990, 1991, 1993
2 .\" The Regents of the University of California. All rights reserved.
4 .\" This code is derived from software contributed to Berkeley by
5 .\" the Systems Programming Group of the University of Utah Computer
6 .\" Science Department.
8 .\" Redistribution and use in source and binary forms, with or without
9 .\" modification, are permitted provided that the following conditions
11 .\" 1. Redistributions of source code must retain the above copyright
12 .\" notice, this list of conditions and the following disclaimer.
13 .\" 2. Redistributions in binary form must reproduce the above copyright
14 .\" notice, this list of conditions and the following disclaimer in the
15 .\" documentation and/or other materials provided with the distribution.
16 .\" 3. All advertising materials mentioning features or use of this software
17 .\" must display the following acknowledgement:
18 .\" This product includes software developed by the University of
19 .\" California, Berkeley and its contributors.
20 .\" 4. Neither the name of the University nor the names of its contributors
21 .\" may be used to endorse or promote products derived from this software
22 .\" without specific prior written permission.
24 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
25 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
26 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
27 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
28 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
29 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
30 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
31 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
32 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
33 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
36 .\" @(#)boot_hp300.8 8.2 (Berkeley) 4/19/94
39 .Dt BOOT_HP300 8 hp300
44 system bootstrapping procedures
46 .Sy Power fail and crash recovery.
47 Normally, the system will reboot itself at power-up or after crashes.
48 An automatic consistency check of the file systems will be performed,
49 and unless this fails, the system will resume multi-user operations.
52 On an HP300, the boot procedure uses the boot ROM to load a boot program
55 format directory at the beginning of an attached disk.
58 directory contains a disk boot programs which should be placed in a
59 new pack automatically by
61 when the ``a'' partition file system on the pack is created.
66 finds the corresponding file on the given device
69 loads that file into memory,
70 and starts the program at the entry address specified in the program header.
72 The boot program can be interrupted by typing `^C' (ctrl-C).
73 This will force the boot program to interactively prompt for a system to boot.
74 If not interrupted, it will boot from the device from which the boot
75 program itself was loaded.
77 The file specifications used for an interactive boot are of the form:
79 .Dl device(unit, minor)
83 is the type of the device to be searched,
85 is 8 * the hpib number plus the unit number of the disk or tape,
88 is the disk partition or tape file number.
89 Normal line editing characters can be used when typing the file specification.
90 Currently, ``rd'' and ``sd'' are the only valid
95 to boot from the `a' file system of unit 0 on HP-IB 2,
99 For tapes, the minor device number gives a file offset.
101 In an emergency, the bootstrap methods described in the paper
102 .%T Installing 4.3bsd on the HP300
103 can be used to boot from a distribution tape.
105 .Bl -tag -width /usr/mdec/installboot -compact
108 .It Pa /usr/mdec/bootrd
111 .It Pa /usr/mdec/installboot
112 program to install boot blocks