[apple/system_cmds.git] / reboot.tproj / boot_hp300.8

.\" Copyright (c) 1990, 1991, 1993
.\"	The Regents of the University of California.  All rights reserved.
.\"
.\" This code is derived from software contributed to Berkeley by
.\" the Systems Programming Group of the University of Utah Computer
.\" Science Department.
.\"
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" are met:
.\" 1. Redistributions of source code must retain the above copyright
.\"    notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\"    notice, this list of conditions and the following disclaimer in the
.\"    documentation and/or other materials provided with the distribution.
.\" 3. All advertising materials mentioning features or use of this software
.\"    must display the following acknowledgement:
.\"	This product includes software developed by the University of
.\"	California, Berkeley and its contributors.
.\" 4. Neither the name of the University nor the names of its contributors
.\"    may be used to endorse or promote products derived from this software
.\"    without specific prior written permission.
.\"
.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE.
.\"
.\"	@(#)boot_hp300.8	8.2 (Berkeley) 4/19/94
.\"
.Dd April 19, 1994
.Dt BOOT_HP300 8 hp300
.Os
.Sh NAME
.Nm boot
.Nd
system bootstrapping procedures
.Sh DESCRIPTION
.Sy Power fail and crash recovery.
Normally, the system will reboot itself at power-up or after crashes.
An automatic consistency check of the file systems will be performed,
and unless this fails, the system will resume multi-user operations.
.Pp
.Sy Cold starts.
On an HP300, the boot procedure uses the boot ROM to load a boot program
from an
.Tn LIF
format directory at the beginning of an attached disk.
The
.Pa /usr/mdec
directory contains a disk boot programs which should be placed in a
new pack automatically by
.Xr newfs 8
when the ``a'' partition file system on the pack is created.
.Pp
This
.Em boot
program
finds the corresponding file on the given device 
.Pf ( Ar vmunix
by default),
loads that file into memory,
and starts the program at the entry address specified in the program header.
.Pp
The boot program can be interrupted by typing `^C' (ctrl-C).
This will force the boot program to interactively prompt for a system to boot.
If not interrupted, it will boot from the device from which the boot
program itself was loaded.
.Pp
The file specifications used for an interactive boot are of the form:
.Pp
.Dl device(unit, minor)
.Pp
where
.Ar device
is the type of the device to be searched,
.Ar unit
is 8 * the hpib number plus the unit number of the disk or tape,
and
.Ar minor
is the disk partition or tape file number.
Normal line editing characters can be used when typing the file specification.
Currently, ``rd'' and ``sd'' are the only valid
.Ar device
specifiers.
.Pp
For example,
to boot from the `a' file system of unit 0 on HP-IB 2,
type
.Ql rd(16, 0)vmunix
to the boot prompt.
For tapes, the minor device number gives a file offset.
.Pp
In an emergency, the bootstrap methods described in the paper
.%T Installing 4.3bsd on the HP300
can be used to boot from a distribution tape.
.Sh FILES
.Bl -tag -width /usr/mdec/installboot -compact
.It Pa /vmunix
system code
.It Pa /usr/mdec/bootrd
.Tn LIF
format boot block
.It Pa /usr/mdec/installboot
program to install boot blocks
.El
.Sh SEE ALSO
.Xr halt 8 ,
.Xr reboot 8 ,
.Xr shutdown 8
Commit	Line	Data
1815bff5 A	1	.\" Copyright (c) 1990, 1991, 1993
	2	.\" The Regents of the University of California. All rights reserved.
	3	.\"
	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.
	7	.\"
	8	.\" Redistribution and use in source and binary forms, with or without
	9	.\" modification, are permitted provided that the following conditions
	10	.\" are met:
	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.
	23	.\"
	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
	34	.\" SUCH DAMAGE.
	35	.\"
	36	.\" @(#)boot_hp300.8 8.2 (Berkeley) 4/19/94
	37	.\"
	38	.Dd April 19, 1994
	39	.Dt BOOT_HP300 8 hp300
	40	.Os
	41	.Sh NAME
	42	.Nm boot
	43	.Nd
	44	system bootstrapping procedures
	45	.Sh DESCRIPTION
	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.
	50	.Pp
	51	.Sy Cold starts.
	52	On an HP300, the boot procedure uses the boot ROM to load a boot program
	53	from an
	54	.Tn LIF
	55	format directory at the beginning of an attached disk.
	56	The
	57	.Pa /usr/mdec
	58	directory contains a disk boot programs which should be placed in a
	59	new pack automatically by
	60	.Xr newfs 8
	61	when the ``a'' partition file system on the pack is created.
	62	.Pp
	63	This
	64	.Em boot
65	program
66	finds the corresponding file on the given device
67	.Pf ( Ar vmunix
68	by default),
69	loads that file into memory,
70	and starts the program at the entry address specified in the program header.
71	.Pp
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.
76	.Pp
77	The file specifications used for an interactive boot are of the form:
78	.Pp
79	.Dl device(unit, minor)
80	.Pp
81	where
82	.Ar device
83	is the type of the device to be searched,
84	.Ar unit
85	is 8 * the hpib number plus the unit number of the disk or tape,
86	and
87	.Ar minor
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
91	.Ar device
92	specifiers.
93	.Pp
94	For example,
95	to boot from the `a' file system of unit 0 on HP-IB 2,
96	type
97	.Ql rd(16, 0)vmunix
98	to the boot prompt.
99	For tapes, the minor device number gives a file offset.
100	.Pp
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.
104	.Sh FILES
105	.Bl -tag -width /usr/mdec/installboot -compact
106	.It Pa /vmunix
107	system code
108	.It Pa /usr/mdec/bootrd
109	.Tn LIF
110	format boot block
111	.It Pa /usr/mdec/installboot
112	program to install boot blocks
113	.El
114	.Sh SEE ALSO
115	.Xr halt 8 ,
116	.Xr reboot 8 ,
117	.Xr shutdown 8