Remove no longer relevant manpages; attempt to modernize boot_vax(8) a bit

as well. Prodded by jmc@

5 files changed, 23 insertions, 705 deletions

diff --git a/share/man/man8/man8.vax/Makefile b/share/man/man8/man8.vax/Makefile
index ff822acd019..f1efa72a5ab 100644
--- a/share/man/man8/man8.vax/Makefile
+++ b/share/man/man8/man8.vax/Makefile
@@ -1,8 +1,7 @@
-#	$OpenBSD: Makefile,v 1.7 2002/10/02 17:40:22 miod Exp $
+#	$OpenBSD: Makefile,v 1.8 2011/07/07 19:27:44 miod Exp $
 #	$NetBSD: Makefile,v 1.5 1995/09/06 21:36:42 jtc Exp $
 
-MAN=	MAKEDEV.8 boot_vax.8 format.8
-#MAN+=	drtest.8 installboot.8
+MAN=	MAKEDEV.8 boot_vax.8
 MANSUBDIR=vax
 
 .include <bsd.prog.mk>
diff --git a/share/man/man8/man8.vax/boot_vax.8 b/share/man/man8/man8.vax/boot_vax.8
index 20f66b3613b..bb9fa3bd265 100644
--- a/share/man/man8/man8.vax/boot_vax.8
+++ b/share/man/man8/man8.vax/boot_vax.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: boot_vax.8,v 1.9 2007/05/31 19:20:00 jmc Exp $
+.\"	$OpenBSD: boot_vax.8,v 1.10 2011/07/07 19:27:44 miod Exp $
 .\"	$NetBSD: boot_vax.8,v 1.3 1995/04/23 10:33:39 cgd Exp $
 .\"
 .\" Copyright (c) 1980, 1991, 1993
@@ -30,7 +30,7 @@
 .\"
 .\"     @(#)boot_vax.8	8.2 (Berkeley) 4/19/94
 .\"
-.Dd $Mdocdate: May 31 2007 $
+.Dd $Mdocdate: July 7 2011 $
 .Dt BOOT_VAX 8 vax
 .Os
 .Sh NAME
@@ -45,163 +45,10 @@ 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.
 .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:
-.Bd -unfilled -offset indent
-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
-.Bd -unfilled -offset indent
-.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 system boot procedure loads a boot parameter block
+from block 0 of the disk configured as the boot device.
 The
-.Em 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
@@ -223,14 +70,9 @@ 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,
+is the 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,
@@ -242,87 +84,41 @@ Normal line editing characters can be used when typing the file specification.
 The following list of supported devices may vary from installation to
 installation:
 .Bd -unfilled -offset indent
-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
+hd	MFM disk connected to the MFM controller on some VAXstation systems
+mt	tape drive connected to an MSCP-compatible controller
+ra	disk drive connected to an MSCP-compatible controller
+sd	SCSI disk
+st	SCSI tape
 .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
