Fixed formatting and expanded content
This commit is contained in:
parent
68c1a35cd9
commit
70eaf1d62a
|
@ -34,7 +34,7 @@
|
|||
.\" SUCH DAMAGE.
|
||||
.\"
|
||||
.\" from: @(#)reboot_sparc.8 5.4 (Berkeley) 7/23/91
|
||||
.\" $Id: reboot_pmax.8,v 1.1 1995/01/18 02:01:21 mellon Exp $
|
||||
.\" $Id: reboot_pmax.8,v 1.2 1995/01/18 06:12:48 mellon Exp $
|
||||
.\"
|
||||
.Dd July 23, 1991
|
||||
.Dt REBOOT 8
|
||||
|
@ -114,25 +114,23 @@ and unless this fails, the system will resume multi-user operations.
|
|||
At power up, all DECstation ROMs consult the
|
||||
.Nm haltaction
|
||||
environment
|
||||
variable in EEPROM to determine whether or not to autoboot. If this
|
||||
variable is set to
|
||||
.Fl h,
|
||||
the ROM presents a prompt on the console. If
|
||||
set to
|
||||
.Fl b,
|
||||
the ROM attempts to autoboot.
|
||||
variable in EEPROM to determine whether or not to attempt to boot
|
||||
automatically. If this
|
||||
variable is set to \fBh\fR, the ROM prints a prompt on the console and
|
||||
waits for user commands. If set to \fBb\fR, the ROM attempts to autoboot.
|
||||
.Pp
|
||||
On the DECstation 2100 and 3100, the autoboot path is stored in the
|
||||
On the DECstation 2100 and 3100, the path used for automatic booting is
|
||||
stored in the
|
||||
.Nm bootpath
|
||||
environment variable. The path is made up of a
|
||||
device type specifier (e.g., rz, tz, mop or tftp) followed by
|
||||
a triplet in the form (x, y, z), followed by a filename to load.
|
||||
a triplet in the form (x,y,z), followed by a filename to load.
|
||||
.Pp
|
||||
X is the controller (always 0), y is the SCSI id of the drive to
|
||||
Within the triplet, x is the controller (always 0), y is the SCSI id of
|
||||
the drive to
|
||||
boot from or 0 for net boots, and z is the partition to boot from
|
||||
(usually 0 for SCSI devices, always zero for network booting.
|
||||
Network boots may simply specify () since all three values are
|
||||
always zero.
|
||||
For network boots, () may be specified instead of (0,0,0).
|
||||
.Pp
|
||||
The filename is optional for bootp/tftp and mop booting, since in
|
||||
these cases the network protocol can be used to determine which
|
||||
|
@ -141,26 +139,61 @@ specified, and when booting off of disk, the filename of a kernel
|
|||
must be specified. Generally, the kernel is named
|
||||
.Nm netbsd.
|
||||
.Pp
|
||||
For autoboots, the ROM automatically passes a
|
||||
.Fl -a
|
||||
An example bootpath setting would be:
|
||||
.nf
|
||||
.sp 1
|
||||
.ce 1
|
||||
setenv bootpath rz(0,1,0)netbsd
|
||||
.fi
|
||||
.Pp
|
||||
For automatic boots, the ROM automatically passes a
|
||||
.Fl a
|
||||
argument to the boot
|
||||
loader, indicating an autoboot. If booting is invoked manually,
|
||||
the
|
||||
.Fl -a
|
||||
argument is passed only when the
|
||||
loader, requesting that
|
||||
.Tn NetBSD
|
||||
attempt to come up to multi-user mode. At the boot ROM prompt,
|
||||
the user may boot
|
||||
.Tn NetBSD
|
||||
with either the
|
||||
.Nm auto
|
||||
command is used.
|
||||
or the
|
||||
.Nm boot
|
||||
command. If the
|
||||
.Nm auto
|
||||
command is used, the
|
||||
.Fl a
|
||||
argument is passed to the kernel, requesting a multi-user boot; otherwise
|
||||
the
|
||||
.Fl s
|
||||
argument is passed, requesting that
|
||||
.Tn NetBSD
|
||||
boot to single user mode.
|
||||
.Pp
|
||||
When either the
|
||||
.Nm boot
|
||||
or the
|
||||
.Nm auto
|
||||
command is issued with no arguments, the kernel specified in the bootpath
|
||||
environment variable is booted. An alternate kernel may be specified
|
||||
with the
|
||||
.Fl f
|
||||
flag, followed by the path of the kernel to boot, as described above.
|
||||
For example:
|
||||
.sp 1
|
||||
.ce 1
|
||||
boot -f rz(0,4,0)netbsd.new
|
||||
.Pp
|
||||
On TurboChannel machines (all DECstation 5000 models), the boot path
|
||||
is specified in the boot environment variable, along with any arguments
|
||||
to be passed to the kernel. Note that to specify boot arguments (e.g.,
|
||||
.Fl -a
|
||||
) when setting the
|
||||
.Fl a)
|
||||
when setting the
|
||||
.Nm boot
|
||||
environment variable, the filename and arguments
|
||||
must be enclosed in quotes. For example:
|
||||
.nf
|
||||
.sp 1
|
||||
.ce 1
|
||||
setenv boot "3/rz4/netbsd -a"
|
||||
.fi
|
||||
.Pp
|
||||
|
@ -182,6 +215,20 @@ disks or tz# for tapes, where # is the SCSI id of the device. For network
|
|||
devices, the option-specific protocol identifier is either mop or tftp.
|
||||
Filename requirements are as for the DECstation 2100 and 3100.
|
||||
.Pp
|
||||
To start
|
||||
.Tn NetBSD
|
||||
from the boot prompt, the
|
||||
.Nm boot
|
||||
command must be used. With no arguments, this simply boots the default
|
||||
kernel with the default arguments as set with
|
||||
.Nm setenv
|
||||
.Nm boot.
|
||||
If no boot environment variable is set or if an alternate kernel is to be
|
||||
booted, the path of that kernel may be specified after the boot command as
|
||||
described above, and any arguments may be passed similarly. For example:
|
||||
.sp 1
|
||||
.ce 1
|
||||
boot 3/rz4/netbsd.new -a
|
||||
.Sh SEE ALSO
|
||||
.Xr crash 8m ,
|
||||
.Xr fsck 8 ,
|
||||
|
|
Loading…
Reference in New Issue