incomplete work. moved them, repaired some, it is a giant mess

27 files changed, 1704 insertions, 497 deletions

diff --git a/share/man/man8/Makefile b/share/man/man8/Makefile
index 229358e083b..d947fc0d3ea 100644
--- a/share/man/man8/Makefile
+++ b/share/man/man8/Makefile
@@ -1,4 +1,4 @@
-#	$OpenBSD: Makefile,v 1.30 2000/10/26 00:46:17 miod Exp $
+#	$OpenBSD: Makefile,v 1.31 2000/11/09 03:57:33 deraadt Exp $
 #	$NetBSD: Makefile,v 1.13 1996/03/28 21:36:40 mark Exp $
 #	@(#)Makefile	8.1 (Berkeley) 6/5/93
 
@@ -7,8 +7,8 @@ MAN=	afterboot.8 compat_bsdos.8 compat_freebsd.8 compat_ibcs2.8 \
 	compat_svr4.8 compat_ultrix.8 crash.8 dhcp.8 diskless.8 intro.8 rc.8 \
 	rc.conf.8 rc.shutdown.8 ssl.8 sticky.8 update.8 yp.8 boot_config.8 \
 	vpn.8 release.8
-SUBDIR=	man8.amiga man8.hp300 man8.i386 man8.mac68k man8.sparc man8.sun3 \
-	man8.vax
+SUBDIR=	man8.alpha man8.amiga man8.hp300 man8.i386 man8.mac68k man8.mvme68k \
+	man8.powerpc man8.sparc man8.sun3 man8.vax
 
 MLINKS=	afterboot.8 faq.8 \
 	boot_config.8 UKC.8 \
diff --git a/share/man/man8/man8.alpha/Makefile b/share/man/man8/man8.alpha/Makefile
new file mode 100644
index 00000000000..ba7a31765d7
--- /dev/null
+++ b/share/man/man8/man8.alpha/Makefile
@@ -0,0 +1,9 @@
+#	@(#)Makefile	5.1 (Berkeley) 3/22/91
+#	$NetBSD: Makefile,v 1.3 1995/09/06 21:36:38 jtc Exp $
+
+MAN=	boot_alpha.8
+#MAN=	MAKEDEV.8 boot_alpha.8
+#MLINKS=	MAKEDEV.8 makedev.8
+MANSUBDIR=/alpha
+
+.include <bsd.prog.mk>
diff --git a/share/man/man8/man8.alpha/boot_alpha.8 b/share/man/man8/man8.alpha/boot_alpha.8
new file mode 100644
index 00000000000..40d8c80a28d
--- /dev/null
+++ b/share/man/man8/man8.alpha/boot_alpha.8
@@ -0,0 +1,156 @@
+.\" $NetBSD: boot.8,v 1.3 2000/06/14 17:25:48 cgd Exp $
+.\"
+.\" Copyright (c) 1999 Christopher G. Demetriou
+.\" All rights reserved.
+.\" 
+.\" 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 for the
+.\"          NetBSD Project.  See http://www.netbsd.org/ for
+.\"          information about NetBSD.
+.\" 4. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission.
+.\" 
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``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 AUTHOR 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.
+.\" 
+.\" <<Id: LICENSE,v 1.2 2000/06/14 15:57:33 cgd 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.
+.\"
+.\"     @(#)boot_hp300.8        8.2 (Berkeley) 4/19/94
+.\"
+.Dd April 5, 1999
+.Dt BOOT 8 alpha
+.Os
+.Sh NAME
+.Nm boot
+.Nd Alpha system bootstrapping procedures
+.Sh DESCRIPTION
+When the
+.Ox
+.Ns Tn /alpha
+kernel is booted normally
+it initializes itself and proceeds to start the system.  An automatic
+consistency check of the file systems takes place, and unless this
+fails, the system comes up to multi-user operation.  The proper way
+to shut the system down is with the
+.Xr shutdown 8
+command.
+.Pp
+If the system crashes, it will enter the kernel debugger,
+.Xr ddb 8 ,
+if it is configured in the kernel.
+If the crash occurred during
+initialization and the debugger is not present or is exited, the
+kernel will halt the system.
+If the crash occurred during normal operation and the debugger
+is not present or is exited, the system will attempt a dump to the
+configured dump device (which will be automatically recovered with
+.Xr savecore 8
+during the next boot cycle), and after the dump is complete (successful
+or not) the kernel will attempt a reboot.
+.\" XXX .Pp
+.\" XXX .Ss Use of SRM Console
+.\" XXX .Pp
+.\" XXX console is used to bootstrap system
+.\" XXX .Pp
+.\" XXX boot flags, boot file
+.\" XXX .Pp
+.\" XXX console device names
+.\" XXX .Pp
+.\" XXX .Ss Console Behavior at Power-on, Halt, and Reboot
+.\" XXX .Pp
+.\" XXX auto_action variable
+.\" XXX .Pp
+.\" XXX .Ss System Bootstrapping Procedure
+.\" XXX .Pp
+.\" XXX boot environment
+.\" XXX .Pp
+.\" XXX primary/secondary vs. unified bootstrap
+.Sh FILES
+.Bl -tag -width /usr/mdec/bootxx -compact
+.It Pa /bsd
+default system kernel
+.It Pa /usr/mdec/bootxx
+primary bootstrap for
+.Dq ffs
+file system
+(Berkeley Fast File System)
+.It Pa /usr/mdec/boot
+secondary bootstrap
+.It Pa /usr/mdec/netboot
+network bootstrap
+.It Pa /boot
+secondary bootstrap (installed)
+.El
+.Sh SEE ALSO
+.Xr ddb 4 ,
+.Xr savecore 8 ,
+.Xr shutdown 8 ,
+.Xr installboot 8 ,
+.Xr mkbootimage 8 ,
+.Xr setnetbootinfo 8
+.Rs
+.%T "Alpha Architecture Reference Manual Third Edition"
+.%Q "Alpha Architecture Committee"
+.%I "Digital Press"
+.%D 1998
+.Re
+.Sh BUGS
+The device names used by
+.Ox
+.Ns Tn /alpha
+and the
+.Tn SRM Console
+often have no relation to each other.
diff --git a/share/man/man8/man8.amiga/MAKEDEV.8 b/share/man/man8/man8.amiga/MAKEDEV.8
index b977ea34168..35368666b49 100644
--- a/share/man/man8/man8.amiga/MAKEDEV.8
+++ b/share/man/man8/man8.amiga/MAKEDEV.8
@@ -1,5 +1,4 @@
-.\"	$NetBSD: MAKEDEV.8,v 1.3 1995/12/28 08:53:50 thorpej Exp $
-.\"
+.\"	$OpenBSD: MAKEDEV.8,v 1.6 2000/11/09 03:57:33 deraadt Exp $
 .\" Copyright (c) 1991 The Regents of the University of California.
 .\" All rights reserved.
 .\"