+to boot from a file system in partition
+.Sq a
+of unit 0 of a SCSI disk, type
+.Dq sd(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 .
+.Dq sd(2,0,1,0)bsd
+would specify drive 1 on the second SCSI controller.
 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
 default system kernel
 .It Pa /bsd.rd
 standalone installation kernel, suitable for disaster recovery
-.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
+primary boot block, xx is disk type
+.It Pa /usr/mdec/boot
+secondary bootstrap (usually also installed as
+.Pa /boot )
 .El
 .Sh SEE ALSO
+.Xr disklabel 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/drtest.8 b/share/man/man8/man8.vax/drtest.8
deleted file mode 100644
index 8c0d57d3024..00000000000
--- a/share/man/man8/man8.vax/drtest.8
+++ /dev/null
@@ -1,111 +0,0 @@
-.\"	$OpenBSD: drtest.8,v 1.17 2007/05/31 19:20:00 jmc Exp $
-.\"
-.\" Copyright (c) 1983, 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. 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: @(#)drtest.8	6.3 (Berkeley) 3/16/91
-.\"
-.Dd $Mdocdate: May 31 2007 $
-.Dt DRTEST 8 vax
-.Os
-.Sh NAME
-.Nm drtest
-.Nd stand-alone disk test program
-.Sh DESCRIPTION
-.Nm Drtest
-is a stand-alone program used to read a disk
-track by track.
-It was primarily intended as a test program
-for new stand-alone drivers, but has proved
-useful in other contexts as well, such as
-verifying disks and running speed
-tests.
-For example, when a disk has been formatted (by
-.Xr format 8 ) ,
-you can check that
-hard errors have been taken care of by running
-.Nm drtest .
-No hard errors should be found, but in many cases
-quite a few soft
-.Tn ECC
-errors will be reported.
-.Pp
-While
-.Nm drtest
-is running, the cylinder number is printed on
-the console for every 10th cylinder read.
-.Sh EXAMPLES
-A sample run of
-.Nm
-is shown below.
-In this example (using a 750),
-.Nm drtest
-is loaded from the root file system;
-usually it
-will be loaded from the machine's
-console storage device.
-Boldface means user input.
-As usual, ``#'' and ``@'' may be used to edit input.
-.Bd -unfilled -offset indent
-.Li \&>>> Ns Sy B/3
-.Li \&%%
-.Li \&loading hk(0,0)boot
-.Li \&Boot
-.Li \&: Sy \&hk(0,0)drtest
-.Li Test program for stand-alone up and hp driver
-
-.Li Debugging level (1=bse, 2=ecc, 3=bse+ecc)?
-.Li Enter disk name [type(adapter,unit),\ e.g.\ hp(1,3)]? Sy hp(0,0)
-.Li Device data: #cylinders=1024, #tracks=16, #sectors=32
-.Li Testing hp(0,0), chunk size is 16384 bytes.
-.Em (chunk\ size\ is\ the\ number\ of\ bytes read per disk access)
-.Li Start ...Make sure hp(0,0) is online
-.Li \ ...
-.Em (errors are reported as they occur)
-.Li \ ...
-.Em (...program restarts to allow checking other disks)
-.Em (...to abort halt machine with \&^P)
-.Ed
-.Sh DIAGNOSTICS
-The diagnostics are intended to be self explanatory.
-Note, however, that the device number in the diagnostic messages
-is identified as
-.Em typeX
-instead of
-.Em type(a,u)
-where
-.Ar X
-\&= a*8+u, e.g., hp(1,3) becomes hp11.
-.Sh SEE ALSO
-.Xr format 8
-.Sh HISTORY
-The
-.Nm
-command appeared in
-.Bx 4.2 .
-.Sh AUTHORS
-Helge Skrivervik
diff --git a/share/man/man8/man8.vax/format.8 b/share/man/man8/man8.vax/format.8
deleted file mode 100644
index fbe3e219b4b..00000000000
--- a/share/man/man8/man8.vax/format.8
+++ /dev/null
@@ -1,288 +0,0 @@
-.\"	$OpenBSD: format.8,v 1.17 2007/05/31 19:20:00 jmc Exp $
-.\" Copyright (c) 1980, 1983 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. 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: @(#)format.8	6.6 (Berkeley) 4/20/91
-.\"
-.Dd $Mdocdate: May 31 2007 $
-.Dt FORMAT 8 vax
-.Os
-.Sh NAME
-.Nm format
-.Nd how to format disk packs
-.Sh DESCRIPTION
-There are two ways to format disk packs.
-The simplest is to use the
-.Nm
-program.
-The alternative is to use the DEC standard formatting
-software which operates under the DEC diagnostic supervisor.
-This manual page describes the operation of
-.Nm format ,
-then concludes with some remarks about using the DEC formatter.
-.Pp
-.Nm
-is a stand-alone program used to
-format and check disks prior to constructing
-file systems.
-In addition to the formatting
-operation,
-.Nm
-records any bad sectors encountered
-according to DEC standard 144.
-Formatting is performed one track at a
-time by writing the appropriate
-headers and a test pattern and then checking
-the sector by reading and verifying the pattern, using
-the controller's ECC for error detection.
-A sector is marked bad if an unrecoverable media
-error is detected, or if a correctable
-ECC error too many bits in length
-is detected (such errors are indicated as
-.Dq ECC
-in the summary printed upon
-completing the format operation).
-.Pp
-After the entire disk
-has been formatted and checked,
-the total number of errors are reported,
-any bad sectors and skip sectors are marked,
-and a bad sector forwarding table
-is written to the disk in the first five
-even numbered sectors of the last track.
-It is also possible to reformat sections of the disk
-in units of tracks.
-.Nm
-may be used on any UNIBUS or MASSBUS drive
-supported by the
-.Xr up 4
-and
-.Xr hp 4
-device
-drivers which uses 4-byte headers (everything except RPs).
-.Pp
-The test pattern used during the media check
-may be selected from one of: 0xf00f (RH750 worst case),
-0xec6d (media worst case), and 0xa5a5 (alternating
-1's and 0's).
-Normally the media worst case pattern is used.
-.Pp
-.Nm
-also has an option to perform an extended
-.Dq severe burn-in ,
-which makes a number of passes using different patterns.
-The number of passes can be selected at run time,
-up to a maximum of 48,
-with provision for additional passes or termination
-after the preselected number of passes.
-This test runs for many hours, depending on the disk and processor.
-.Pp
-Each time
-.Nm
-is run to format an entire disk,
-a completely new bad sector table is generated
-based on errors encountered while formatting.
-The device driver, however, will always attempt to
-read any existing bad sector table when the device is
-first opened.
-Thus, if a disk pack has never previously been formatted,
-or has been formatted with different sectoring,
-five error messages will be printed when the driver attempts
-to read the bad sector table; these diagnostics should be ignored.
-.Pp
-Formatting a 400 megabyte disk on a MASSBUS disk controller
-usually takes about 20 minutes.
-Formatting on a UNIBUS disk controller takes significantly
-longer.
-For every hundredth cylinder formatted,
-.Nm format
-prints a message indicating the current cylinder being formatted.
-(This message is just to reassure people that nothing is
-amiss.)
-.Pp
-.Nm
-uses the standard notation of the stand-alone I/O library
-in identifying a drive to be formatted.
-A drive is specified as
-.Dq Ar zz Ns (x,y) ,
-where
-.Ar zz
-refers to the controller type (either
-.Ar hp
-or
-.Ar up ) ,
-.Ar x
-is the unit number of the drive;
-8 times the UNIBUS or MASSBUS
-adaptor number plus the MASSBUS drive number or UNIBUS
-drive unit number; and
-.Ar y
-is the file system partition
-on drive
-.Ar x
-(this should always be 0).
-For example,
-.Dq hp(1,0)
-indicates that drive
-1 on MASSBUS adaptor 0 should be formatted; while
-.Dq up(10,0)
-indicates that UNIBUS drive 2 on UNIBUS adaptor 1
-should be formatted.
-.Pp
-Before each formatting attempt,
-.Nm
-prompts the user in case debugging should be enabled
-in the appropriate device driver.
-A carriage return disables debugging information.
-.Pp
-.Nm
-should be used prior to building file systems (with
-.Xr newfs 8
-to ensure that all sectors with uncorrectable media errors
-are remapped).
-If a drive develops uncorrectable defects after formatting,
-.Xr badsect 8
-should be able to avoid the bad sectors.
-.Sh EXAMPLES
-A sample run of
-.Nm
-is shown below.
-In this example (using a VAX-11/780),
-.Nm
-is loaded from the console floppy;
-on an 11/750,
-.Nm
-will be loaded from the root file system with
-.Xr boot 8
-following a B/3 command.
-Boldface means user input.
-As usual, ``#'' and ``@'' may be used to edit input.
-.Bd -literal -offset indent
->>>\fBL FORMAT\fP
-	LOAD DONE, 00004400 BYTES LOADED
->>>\fBS 2\fP
-Disk format/check utility
-
-Enable debugging (0=none, 1=bse, 2=ecc, 3=bse+ecc)? \fB0\fP
-Device to format? \fBhp(8,0)\fP
-(\fIerror messages may occur as old bad sector table is read\fP)
-Formatting drive hp0 on adaptor 1: verify (yes/no)? \fByes\fP
-Device data: #cylinders=842, #tracks=20, #sectors=48
-Starting cylinder (0):
-Starting track (0):
-Ending cylinder (841):
-Ending track (19):
-Available test patterns are:
-.Ed
-.Bd -literal -offset indent-two
-1 - (f00f) RH750 worst case
-2 - (ec6d) media worst case
-3 - (a5a5) alternating 1's and 0's
-4 - (ffff) Severe burnin (up to 48 passes)
-.Ed
-.Bd -literal -offset indent
-Pattern (one of the above, other to restart)? \fB2\fP
-Maximum number of bit errors to allow for soft ECC (3):
-Start formatting...make sure the drive is online
- ...
-(\fIsoft ecc's and other errors are reported as they occur\fP)
- ...
-(\fIif 4 write check errors were found, the program terminates like this...\fP)
- ...
-Errors:
-Bad sector: 0
-Write check: 4
-Hard ECC: 0
-Other hard: 0
-Marked bad: 0
-Skipped: 0
-Total of 4 hard errors revectored.
-Writing bad sector table at block 808272
-(\fI808272 is the block # of the first block in the bad sector table\fP)
-Done
-(\fI...program restarts to allow formatting other disks\fP)
-(\fI...to abort halt machine with ^P\fP)
-.Ed
-.Sh DIAGNOSTICS
-The diagnostics are intended to be self explanatory.
-.Sh USING DEC SOFTWARE TO FORMAT
-.Sy Warning:  These instructions are for people with 11/780 CPUs.
-The steps needed for 11/750 or 11/730 CPUs are similar, but not
-covered in detail here.
-.Pp
-The formatting procedures are different for each type of disk.
-Listed here are the formatting procedures for RK07's, RP0X, and RM0X disks.
-.Pp
-You should shut down UNIX and halt the machine to do any disk formatting.
-Make certain you put in the pack you want formatted.
-It is also a good idea to spin down or write protect the disks you don't
-want to format, just in case.
-.Ss Formatting an RK07
-Load the console floppy labeled, "RX11 VAX DSK LD DEV #1" in
-the console disk drive, and type the following commands:
-.RS
-.Bd -literal
->>>BOOT
-DIAGNOSTIC SUPERVISOR.  ZZ-ESSAA-X5.0-119  23-JAN-1980 12:44:40.03
-DS>ATTACH DW780 SBI DW0 3 5
-DS>ATTACH RK611 DMA
-DS>ATTACH RK07 DW0 DMA0
-DS>SELECT DMA0
-DS>LOAD EVRAC
-DS>START/SEC:PACKINIT
-.Ed
-.Ss Formatting an RP0X
-Follow the above procedures except that the
-ATTACH and SELECT lines should read:
-.nf
-.Bd -literal
-DS>ATTACH RH780 SBI RH0 8 5
-DS>ATTACH RP0X RH0 DBA0		(RP0X is, e.g. RP06)
-DS>SELECT DBA0
-.Ed
-.Pp
-This is for drive 0 on mba0; use 9 instead of 8 for mba1, etc.
-.Ss Formatting an RM0X
-Follow the above procedures except that the
-ATTACH and SELECT lines should read:
-.Bd -literal
-DS>ATTACH RH780 SBI RH0 8 5
-DS>ATTACH RM0X RH0 DRA0
-DS>SELECT DRA0
-.Ed
-.Pp
-Don't forget to put your UNIX console floppy back
-in the floppy disk drive.
-.Sh SEE ALSO
-.Xr badsect 8 ,
-.Xr newfs 8
-.Sh BUGS
-An equivalent facility should be available which operates under
-a running UNIX system.
-.Pp
-It should be possible to reformat or verify part or all of a disk,
-then update the existing bad sector table.
diff --git a/share/man/man8/man8.vax/installboot.8 b/share/man/man8/man8.vax/installboot.8
deleted file mode 100644
index 5601590f6da..00000000000
--- a/share/man/man8/man8.vax/installboot.8
+++ /dev/null
@@ -1,78 +0,0 @@
-.\"	$OpenBSD: installboot.8,v 1.13 2007/05/31 19:20:00 jmc Exp $
-.\" Copyright (c) 1986, 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. 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: @(#)installboot.8	7.2 (Berkeley) 3/16/91
-.\"
-.Dd $Mdocdate: May 31 2007 $
-.Dt INSTALLBOOT 8 vax
-.Os
-.Sh NAME
-.Nm installboot
-.Nd installs a boot program in a file system
-.Sh SYNOPSIS
-.Nm installboot
-.Ar bootblock bootprog special
-.Sh DESCRIPTION
-.Nm installboot
-concatenates
-.Ar bootblock
-and
-.Ar bootprog
-and writes at most
-.Dv BBSIZE
-bytes (from
-.Aq Pa sys/fs.h )
-of them on the first bytes of
-.Ar special .
-.Sh FILES
-.Bl -tag -width /usr/mdec/bootxxx -compact
-.It Pa /usr/mdec/??boot
-boot blocks
-.It Pa /usr/mdec/boot??
-boot programs
-.El
-.Sh EXAMPLES
-.Bd -literal -offset indent
-cd /usr/mdec
-installboot raboot bootra /dev/ra0a
-.Ed
-.Sh SEE ALSO
-.Xr dd 1 ,
-.Xr newfs 8
-.Sh HISTORY
-The
-.Nm
-command appeared in
-.Bx 4.3 tahoe .
-.Sh AUTHORS
-This manual page was written by Geoff Collyer.
-.Sh BUGS
-There is no convenient way to determine the names of the boot blocks
-and boot programs without
-.Em a priori
-knowledge of one's make of disk.