diff options
author | Michael Shalayeff <mickey@cvs.openbsd.org> | 2000-11-09 15:39:08 +0000 |
---|---|---|
committer | Michael Shalayeff <mickey@cvs.openbsd.org> | 2000-11-09 15:39:08 +0000 |
commit | fa5ba76a2b5340a16f854608c0428a4a55090aa3 (patch) | |
tree | 3721b33abbc4edcb59ccf2633c1ffb5ed1faa95b | |
parent | 0283e694bb405a5173965f525b0e096770913b43 (diff) |
it's been moved
-rw-r--r-- | sbin/reboot/boot_pmax.8 | 213 |
1 files changed, 0 insertions, 213 deletions
diff --git a/sbin/reboot/boot_pmax.8 b/sbin/reboot/boot_pmax.8 deleted file mode 100644 index a04839ef053..00000000000 --- a/sbin/reboot/boot_pmax.8 +++ /dev/null @@ -1,213 +0,0 @@ -.\" $OpenBSD: boot_pmax.8,v 1.15 2000/03/18 22:56:03 aaron Exp $ -.\" $NetBSD: boot_pmax.8,v 1.1 1995/04/25 23:55:11 mellon Exp $ -.\" -.\" Copyright (c) 1990, 1991 The Regents of the University of California. -.\" All rights reserved. -.\" -.\" This code is derived from software contributed to Berkeley by -.\" the Systems Programming Group of the University of Utah Computer -.\" Science Department. -.\" -.\" 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. -.\" -.\" 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. -.\" -.Dd July 23, 1991 -.Dt BOOT_PMAX 8 pmax -.Os -.Sh NAME -.Nm boot -.Nd -.Tn sparc-specific -system bootstrapping procedures -.Sh DESCRIPTION -The -.Ox -kernel is started by placing it at the beginning of physical memory -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 -.Ss Power fail and crash recovery -Normally, the system will boot itself at power-up or after crashes. -An automatic consistency check of the file systems will be performed, -and unless this fails, the system will resume multi-user operations. -.Pp -.Ss Cold starts -At power up, all DECstation ROMs consult the -.Nm haltaction -environment -variable in EEPROM to determine whether or not to attempt an automatic -boot. -If this variable is set to -.Dq h , -the ROM prints a prompt on the console and -waits for user commands. -If set to -.Dq b , -the ROM attempts to autoboot. -.Pp -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. -.Pp -Within the triplet, -.Dq x -is the controller (always 0), -.Dq y -is the SCSI ID of -the drive to -boot from or 0 for net boots, and -.Dq z -is the partition to boot from -(usually 0 for SCSI devices, always zero for network booting). -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 -file to boot. -When booting off the tape, no filename should be -specified, and when booting off disk, the filename of a kernel -must be specified. -Generally, the kernel is named -.Pa bsd . -.Pp -An example -.Nm bootpath -setting would be: -.Pp -.Dl setenv bootpath rz(0,1,0)bsd -.Pp -For automatic boots, the ROM automatically passes a -.Fl a -argument to the bootloader, -requesting that -.Ox -attempt to come up to multi-user mode. -At the boot ROM prompt, the user may boot -.Ox -with either the -.Nm auto -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 -.Ox -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 -.Nm 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: -.Pp -.Dl boot -f rz(0,4,0)bsd.new -.Pp -On TurboChannel machines (all DECstation 5000 models), the bootpath -is specified in the -.Nm 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 -.Nm boot -environment variable, the filename and arguments -must be enclosed in quotes. -For example: -.Pp -.Dl setenv boot "3/rz4/bsd -a" -.Pp -The device from which to boot is specified as the TurboChannel slot -number, a TurboChannel-option-specific device name, and a path to the -file to load, all separated by slashes. -You can get a list of the -devices installed in your TurboChannel slots (as well as any built-in -devices which appear as TurboChannel slots) by typing the -.Nm cnfg -command -at the boot prompt. -You can get more detailed information about a specific -TurboChannel option by typing -.Nm cnfg -followed by the slot number of that -option. -.Pp -For SCSI devices, the option-specific device identifier is either -.Dq rz# -for disks or -.Dq 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 -.Ox -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 -.Nm 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: -.Pp -.Dl boot 3/rz4/bsd.new -a -.Sh SEE ALSO -.Xr crash 8 , -.Xr fsck 8 , -.Xr halt 8 , -.Xr init 8 , -.Xr newfs 8 , -.Xr rc 8 , -.Xr reboot 8 , -.Xr shutdown 8 , -.Xr syslogd 8 |