cloned from vax version

SCCS-vsn: sbin/reboot/boot_tahoe.8 6.1

diff --git a/usr/src/sbin/reboot/boot_tahoe.8 b/usr/src/sbin/reboot/boot_tahoe.8
new file mode 100644 (file)
index 0000000..e9e722d
--- /dev/null
+++ b/usr/src/sbin/reboot/boot_tahoe.8
@@ -0,0 +1,149 @@
+.\" Copyright (c) 1980 Regents of the University of California.
+.\" All rights reserved.  The Berkeley software License Agreement
+.\" specifies the terms and conditions for redistribution.
+.\"
+.\"    @(#)boot_tahoe.8        6.1 (Berkeley) %G%
+.\"
+.TH REBOOT 8 ""
+.UC 4
+.SH NAME
+reboot \- UNIX bootstrapping procedures
+.SH SYNOPSIS
+.B /etc/reboot
+[
+.B \-n
+] [
+.B \-q
+]
+.SH DESCRIPTION
+.PP
+UNIX is started by placing it in memory
+at location zero and transferring to the entry point.
+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 UNIX 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 allows the system
+to perform other shutdown activities such as resynchronizing
+hardware time-of-day clocks.
+A multi-user reboot (as described below) is then 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
+.I Reboot
+normally logs the reboot using
+.IR syslog (8)
+and places a shutdown record in the login accounting file
+/usr/adm/wtmp.
+These actions are inhibited if the
+.B \-n
+or
+.B \-q
+options are present.
+.PP
+.B "Power fail and crash recovery."
+Normally, the system will reboot itself at power-up or after crashes.
+An automatic consistency check of the file systems will be performed
+as described in
+.IR fsck (8).
+and unless this fails, the system will resume multi-user operations.
+.PP
+.B Cold starts.
+These are processor-type dependent.
+On the CCI Power 6/32 and related processors,
+the system will do a standard autoboot from drive 0
+upon power-up or reset.
+This automatic boot may be cancelled by typing a \*(lq#\*(rq
+in the first few seconds after reset.
+This enters console mode; the console prompt is \*(lq>\*(rq or \*(lq#>\*(rq.
+The boot flags can be set to any hexadecimal value \fIn\fP with the command
+.IP
+#> p23 \fIn\fP.
+.LP
+The default device may be examined or set; see the Diagnostics and Debugging
+manual for the processor for details on device naming and syntax.
+After setting the boot flags and/or device,
+a bootstrap sequence can be initiated with
+.IP
+#> fb
+.LP
+A specific device or bootstrap file may be used; for example,
+.IP
+#> fb xfd(1,0)
+.LP
+would boot from the `a' partition on XFD drive 1.
+.PP
+The file specifications used for the boostrap
+when loaded with the \*(lqaskme\*(rq flag
+(register 23 set to 1 or 3)
+are of the form:
+.IP
+device(adaptor,controller,unit,minor)
+.PP
+where
+.I device
+is the type of the device to be searched,
+.I adaptor
+is number of the VERSAbus (or VMEbus) to which the device is attached,
+.I controller
+is the unit number of the controller on that buss,
+.I unit
+is the unit number of the disk or tape,
+and
+.I minor
+is the disk partition or tape file number.
+Leading adaptor or controller numbers default to 0.
+Normal line editing characters can be used when typing the file specification.
+The following list of supported devices may vary from installation to
+installation:
+.LP
+.ta 5 10
+.nf
+       dk      SMD or ESDI disks on VDDC or SMD-E
+       cy      tape on Ciprico Tapemaster controller
+.fi
+.PP
+For example,
+to boot from a file system which starts at cylinder 0
+of unit 0 of an SMD-E disk, type \*(lqdk(0,0)vmunix\*(rq
+to the boot prompt; \*(lqdk(2,1,0)vmunix\*(rq
+would specify drive 1 on SMD-E controller 2.
+.PP
+In an emergency, the bootstrap methods described in the paper
+``Installing and Operating 4.3BSD-tahoe UNIX on the Tahoe'' can be used
+to boot from a distribution tape.
+.SH FILES
+.ta \w'/vmunix   'u
+/vmunix        system code
+.br
+/boot  system bootstrap
+.SH "SEE ALSO"
+crash(8),
+disklabel(8),
+fsck(8),
+halt(8),
+init(8),
+rc(8),
+shutdown(8),
+syslogd(8)
+.SH BUGS
+The disklabel format used by some versions of the console processor
+is different than the format used by UNIX and the bootstrap.