Return to reboot.8 CVS log

Up to [Power 6/32 Unix Tahoe 4.2BSD] / cci / usr / src / man / man8

Power 6/32 Unix version 1.2b

.TH REBOOT 8 "10 May 1981"
.UC 4
.SH NAME
reboot \- OSPower bootstrapping procedures
.SH SYNOPSIS
.B /etc/reboot
[
.B \-n
] [
.B \-q
]
.SH DESCRIPTION
.PP
OSPower is started by placing it in memory
at location 0x800 and transferring to 0x800.
Since the system is not reenterable,
it is necessary to read it in from disk or tape
each time it is to be bootstrapped.
.PP
.B Rebooting a running system.
When a OSPower is running and a reboot is desired,
.IR shutdown (8)
is normally used.
If there are no users then
.B /etc/reboot
can be used.
Reboot causes the disks to be synced, and then a multi-user
reboot (as described below) is initiated.  This causes a system to be
booted and an automatic disk check to be performed.  If all this succeeds
without incident, the system is then brought up for many users.
.PP
Options to reboot are:
.TP
.B \-n
option avoids the sync.  It can be used if a disk or the processor
is on fire. 
.TP
.B \-q
reboots quickly and ungracefully, without shutting down running
processes first.
.PP
.B "Power fail and crash recovery."
Normally, the system will attempt to reboot itself at power-up or after crashes.
An automatic consistency check of the file systems will be performed
then and unless this fails the system will resume multi-user operations.
.PP
.B Cold starts.
.br
These are processor type dependent.
On the Power 6/32, the front panel PROM takes care of initialization
and power-up confidence checks,
then tries to load and execute
.I /boot;
if that fails, a boot from the console is still possible.
.PP
Giving the command
.IP
>fb.
or
.IP
>fr /boot
.LP
Would boot the system from (e.g.) an FSD and run the automatic consistency
check as described in
.IR fsck (8).
(Note that it may
be necessary to type `<return>~h'
to gain the attention of the panel processor before getting the > prompt.)
.PP
To boot with boot flags you
may specify
.IP
>gb \fIn\fR
.LP
where, giving a \fIn\fR of 1 causes the boot program
to ask for the name of the system to be bootstrapped,
giving a \fIn\fR of 2 causes the boot program to come up single
user, and a \fIn\fR of 3 causes both of these actions to occur.
.PP
The 
.I boot
program
finds the corresponding file on the given device, loads that file
into memory location 0x800, and starts the program at the entry address
specified in the program header (after clearing off the high bits
of the specified entry address.)
Normal line editing characters can be used in specifying the pathname.
.PP
A device specification has the following form:
.IP
device(unit, minor)
.PP
where
.I device
is the type of the device to be searched,
.I unit
is the unit number of the device,
and
.I minor
is the minor device index.
The following list of supported devices may vary from installation to
installation:
.ta 5 10
.nf
	fsd	FSD disk drive
	xmd	SMD disk drive
	xsd	XFSD disk drive
	cyp	CYPHER tape drive
.fi
.PP
For tapes, the minor device number gives a file offset.
.SH FILES
.ta \w'/vmunix   'u
/vmunix	system code
.br
/boot	system bootstrap
.br
/poc	power-up confidence tests
.br
/wcs	microcode writable control storage
.SH "SEE ALSO"
crash(8V),
fsck(8),
init(8),
rc(8),
shutdown(8),
halt(8),
newfs(8)
.br
Console Processor handbook

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.