![[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 [Power 6/32 Unix Tahoe 4.2BSD] / cci / usr / src / man / man8|
Return to reboot.8 CVS log | Up to [Power 6/32 Unix Tahoe 4.2BSD] / cci / usr / src / man / man8 |
1.1 root 1: .TH REBOOT 8 "10 May 1981"
2: .UC 4
3: .SH NAME
4: reboot \- OSPower bootstrapping procedures
5: .SH SYNOPSIS
6: .B /etc/reboot
7: [
8: .B \-n
9: ] [
10: .B \-q
11: ]
12: .SH DESCRIPTION
13: .PP
14: OSPower is started by placing it in memory
15: at location 0x800 and transferring to 0x800.
16: Since the system is not reenterable,
17: it is necessary to read it in from disk or tape
18: each time it is to be bootstrapped.
19: .PP
20: .B Rebooting a running system.
21: When a OSPower is running and a reboot is desired,
22: .IR shutdown (8)
23: is normally used.
24: If there are no users then
25: .B /etc/reboot
26: can be used.
27: Reboot causes the disks to be synced, and then a multi-user
28: reboot (as described below) is initiated. This causes a system to be
29: booted and an automatic disk check to be performed. If all this succeeds
30: without incident, the system is then brought up for many users.
31: .PP
32: Options to reboot are:
33: .TP
34: .B \-n
35: option avoids the sync. It can be used if a disk or the processor
36: is on fire.
37: .TP
38: .B \-q
39: reboots quickly and ungracefully, without shutting down running
40: processes first.
41: .PP
42: .B "Power fail and crash recovery."
43: Normally, the system will attempt to reboot itself at power-up or after crashes.
44: An automatic consistency check of the file systems will be performed
45: then and unless this fails the system will resume multi-user operations.
46: .PP
47: .B Cold starts.
48: .br
49: These are processor type dependent.
50: On the Power 6/32, the front panel PROM takes care of initialization
51: and power-up confidence checks,
52: then tries to load and execute
53: .I /boot;
54: if that fails, a boot from the console is still possible.
55: .PP
56: Giving the command
57: .IP
58: >fb.
59: or
60: .IP
61: >fr /boot
62: .LP
63: Would boot the system from (e.g.) an FSD and run the automatic consistency
64: check as described in
65: .IR fsck (8).
66: (Note that it may
67: be necessary to type `<return>~h'
68: to gain the attention of the panel processor before getting the > prompt.)
69: .PP
70: To boot with boot flags you
71: may specify
72: .IP
73: >gb \fIn\fR
74: .LP
75: where, giving a \fIn\fR of 1 causes the boot program
76: to ask for the name of the system to be bootstrapped,
77: giving a \fIn\fR of 2 causes the boot program to come up single
78: user, and a \fIn\fR of 3 causes both of these actions to occur.
79: .PP
80: The
81: .I boot
82: program
83: finds the corresponding file on the given device, loads that file
84: into memory location 0x800, and starts the program at the entry address
85: specified in the program header (after clearing off the high bits
86: of the specified entry address.)
87: Normal line editing characters can be used in specifying the pathname.
88: .PP
89: A device specification has the following form:
90: .IP
91: device(unit, minor)
92: .PP
93: where
94: .I device
95: is the type of the device to be searched,
96: .I unit
97: is the unit number of the device,
98: and
99: .I minor
100: is the minor device index.
101: The following list of supported devices may vary from installation to
102: installation:
103: .ta 5 10
104: .nf
105: fsd FSD disk drive
106: xmd SMD disk drive
107: xsd XFSD disk drive
108: cyp CYPHER tape drive
109: .fi
110: .PP
111: For tapes, the minor device number gives a file offset.
112: .SH FILES
113: .ta \w'/vmunix 'u
114: /vmunix system code
115: .br
116: /boot system bootstrap
117: .br
118: /poc power-up confidence tests
119: .br
120: /wcs microcode writable control storage
121: .SH "SEE ALSO"
122: crash(8V),
123: fsck(8),
124: init(8),
125: rc(8),
126: shutdown(8),
127: halt(8),
128: newfs(8)
129: .br
130: Console Processor handbook
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.