@@ -90,39 +89,31 @@ by a unit number.
 All known devices for the Amiga.
 .It Ar std
 The standard devices (console, drum, fd/*, klog, kmem, mem, null,
-reload, stderr, stdin, stdout, tty, zero)
+stderr, stdin, stdout, tty, zero)
 .It Ar local
 Configuration specific devices
 .El
 .Pp
 .Sy Device\-names
 .Bl -tag -width indent -compact
-.It Ar aconf
-Autoconfig information
 .It Ar bpf#
 Berkeley packet filters
-.It Ar grf#
-Graphic "frame buffers"
-.It Ar ite#
-Bit-mapped based character consoles
+.It Ar cd#
+SCSI CD-ROM drives
 .It Ar kbd
 The keyboard
 .It Ar lkm
 Loadable kernel modules.
 .It Ar mouse#
 Mouse ports
-.It Ar par#
-Parallel ports
 .It Ar pty#
 Set of 16 master and slave pseudo terminals
 .It Ar sd#
-SCSI disks drives
+SCSI disk drives
 .It Ar st#
 SCSI tape drives
 .It Ar tty#
-Serial ports
-.It Ar view#
-Abstract graphics interface to grf#'s
+Onboard Serial ports
 .It Ar vnd#
 "File" pseudo-disks
 .El
@@ -134,4 +125,5 @@ The special file directory.
 .Sh SEE ALSO
 .Xr intro 4 ,
 .Xr config 8 ,
-.Xr mknod 8
+.Xr mknod 8 ,
+.Xr special 8
diff --git a/share/man/man8/man8.amiga/Makefile b/share/man/man8/man8.amiga/Makefile
index 0bed09842b5..71e25624e37 100644
--- a/share/man/man8/man8.amiga/Makefile
+++ b/share/man/man8/man8.amiga/Makefile
@@ -1,7 +1,7 @@
 #	 @(#)Makefile	5.1 (Berkeley) 3/22/91
 #	$NetBSD: Makefile,v 1.3 1995/09/06 21:36:32 jtc Exp $
 
-MAN=	MAKEDEV.8
+MAN=	MAKEDEV.8 boot_amiga.8
 MLINKS=	MAKEDEV.8 makedev.8
 MANSUBDIR=/amiga
 
diff --git a/share/man/man8/man8.amiga/boot_amiga.8 b/share/man/man8/man8.amiga/boot_amiga.8
new file mode 100644
index 00000000000..05690a20b5a
--- /dev/null
+++ b/share/man/man8/man8.amiga/boot_amiga.8
@@ -0,0 +1,124 @@
+.\"	$OpenBSD: boot_amiga.8,v 1.1 2000/11/09 03:57:33 deraadt Exp $
+.\"	$NetBSD: boot_Amiga.8,v 1.1 1995/07/02 02:09:52 briggs 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.
+.\"
+.\"	From:
+.\"	@(#)boot_hp300.8	8.2 (Berkeley) 4/19/94
+.\"
+.Dd July 1, 1995
+.Dt BOOT_AMIGA 8 Amiga
+.Os
+.Sh NAME
+.Nm boot
+.Nd
+system bootstrapping procedures
+.Sh DESCRIPTION
+.Ss Power fail and crash recovery
+Normally, the
+.Ox
+kernel on the Amiga architecture is booted from the native operating
+system by means of an application program.
+When the kernel takes over,
+it initializes itself and proceeds to boot the system.
+An automatic
+consistency check of the file systems takes place, and unless this
+fails, the system comes up to multi-user operations.
+The proper way to shut the system down is with the
+.Xr shutdown 8
+command.
+.Pp
+If the system crashes, it will enter the kernel debugger,
+.Xr ddb 8 ,
+if it is configured in the kernel.
+If the debugger is not present
+or has exited, the system will attempt a dump to the
+configured dump device (which will be automatically recovered with
+.Xr savecore 8
+during the next boot cycle).
+After the dump completes (successful
+or not), the system will attempt a reboot.
+.Pp
+.Pp
+.Ss The boot application
+The boot application runs in the native OS on the system.
+It has a
+dialog where booting preferences may be changed and an option whereby
+these options may be saved.
+The preferences are stored in the program
+itself, not in a preferences folder, thus allowing two separate copies
+of the program to be configured differently (e.g., to boot different
+bsd or bsd.test, or to boot from two different drives).
+.Pp
+One option that may be specified is a boot to single-user mode.
+This stops the boot process very early on and allows system maintenance.
+If one wishes to provide some security at this phase of the boot, remove
+the
+.Dq secure
+option from ttye0 in the
+.Xr ttys 5
+file.
+.Pp
+Another useful option that may be specified is the
+.Dq serial console
+option.
+This will allow a serial device (terminal or computer) to
+act as a console for the system.
+This device must be configured to
+use 9600 baud, eight bits, no parity, and one stop bit (9600-8N1).
+Either the printer port or the modem port (tty01 and tty00,
+respectively) may be used for this.
+.Pp
+It is sometimes useful to boot a kernel that resides in a folder
+in native OS rather than from the usual location in the
+.Ox
+file system.
+A radio button is supplied for this purpose.
+Note that some programs will not run properly if the kernel is not found as
+.Pa /bsd
+within the
+.Ox
+file system.
+.Sh FILES
+.Bl -tag -width /bsd -compact
+.It Pa /bsd
+system kernel
+.El
+.Sh SEE ALSO
+.Xr ttys 5 ,
+.Xr ddb 8 ,
+.Xr savecore 8 ,
+.Xr shutdown 8
diff --git a/share/man/man8/man8.arm32/Makefile b/share/man/man8/man8.arm32/Makefile
index 081f482b3e8..b18b3a4e621 100644
--- a/share/man/man8/man8.arm32/Makefile
+++ b/share/man/man8/man8.arm32/Makefile
@@ -1,7 +1,7 @@
-#	$OpenBSD: Makefile,v 1.1 1996/04/22 01:28:17 deraadt Exp $
+#	$OpenBSD: Makefile,v 1.2 2000/11/09 03:57:33 deraadt Exp $
 #	from: @(#)Makefile	5.1 (Berkeley) 3/22/91
 
-MAN=	MAKEDEV.8
+MAN=	MAKEDEV.8 boot_arm32.8
 MLINKS=	MAKEDEV.8 makedev.8
 MANSUBDIR=/arm32
 
diff --git a/share/man/man8/man8.atari/Makefile b/share/man/man8/man8.atari/Makefile
index 342e1a7d398..00cfeceb47e 100644
--- a/share/man/man8/man8.atari/Makefile
+++ b/share/man/man8/man8.atari/Makefile
@@ -1,7 +1,7 @@
 #	$NetBSD: Makefile,v 1.1.1.1 1995/10/17 20:44:26 leo Exp $
 #
 
-MAN=	MAKEDEV.8
+MAN=	MAKEDEV.8 boot_atari.8
 MLINKS=	MAKEDEV.8 makedev.8
 MANSUBDIR=/atari
 
diff --git a/share/man/man8/man8.hp300/Makefile b/share/man/man8/man8.hp300/Makefile
index 79400d339b4..b155afeb812 100644
--- a/share/man/man8/man8.hp300/Makefile
+++ b/share/man/man8/man8.hp300/Makefile
@@ -1,7 +1,7 @@
 #	@(#)Makefile	5.2 (Berkeley) 3/22/91
 #	$NetBSD: Makefile,v 1.6 1995/09/06 21:36:34 jtc Exp $
 
-MAN=	MAKEDEV.8 crash.8 format.8
+MAN=	MAKEDEV.8 boot_hp300.8 format.8
 MLINKS=	MAKEDEV.8 makedev.8
 MANSUBDIR=/hp300
 
diff --git a/share/man/man8/man8.hp300/boot_hp300.8 b/share/man/man8/man8.hp300/boot_hp300.8
new file mode 100644
index 00000000000..db95572f6c9
--- /dev/null
+++ b/share/man/man8/man8.hp300/boot_hp300.8
@@ -0,0 +1,130 @@
+.\"	$OpenBSD: boot_hp300.8,v 1.1 2000/11/09 03:57:34 deraadt Exp $
+.\"	$NetBSD: boot_hp300.8,v 1.3 1995/04/23 10:33:34 cgd Exp $
+.\"
+.\" Copyright (c) 1990, 1991, 1993
+.\"	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.
+.\"
+.\"	@(#)boot_hp300.8	8.2 (Berkeley) 4/19/94
+.\"
+.Dd April 19, 1994
+.Dt BOOT_HP300 8 hp300
+.Os
+.Sh NAME
+.Nm boot
+.Nd
+.Tn hp300-specific
+system bootstrapping procedures
+.Sh DESCRIPTION
+.Ss 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,
+and unless this fails, the system will resume multi-user operations.
+.Pp
+.Ss Cold starts
+On an HP300, the boot procedure uses the boot ROM to load a boot program
+from an
+.Tn LIF
+format directory at the beginning of an attached disk.
+The
+.Pa /usr/mdec
+directory contains a disk boot program
+.Pa ( /usr/mdec/bootsd
+or
+.Pa /usr/mdec/boothd )
+which is placed on a
+new disk automatically by
+.Xr disklabel 8
+when the
+partitions of the disk are setup.
+.Pp
+This boot program
+finds the corresponding file on the given device
+.Pf ( Ar bsd
+by default),
+loads that file into memory,
+and starts the program at the entry address specified in the program header.
+.Pp
+The boot program can be interrupted by typing ^C (ctrl-C).
+This will force the boot program to interactively prompt for a system to boot.
+If not interrupted, it will boot from the device from which the boot
+program itself was loaded.
+.Pp
+The file specifications used for an interactive boot are of the form:
+.Pp
+.Dl device(unit, minor)
+.Pp
+where
+.Ar device
+is the type of the device to be searched,
+.Ar unit
+is 8 * the hpib number plus the unit number of the disk or tape,
+and
+.Ar minor
+is the disk partition or tape file number.
+Normal line editing characters can be used when typing the file specification.
+Currently,
+.Dq rd
+and
+.Dq sd
+are the only valid
+.Ar device
+specifiers.
+.Pp
+For example,
+to boot from the
+.Dq a
+file system of unit 0 on HP-IB 2, type
+.Dq rd(16, 0)bsd
+at the boot prompt.
+For tapes, the minor device number gives a file offset.
+.Pp
+In an emergency, the bootstrap methods described in the paper
+.%T Installing 4.3bsd on the HP300
+can be used to boot from a distribution tape.
+.Sh FILES
+.Bl -tag -width /usr/mdec/installboot -compact
+.It Pa /bsd
+system code
+.It Pa /usr/mdec/bootrd
+.Tn LIF
+format boot block
+.It Pa /usr/mdec/installboot
+program to install boot blocks
+.El
+.Sh SEE ALSO
+.Xr disklabel 8 ,
+.Xr halt 8 ,
+.Xr reboot 8 ,
+.Xr shutdown 8
diff --git a/share/man/man8/man8.hp300/crash.8 b/share/man/man8/man8.hp300/crash.8
deleted file mode 100644
index c9968efe239..00000000000
--- a/share/man/man8/man8.hp300/crash.8
+++ /dev/null
@@ -1,227 +0,0 @@
-.\"	$OpenBSD: crash.8,v 1.4 1999/07/09 13:35:35 aaron Exp $
-.\"
-.\" Copyright (c) 1990, 1991 Regents of the University of California.
-.\" All rights reserved.
-.\"
-.\" 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.
-.\"
-.\"     from: @(#)crash.8	5.2 (Berkeley) 3/16/91
-.\"
-.Dd March 16, 1991
-.Dt CRASH 8
-.Os
-.Sh NAME
-.Nm crash
-.Nd UNIX system failures
-.Sh DESCRIPTION
-This section explains a bit about system crashes
-and (very briefly) how to analyze crash dumps.
-.Pp
-When the system crashes voluntarily it prints a message of the form
-.Bd -ragged -offset indent
-panic: why i gave up the ghost
-.Ed
-.Pp
-on the console, takes a dump on a mass storage peripheral,
-and then invokes an automatic reboot procedure as
-described in
-.Xr reboot 8 .
-Unless some unexpected inconsistency is encountered in the state
-of the file systems due to hardware or software failure, the system
-will then resume multi-user operations.
-.Pp
-The system has a large number of internal consistency checks; if one
-of these fails, then it will panic with a very short message indicating
-which one failed.
-In many instances, this will be the name of the routine which detected
-the error, or a two-word description of the inconsistency.
-A full understanding of most panic messages requires perusal of the
-source code for the system.
-.Pp
-The most common cause of system failures is hardware failure, which
-can reflect itself in different ways.  Here are the messages which
-are most likely, with some hints as to causes.
-Left unstated in all cases is the possibility that hardware or software
-error produced the message in some unexpected way.
-.Pp
-.Bl -tag -width Ds -compact
-.It Sy iinit
-This cryptic panic message results from a failure to mount the root filesystem
-during the bootstrap process.
-Either the root filesystem has been corrupted,
-or the system is attempting to use the wrong device as root filesystem.
-Usually, an alternate copy of the system binary or an alternate root
-filesystem can be used to bring up the system to investigate.
-.Pp
-.It Sy "Can't exec /etc/init"
-This is not a panic message, as reboots are likely to be futile.
-Late in the bootstrap procedure, the system was unable to locate
-and execute the initialization process,
-.Xr init 8 .
-The root filesystem is incorrect or has been corrupted, or the mode
-or type of
-.Pa /etc/init
-forbids execution.
-.Pp
-.It Sy "IO err in push"
-.It Sy "hard IO err in swap"
-The system encountered an error trying to write to the paging device
-or an error in reading critical information from a disk drive.
-The offending disk should be fixed if it is broken or unreliable.
-.Pp
-.It Sy "realloccg: bad optim"
-.It Sy "ialloc: dup alloc"
-.It Sy "alloccgblk:cyl groups corrupted"
-.It Sy "ialloccg: map corrupted"
-.It Sy "free: freeing free block"
-.It Sy "free: freeing free frag"
-.It Sy "ifree: freeing free inode"
-.It Sy "alloccg: map corrupted"
-These panic messages are among those that may be produced
-when filesystem inconsistencies are detected.
-The problem generally results from a failure to repair damaged filesystems
-after a crash, hardware failures, or other condition that should not
-normally occur.
-A filesystem check will normally correct the problem.
-.Pp
-.It Sy "timeout table overflow"
-This really shouldn't be a panic, but until the data structure
-involved is made to be extensible, running out of entries causes a crash.
-If this happens, make the timeout table bigger.
-.Pp
-.It Sy "trap type %d, code = %x, v = %x"
-An unexpected trap has occurred within the system; the trap types are:
-.Bl -column xxxx -offset indent
-0	bus error
-1	address error
-2	illegal instruction
-3	divide by zero
-.No 4\t Em chk No instruction
-.No 5\t Em trapv No instruction
-6	privileged instruction
-7	trace trap
-8	MMU fault
-9	simulated software interrupt
-10	format error
-11	FP coprocessor fault
-12	coprocessor fault
-13	simulated AST
-.El
-.Pp
-The favorite trap type in system crashes is trap type 8,
-indicating a wild reference.
-``code'' (hex) is the concatenation of the
-MMU
-status register
-(see <hp300/cpu.h>)
-in the high 16 bits and the 68020 special status word
-(see the 68020 manual, page 6-17)
-in the low 16.
-``v'' (hex) is the virtual address which caused the fault.
-Additionally, the kernel will dump about a screenful of semi-useful
-information.
-``pid'' (decimal) is the process ID of the process running at the
-time of the exception.
-Note that if we panic in an interrupt routine,
-this process may not be related to the panic.
-``ps'' (hex) is the 68020 processor status register ``ps''.
-``pc'' (hex) is the value of the program counter saved
-on the hardware exception frame.
-It may
-.Em not
-be the PC of the instruction causing the fault.
-``sfc'' and ``dfc'' (hex) are the 68020 source/destination function codes.
-They should always be one.
-``p0'' and ``p1'' are the
-VAX-like
-region registers.
-They are of the form:
-.Pp
-.Bd -ragged -offset indent
-<length> '@' <kernel VA>
-.Ed
-.Pp
-where both are in hex.
-Following these values are a dump of the processor registers (hex).
-Finally, is a dump of the stack (user/kernel) at the time of the offense.
-.Pp
-.It Sy "init died"
-The system initialization process has exited.  This is bad news, as no new
-users will then be able to log in.  Rebooting is the only fix, so the
-system just does it right away.
-.Pp
-.It Sy "out of mbufs: map full"
-The network has exhausted its private page map for network buffers.
-This usually indicates that buffers are being lost, and rather than
-allow the system to slowly degrade, it reboots immediately.
-The map may be made larger if necessary.
-.El
-.Pp
-That completes the list of panic types you are likely to see.
-.Pp
-When the system crashes it writes (or at least attempts to write)
-an image of memory into the back end of the dump device,
-usually the same as the primary swap
-area.  After the system is rebooted, the program
-.Xr savecore 8
-runs and preserves a copy of this core image and the current
-system in a specified directory for later perusal.  See
-.Xr savecore 8
-for details.
-.Pp
-To analyze a dump you should begin by running
-.Xr adb 1
-with the
-.Fl k
-flag on the system load image and core dump.
-If the core image is the result of a panic,
-the panic message is printed.
-Normally the command
-``$c''
-will provide a stack trace from the point of
-the crash and this will provide a clue as to
-what went wrong.
-For more details consult
-.%T "Using ADB to Debug the UNIX Kernel" .
-.Sh SEE ALSO
-.Xr adb 1 ,
-.Xr reboot 8
-.Rs
-.%T "MC68020 32-bit Microprocessor User's Manual"
-.Re
-.Rs
-.%T "Using ADB to Debug the UNIX Kernel
-.Re
-.Rs
-.%T "4.3BSD for the HP300"
-.Re
-.Sh HISTORY
-A
-.Nm
-man page appeared in Version 6 AT&T UNIX.
diff --git a/share/man/man8/man8.i386/Makefile b/share/man/man8/man8.i386/Makefile
index 499800136d5..effb6fe01b2 100644
--- a/share/man/man8/man8.i386/Makefile
+++ b/share/man/man8/man8.i386/Makefile
@@ -1,7 +1,7 @@
 #	@(#)Makefile	5.1 (Berkeley) 3/22/91
 #	$NetBSD: Makefile,v 1.5 1995/09/06 21:36:35 jtc Exp $
 
-MAN=	MAKEDEV.8
+MAN=	MAKEDEV.8 boot_i386.8
 MLINKS=	MAKEDEV.8 makedev.8
 MANSUBDIR=/i386
 
diff --git a/share/man/man8/man8.i386/boot_i386.8 b/share/man/man8/man8.i386/boot_i386.8
new file mode 100644
index 00000000000..2e195089246
--- /dev/null
+++ b/share/man/man8/man8.i386/boot_i386.8
@@ -0,0 +1,165 @@
+.\"	$OpenBSD: boot_i386.8,v 1.1 2000/11/09 03:57:34 deraadt Exp $
+.\"
+.\" Copyright (c) 1997 Tobias Weingartner
+.\"
+.\" All rights reserved.
+.\"
+.\" 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 Michael Shalayeff.
+.\" 4. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``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 September 4, 1997
+.Dt BOOT_I386 8 i386
+.Os
+.Sh NAME
+.Nm boot
+.Nd
+system bootstrapping procedures
+.Sh DESCRIPTION
+.Ss 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,
+and unless this fails, the system will resume multi-user operations.
+.Pp
+.Ss Cold starts
+The
+.Tn "PC AT"
+clones will perform a POST (Power On Self Test) upon being booted cold.
+This test will find and initialize memory, keyboard, and other devices.
+It will search for and initialize any extension ROMs that are present,
+and then attempt to boot the operating system from an available boot
+drive.
+Failing this, older IBM systems came up in ROM BASIC.
+.Pp
+The newer
+.Tn "PC AT"
+clones attempt to boot off the drive specified in the BIOS setup, or
+if it is an older BIOS, it will start with checking for a disk in floppy
+drive A (otherwise known as drive 0) first, and failing that, attempt to
+boot the hard disk C (otherwise known as hard disk controller 1, drive 0).
+.Pp
+.Ss Warm starts
+The BIOS loads the first block (at physical location: track 0, head 0,
+sector 1) off the boot device into memory, and if the last two bytes in the
+block match the signature 0x55AA, the BIOS considers the block a valid
+bootable drive.
+The BIOS then proceeds to call the machine code program in this block.
+If the BIOS is current, it will also pass the boot drive
+to the boot block in register %dl.
+.Pp
+There are two different types of boot blocks on devices.
+There is the
+MBR (master boot record) and the PBR (partition boot record).
+A digression
+into a little piece of history will quickly give light as to why this is so.
+In the beginning, the PC
+.Dq architecture
+came with a single or dual floppy
+drives, and no hard drives.
+The only type of bootable sectors on any device were the PBRs.
+They were responsible for loading the rest of the operating
+system from the correct device.
+When hard disks came out, it was felt that
+such a huge space should be able to be partitioned into separate drives,
+and this is when the MBR was invented.
+.Pp
+The MBR relocates itself upon being loaded and invoked by the BIOS.
+Embeded within the MBR is a partition table, with four partition table
+entries.
+The MBR code traverses this table (which was loaded with the
+MBR by the BIOS), looking for an active entry, and then loads the MBR or
+PBR from the disk location specified by the partition table entry.
+So in reality, the MBR is nothing more than a fancy chaining PBR.
+.Pp
+Note: The MBR could load another MBR, which is the case when you are booting
+off an extended partition.
+In other words, the first block of an extended
+partition is really an MBR, which will then load the corresponding MBR or PBR
+out of its extended partition's partition table.
+.Sh GEOMETRY TRANSLATION
+.Em WARNING :
+This portion of the
+.Dq PC BIOS Architecture
+is a mess, and a compatibility nightmare.
+.Pp
+The PC BIOS has an API to manipulate any disk that the BIOS happens to
+support.
+This interface uses 10 bits to address the cylinder, 8 bits to
+address the head, and 6 bits to address the sector of a drive.
+This restricts any application using the BIOS to being able to address only
+1024 cylinders, 256 heads, and 63 (since the sectors are 1 based) sectors
+on a disk.
+These limitations proved to be fine for roughly 3 years after
+the debut of hard disks on PC computers.
+.Pp
+Many (if not all) newer drives have many more cylinders than the BIOS API
+can support, and likely more sectors per track as well.
+To allow the BIOS the ability of accessing these large drives, the BIOS would
+.Dq re-map
+the
+cylinder/head/sector of the real drive geometry into something that would
+allow the applications using the BIOS to access a larger portion of the
+drive, still using the restricted BIOS API.
+.Pp
+The reason this has become a problem is that any modern OS will use its own
+drivers to access the disk drive, bypassing the BIOS completely.
+However,
+the MBR, PBR, and partition tables are all still written using the original
+BIOS access methods.
+This is for backwards compatibility to the original IBM PC!
+.Pp
+So the gist of it is, the MBR, PBR, and partition table need to have BIOS
+geometry offsets and cylinder/head/sector values for them to be able to
+load any type of operating system.
+This geometry can, and likely will,
+change whenever you move a disk from machine to machine, or from controller
+to controller.
+.Em They are controller and machine specific .
+.Sh FILES
+.Bl -tag -width /usr/mdec/biosboot -compact
+.It Pa /bsd
+system code
+.It Pa /usr/mdec/mbr
+system MBR image
+.It Pa /usr/mdec/biosboot
+system primary stage bootstrap (PBR)
+.It Pa /boot
+system second stage bootstrap
+.El
+.Sh SEE ALSO
+.Xr boot 8 ,
+.Xr halt 8 ,
+.Xr installboot 8 ,
+.Xr reboot 8 ,
+.Xr shutdown 8
+.Sh BUGS
+The
+.Dq PC BIOS Architecture
+makes this process very prone to weird and
+wonderful interactions between differing operating systems.
+There is no published standard to the MBR and PBR,
+which makes coding these a nightmare.
+Somebody *please* write me a decent BIOS, and make them (the masses) use it!
diff --git a/share/man/man8/man8.mac68k/MAKEDEV.8 b/share/man/man8/man8.mac68k/MAKEDEV.8
new file mode 100644
index 00000000000..ded8920efb5
--- /dev/null
+++ b/share/man/man8/man8.mac68k/MAKEDEV.8
@@ -0,0 +1,129 @@
+.\"	$OpenBSD: MAKEDEV.8,v 1.1 2000/11/09 03:57:34 deraadt Exp $
+.\" Copyright (c) 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" 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.
+.\"
+.\"	from: @(#)MAKEDEV.8	5.2 (Berkeley) 3/22/91
+.\"
+.Dd February 21, 1994
+.Dt MAKEDEV 8 mac68k
+.Os
+.Sh NAME
+.Nm MAKEDEV
+.Nd create system and device special files
+.Sh SYNOPSIS
+.Nm MAKEDEV
+.Ar name
+.Op Ar ...
+.Sh DESCRIPTION
+The shell script
+.Nm MAKEDEV ,
+found in the
+.Pa /dev
+directory, is used to create
+the common special
+files.
+See
+.Xr special 8
+for a more complete discussion of special files.
+.Pp
+.Nm MAKEDEV
+takes any number of device names as arguments,
+where the names are the common abbreviation for
+the device.  There are three special device names,
+.Ar all ,
+.Ar std
+and
+.Ar local .
+If
+given,
+.Ar all
+creates device files for all devices on
+the Mac68k.  If units are expected for a device
+.Nm MAKEDEV
+supplies the standard numbers.
+The
+.Ar std
+argument creates the standard devices for the Mac68k.
+Finally
+.Ar local
+is for devices specific to the local site, and
+executes the shell file
+.Pa MAKEDEV.local .
+.Pp
+The Mac68k supports the following devices.
+Where a device name is followed by a hash
+sign ("#"), the hash sign must be replaced
+by a unit number.
+.Pp
+.Sy Pseudo\-names
+.Bl -tag -width indent -compact
+.It Ar all
+All known devices for the Mac68k.
+.It Ar std
+The standard devices (console, drum, fd/*, klog, kmem, mem, null,
+stderr, stdin, stdout, tty, zero)
+.It Ar local
+Configuration specific devices
+.El
+.Pp
+.Sy Device\-names
+.Bl -tag -width indent -compact
+.It Ar bpf#
+Berkeley packet filters
+.It Ar cd#
+SCSI CD-ROM drives
+.It Ar kbd
+The keyboard
+.It Ar lkm
+Loadable kernel modules.
+.It Ar mouse#
+Mouse ports
+.It Ar pty#
+Set of 16 master and slave pseudo terminals
+.It Ar sd#
+SCSI disk drives
+.It Ar st#
+SCSI tape drives
+.It Ar tty#
+Onboard Serial ports
+.It Ar vnd#
+"File" pseudo-disks
+.El
+.Sh FILES
+.Bl -tag -width /dev -compact
+.It Pa /dev
+The special file directory.
+.El
+.Sh SEE ALSO
+.Xr intro 4 ,
+.Xr config 8 ,
+.Xr mknod 8 ,
+.Xr special 8
diff --git a/share/man/man8/man8.mac68k/Makefile b/share/man/man8/man8.mac68k/Makefile
index 46050a33a45..e2918a21de3 100644
--- a/share/man/man8/man8.mac68k/Makefile
+++ b/share/man/man8/man8.mac68k/Makefile
@@ -1,7 +1,8 @@
 #	@(#)Makefile	5.2 (Berkeley) 3/22/91
 #	$NetBSD: Makefile,v 1.3 1995/09/06 21:36:37 jtc Exp $
 
-MAN=
+MAN=	MAKEDEV.8 boot_mac68k.8
+MLINKS=	MAKEDEV.8 makedev.8
 MANSUBDIR=/mac68k
 
 .include <bsd.prog.mk>
diff --git a/share/man/man8/man8.mac68k/boot_mac68k.8 b/share/man/man8/man8.mac68k/boot_mac68k.8
new file mode 100644
index 00000000000..69e10759ad3
--- /dev/null
+++ b/share/man/man8/man8.mac68k/boot_mac68k.8
@@ -0,0 +1,141 @@
+.\"	$OpenBSD: boot_mac68k.8,v 1.1 2000/11/09 03:57:34 deraadt Exp $
+.\"	$NetBSD: boot_mac68k.8,v 1.1 1995/07/02 02:09:52 briggs 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.
+.\"
+.\"	From:
+.\"	@(#)boot_hp300.8	8.2 (Berkeley) 4/19/94
+.\"
+.Dd July 1, 1995
+.Dt BOOT_MAC68K 8 mac68k
+.Os
+.Sh NAME
+.Nm boot
+.Nd
+system bootstrapping procedures
+.Sh DESCRIPTION
+.Ss Power fail and crash recovery
+Normally, the
+.Ox
+kernel on the mac68k architecture is booted from the native operating
+system by means of an application program.
+When the kernel takes over,
+it initializes itself and proceeds to boot the system.
+An automatic
+consistency check of the file systems takes place, and unless this
+fails, the system comes up to multi-user operations.
+The proper way to shut the system down is with the
+.Xr shutdown 8
+command.
+.Pp
+If the system crashes, it will enter the kernel debugger,
+.Xr ddb 8 ,
+if it is configured in the kernel.
+If the debugger is not present
+or has exited, the system will attempt a dump to the
+configured dump device (which will be automatically recovered with
+.Xr savecore 8
+during the next boot cycle).
+After the dump completes (successful
+or not), the system will attempt a reboot.
+.Pp
+On most mac68k machines with
+.Dq soft-power
+after the IIcx, the power
+switch can be physically rotated and locked in the
+.Dq on
+position.
+The native OS can be configured to automatically start the
+.Ox
+boot program.
+Additionally, the
+.Ox
+boot program can be configured to boot
+.Ox
+without intervention.
+When a system is so configured, it can crash
+or lose power and reboot back to a fully multi-user state without
+any intervention.
+.Pp
+.Ss The boot application
+The boot application runs in the native OS on the system.
+It has a
+dialog where booting preferences may be changed and an option whereby
+these options may be saved.
+The preferences are stored in the program
+itself, not in a preferences folder, thus allowing two separate copies
+of the program to be configured differently (e.g., to boot different
+bsd or bsd.test, or to boot from two different drives).
+.Pp
+One option that may be specified is a boot to single-user mode.
+This stops the boot process very early on and allows system maintenance.
+If one wishes to provide some security at this phase of the boot, remove
+the
+.Dq secure
+option from ttye0 in the
+.Xr ttys 5
+file.
+.Pp
+Another useful option that may be specified is the
+.Dq serial console
+option.
+This will allow a serial device (terminal or computer) to
+act as a console for the system.
+This device must be configured to
+use 9600 baud, eight bits, no parity, and one stop bit (9600-8N1).
+Either the printer port or the modem port (tty01 and tty00,
+respectively) may be used for this.
+.Pp
+It is sometimes useful to boot a kernel that resides in a folder
+in native OS rather than from the usual location in the
+.Ox
+file system.
+A radio button is supplied for this purpose.
+Note that some programs will not run properly if the kernel is not found as
+.Pa /bsd
+within the
+.Ox
+file system.
+.Sh FILES
+.Bl -tag -width /bsd -compact
+.It Pa /bsd
+system kernel
+.El
+.Sh SEE ALSO
+.Xr ttys 5 ,
+.Xr ddb 8 ,
+.Xr savecore 8 ,
+.Xr shutdown 8
diff --git a/share/man/man8/man8.mvme68k/Makefile b/share/man/man8/man8.mvme68k/Makefile
index f40412c6fd7..a3f81fc3891 100644
--- a/share/man/man8/man8.mvme68k/Makefile
+++ b/share/man/man8/man8.mvme68k/Makefile
@@ -1,7 +1,7 @@
 #	@(#)Makefile	5.1 (Berkeley) 3/22/91
 #	$NetBSD: Makefile,v 1.3 1995/09/06 21:36:38 jtc Exp $
 
-#MAN=	MAKEDEV.8
+#MAN=	MAKEDEV.8 boot_mvme68k.8
 #MLINKS=	MAKEDEV.8 makedev.8
 MANSUBDIR=/mvme68k
 
diff --git a/share/man/man8/man8.pmax/Makefile b/share/man/man8/man8.pmax/Makefile
new file mode 100644
index 00000000000..9548f803be2
--- /dev/null
+++ b/share/man/man8/man8.pmax/Makefile
@@ -0,0 +1,8 @@
+#	@(#)Makefile	5.1 (Berkeley) 3/22/91
+#	$NetBSD: Makefile,v 1.3 1995/09/06 21:36:38 jtc Exp $
+
+MAN=	MAKEDEV.8 boot_pmax.8
+MLINKS=	MAKEDEV.8 makedev.8
+MANSUBDIR=/pmax
+
+.include <bsd.prog.mk>
diff --git a/share/man/man8/man8.pmax/boot_pmax.8 b/share/man/man8/man8.pmax/boot_pmax.8
new file mode 100644
index 00000000000..2778c80afb3
--- /dev/null
+++ b/share/man/man8/man8.pmax/boot_pmax.8
@@ -0,0 +1,213 @@
+.\"	$OpenBSD: boot_pmax.8,v 1.1 2000/11/09 03:57:34 deraadt 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
diff --git a/share/man/man8/man8.powerpc/Makefile b/share/man/man8/man8.powerpc/Makefile
new file mode 100644
index 00000000000..dd6174bb528
--- /dev/null
+++ b/share/man/man8/man8.powerpc/Makefile
@@ -0,0 +1,8 @@
+#	@(#)Makefile	5.1 (Berkeley) 3/22/91
+#	$NetBSD: Makefile,v 1.3 1995/09/06 21:36:38 jtc Exp $
+
+#MAN=	MAKEDEV.8 boot_powerpc.8
+#MLINKS=	MAKEDEV.8 makedev.8
+MANSUBDIR=/powerpc
+
+.include <bsd.prog.mk>
diff --git a/share/man/man8/man8.sparc/Makefile b/share/man/man8/man8.sparc/Makefile
index e2edb5b047b..75135186fa3 100644
--- a/share/man/man8/man8.sparc/Makefile
+++ b/share/man/man8/man8.sparc/Makefile
@@ -1,7 +1,7 @@
 #	@(#)Makefile	5.1 (Berkeley) 3/22/91
 #	$NetBSD: Makefile,v 1.3 1995/09/06 21:36:38 jtc Exp $
 
-MAN=	MAKEDEV.8
+MAN=	MAKEDEV.8 boot_sparc.8
 MLINKS=	MAKEDEV.8 makedev.8
 MANSUBDIR=/sparc
 
diff --git a/share/man/man8/man8.sparc/boot_sparc.8 b/share/man/man8/man8.sparc/boot_sparc.8
new file mode 100644
index 00000000000..ef4f7491a4e
--- /dev/null
+++ b/share/man/man8/man8.sparc/boot_sparc.8
@@ -0,0 +1,146 @@
+.\"	$OpenBSD: boot_sparc.8,v 1.1 2000/11/09 03:57:35 deraadt Exp $
+.\"	$NetBSD: boot_sparc.8,v 1.4 1995/04/25 11:37:25 pk Exp $
+.\"
+.\" Copyright (c) 1992, 1993
+.\"	The Regents of the University of California.  All rights reserved.
+.\"
+.\" 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.
+.\"
+.\"     @(#)boot_sparc.8	8.2 (Berkeley) 4/19/94
+.\"
+.Dd April 19, 1994
+.Dt BOOT_SPARC 8 sparc
+.Os
+.Sh NAME
+.Nm boot
+.Nd
+.Tn sparc-specific
+system bootstrapping procedures
+.Sh DESCRIPTION
+.Ss 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
+.Xr fsck 8 ) ,
+and unless this fails, the system will resume multi-user operations.
+.Pp
+.Ss Cold starts
+System boot blocks are installed near the start of the boot disk
+using the procedure described in
+.Xr installboot 8 .
+The boot program attempts to load
+.Pa bsd
+from partition
+.Dq a
+of the boot device,
+which must currently be an
+.Dq sd
+disk.
+.Pp
+The
+.Fl s
+flag to the bootloader will bring the system up in single-user mode.
+The
+.Fl a
+flag instructs the system to prompt for the location of the root filesystem
+and the primary swap partition.
+Other flags are currently ignored.
+.Pp
+The SPARC boot ROM comes in two flavours: an
+.Dq old-style
+ROM is used in
+sun4 machines, while a
+.Dq new-style
+ROM can be found on sun4c and sun4m models.
+The
+.Dq new-style
+SPARC boot ROM is a full-featured Forth system with emacs
+key bindings.
+It can be put in
+.Dq old-style
+user-interface compatibility
+mode (in which case it shows a simple
+.Dq \&>
+prompt), but this is essentially
+useless.
+However, by default the ROM runs in old-mode; to enter new-mode type
+.Dq n .
+The ROM then shows a Forth-style
+.Dq ok
+prompt.
+It is recommended to have the ROM always start in its native
+.Dq new-style
+mode.
+Utter the following
+incantation in new-mode to force the ROM to always start in new-mode:
+.Pp
+.Em \	ok
+setenv sunmon-compat? false
+.Pp
+The ROM will normally load the kernel from
+.Dq sd(0,0,0)bsd .
+To change the
+default so that
+.Ox
+will be loaded, type the following:
+.Pp
+.Em \	ok
+setenv boot-from sd(0,0,0)bsd
+.Pp
+If the
+.Xr sysctl 8
+variable
+.Ev ddb.console
+is enabled, at any time you can break back to the ROM by pressing the
+.Dq L1
+and
+.Dq a
+keys at the same time (if the console is a serial port the same is
+achieved by sending a
+.Dq break ) .
+If you do this accidentally you can continue whatever was in progress
+by typing
+.Dq go .
+.Sh FILES
+.Bl -tag -width /bsdxx -compact
+.It Pa /bsd
+system code
+.It Pa /boot
+system bootstrap
+.El
+.Sh SEE ALSO
+.Xr crash 8 ,
+.Xr disklabel 8 ,
+.Xr fsck 8 ,
+.Xr halt 8 ,
+.Xr init 8 ,
+.Xr installboot 8 ,
+.Xr rc 8 ,
+.Xr shutdown 8 ,
+.Xr syslogd 8
diff --git a/share/man/man8/man8.sun3/Makefile b/share/man/man8/man8.sun3/Makefile
index e791c380111..3b961beffb0 100644
--- a/share/man/man8/man8.sun3/Makefile
+++ b/share/man/man8/man8.sun3/Makefile
@@ -1,7 +1,7 @@
 #	@(#)Makefile	5.1 (Berkeley) 3/22/91
 #	$NetBSD: Makefile,v 1.3 1995/09/06 21:36:39 jtc Exp $
 
-MAN=	MAKEDEV.8
+MAN=	MAKEDEV.8 boot_sun3.8
 MLINKS=	MAKEDEV.8 makedev.8
 MANSUBDIR=/sun3
 
diff --git a/share/man/man8/man8.sun3/boot_sun3.8 b/share/man/man8/man8.sun3/boot_sun3.8
new file mode 100644
index 00000000000..a16aa93d13d
--- /dev/null
+++ b/share/man/man8/man8.sun3/boot_sun3.8
@@ -0,0 +1,117 @@
+.\"	$OpenBSD: boot_sun3.8,v 1.1 2000/11/09 03:57:35 deraadt Exp $
+.\"	$NetBSD: boot_sun3.8,v 1.1 1995/08/08 20:46:20 gwr Exp $
+.\"
+.\" Copyright (c) 1992, 1993
+.\"	The Regents of the University of California.  All rights reserved.
+.\"
+.\" 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.
+.\"
+.\"     @(#)boot_sparc.8	8.2 (Berkeley) 4/19/94
+.\"
+.Dd April 19, 1994
+.Dt BOOT_SUN3 8 sun3
+.Os
+.Sh NAME
+.Nm boot
+.Nd
+.Tn sun3-specific
+system bootstrapping procedures
+.Sh DESCRIPTION
+.Ss 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
+.Xr fsck 8 .
+and unless this fails, the system will resume multi-user operations.
+.Pp
+.Ss Cold starts
+A disk-boot program
+.Pq Pa /usr/mdec/ufsboot
+will attempt to load
+.Pa bsd
+from partition
+.Dq a
+of the boot device,
+which must currently be an
+.Dq sd
+disk.
+Alternatively, the network boot program
+.Pq Pa /usr/mdec/netboot
+will load
+.Pa bsd
+from the NFS root as determined by the procedure described in
+.Xr diskless 8 .
+.Pp
+The
+.Fl s
+flag to the bootloader will bring the system up in single-user mode.
+The
+.Fl a
+flag instructs the system to prompt for the location of the root filesystem
+and the primary swap partition.
+The
+.Fl d
+flag to the bootloader will bring the system up in debug mode.
+Here it waits for a kernel debugger connect; see
+.Xr ddb 8 .
+Other flags are currently ignored.
+.Pp
+At any time you can break back to the ROM by pressing the
+.Dq L1
+and
+.Dq a
+keys at the same time (if the console is a serial port the same is
+achieved by sending a
+.Dq break ) .
+If you do this accidentally you can continue whatever was in progress
+by typing
+.Dq c
+followed by the return key.
+.Sh FILES
+.Bl -tag -width /usr/mdec/installboot -compact
+.It Pa /bsd
+system code
+.It Pa /usr/mdec/bootxx
+first-level boot block for disks
+.It Pa /usr/mdec/netboot
+boot program for NFS (diskless) boot
+.It Pa /usr/mdec/ufsboot
+second-level boot program for UFS disks
+.It Pa /usr/mdec/installboot
+program to install bootxx on a disk
+.El
+.Sh SEE ALSO
+.Xr crash 8 ,
+.Xr disklabel 8 ,
+.Xr fsck 8 ,
+.Xr halt 8 ,
+.Xr init 8 ,
+.Xr rc 8 ,
+.Xr shutdown 8 ,
+.Xr syslogd 8
diff --git a/share/man/man8/man8.vax/Makefile b/share/man/man8/man8.vax/Makefile
index 712892af312..3d0611a88a6 100644
--- a/share/man/man8/man8.vax/Makefile
+++ b/share/man/man8/man8.vax/Makefile
@@ -1,7 +1,7 @@
 #	@(#)Makefile	5.5 (Berkeley) 3/22/91
 #	$NetBSD: Makefile,v 1.5 1995/09/06 21:36:42 jtc Exp $
 
-MAN=	MAKEDEV.8 crash.8 drtest.8 format.8 installboot.8
+MAN=	MAKEDEV.8 boot_vax.8 drtest.8 format.8 installboot.8
 MLINKS=	MAKEDEV.8 makedev.8
 MANSUBDIR=/vax
 
diff --git a/share/man/man8/man8.vax/boot_vax.8 b/share/man/man8/man8.vax/boot_vax.8
new file mode 100644
index 00000000000..047b3111212
--- /dev/null
+++ b/share/man/man8/man8.vax/boot_vax.8
@@ -0,0 +1,335 @@
+.\"	$OpenBSD: boot_vax.8,v 1.1 2000/11/09 03:57:35 deraadt Exp $
+.\"	$NetBSD: boot_vax.8,v 1.3 1995/04/23 10:33:39 cgd Exp $
+.\"
+.\" Copyright (c) 1980, 1991, 1993
+.\"	The Regents of the University of California.  All rights reserved.
+.\"
+.\" 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.
+.\"
+.\"     @(#)boot_vax.8	8.2 (Berkeley) 4/19/94
+.\"
+.Dd April 19, 1994
+.Dt BOOT_VAX 8 vax
+.Os
+.Sh NAME
+.Nm boot
+.Nd
+.Tn vax-specific
+system bootstrapping procedures
+.Sh DESCRIPTION
+.Ss Power fail and crash recovery
+Normally, the system will reboot itself at power-up or after crashes.
+Provided the auto-restart is enabled on the machine's front panel,
+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
+These are processor-type dependent.
+On an 11/780, there are two floppy files for each disk controller,
+both of which cause boots from unit 0 of the root file system
+of a controller located on mba0 or uba0.
+One gives a single-user shell, while the other invokes the multi-user
+automatic reboot.
+Thus these files are
+.Tn HPS
+and
+.Tn HPM
+for the single
+and multi-user boot from
+.Tn MASSBUS
+RP06/RM03/RM05 disks,
+.Tn UPS
+and
+.Tn UPM
+for
+.Tn UNIBUS
+storage module controller and disks
+such as the
+.Tn EMULEX
+SC-21
+and
+.Tn AMPEX
+9300 pair,
+.Tn RAS
+and
+.Tn RAM
+to boot from
+.Tn MSCP
+controllers and disks such as the RA81,
+or
+.Tn HKS
+and
+.Tn HKM
+for RK07 disks.
+There is also a script for booting from the default device,
+which is normally a copy of one of the standard multi-user boot scripts,
+but which may be modified to perform other actions
+or to boot from a different unit.
+The situation on the 8600 is similar, with scripts loaded from the console RL02.
+.Pp
+Giving the command
+.Pp
+.Dl >>>BOOT HPM
+.Pp
+would boot the system from (e.g.) an RP06 and run the automatic consistency
+check as described in
+.Xr fsck 8 .
+(Note that it may
+be necessary to type control-P
+and halt the processor
+to gain the attention of the
+.Tn LSI-11
+before getting the >>> prompt.)
+The command
+.Pp
+.Dl >>>BOOT ANY
+.Pp
+invokes a version of the boot program in a way which allows you to
+specify any system as the system to be booted.
+It reads from the console a device specification (see below) followed
+immediately by a pathname.
+.Pp
+The scripts may be modified for local configuration if necessary.
+The flags are placed in register 11 (as defined in
+.Aq Pa sys/reboot.h ) .
+The boot device is specified in register 10.
+The encoding of this register is also defined in
+.Aq Pa sys/reboot.h .
+The current encoding has a historical basis, and is shown in the following
+table:
+.Pp
+.Bd -unfilled -offset indent -compact
+bits		usage
+0-7		boot device type (the device major number)
+8-15		disk partition
+16-19	drive unit
+20-23	controller number
+24-27	adaptor number (UNIBUS or MASSBUS as appropriate)
+.Ed
+.Pp
+The adaptor number corresponds to the normal configuration on the 11/750,
+and to the order in which adaptors are found on the 11/780 and 8600
+(generally the same as the numbers used by
+.Tn UNIX ) .
+.Pp
+On an 11/750, the reset button will boot from the device
+selected by the front panel boot device switch.
+In systems with RK07's, position B normally selects the RK07 for boot.
+This will boot multi-user.
+To boot from RK07 with boot flags you may specify
+.Pp
+.Bd -unfilled -offset indent -compact
+.Li \&>>>B/ Ns Fl n No DMA0
+.Ed
+.Pp
+where, giving an
+.Ar n
+of 1 causes the boot program
+to ask for the name of the system to be bootstrapped,
+giving an
+.Ar n
+of 2 causes the boot program to come up single-user,
+and an
+.Ar n
+of 3 causes both of these actions to occur.
+The
+.Dq DM
+specifies RK07, the
+.Dq A
+represents the adaptor number
+.Pf ( Tn UNIBUS
+or
+.Tn MASSBUS ) ,
+and the
+.Dq 0
+is the drive unit number.
+Other disk types which may be used are DB
+.Pq Tn MASSBUS ,
+DD (TU58),
+and DU
+.Pf ( Tn UDA-50/RA
+disk).
+A non-zero disk partition can be used by adding (partition times 1000 hex)
+to
+.Ar n .
+.Pp
+The boot procedure on the Micro
+.Tn VAX
+II
+is similar.
+A switch on the back panel sets the power-up action
+to autoboot or to halt.
+When halted, the processor may be booted using the same syntax
+as on the 11/750.
+.Pp
+The 11/750 boot procedure uses the boot ROMs to load block 0 off
+the specified device.
+The
+.Pa /usr/mdec
+directory contains a number
+of bootstrap programs for the various disks which should be placed
+in a new pack by
+.Xr disklabel 8 .
+Similarly, the Micro
+.Tn VAX
+II boot procedure loads a boot parameter block
+from block 0 of the disk.
+The
+.Xr rdboot
+.Dq bootstrap
+contains the correct parameters for an
+.Tn MSCP
+disk such
+as the RD53.
+.Pp
+On any processor, the
+.Nm boot
+program
+finds the corresponding file on the given device
+.Pf ( Pa bsd
+by default), loads that file
+into memory location zero, and starts the program at the entry address
+specified in the program header (after clearing off the high bit
+of the specified entry address).
+.Pp
+The file specifications used with
+.Dq BOOT ANY
+or
+.Dq \&B/3
+are of the form:
+.Pp
+.Dl device(adaptor,controller,unit,minor)
+.Pp
+where
+.Ar device
+is the type of the device to be searched,
+.Ar adaptor
+is the
+.Tn UNIBUS
+or
+.Tn MASSBUS
+number of the adaptor to which the device is attached,
+.Ar controller
+is the unit number of the controller or
+.Tn MASSBUS
+tape formatter on that adaptor,
+.Ar unit
+is the unit number of the disk or transport slave unit of the tape,
+and
+.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:
+.Pp
+.Bd -unfilled -offset indent -compact
+hp	MASSBUS disk drive
+up	UNIBUS storage module drive
+ht	TE16,TU45,TU77 on MASSBUS
+kra	storage module on a KDB50
+mt	TU78 on MASSBUS
+hk	RK07 on UNIBUS
+ra	storage module on a MSCP-compatible UNIBUS controller
+rb	storage module on a 730 IDC
+rl	RL02 on UNIBUS
+tm	TM11 emulation tape drives on UNIBUS
+tms	TMSCP-compatible tape
+ts	TS11 on UNIBUS
+ut	UNIBUS TU45 emulator
+.Ed
+.Pp
+For example,
+to boot from a file system which starts at cylinder 0
+of unit 0 of a
+.Tn MASSBUS
+disk, type
+.Dq hp(0,0)bsd
+at the boot prompt;
+.Dq hp(2,0,1,0)bsd
+would specify drive 1 on
+.Tn MASSBUS
+adaptor 2;
+.Dq up(0,0)bsd
+would specify a
+.Tn UNIBUS
+drive,
+.Dq hk(0,0)bsd
+would specify
+an RK07 disk drive,
+.Dq ra(1,0,0,0)bsd
+would specify a
+.Tn UDA50
+disk drive on a second
+.Tn UNIBUS ,
+and
+.Dq rb(0,0)bsd
+would specify a
+disk on a 730
+.Tn IDC .
+For tapes, the minor device number gives a file offset;
+.Dq mt(1,2,3,4)
+would specify the fifth file on slave 3 of the formatter
+at
+.Dq drive
+2 on mba 1.
+.Pp
+On an 11/750 with patchable control store,
+microcode patches will be installed by
+.Nm boot
+if the file
+.Pa psc750.bin
+exists in the root of the filesystem from which the system is booted.
+.Pp
+In an emergency, the bootstrap methods described in the paper
+.%T Installing and Operating 4.3bsd
+can be used to boot from a distribution tape.
+.Sh FILES
+.Bl -tag -width /usr/mdec/xxboot -compact
+.It Pa /bsd
+system code
+.It Pa /boot
+system bootstrap
+.It Pa /usr/mdec/xxboot
+sector-0 boot block for 750, xx is disk type
+.It Pa /usr/mdec/bootxx
+second-stage boot for 750, xx is disk type
+.It Pa /pcs750.bin
+microcode patch file on 750
+.El
+.Sh SEE ALSO
+.Xr arff 8 ,
+.Xr halt 8 ,
+.Xr reboot 8 ,
+.Xr shutdown 8
+.Sh HISTORY
+The
+.Nm
+command appeared in
+.Bx 4.0 .
diff --git a/share/man/man8/man8.vax/crash.8 b/share/man/man8/man8.vax/crash.8
deleted file mode 100644
index 1f1ab7b90cd..00000000000
--- a/share/man/man8/man8.vax/crash.8
+++ /dev/null
@@ -1,240 +0,0 @@
-.\"	$OpenBSD: crash.8,v 1.4 2000/10/13 04:09:23 aaron Exp $
-.\" Copyright (c) 1980, 1991 The Regents of the University of California.
-.\" All rights reserved.
-.\"
-.\" 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.
-.\"
-.\"	from: @(#)crash.8	6.5 (Berkeley) 4/20/91
-.\"
-.TH CRASH 8 "April 20, 1991"
-.UC 4
-.SH NAME
-crash \- UNIX system failures
-.SH DESCRIPTION
-This section explains what happens when the system crashes
-and (very briefly) how to analyze crash dumps.
-.PP
-When the system crashes voluntarily it prints a message of the form
-.IP
-panic: why i gave up the ghost
-.LP
-on the console, takes a dump on a mass storage peripheral,
-and then invokes an automatic reboot procedure as
-described in
-.IR reboot (8).
-(If auto-reboot is disabled on the front panel of the machine the system
-will simply halt at this point.)
-Unless some unexpected inconsistency is encountered in the state
-of the file systems due to hardware or software failure, the system
-will then resume multi-user operations.
-.PP
-The system has a large number of internal consistency checks; if one
-of these fails, then it will panic with a very short message indicating
-which one failed.
-In many instances, this will be the name of the routine which detected
-the error, or a two-word description of the inconsistency.
-A full understanding of most panic messages requires perusal of the
-source code for the system.
-.PP
-The most common cause of system failures is hardware failure, which
-can reflect itself in different ways.  Here are the messages which
-are most likely, with some hints as to causes.
-Left unstated in all cases is the possibility that hardware or software
-error produced the message in some unexpected way.
-.TP
-.B iinit
-This cryptic panic message results from a failure to mount the root filesystem
-during the bootstrap process.
-Either the root filesystem has been corrupted,
-or the system is attempting to use the wrong device as root filesystem.
-Usually, an alternate copy of the system binary or an alternate root
-filesystem can be used to bring up the system to investigate.
-.TP
-.B Can't exec /sbin/init
-This is not a panic message, as reboots are likely to be futile.
-Late in the bootstrap procedure, the system was unable to locate
-and execute the initialization process,
-.IR init (8).
-The root filesystem is incorrect or has been corrupted, or the mode
-or type of /sbin/init forbids execution.
-.TP
-.B IO err in push
-.ns
-.TP
-.B hard IO err in swap
-The system encountered an error trying to write to the paging device
-or an error in reading critical information from a disk drive.
-The offending disk should be fixed if it is broken or unreliable.
-.TP
-.B realloccg: bad optim
-.ns
-.TP
-.B ialloc: dup alloc
-.ns
-.TP
-.B alloccgblk: cyl groups corrupted
-.ns
-.TP
-.B ialloccg: map corrupted
-.ns
-.TP
-.B free: freeing free block
-.ns
-.TP
-.B free: freeing free frag
-.ns
-.TP
-.B ifree: freeing free inode
-.ns
-.TP
-.B alloccg: map corrupted
-These panic messages are among those that may be produced
-when filesystem inconsistencies are detected.
-The problem generally results from a failure to repair damaged filesystems
-after a crash, hardware failures, or other condition that should not
-normally occur.
-A filesystem check will normally correct the problem.
-.TP
-.B timeout table overflow
-.ns
-This really shouldn't be a panic, but until the data structure
-involved is made to be extensible, running out of entries causes a crash.
-If this happens, make the timeout table bigger.
-.TP
-.B KSP not valid
-.ns
-.TP
-.B SBI fault
-.ns
-.TP
-.B CHM? in kernel
-These indicate either a serious bug in the system or, more often,
-a glitch or failing hardware.
-If SBI faults recur, check out the hardware or call
-field service.  If the other faults recur, there is likely a bug somewhere
-in the system, although these can be caused by a flakey processor.
-Run processor microdiagnostics.
-.TP
-.B machine check %x:
-.I description
-.ns
-.TP
-.I \0\0\0machine dependent machine-check information
-.ns
-Machine checks are different on each type of CPU.
-Most of the internal processor registers are saved at the time of the fault
-and are printed on the console.
-For most processors, there is one line that summarizes the type of machine
-check.
-Often, the nature of the problem is apparent from this message
-and/or the contents of key registers.
-The VAX Hardware Handbook should be consulted,
-and, if necessary, your friendly field service people should be informed
-of the problem.
-.TP
-.B trap type %d, code=%x, pc=%x
-A unexpected trap has occurred within the system; the trap types are:
-.sp
-.nf
-0	reserved addressing fault
-1	privileged instruction fault
-2	reserved operand fault
-3	bpt instruction fault
-4	xfc instruction fault
-5	system call trap
-6	arithmetic trap
-7	ast delivery trap
-8	segmentation fault
-9	protection fault
-10	trace trap
-11	compatibility mode fault
-12	page fault
-13	page table fault
-.fi
-.sp
-The favorite trap types in system crashes are trap types 8 and 9,
-indicating
-a wild reference.  The code is the referenced address, and the pc at the
-time of the fault is printed.  These problems tend to be easy to track
-down if they are kernel bugs since the processor stops cold, but random
-flakiness seems to cause this sometimes.
-The debugger can be used to locate the instruction and subroutine
-corresponding to the PC value.
-If that is insufficient to suggest the nature of the problem,
-more detailed examination of the system status at the time of the trap
-usually can produce an explanation.
-.TP
-.B init died
-The system initialization process has exited.  This is bad news, as no new
-users will then be able to log in.  Rebooting is the only fix, so the
-system just does it right away.
-.TP
-.B out of mbufs: map full
-The network has exhausted its private page map for network buffers.
-This usually indicates that buffers are being lost, and rather than
-allow the system to slowly degrade, it reboots immediately.
-The map may be made larger if necessary.
-.PP
-That completes the list of panic types you are likely to see.
-.PP
-When the system crashes it writes (or at least attempts to write)
-an image of memory into the back end of the dump device,
-usually the same as the primary swap
-area.  After the system is rebooted, the program
-.IR savecore (8)
-runs and preserves a copy of this core image and the current
-system in a specified directory for later perusal.  See
-.IR savecore (8)
-for details.
-.PP
-To analyze a dump you should begin by running
-.IR adb (1)
-with the
-.B \-k
-flag on the system load image and core dump.
-If the core image is the result of a panic,
-the panic message is printed.
-Normally the command
-``$c''
-will provide a stack trace from the point of
-the crash and this will provide a clue as to
-what went wrong.
-For more detail
-see
-``Using ADB to Debug the UNIX Kernel''.
-.SH "SEE ALSO"
-adb(1),
-reboot(8)
-.br
-.I "VAX 11/780 System Maintenance Guide"
-and
-.I "VAX Hardware Handbook"
-for more information about machine checks.
-.br
-.I "Using ADB to Debug the UNIX Kernel"