![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to reboot.8 CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [CSRG BSD Unix] / 43BSDTahoe / man / man8 / tahoe|
Return to reboot.8 CVS log | Up to [CSRG BSD Unix] / 43BSDTahoe / man / man8 / tahoe |
1.1 root 1: .\" Copyright (c) 1980 Regents of the University of California.
2: .\" All rights reserved. The Berkeley software License Agreement
3: .\" specifies the terms and conditions for redistribution.
4: .\"
5: .\" @(#)reboot.8 6.1 (Berkeley) 7/12/88
6: .\"
7: .TH REBOOT 8 "July 12, 1988"
8: .UC 4
9: .SH NAME
10: reboot \- UNIX bootstrapping procedures
11: .SH SYNOPSIS
12: .B /etc/reboot
13: [
14: .B \-n
15: ] [
16: .B \-q
17: ]
18: .SH DESCRIPTION
19: .PP
20: UNIX is started by placing it in memory
21: at location zero and transferring to the entry point.
22: Since the system is not reenterable,
23: it is necessary to read it in from disk or tape
24: each time it is to be bootstrapped.
25: .PP
26: .B Rebooting a running system.
27: When a UNIX is running and a reboot is desired,
28: .IR shutdown (8)
29: is normally used.
30: If there are no users then
31: .B /etc/reboot
32: can be used.
33: Reboot causes the disks to be synced and allows the system
34: to perform other shutdown activities such as resynchronizing
35: hardware time-of-day clocks.
36: A multi-user reboot (as described below) is then initiated.
37: This causes a system to be
38: booted and an automatic disk check to be performed. If all this succeeds
39: without incident, the system is then brought up for many users.
40: .PP
41: Options to reboot are:
42: .TP
43: .B \-n
44: option avoids the sync. It can be used if a disk or the processor
45: is on fire.
46: .TP
47: .B \-q
48: reboots quickly and ungracefully, without shutting down running
49: processes first.
50: .PP
51: .I Reboot
52: normally logs the reboot using
53: .IR syslog (8)
54: and places a shutdown record in the login accounting file
55: /usr/adm/wtmp.
56: These actions are inhibited if the
57: .B \-n
58: or
59: .B \-q
60: options are present.
61: .PP
62: .B "Power fail and crash recovery."
63: Normally, the system will reboot itself at power-up or after crashes.
64: An automatic consistency check of the file systems will be performed
65: as described in
66: .IR fsck (8).
67: and unless this fails, the system will resume multi-user operations.
68: .PP
69: .B Cold starts.
70: These are processor-type dependent.
71: On the CCI Power 6/32 and related processors,
72: the system will do a standard autoboot from drive 0
73: upon power-up or reset.
74: This automatic boot may be cancelled by typing a \*(lq#\*(rq
75: in the first few seconds after reset.
76: This enters console mode; the console prompt is \*(lq>\*(rq or \*(lq#>\*(rq.
77: The boot flags can be set to any hexadecimal value \fIn\fP with the command
78: .IP
79: #> p23 \fIn\fP.
80: .LP
81: The default device may be examined or set; see the Diagnostics and Debugging
82: manual for the processor for details on device naming and syntax.
83: After setting the boot flags and/or device,
84: a bootstrap sequence can be initiated with
85: .IP
86: #> fb
87: .LP
88: A specific device or bootstrap file may be used; for example,
89: .IP
90: #> fb xfd(1,0)
91: .LP
92: would boot from the `a' partition on XFD drive 1.
93: .PP
94: The file specifications used for the boostrap
95: when loaded with the \*(lqaskme\*(rq flag
96: (register 23 set to 1 or 3)
97: are of the form:
98: .IP
99: device(adaptor,controller,unit,minor)
100: .PP
101: where
102: .I device
103: is the type of the device to be searched,
104: .I adaptor
105: is number of the VERSAbus (or VMEbus) to which the device is attached,
106: .I controller
107: is the unit number of the controller on that buss,
108: .I unit
109: is the unit number of the disk or tape,
110: and
111: .I minor
112: is the disk partition or tape file number.
113: Leading adaptor or controller numbers default to 0.
114: Normal line editing characters can be used when typing the file specification.
115: The following list of supported devices may vary from installation to
116: installation:
117: .LP
118: .ta 5 10
119: .nf
120: dk SMD or ESDI disks on VDDC or SMD-E
121: cy tape on Ciprico Tapemaster controller
122: .fi
123: .PP
124: For example,
125: to boot from a file system which starts at cylinder 0
126: of unit 0 of an SMD-E disk, type \*(lqdk(0,0)vmunix\*(rq
127: to the boot prompt; \*(lqdk(2,1,0)vmunix\*(rq
128: would specify drive 1 on SMD-E controller 2.
129: .PP
130: In an emergency, the bootstrap methods described in the paper
131: ``Installing and Operating 4.3BSD-tahoe UNIX on the Tahoe'' can be used
132: to boot from a distribution tape.
133: .SH FILES
134: .ta \w'/vmunix 'u
135: /vmunix system code
136: .br
137: /boot system bootstrap
138: .SH "SEE ALSO"
139: crash(8),
140: disklabel(8),
141: fsck(8),
142: halt(8),
143: init(8),
144: rc(8),
145: shutdown(8),
146: syslogd(8)
147: .SH BUGS
148: The disklabel format used by some versions of the console processor
149: 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.