|
|
1.1 root 1: .\" Copyright (c) 1990 The Regents of the University of California.
2: .\" 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 are permitted provided
9: .\" that: (1) source distributions retain this entire copyright notice and
10: .\" comment, and (2) distributions including binaries display the following
11: .\" acknowledgement: ``This product includes software developed by the
12: .\" University of California, Berkeley and its contributors'' in the
13: .\" documentation or other materials provided with the distribution and in
14: .\" all advertising materials mentioning features or use of this software.
15: .\" Neither the name of the University nor the names of its contributors may
16: .\" be used to endorse or promote products derived from this software without
17: .\" specific prior written permission.
18: .\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED
19: .\" WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
20: .\" MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
21: .\"
22: .\" @(#)reboot_hp300.8 5.1 (Berkeley) 6/29/90
23: .\"
24: .TH REBOOT 8 "June 29, 1990"
25: .UC 7
26: .SH NAME
27: reboot \- UNIX bootstrapping procedures
28: .SH SYNOPSIS
29: .B reboot
30: [
31: .B \-d
32: ] [
33: .B \-n
34: ] [
35: .B \-q
36: ] [
37: .B \-s
38: ]
39: .SH DESCRIPTION
40: .PP
41: UNIX is started by placing it at the beginning of physical memory
42: and transferring to the entry point.
43: Since the system is not reenterable,
44: it is necessary to read it in from disk or tape
45: each time it is to be bootstrapped.
46: .PP
47: .B Rebooting a running system.
48: When a UNIX is running and a reboot is desired,
49: .IR shutdown (8)
50: is normally used.
51: If there are no users then
52: .B reboot
53: can be used.
54: Reboot causes the disks to be synced and allows the system
55: to perform other shutdown activities such as resynchronizing
56: hardware time-of-day clocks.
57: A multi-user reboot (as described below) is then initiated.
58: This causes a system to be
59: booted and an automatic disk check to be performed. If all this succeeds
60: without incident, the system is then brought up for many users.
61: .PP
62: Options to reboot are:
63: .TP
64: .B \-d
65: option forces a memory dump to the swap area (see
66: .IR crash (8v))
67: before rebooting.
68: This can be used if the system is in a funny state that you would
69: like to ``snapshot'' and analyze later.
70: .TP
71: .B \-n
72: option avoids the sync. It can be used if a disk or the processor
73: is on fire.
74: .TP
75: .B \-q
76: reboots quickly and ungracefully, without shutting down running
77: processes first.
78: .TP
79: .B \-s
80: option reboots to single user mode.
81: .PP
82: .I Reboot
83: normally logs the reboot using
84: .IR syslog (8)
85: and places a shutdown record in the login accounting file (see
86: .IR utmp (5).
87: These actions are inhibited if the
88: .B \-n
89: or
90: .B \-q
91: options are present.
92: .PP
93: .B "Power fail and crash recovery."
94: Normally, the system will reboot itself at power-up or after crashes.
95: An automatic consistency check of the file systems will be performed,
96: and unless this fails, the system will resume multi-user operations.
97: .PP
98: .B "Cold starts."
99: On an HP300, the boot procedure uses the boot rom to load a boot program
100: from an LIF format directory at the beginning of an attached disk.
101: The /usr/mdec directory contains a disk boot program ``bootrd''
102: which should be placed in a new pack automatically by
103: .IR newfs (8)
104: when the ``a'' partition file system on the pack is created.
105: .PP
106: This
107: .I boot
108: program
109: finds the corresponding file on the given device
110: .RI ( vmunix
111: by default),
112: loads that file into memory,
113: and starts the program at the entry address specified in the program header.
114: .PP
115: The boot program can be interrupted by typing `^C' (ctrl-C).
116: This will force the boot program to interactively prompt for a system to boot.
117: If not interrupted, it will boot from the device from which the boot
118: program itself was loaded.
119: .PP
120: The file specifications used for an interactive boot are of the form:
121: .IP
122: device(unit,minor)
123: .PP
124: where
125: .I device
126: is the type of the device to be searched,
127: .I unit
128: is 8 * the hpib number plus the unit number of the disk or tape,
129: and
130: .I minor
131: is the disk partition or tape file number.
132: Normal line editing characters can be used when typing the file specification.
133: Currently, ``rd'' is the only valid
134: .I device
135: specifier.
136: .PP
137: For example,
138: to boot from the `a' file system of unit 0 on HP-IB 2,
139: type \*(lqrd(16,0)vmunix\*(rq
140: to the boot prompt.
141: For tapes, the minor device number gives a file offset.
142: .PP
143: In an emergency, the bootstrap methods described in the paper
144: ``Installing 4.3bsd on the HP300''
145: can be used to boot from a distribution tape.
146: .SH FILES
147: .ta \w'/usr/mdec/installboot 'u
148: /vmunix system code
149: .br
150: /usr/mdec/bootrd LIF format boot block
151: .br
152: /usr/mdec/installboot program to install boot blocks
153: .SH "SEE ALSO"
154: crash(8V),
155: fsck(8),
156: halt(8),
157: init(8),
158: newfs(8),
159: rc(8),
160: shutdown(8),
161: syslogd(8)
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.