BSD 4_4_Lite1 release

[unix-history] / usr / src / sbin / reboot / boot_tahoe.8

diff --git a/usr/src/sbin/reboot/boot_tahoe.8 b/usr/src/sbin/reboot/boot_tahoe.8
index 57f5b54..01c7f81 100644 (file)
--- a/usr/src/sbin/reboot/boot_tahoe.8
+++ b/usr/src/sbin/reboot/boot_tahoe.8
@@ -1,150 +1,152 @@
-.\" Copyright (c) 1980 The Regents of the University of California.
-.\" All rights reserved.
+.\" Copyright (c) 1980, 1991, 1993
+.\"    The Regents of the University of California.  All rights reserved.

 .\"
 .\"

-.\" %sccs.include.redist.man%
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"    This product includes software developed by the University of
+.\"    California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.

 .\"
 .\"

-.\"    @(#)boot_tahoe.8        6.3 (Berkeley) %G%
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.

 .\"
 .\"

-.TH REBOOT 8 ""
-.UC 4
-.SH NAME
-reboot \- UNIX bootstrapping procedures
-.SH SYNOPSIS
-.B 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 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
-/var/log/wtmp.
-These actions are inhibited if the
-.B \-n
-or
-.B \-q
-options are present.
-.PP
-.B "Power fail and crash recovery."
+.\"     @(#)boot_tahoe.8       8.2 (Berkeley) 4/19/94
+.\"
+.Dd April 19, 1994
+.Dt BOOT 8 tahoe
+.Os
+.Sh NAME
+.Nm boot
+.Nd
+system bootstrapping procedures
+.Sh DESCRIPTION
+.Sy Power fail and crash recovery.

 Normally, the system will reboot itself at power-up or after crashes.
 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).
+An automatic consistency check of the file systems will be performed,

 and unless this fails, the system will resume multi-user operations.
 and unless this fails, the system will resume multi-user operations.

-.PP
-.B Cold starts.
+.Pp
+.Sy Cold starts.

 These are processor-type dependent.
 These are processor-type dependent.

-On the CCI Power 6/32 and related processors,
+On the
+.Tn CCI
+Power 6/32 and related processors,

 the system will do a standard autoboot from drive 0
 upon power-up or reset.
 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
+This automatic boot may be cancelled by typing a
+.Ql \&#

 in the first few seconds after reset.
 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
+This enters console mode; the console prompt is
+.Ql >
+or
+.Ql \&# .
+The boot flags can be set to any hexadecimal value
+.Fl n
+with the command
+.Pp
+.Bd -filled -offset indent -compact
+.Li \&#> p23
+.Ar n .
+.Ed
+.Pp

 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
 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
+.Pp
+.Dl #> fb
+.Pp

 A specific device or bootstrap file may be used; for example,
 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
+.Pp
+.Dl \&#> \&fb xfd(1,0)
+.Pp
+would boot from the `a' partition on
+.Tn XFD
+drive 1.
+.Pp

 The file specifications used for the boostrap
 The file specifications used for the boostrap

-when loaded with the \*(lqaskme\*(rq flag
+when loaded with the
+.Dq askme
+flag

 (register 23 set to 1 or 3)
 are of the form:
 (register 23 set to 1 or 3)
 are of the form:

-.IP
-device(adaptor,controller,unit,minor)
-.PP
+.Pp
+.Dl device(adaptor,controller,unit,minor)
+.Pp

 where
 where

-.I device
+.Ar device

 is the type of the device to be searched,
 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
+.Ar adaptor
+is number of the
+.Tn VERSAbus
+(or
+.Tn VMEbus )
+to which the device is attached,
+.Ar controller

 is the unit number of the controller on that buss,
 is the unit number of the controller on that buss,

-.I unit
+.Ar unit

 is the unit number of the disk or tape,
 and
 is the unit number of the disk or tape,
 and

-.I minor
+.Ar 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:
 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
+.Pp
+.Bd -unfilled -offset indent -compact
+dk     SMD or ESDI disks on VDDC or SMD-E
+cy     tape on Ciprico Tapemaster controller
+.Ed
+.Pp

 For example,
 to boot from a file system which starts at cylinder 0
 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
+of unit 0 of an
+.Tn SMD-E
+disk, type
+.Ql dk(0,0)vmunix
+to the boot prompt;
+.Ql dk(2,1,0)vmunix
+would specify drive 1 on
+.Tn SMD-E
+controller 2.
+.Pp

 In an emergency, the bootstrap methods described in the paper
 In an emergency, the bootstrap methods described in the paper

-``Installing and Operating 4.3BSD-tahoe UNIX on the Tahoe'' can be used
+.%T "Installing and Operating 4.3 BSD-tahoe UNIX on the Tahoe"
+can be used

 to boot from a distribution tape.
 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
+.Sh FILES
+.Bl -tag -width /vmunix -compact
+.It Pa /vmunix
+system code
+.It Pa /boot
+system bootstrap
+.El
+.Sh SEE ALSO
+.Xr halt 8 ,
+.Xr reboot 8 ,
+.Xr shutdown 8
+.Sh BUGS

 The disklabel format used by some versions of the console processor
 The disklabel format used by some versions of the console processor

-is different than the format used by UNIX and the bootstrap.
+is different than the format used by
+.Tn UNIX
+and the bootstrap.
+.Sh HISTORY