|
|
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_tahoe.8 6.3 (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: An automatic consistency check of the file systems will be performed
78: as described in
79: .IR fsck (8).
80: and unless this fails, the system will resume multi-user operations.
81: .PP
82: .B Cold starts.
83: These are processor-type dependent.
84: On the CCI Power 6/32 and related processors,
85: the system will do a standard autoboot from drive 0
86: upon power-up or reset.
87: This automatic boot may be cancelled by typing a \*(lq#\*(rq
88: in the first few seconds after reset.
89: This enters console mode; the console prompt is \*(lq>\*(rq or \*(lq#>\*(rq.
90: The boot flags can be set to any hexadecimal value \fIn\fP with the command
91: .IP
92: #> p23 \fIn\fP.
93: .LP
94: The default device may be examined or set; see the Diagnostics and Debugging
95: manual for the processor for details on device naming and syntax.
96: After setting the boot flags and/or device,
97: a bootstrap sequence can be initiated with
98: .IP
99: #> fb
100: .LP
101: A specific device or bootstrap file may be used; for example,
102: .IP
103: #> fb xfd(1,0)
104: .LP
105: would boot from the `a' partition on XFD drive 1.
106: .PP
107: The file specifications used for the boostrap
108: when loaded with the \*(lqaskme\*(rq flag
109: (register 23 set to 1 or 3)
110: are of the form:
111: .IP
112: device(adaptor,controller,unit,minor)
113: .PP
114: where
115: .I device
116: is the type of the device to be searched,
117: .I adaptor
118: is number of the VERSAbus (or VMEbus) to which the device is attached,
119: .I controller
120: is the unit number of the controller on that buss,
121: .I unit
122: is the unit number of the disk or tape,
123: and
124: .I minor
125: is the disk partition or tape file number.
126: Leading adaptor or controller numbers default to 0.
127: Normal line editing characters can be used when typing the file specification.
128: The following list of supported devices may vary from installation to
129: installation:
130: .LP
131: .ta 5 10
132: .nf
133: dk SMD or ESDI disks on VDDC or SMD-E
134: cy tape on Ciprico Tapemaster controller
135: .fi
136: .PP
137: For example,
138: to boot from a file system which starts at cylinder 0
139: of unit 0 of an SMD-E disk, type \*(lqdk(0,0)vmunix\*(rq
140: to the boot prompt; \*(lqdk(2,1,0)vmunix\*(rq
141: would specify drive 1 on SMD-E controller 2.
142: .PP
143: In an emergency, the bootstrap methods described in the paper
144: ``Installing and Operating 4.3BSD-tahoe UNIX on the Tahoe'' can be used
145: to boot from a distribution tape.
146: .SH FILES
147: .ta \w'/vmunix 'u
148: /vmunix system code
149: .br
150: /boot system bootstrap
151: .SH "SEE ALSO"
152: crash(8),
153: disklabel(8),
154: fsck(8),
155: halt(8),
156: init(8),
157: rc(8),
158: shutdown(8),
159: syslogd(8)
160: .SH BUGS
161: The disklabel format used by some versions of the console processor
162: is different than the format used by UNIX and the bootstrap.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.