initial import of NetBSD tree

52 files changed, 7664 insertions, 0 deletions

diff --git a/share/man/man4/man4.vax/Makefile b/share/man/man4/man4.vax/Makefile
new file mode 100644
index 00000000000..1904613f5a1
--- /dev/null
+++ b/share/man/man4/man4.vax/Makefile
@@ -0,0 +1,12 @@
+#	from: @(#)Makefile	5.4 (Berkeley) 5/11/90
+#	$Id: Makefile,v 1.1 1995/10/18 08:44:33 deraadt Exp $
+
+MAN=	acc.4 ad.4 autoconf.4 cons.4 crl.4 css.4 ct.4 ddn.4 de.4 dh.4 dhu.4 \
+	dmc.4 dmf.4 dmz.4 dn.4 dz.4 ec.4 en.4 ex.4 fl.4 hdh.4 hk.4 hp.4 \
+	ht.4 hy.4 ik.4 il.4 intro.4 ix.4 kg.4 lp.4 mem.4 mt.4 mtio.4 np.4 \
+	pcl.4 ps.4 qe.4 rx.4 tm.4 tmscp.4 ts.4 tu.4 uda.4 up.4 ut.4 \
+	uu.4 va.4 vp.4 vv.4
+MLINKS=	mem.4 kmem.4
+MANSUBDIR=/vax
+
+.include <bsd.prog.mk>
diff --git a/share/man/man4/man4.vax/acc.4 b/share/man/man4/man4.vax/acc.4
new file mode 100644
index 00000000000..d1d7f56afcb
--- /dev/null
+++ b/share/man/man4/man4.vax/acc.4
@@ -0,0 +1,105 @@
+.\" Copyright (c) 1983, 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: @(#)acc.4	6.4 (Berkeley) 3/27/91
+.\"	$Id: acc.4,v 1.1 1995/10/18 08:44:33 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt ACC 4 vax
+.Os BSD 4.2
+.Sh NAME
+.Nm acc
+.Nd
+.Tn ACC LH/DH IMP
+interface
+.Sh SYNOPSIS
+.Cd pseudo-device imp "device acc0 at uba0 csr 167600 vector accrint accxint"
+.Sh DESCRIPTION
+The 
+.Nm acc
+device provides a Local Host/Distant Host
+interface to an
+.Tn IMP .
+It is normally used when participating
+in the
+.Tn DARPA
+Internet.  The controller itself is not accessible
+to users, but instead provides the hardware support to the
+.Tn IMP
+interface described in
+.Xr imp 4 .
+The configuration entry for the
+.Xr imp
+must also include the
+.Em pseudo-device
+as shown above.
+.Sh DIAGNOSTICS
+.Bl -diag
+.It acc%d: not alive.
+The initialization routine was entered even though the device
+did not autoconfigure.  This indicates a system problem.
+.Pp
+.It acc%d: can't initialize.
+Insufficient UNIBUS resources existed to initialize the device.
+This is likely to occur when the device is run on a buffered
+data path on an 11/750 and other network interfaces are also
+configured to use buffered data paths, or when it is configured
+to use buffered data paths on an 11/730 (which has none).
+.Pp
+.It acc%d: imp doesn't respond, icsr=%b.
+The driver attempted to initialize the device, but the
+.Tn IMP
+failed to respond after 500 tries.  Check the cabling.
+.Pp
+.It acc%d: stray xmit interrupt, csr=%b.
+An interrupt occurred when no output had previously been started. 
+.Pp
+.It acc%d: output error, ocsr=%b, icsr=%b.
+The device indicated a problem sending data on output.
+.Pp
+.It acc%d: input error, csr=%b.
+The device indicated a problem receiving data on input.
+.Pp
+.It acc%d: bad length=%d.
+An input operation resulted in a data transfer of less than
+0 or more than 1008 bytes of
+data into memory (according to the word count register).
+This should never happen as the maximum size of a
+.Pf host- Tn IMP
+message is 1008 bytes.
+.El
+.Sh SEE ALSO
+.Xr netintro 4
+.Sh HISTORY
+The
+.Nm
+interface appeared in
+.Bx 4.2 .
diff --git a/share/man/man4/man4.vax/ad.4 b/share/man/man4/man4.vax/ad.4
new file mode 100644
index 00000000000..76b3e53530b
--- /dev/null
+++ b/share/man/man4/man4.vax/ad.4
@@ -0,0 +1,88 @@
+.\" 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. 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: @(#)ad.4	6.2 (Berkeley) 3/27/91
+.\"	$Id: ad.4,v 1.1 1995/10/18 08:44:33 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt AD 4 vax
+.Os BSD 4.2
+.Sh NAME
+.Nm ad
+.Nd Data Translation A/D converter
+.Sh SYNOPSIS
+.Cd "device ad0 at uba0 csr 0170400 vector adintr"
+.Sh DESCRIPTION
+The
+.Nm \&ad
+driver
+provides an interface to the Data Translation A/D converter.
+This is
+.Em not
+a real-time driver, but merely allows
+the user process to sample the board's channels one at a time.
+Each minor device selects a different
+.Tn A/D
+board.
+.Pp
+The driver communicates to a user process by means of
+.Xr ioctl 2 Ns s.
+The
+.Dv AD_CHAN
+.Xr ioctl
+selects which channel of the board to read.
+For example,
+.Bd -literal -offset indent
+chan = 5;
+ioctl(fd, AD_CHAN, &chan);
+.Ed
+.Pp
+selects channel 5.
+The
+.Dv AD_READ
+.Xr ioctl 2
+actually reads the data and returns it to the user
+process.
+An example is
+.Bd -literal -offset indent
+ioctl(fd, AD_READ, &data);
+.Ed
+.Sh FILES
+.Bl -tag -width /dev/adx -compact
+.It Pa /dev/ad
+.El
+.Sh DIAGNOSTICS
+None.
+.Sh HISTORY
+The
+.Nm
+driver appeared in
+.Bx 4.1 .
diff --git a/share/man/man4/man4.vax/autoconf.4 b/share/man/man4/man4.vax/autoconf.4
new file mode 100644
index 00000000000..765b154c8f4
--- /dev/null
+++ b/share/man/man4/man4.vax/autoconf.4
@@ -0,0 +1,274 @@
+.\" Copyright (c) 1980, 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: @(#)autoconf.4	6.3 (Berkeley) 3/27/91
+.\"	$Id: autoconf.4,v 1.1 1995/10/18 08:44:33 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt AUTOCONF 4
+.Os BSD 4
+.Sh NAME
+.Nm autoconf
+.Nd "diagnostics from the autoconfiguration code"
+.Sh DESCRIPTION
+When
+.Tn UNIX
+bootstraps it probes the innards of the machine
+on which it is running and
+locates controllers, drives, and other devices.
+Each item found is recorded on the console.
+This procedure is driven by a system
+configuration table which is processed by
+.Xr config 8
+and compiled into each kernel.
+.Pp
+On the
+.Tn VAX ,
+devices in
+.Tn NEXUS
+slots are normally noted, thus memory controllers,
+.Tn UNIBUS
+and
+.Tn MASSBUS
+adaptors.  Devices which are not supported which
+are found in
+.Tn NEXUS
+slots are noted also.
+The Q-bus on the
+.Tn MICROVAX
+is configured in the same way as the
+.Tn UNIBUS.
+.Pp
+.Tn MASSBUS
+devices are located by a very deterministic procedure since
+.Tn MASSBUS
+space is completely probe-able.  If devices exist which
+are not configured they will be silently ignored; if devices exist of
+unsupported type they will be noted.
+.Pp
+.Tn UNIBUS
+devices are located by probing to see if their control-status
+registers respond.  If not, they are silently ignored.  If the control
+status register responds but the device cannot be made to interrupt,
+a diagnostic warning will be printed on the console and the device
+will not be available to the system. 
+.Pp
+Normally, the system uses the disk from which it was loaded as the root
+filesystem.
+If that is not possible,
+a generic system will pick its root device
+as the
+.Dq best
+available device
+.Pf ( Tn MASSBUS
+disks are better than
+.Tn SMD UNIBUS
+disks are better than
+.Tn RK07 Ns s ;
+the device must be drive 0
+to be considered).
+If such a system is booted with the
+.Dv RB_ASKNAME
+option (see
+.Xr reboot 2 ) ,
+then the name of the root device is read from the console terminal at boot
+time, and any available device may be used.
+.Sh DIAGNOSTICS
+.Bl -diag
+.It cpu type %d not configured.
+You tried to boot
+.Tn UNIX
+on a
+.Tn CPU
+type which it doesn't (or at least this compiled version of
+.Tn UNIX
+doesn't)
+understand.
+.Pp
+.It mba%d at tr%d.
+A
+.Tn MASSBUS
+adapter was found in
+.Ql tr%d
+(the
+.Tn NEXUS
+slot number).
+.Tn UNIX
+will call it
+.Ql mba%d .
+.Pp
+.It %d mba's not configured.
+More
+.Tn MASSBUS
+adapters were found on
+the machine than were declared in the machine configuration; the excess
+.Tn MASSBUS
+adapters will not be accessible.
+.Pp
+.It uba%d at tr%d.
+A
+.Tn UNIBUS
+adapter was found in
+.Ql tr%d
+(the
+.Tn NEXUS
+slot number).
+.Tn UNIX
+will call it
+.Ql uba%d .
+.Pp
+.It dr32 unsupported (at tr %d).
+A
+.Tn DR Ns 32
+interface was found in
+a
+.Tn NEXUS ,
+for which
+.Tn UNIX
+does not have a driver.
+.Pp
+.It ci unsupported (at tr %d).
+A
+.Tn CI
+interface was found in
+a
+.Tn NEXUS ,
+for which
+.Tn UNIX
+does not have a driver.
+.Pp
+.It mcr%d at tr%d.
+A memory controller was found in
+.Ql tr%d
+(the
+.Tn NEXUS
+slot number).
+.Tn UNIX
+will call it
+.Ql mcr%d .
+.Pp
+.It 5 mcr's unsupported.
+.Tn UNIX
+supports only 4 memory controllers
+per
+.Tn CPU .
+.Pp
+.It mpm unsupported (at tr%d).
+Multi-port memory is unsupported
+in the sense that
+.Tn UNIX
+does not know how to poll it for
+.Tn ECC
+errors.
+.Pp
+.It %s%d at mba%d drive %d.
+A tape formatter or a disk was found
+on the
+.Tn MASSBUS ;
+for disks
+.Ql %s%d
+will look like
+.Dq Li hp0 ,
+for tape formatters
+like
+.Dq Li ht1 .
+The drive number comes from the unit plug on the drive
+or in the
+.Tn TM
+formatter
+.Pf ( Em not
+on the tape drive; see below).
+.Pp
+.It %s%d at %s%d slave %d.
+(For
+.Tn MASSBUS
+devices).
+Which would look like
+.Dq Li tu0 at ht0 slave 0 ,
+where
+.Dq Li tu0
+is the name for the tape device and
+.Dq Li ht0
+is the name
+for the formatter.  A tape slave was found on the tape formatter at the
+indicated drive number (on the front of the tape drive).
+.Ux
+will call the device, e.g.,
+.Dq Li tu0 .
+.Pp
+.It "%s%d at uba%d csr %o vec %o ipl %x."
+The device
+.Ql %s%d ,
+e.g.
+.Dq Li dz0
+was found on
+.Ql uba%d
+at control-status register address
+.Ql \&%o
+and with
+device vector
+.Ql \&%o .
+The device interrupted at priority level
+.Ql \&%x .
+.Pp
+.It %s%d at uba%d csr %o zero vector.
+The device did not present
+a valid interrupt vector, rather presented 0 (a passive release condition)
+to the adapter.
+.Pp
+.It %s%d at uba%d csr %o didn't interrupt.
+The device did not interrupt,
+likely because it is broken, hung, or not the kind of device it is advertised
+to be.
+.Pp
+.It %s%d at %s%d slave %d.
+(For UNIBUS devices).
+Which would look like 
+.Dq Li up0 at sc0 slave 0 ,
+where
+.Dq Li up0
+is the name of a disk drive and
+.Dq Li sc0
+is the name
+of the controller.  Analogous to
+.Tn MASSBUS
+case.
+.El
+.Sh SEE ALSO
+.Xr intro 4 ,
+.Xr boot 8 ,
+.Xr config 8
+.Sh HISTORY
+The
+.Nm
+feature
+appeared in
+.Bx 4.1 .
diff --git a/share/man/man4/man4.vax/cons.4 b/share/man/man4/man4.vax/cons.4
new file mode 100644
index 00000000000..f6c76f91bc6
--- /dev/null
+++ b/share/man/man4/man4.vax/cons.4
@@ -0,0 +1,151 @@
+.\" Copyright (c) 1980, 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: @(#)cons.4	6.3 (Berkeley) 3/27/91
+.\"	$Id: cons.4,v 1.1 1995/10/18 08:44:33 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt CONS 4 vax
+.Os BSD 4
+.Sh NAME
+.Nm cons
+.Nd "VAX-11 console interface"
+.Sh DESCRIPTION
+The console is available to the processor through the console registers.
+It acts like a normal terminal, except that when the local functions are
+not disabled,
+.Ic \&^P
+(control-P) puts the console in local console mode (where
+the prompt is
+.Sq Li >>> ) .
+The operation of the console in this mode varies
+slightly per-processor.
+.Ss Tn VAX No 11/780 or 785
+On either the
+.Tn VAX
+11/780 or 785 the following commands may be used
+after placing the console in local mode with
+.Ic ^P .
+.Pp
+.Bl -tag -width continue -compact -offset 4n
+.It Ic c
+.It Ic continue
+Re-enter conversational mode
+if the processor was halted.
+.Pp
+.It Ic h
+.It Ic halt
+Halt the CPU.
+On an 11/780 or 785
+the processor is not stopped by entering local console mode.
+.Pp
+.It Ic set t p
+(set terminal program)
+Re-enter conversational mode
+if the processor is still
+running.
+.Pp
+.It Ic P
+(proceed)
+Get out of
+.Tn ODT
+mode.
+.Pp
+.It Ic <break>
+If you hit the break key on the console, then the console
+.Tn LSI Ns -11
+will go into
+.Tn ODT
+(console debugger mode).
+.El
+.Pp
+.Ss Tn VAX No 11/750 or 11/730
+On an 11/750
+or an 11/730
+the processor is halted whenever the console is not in conversational mode.
+.Pp
+.Bl -tag -width continue -compact -offset 4n
+.It Ic C
+Return to conversational mode.
+.Pp
+.It Ic ret
+Return from remote diagnosis mode to local console
+mode.
+.Pp
+.It Ic \&^D
+(11/750 only)
+When in console mode on an 11/750 which has a remote diagnosis module,
+a
+.Ic \&^D
+will put you in remote diagnosis mode, where the prompt will be
+.ql RDM> .
+.El
+.Pp
+.Ss Tn VAX No 8600 or 8650
+The
+.Tn VAX
+8600 (8650) console normally works in the same way as the 11/750,
+except that there are many additional modes and commands.
+.Pp
+.Bl -tag -width continue -compact -offset 4n
+.It Ic c
+.It Ic continue
+Return to
+conversational mode.
+.Pp
+.It Ic halt
+Halt the processor if
+.Tn HEX
+debug enabled.
+.Pp
+.It Ic p
+Halt the processor if in normal mode.
+.El
+.Pp
+With the above proviso's the console works like any other
+.Ux
+terminal.
+.Sh FILES
+.Bl -tag -width /dev/console -compact
+.It Pa /dev/console
+.El
+.Sh SEE ALSO
+.Xr tty 4 ,
+.Xr reboot 8
+.Rs
+.%T "VAX Hardware Handbook"
+.Re
+.Sh HISTORY
+The
+.Nm cons
+interface
+appeared in
+.Bx 4.0 .
diff --git a/share/man/man4/man4.vax/crl.4 b/share/man/man4/man4.vax/crl.4
new file mode 100644
index 00000000000..4617045b047
--- /dev/null
+++ b/share/man/man4/man4.vax/crl.4
@@ -0,0 +1,83 @@
+.\" 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. 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: @(#)crl.4	6.3 (Berkeley) 3/27/91
+.\"	$Id: crl.4,v 1.1 1995/10/18 08:44:33 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt CRL 4 vax
+.Os BSD 4.3
+.Sh NAME
+.Nm crl
+.Nd
+.Tn VAX
+8600 console
+.Tn RL Ns 02
+interface
+.Sh DESCRIPTION
+This is a simple interface to the
+.Tn DEC
+.Tn RL Ns 02
+disk unit which is part of the console
+subsystem on the
+.Tn VAX
+8600 and 8650.
+Access is given to the entire
+.Tn RL Ns 02
+disk; the pack format is the same
+as that of
+.Tn RL Ns 02
+disks on other controllers.
+As on other
+.Tn VAX
+console media, transfers are done a word at a time
+using privileged registers (i.e., slowly).
+.Pp
+All
+.Tn I/O
+is raw; the seek addresses in raw transfers should be a multiple
+of 512 bytes and a multiple of 512 bytes should be transferred,
+as in other
+.Dq raw
+disk interfaces.
+(Although the sector size is actually 256 bytes, the driver allows
+operations only on 512-byte boundaries.)
+.Sh FILES
+.Bl -tag -width /dev/crl -compact
+.It Pa /dev/crl
+.El
+.Sh SEE ALSO
+.Xr arff 8
+.Sh HISTORY
+The
+.Nm
+driver appeared in
+.Bx 4.3 .
diff --git a/share/man/man4/man4.vax/css.4 b/share/man/man4/man4.vax/css.4
new file mode 100644
index 00000000000..c4f60e000e0
--- /dev/null
+++ b/share/man/man4/man4.vax/css.4
@@ -0,0 +1,105 @@
+.\" 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. 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: @(#)css.4	6.2 (Berkeley) 3/27/91
+.\"	$Id: css.4,v 1.1 1995/10/18 08:44:33 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt CSS 4 vax
+.Os BSD 4.2
+.Sh NAME
+.Nm css
+.Nd
+.Tn DEC IMP-11A LH/DH IMP
+interface
+.Sh SYNOPSIS
+.Cd "pseudo-device imp device css0 \&at uba0 csr 167600 flags 10 vector cssrint cssxint"
+.Sh DESCRIPTION
+The 
+.Nm css
+device provides a Local Host/Distant Host
+interface to an
+.Tn IMP .
+It is normally used when participating
+in the
+.Tn DARPA
+Internet.  The controller itself is not accessible
+to users, but instead provides the hardware support to the
+.Tn IMP
+interface described in
+.Xr imp 4 .
+The configuration entry for the
+.Xr imp
+must also include the
+.Em pseudo-device
+as shown above.
+.Sh DIAGNOSTICS
+.Bl -diag
+.It css%d: not alive.
+The initialization routine was entered even though the device
+did not autoconfigure.  This is indicates a system problem.
+.Pp
+.It css%d: can't initialize.
+Insufficient
+.Tn UNIBUS
+resources existed to initialize the device.
+This is likely to occur when the device is run on a buffered
+data path on an 11/750 and other network interfaces are also
+configured to use buffered data paths, or when it is configured
+to use buffered data paths on an 11/730 (which has none).
+.Pp
+.It css%d: imp doesn't respond, icsr=%b.
+The driver attempted to initialize the device, but the
+.Tn IMP
+failed to respond after 500 tries.  Check the cabling.
+.Pp
+.It css%d: stray output interrupt csr=%b.
+An interrupt occurred when no output had previously been started. 
+.Pp
+.It css%d: output error, ocsr=%b icsr=%b.
+The device indicated a problem sending data on output.
+.Pp
+.It css%d: recv error, csr=%b.
+The device indicated a problem receiving data on input.
+.Pp
+.It css%d: bad length=%d.
+An input operation resulted in a data transfer of less than
+0 or more than 1008 bytes of
+data into memory (according to the word count register).
+This should never happen as the maximum size of a
+.Pf host- Tn IMP
+message is 1008 bytes.
+.El
+.Sh HISTORY
+The
+.Nm
+interface appeared in
+.Bx 4.2 .
diff --git a/share/man/man4/man4.vax/ct.4 b/share/man/man4/man4.vax/ct.4
new file mode 100644
index 00000000000..d53e26bface
--- /dev/null
+++ b/share/man/man4/man4.vax/ct.4
@@ -0,0 +1,71 @@
+.\" Copyright (c) 1980, 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: @(#)ct.4	6.3 (Berkeley) 3/27/91
+.\"	$Id: ct.4,v 1.1 1995/10/18 08:44:33 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt CT 4 vax
+.Os BSD 4
+.Sh NAME
+.Nm \&ct
+.Nd "C/A/T phototypesetter interface"
+.Sh SYNOPSIS
+.Cd "device ct0 at uba0 csr 0167760 vector ctintr"
+.Sh DESCRIPTION
+This is an interface to either a Graphic Systems
+.Tn C/A/T
+phototypesetter
+or an Autologic
+.Tn APS-Micro5
+using a
+.Tn DR-11 C
+interface.
+.Pp
+The
+.Nm \&ct
+is a write only device.
+.Sh FILES
+.Bl -tag -width /dev/catxx -compact
+.It Pa /dev/cat
+.El
+.Sh DIAGNOSTICS
+None.
+.Sh SEE ALSO
+.Xr troff 1
+.Rs
+.%T Phototypesetter interface specification
+.Re
+.Sh HISTORY
+The
+.Nm \&ct
+driver appeared in
+.Bx 4.1 .
diff --git a/share/man/man4/man4.vax/ddn.4 b/share/man/man4/man4.vax/ddn.4
new file mode 100644
index 00000000000..3c6119cde00
--- /dev/null
+++ b/share/man/man4/man4.vax/ddn.4
@@ -0,0 +1,133 @@
+.\" Copyright (c) 1983, 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: @(#)ddn.4	6.5 (Berkeley) 3/27/91
+.\"	$Id: ddn.4,v 1.1 1995/10/18 08:44:33 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt DDN 4 vax
+.Os BSD 4.3
+.Sh NAME
+.Nm ddn
+.Nd
+.Tn DDN
+Standard Mode
+.Tn X.25
+.Tn IMP
+interface
+.Sh SYNOPSIS
+.Cd "device ddn0 at uba0 csr 166740 vector ddnintr"
+.Sh DESCRIPTION
+The 
+.Nm ddn
+device provides a
+.Tn DDN
+Standard Mode
+.Tn X.25
+interface to an
+.Tn IMP
+using
+the
+.Tn ACC ACP625
+.Tn X.25
+board.  It is normally used for connecting to
+the Defense Data Network
+.Pq Tn DDN .
+The controller itself is not accessible
+to users, but instead provides a network interface for the
+Internet Protocol described in
+.Xr ip 4 .
+.Sh DIAGNOSTICS
+.Bl -diag
+.It ddn%d: not alive.
+The initialization routine was entered even though the device
+did not autoconfigure.  This indicates a system problem.
+.Pp
+.It ddn%d: failed getting UBA resources for lcn %d."
+Insufficient
+.Tn UNIBUS
+resources existed to initialize the device.
+This is likely to be a shortage of
+.Tn UNIBUS
+mapping registers.
+.Pp
+.It ddn%d: couldn't get X25 init buffer.
+This indicates that an 
+.Em mbuf
+could not be allocated for sending the initialization message to the
+.Tn ACP Ns 625.
+.Pp
+.It DDN: illegal X25 address length!
+.It DDN: illegal X25 address format!
+These errors indicate a problem with the called
+.Tn X.25
+address received
+from the
+.Tn IMP
+on an incoming call.
+.Pp
+.It X25 RESET on lcn = %d.
+This indicates that an unexpected
+.Tn X.25
+.Tn RESET
+was received on the
+indicated
+.Tn LCN .
+.Pp
+.It X25 INTERRUPT on lcn = %d, code = %d.
+This indicates that an unexpected
+.Tn X.25
+.Tn INTERRUPT
+Packet was received on the
+indicated
+.Tn LCN .
+.Pp
+.It ddn%d: failed to get supr msg bfr!
+This indicates that an 
+.Em mbuf
+could not be allocated for sending a supervisor message to the
+.Tn ACP625 .
+.El
+.Pp
+Any other error message from
+.Ql ddn%d:
+indicates a serious error
+detected by either the driver or the
+.Tn ACP Ns 625
+firmware.
+.Sh SEE ALSO
+.Xr netintro 4 ,
+.Xr ip 4
+.Sh HISTORY
+The
+.Nm
+interface appeared in
+.Bx 4.3 .
diff --git a/share/man/man4/man4.vax/de.4 b/share/man/man4/man4.vax/de.4
new file mode 100644
index 00000000000..678cdaadf67
--- /dev/null
+++ b/share/man/man4/man4.vax/de.4
@@ -0,0 +1,132 @@
+.\" Copyright (c) 1986, 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: @(#)de.4	6.5 (Berkeley) 3/27/91
+.\"	$Id: de.4,v 1.1 1995/10/18 08:44:34 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt DE 4 vax
+.Os BSD 4.2
+.Sh NAME
+.Nm de
+.Nd
+.Tn DEC DEUNA
+10 Mb/s Ethernet interface
+.Sh SYNOPSIS
+.Cd "device de0 at uba0 csr 174510 vector deintr"
+.Sh DESCRIPTION
+The
+.Nm de
+interface provides access to a 10 Mb/s Ethernet network through
+a Digital Equipment
+.Tn UNIBUS
+Network Adapter
+.Pq Tn DEUNA .
+.Pp
+Each of the host's network addresses
+is specified at boot time with an
+.Dv SIOCSIFADDR
+.Xr ioctl 2 .
+The
+.Nm de
+interface employs the address resolution protocol described in
+.Xr arp 4
+to dynamically map between Internet and Ethernet addresses on the local
+network.
+.Pp
+The interface normally tries to use a
+.Dq trailer
+encapsulation
+to minimize copying data on input and output.
+The use of trailers is negotiated with
+.Tn ARP .
+This negotiation may be disabled, on a per-interface basis,
+by setting the
+.Dv IFF_NOTRAILERS
+flag with an 
+.Dv SIOCSIFFLAGS
+.Xr ioctl .
+.Sh DIAGNOSTICS
+.Bl -diag
+.It de%d: hardware address %s.
+This is a normal autoconfiguration message noting the 6 byte physical
+ethernet address of the adapter.
+.Pp
+.It de%d: oerror, flags=%b tdrerr=%b (len=%d).
+The hardware indicated an error
+in transmitting a packet to the cable.
+The status and error flags are reported.
+.Pp
+.It de%d: ierror, flags=%b lenerr=%b (len=%d).
+The hardware indicated an error
+in reading a packet from the cable.
+The status and error flags are reported.
+.Pp
+.It de%d: can't handle af%d.
+The interface was handed
+a message with addresses formatted in an unsuitable address
+family; the packet was dropped.
+.Pp
+.It de%d: buffer unavailable.
+The interface received more packets
+than it had buffers allocated to receive them.
+.Pp
+.It de%d: address change failed, csr0=%b csr1=%b.
+The interface was unable to reprogram
+its physical ethernet address.
+This may happen with very early models of the interface.
+This facility is used only when
+the controller is not the first network interface configured for
+.Tn XNS .
+.El
+.Pp
+The following messages indicate a probable hardware error performing
+the indicated operation during autoconfiguration or initialization.
+The two control and status registers
+should indicate the nature of the failure.
+See the hardware manual for details.
+.Pp
+.Bl -diag
+.It de%d: reset failed, csr0=%b csr1=%b.
+.It de%d: ppcb failed, csr0=%b csr1=%b.
+.It de%d: read addr failed, csr0=%b csr1=%b.
+.It de%d: wtring failed, csr0=%b csr1=%b.
+.It de%d: wtmode failed, csr0=%b csr1=%b.
+.El
+.Sh SEE ALSO
+.Xr netintro 4 ,
+.Xr inet 4 ,
+.Xr arp 4
+.Sh HISTORY
+The
+.Nm
+driver appeared in
+.Bx 4.3 .
diff --git a/share/man/man4/man4.vax/dh.4 b/share/man/man4/man4.vax/dh.4
new file mode 100644
index 00000000000..4fb8f4b1ea3
--- /dev/null
+++ b/share/man/man4/man4.vax/dh.4
@@ -0,0 +1,134 @@
+.\" Copyright (c) 1980, 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: @(#)dh.4	6.3 (Berkeley) 3/27/91
+.\"	$Id: dh.4,v 1.1 1995/10/18 08:44:34 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt DH 4 vax
+.Os BSD 4
+.Sh NAME
+.Nm dh
+.Nd
+.Tn DH-11 Ns / Tn DM-11
+multiplexer device interface
+.Sh SYNOPSIS
+.Cd "device dh0 at uba0 csr 0160020 vector dhrint dhxint" Op Ar flags
+.Cd "device dm0 at uba0 csr 0170500 vector dmintr" Op Ar flags
+.Sh DESCRIPTION
+A
+.Tn DH-11
+provides 16 serial communication lines;
+.Tn DM-11 Ns s
+may optionally be
+paired with
+.Tn DH-11 Ns s
+to provide modem control for the lines.
+.Pp
+An optional argument
+.Ar flags
+may be supplied with the device specification
+in the
+.Xr config 8
+file indicating
+that the line corresponding to
+bit number
+.Ar i
+is not properly
+connected, and should be treated as hard-wired with carrier
+always present.  Thus specifying
+.Ql flags 0x0004
+for
+.Li dh0
+would cause line
+.Pa ttyh2
+to be treated in this way.
+.Pp
+Normal I/O
+control parameters for individual lines are managed by
+.Xr ioctl 2
+calls.
+Line speeds may be initiated via
+.Xr getty 8
+and
+.Xr stty 1
+or may be communicated by other programs which
+utilize
+.Xr ioctl
+such as
+.Xr ifcongif 8 ,
+see
+.Xr tty 4  .
+.Pp
+The
+.Nm dh
+driver monitors the rate of input on each board,
+and switches between the use of character-at-a-time interrupts
+and input silos.
+While the silo is enabled during periods of high-speed input,
+the driver polls for input 30 times per second.
+.Sh FILES
+.Bl -tag -width /dev/tty[h-o][0-9a-f]x -compact
+.It Pa /dev/tty[h-o][0-9a-f]
+.It Pa /dev/ttyd[0-9a-f]
+.El
+.Sh DIAGNOSTICS
+.Bl -diag
+.It dh%d: NXM.
+No response from
+.Tn UNIBUS
+on a dma transfer
+within a timeout period.  This is often followed by a
+.Tn UNIBUS
+adapter
+error.  This occurs most frequently when the
+.Tn UNIBUS
+is heavily loaded
+and when devices which hog the bus (such as
+.Tn RK07 Ns s) are present.
+It is not serious.
+.Pp
+.It dh%d: silo overflow.
+The character input silo overflowed
+before it could be serviced.  This can happen if a hard error occurs
+when the
+.Tn CPU
+is running with elevated priority, as the system will
+then print a message on the console with interrupts disabled.
+It is not serious.
+.El
+.Sh SEE ALSO
+.Xr tty 4
+.Sh HISTORY
+A
+.Nm
+driver appeared in
+.At v6 .
diff --git a/share/man/man4/man4.vax/dhu.4 b/share/man/man4/man4.vax/dhu.4
new file mode 100644
index 00000000000..b14c5bbd241
--- /dev/null
+++ b/share/man/man4/man4.vax/dhu.4
@@ -0,0 +1,146 @@
+.\" Copyright (c) 1985, 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: @(#)dhu.4	6.3 (Berkeley) 3/27/91
+.\"	$Id: dhu.4,v 1.1 1995/10/18 08:44:34 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt DHU 4 vax
+.Os BSD 4.3
+.Sh NAME
+.Nm dhu
+.Nd
+.Tn DHU-11
+communications multiplexer
+.Sh SYNOPSIS
+.Cd "device dhu0 at uba0 csr 0160440 vector dhurint dhuxint"
+.Sh DESCRIPTION
+A
+.Tn DHU-11
+provides 16 communication lines.
+.Pp
+An optional argument
+.Ar flags
+may be supplied with the device specification
+in the config file indicating
+that the line corresponding to
+bit number
+.Ar i
+is not properly
+connected, and should be treated as hard-wired with carrier
+always present.  Thus specifying
+.Ql flags 0x0004
+for
+.Li dhu0
+would cause line
+.Pa ttyS2
+to be treated in this way.
+.Pp
+Normal I/O
+control parameters for individual lines are managed by
+.Xr ioctl 2
+calls.
+Individual
+.Tn DHU-11
+lines may be configured to run at any of 13 speeds
+(50, 200 and 38400 baud are not available);
+the speed may be set via
+.Xr getty 8
+or
+.Xr stty 1
+or may be communicated by other programs which
+utilize
+.Xr ioctl
+such as
+.Xr ifcongif 8 ,
+see
+.Xr tty 4 .
+.Pp
+The
+.Tn DHU-11
+driver normally uses input silos
+and delays receiver interrupts by 20 milliseconds
+rather than taking an interrupt on each input character.
+.Sh FILES
+.Bl -tag -width /dev/tty[S-Z][0-9a-f]xx -compact
+.It Pa /dev/tty[S-Z][0-9a-f]
+.El
+.Sh DIAGNOSTICS
+.Bl -diag
+.It dhu(%d,%d): NXM fault.
+No response from
+.Tn UNIBUS
+on a
+.Tn DMA
+transfer
+within a timeout period.  This is often followed by a
+.Tn UNIBUS
+adapter
+error.  This occurs most frequently when the
+.Tn UNIBUS
+is heavily loaded
+and when devices which hog the bus (such as
+.Tn RK07 Ns s )
+are present.
+It is not serious.
+.Pp
+.It dhu%d: silo overflow.
+The character input silo overflowed
+before it could be serviced.  This can happen if a hard error occurs
+when the
+.Tn CPU
+is running with elevated priority, as the system may
+then print a message on the console with interrupts disabled.
+.El
+.Sh NOTES
+The driver currently does not make full use of the hardware
+capabilities of the
+.Tn DHU-11 ,
+for dealing with
+.Tn XON/XOFF
+flow-control or hard-wired
+lines for example.
+.Pp
+Although the devices are not the same, a
+.Tn DHU-11
+can convince the
+.Tn DH-11
+autoconfiguration code that it is a
+.Tn DH-11 .
+.Pp
+The 4 40-way cables are a pain.
+.Sh SEE ALSO
+.Xr tty 4
+.Sh HISTORY
+The
+.Nm
+driver appeared in
+.Bx 4.3 .
diff --git a/share/man/man4/man4.vax/dmc.4 b/share/man/man4/man4.vax/dmc.4
new file mode 100644
index 00000000000..36df43d03f5
--- /dev/null
+++ b/share/man/man4/man4.vax/dmc.4
@@ -0,0 +1,159 @@
+.\" 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. 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: @(#)dmc.4	6.5 (Berkeley) 3/27/91
+.\"	$Id: dmc.4,v 1.1 1995/10/18 08:44:34 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt DMC 4 vax
+.Os BSD 4.2
+.Sh NAME
+.Nm dmc
+.Nd
+.Tn DEC
+.Tn DMC-11 Ns / Tn DMR-11
+point-to-point communications device
+.Sh SYNOPSIS
+.Cd "device dmc0 at uba0 csr 167600 vector dmcrint dmcxint"
+.Sh DESCRIPTION
+The
+.Nm dmc
+interface provides access to a point-to-point communications
+device which runs at either 1 Mb/s or 56 Kb/s.
+.Tn DMC-11 Ns s
+communicate
+using the
+.Tn DEC DDCMP
+link layer protocol.
+.Pp
+The
+.Nm dmc
+interface driver also supports a
+.Tn DEC
+.Tn DMR-11
+providing point-to-point
+communication running at data rates from 2.4 Kb/s to 1 Mb/s.
+.Tn DMR-11 Ns s
+are a more recent design and thus are preferred over
+.Tn DMC-11 Ns s .
+The
+.Dv NXMT
+and
+.Dv NRCV
+constants in the driver may be increased in this case,
+as the
+.Tn DMR
+can accept up to 64 transmit and receive buffers, as opposed
+to 7 for the
+.Tn DMC .
+.Pp
+The configuration flags specify how to set up the device,
+.Bl -column xxx -offset indent
+0	full duplex DDCMP (normal mode)
+1	DDCMP Maintence mode (generally useless)
+2	DDCMP Half Duplex, primary station
+3	DDCMP Half Duplex, secondary station
+.El
+.Pp
+Several device error counters are available via
+.Xr adb 1 ,
+for
+more information see the
+.Xr adb
+script
+.Pa /usr/lib/adb/dmcstats ,
+or the
+.Tn DMC-11
+technical manual.
+.Pp
+The host's address must be specified with an
+.Dv SIOCSIFADDR
+.Xr ioctl 2 ,
+and the destination address specified with a
+.Dv SIOCSIFDSTADDR
+.Xr ioctl ,
+before the interface will transmit or receive any packets.
+.Sh ROUTING
+The driver places a
+.Tn HOST
+entry in the kernel routing tables for the
+address given in the
+.Dv SIOCSIFDSTADDR
+.Xr ioctl.
+To use the
+.Tn DMC
+as a
+link between local nets, the route to the remote net must be added manually
+with the
+.Xr route 8
+command, or by the use of the routing process
+.Xr routed 8
+on each end of the link.
+.Sh DIAGNOSTICS
+.Bl -diag
+.It dmc%d: bad control %o.
+A bad parameter was passed to the
+.Em dmcload
+routine.
+.Pp
+.It dmc%d: unknown address type %d.
+An input packet was received which contained a type of
+address unknown to the driver.
+.Pp
+.It DMC fatal error 0%o.
+A fatal error in
+.Tn DDMCP
+occurred, causing the device to be restarted.
+.Pp
+.It DMC soft error 0%o.
+A non-fatal error in
+.Tn DDMCP
+has occurred.
+.Pp
+.It dmc%d: af%d not supported.
+The interface was handed a message which has
+addresses formatted in an unsuitable address family.
+.El
+.Sh SEE ALSO
+.Xr intro 4 ,
+.Xr inet 4
+.Sh HISTORY
+The
+.Nm
+driver appeared in
+.Bx 4.2 .
+.Sh BUGS
+The current version of the driver uses a link-level encapsulation
+so that multiple protocol types may be used.
+It is thus incompatible with earlier drivers,
+including the
+.Bx 4.2
+version.
diff --git a/share/man/man4/man4.vax/dmf.4 b/share/man/man4/man4.vax/dmf.4
new file mode 100644
index 00000000000..9e94e201bb2
--- /dev/null
+++ b/share/man/man4/man4.vax/dmf.4
@@ -0,0 +1,163 @@
+.\" 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. 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: @(#)dmf.4	6.5 (Berkeley) 3/27/91
+.\"	$Id: dmf.4,v 1.1 1995/10/18 08:44:34 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt DMF 4 vax
+.Os BSD 4.2
+.Sh NAME
+.Nm dmf
+.Nd
+.Tn DMF-32
+terminal multiplexor
+.Sh SYNOPSIS
+.Cd "device dmf0 at uba? csr 0160340 vector dmfsrint dmfsxint dmfdaint dmfdbint dmfrint dmfxint dmflint"
+.Sh DESCRIPTION
+The
+.Nm dmf
+device provides 8 lines of asynchronous serial line support.
+The first two of these have full modem control.
+The device also provides a line printer port
+similar to the
+.Tn LP-11 .
+Other features of the
+.Tn DMF-32
+are not supported.
+During autoconfiguration, the driver examines the configuration of each
+.Tn DMF-32
+and adjusts the interrupt vectors so that fewer vector locations are used
+if possible.
+.Pp
+An optional argument
+.Ar flags
+may be supplied with the device specification
+in the config file indicating
+that the line corresponding to
+bit number
+.Ar i
+is not properly
+connected, and should be treated as hard-wired with carrier
+always present.  Thus specifying
+.Ql flags 0x04
+for
+.Li dmf0
+would cause line
+.Pa ttyA2
+to be treated in this way.
+Flags should be set for all lines without hardware support for modem control.
+.Pp
+Normal
+.Tn I/O
+control parameters for individual lines are managed by
+.Xr ioctl 2
+calls.
+Line speeds may be initiated via
+.Xr getty 8
+and
+.Xr stty 1
+or may be communicated by other programs which
+utilize
+.Xr ioctl
+such as
+.Xr ifcongif 8 ,
+see
+.Xr tty 4  .
+.Pp
+The serial line part of the
+.Nm dmf
+driver normally enables the input silos with a short timeout
+(30 milliseconds); this allows multiple characters to be received
+per interrupt during periods of high-speed input.
+.Pp
+A line printer port on a
+.Nm dmf
+is designated by
+a minor device number of the form
+.Pf 128+ Ns Ar n .
+See
+.Xr MAKEDEV 8 .
+Column and lines per page may be changed from the default
+132 columns and 66 lines by encoding the number of columns
+in bits 8-15 of flags and the number of lines in bits 16-23.
+This device does not provide the fancy output canonicalization
+features of the
+.Xr lp 4
+driver.
+.Sh FILES
+.Bl -tag -width "/dev/tty[A-CE-I][0-7]" -compact
+.It Pa /dev/tty[A-CE-I][0-7]
+.It Pa /dev/ttyd[0-7]
+.It Pa /dev/lp
+.El
+.Sh DIAGNOSTICS
+.Bl -diag
+.It dmf%d: NXM line %d.
+No response from
+.Tn UNIBUS
+on a DMA transfer
+within a timeout period.  This is often followed by a
+.Tn UNIBUS
+adapter
+error.  This occurs most frequently when the
+.Tn UNIBUS
+is heavily loaded
+and when devices which hog the bus (such as
+.Tn RK07 Ns s )
+are present.
+It is not serious.
+.Pp
+.It dmf%d: silo overflow.
+The character input silo overflowed
+before it could be serviced.  This can happen if a hard error occurs
+when the
+.Tn CPU
+is running with elevated priority, as the system will
+then print a message on the console with interrupts disabled.
+It is not serious.
+.Pp
+.It dmfsrint, dmfsxint, dmfdaint, dmfdbint.
+One of the unsupported parts of the dmf interrupted; something
+is amiss, check your interrupt vectors for a conflict with another
+device.
+.El
+.Sh SEE ALSO
+.Xr tty 4
+.Sh HISTORY
+The
+.Nm
+driver appeared in
+.Bx 4.2 .
+.Sh BUGS
+It should be possible to set the silo timeout with a configuration file option,
+as the value is a trade-off between efficiency and response time for flow
+control and character echo.
diff --git a/share/man/man4/man4.vax/dmv.4 b/share/man/man4/man4.vax/dmv.4
new file mode 100644
index 00000000000..cce324f6876
--- /dev/null
+++ b/share/man/man4/man4.vax/dmv.4
@@ -0,0 +1,129 @@
+.\" Copyright (c) 1988, 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: @(#)dmv.4	6.2 (Berkeley) 3/27/91
+.\"	$Id: dmv.4,v 1.1 1995/10/18 08:44:34 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt DMV 4 vax
+.Os BSD 4.3
+.Sh NAME
+.Nm dmv
+.Nd
+.Tn DEC
+.Tn DMV-11
+point-to-point communications device
+.Sh SYNOPSIS
+.Cd "device dmv0 at uba0 csr 167000 vector dmvrint dmvxint"
+.Sh DESCRIPTION
+The
+.Nm dmv
+interface provides access to a point-to-point communications
+device which runs at up to 56 Kb/s.
+.Tn DMV-11 Ns s
+communicate
+using the
+.Tn DEC
+.Tn DDCMP
+link layer protocol.
+.Pp
+The host's address must be specified with an
+.Dv SIOCSIFADDR
+.Xr ioctl 2 ,
+and the destination address specified with a
+.Dv SIOCSIFDSTADDR
+.Xr ioctl ,
+before the interface will transmit or receive any packets.
+.Sh ROUTING
+The driver places a
+.Tn HOST
+entry in the kernel routing tables for the
+address given in the
+.Dv SIOCSIFDSTADDR
+.Xr ioctl .
+To use the
+.Tn DMV
+as a
+link between local nets, the route to the remote net must be added manually
+with the
+.Xr route 8
+command, or by the use of the routing process
+.Xr routed 8
+on each end of the link.
+.Sh DIAGNOSTICS
+.Bl -diag
+.It dmvprobe: can't start device.
+.It "dmvprobe: device init failed, bsel4=%o, bsel6=%o."
+The probe routine was unable to start the device.
+.Pp
+.It dmvinit: dmv%d not running.
+.It dmvrestart: can't start device.
+.It "dmv%d: device init failed, bsel4=%o, bsel6=%o."
+The initialization/restart routine was unable to start the device.
+.Pp
+.It dmv%d: far end on-line.
+The other end of the connection has come online.
+.Pp
+.It dmv%d: far end restart.
+The other end of the line has restarted.
+.Pp
+.It dmv%d: bad control %o.
+A bad parameter was passed to the
+.Em dmvload
+routine.
+.Pp
+.It "dmvxint: dmv%d bad rcv pkt addr 0x%x len 0x%x."
+A bad packet was received.
+.Pp
+.It "dmv%d: bad packet address 0x%x."
+An input packet was received which contained a type of
+address unknown to the driver.
+.Pp
+.It "dmvxint: dmv%d unallocated packet 0x%x."
+A protocol error has occured with the board.
+.Pp
+.It "dmvoutput, dmv%d can't handle af%d."
+A packet for an unsupported address family has been sent.
+.Pp
+.It "dmv%d: output timeout, bsel0=%b bsel2=%b."
+A device timeout occurred.
+.El
+.Pp
+Numerous other device errors may be displayed.
+.Sh SEE ALSO
+.Xr dmc 4 ,
+.Xr intro 4 ,
+.Xr inet 4
+.Sh HISTORY
+The
+.Nm
+driver appeared in
+.Bx 4.3 tahoe .
diff --git a/share/man/man4/man4.vax/dmz.4 b/share/man/man4/man4.vax/dmz.4
new file mode 100644
index 00000000000..9ce37d2975b
--- /dev/null
+++ b/share/man/man4/man4.vax/dmz.4
@@ -0,0 +1,136 @@
+.\" 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. 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: @(#)dmz.4	6.4 (Berkeley) 3/27/91
+.\"	$Id: dmz.4,v 1.1 1995/10/18 08:44:34 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt DMZ 4 vax
+.Os BSD 4.2
+.Sh NAME
+.Nm dmz
+.Nd
+.Tn DMZ-32
+terminal multiplexor
+.Sh SYNOPSIS
+.Cd "device dmz0 at uba? csr 0160540" "vector dmzrinta dmzxinta dmzrintb dmzxintb dmzrintc dmzxintc"
+.Sh DESCRIPTION
+The 
+.Nm dmz
+device provides 24 lines of asynchronous serial line support.
+Modem control on all ports is available
+as an option for the H3014 distribution panel.
+.Pp
+An optional argument
+.Ar flags
+may be supplied with the device specification for
+.Nm dmz
+in the config file indicating
+that the line corresponding to
+bit number
+.Ar i
+is not properly
+connected, and should be treated as hard-wired with carrier
+always present.  Thus specifying
+.Ql flags 0x000004
+for
+.Li dmz0
+would cause line
+.Pa ttya2
+to be treated in this way.
+.Pp
+Normal
+.Tn I/O
+control parameters for individual lines are managed by
+.Xr ioctl 2
+calls.
+Line speeds (there are 16 choices for the
+.Tn DMZ )
+may be initiated via
+.Xr getty 8
+and
+.Xr stty 1
+or may be communicated by other programs which
+utilize
+.Xr ioctl
+such as
+.Xr ifcongif 8 ,
+see
+.Xr tty 4  .
+.Pp
+The
+.Nm dmz
+driver normally enables the input silos with a short timeout
+(30 milliseconds); this allows multiple characters to be received
+per interrupt during periods of high-speed input.
+.Sh FILES
+.Bl -tag -width /dev/tty[abcefg][0-9a-n] -compact
+.It Pa /dev/tty[abcefg][0-9a-n]
+.El
+.Sh DIAGNOSTICS
+.Bl -diag
+.It dmz%d: NXM line %d.
+No response from the
+.Tn UNIBUS
+on a
+.Tn DMA
+transfer
+within a timeout period.  This is often followed by a
+.Tn UNIBUS
+adapter
+error.  This occurs most frequently when the
+.Tn UNIBUS
+is heavily loaded
+and when devices which hog the bus (such as
+.Tn RK07 Ns s )
+are present.
+It is not serious.
+.Pp
+.It dmz%d: silo overflow.
+The character input silo overflowed
+before it could be serviced.  This can happen if a hard error occurs
+when the
+.Tn CPU
+is running with elevated priority, as the system will
+then print a message on the console with interrupts disabled.
+It is not serious.
+.El
+.Sh SEE ALSO
+.Xr tty 4
+.Sh HISTORY
+The
+.Nm
+driver appeared in
+.Bx 4.3 .
+.Sh BUGS
+It should be possible to set the silo timeout with a configuration file option,
+as the value is a trade-off between efficiency and response time for flow
+control and character echo.
diff --git a/share/man/man4/man4.vax/dn.4 b/share/man/man4/man4.vax/dn.4
new file mode 100644
index 00000000000..59cf873b1e0
--- /dev/null
+++ b/share/man/man4/man4.vax/dn.4
@@ -0,0 +1,114 @@
+.\" Copyright (c) 1980, 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: @(#)dn.4	6.2 (Berkeley) 3/27/91
+.\"	$Id: dn.4,v 1.1 1995/10/18 08:44:34 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt DN 4 vax
+.Os BSD 4
+.Sh NAME
+.Nm dn
+.Nd
+.Tn DN-11
+autocall unit interface
+.Sh SYNOPSIS
+.Cd "device dn0 at uba? csr 0160020 vector dnintr"
+.Sh DESCRIPTION
+The
+.Nm dn
+device provides an interface through a
+.Tn DEC
+.Tn DN-11
+(or equivalent
+such as the Able Quadracall) to an auto-call unit
+.Pq Tn ACU .
+To place an outgoing call one forks a sub-process which
+opens the appropriate call unit file,
+.Pa /dev/cua?
+and writes the phone number on it.  The parent process
+then opens the corresponding modem line
+.Pa /dev/cul? .
+When the connection has been
+established, the open on the modem line
+.Pa /dev/cul?
+will return and the process will be connected.
+A timer is normally used to timeout the opening of 
+the modem line.
+.Pp
+The codes for the phone numbers are:
+.Bl -column xxxx -offset indent
+0-9	number to be dialed
+*	dial * (`:' is a synonym)
+#	dial # (`;' is a synonym)
+\-	delay 20 milliseconds
+<	end of phone number (`e' is a synonym)
+=	delay for a second dial tone (`w' is a synonym)
+f	force a hangup of any existing connection
+.El
+.Pp
+The phone number to be dialed must be presented as one contiguous string.
+.Pp
+By convention, even numbered call units are for 300 baud
+modem lines, while odd numbered units are for 1200 baud lines.
+For example,
+.Pa /dev/cua0
+is associated with a 300 baud modem line,
+.Pa /dev/cul0 ,
+while
+.Pa /dev/cua1
+is associated with a 1200 baud modem line,
+.Pa /dev/cul1 .
+For devices such as the Quadracall which simulate multiple
+.Tn DN-11
+units, the minor device indicates which outgoing modem to use.
+.Sh FILES
+.Bl -tag -width /dev/cul? -compact
+.It Pa /dev/cua?
+call units
+.It Pa /dev/cul?
+associated modem lines
+.El
+.Sh DIAGNOSTICS
+Two error numbers are of interest at open time.
+.Bl -tag -width EBUSYxx
+.It Bq Er EBUSY
+The dialer is in use.
+.It Bq Er ENXIO
+The device doesn't exist, or there's no power to it.
+.El
+.Sh SEE ALSO
+.Xr tip 1
+.Sh HISTORY
+A
+.Nm
+driver appeared in
+.At v6 .
diff --git a/share/man/man4/man4.vax/dz.4 b/share/man/man4/man4.vax/dz.4
new file mode 100644
index 00000000000..54c211bba84
--- /dev/null
+++ b/share/man/man4/man4.vax/dz.4
@@ -0,0 +1,118 @@
+.\" Copyright (c) 1980, 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: @(#)dz.4	6.3 (Berkeley) 3/27/91
+.\"	$Id: dz.4,v 1.1 1995/10/18 08:44:34 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt DZ 4 vax
+.Os BSD 4
+.Sh NAME
+.Nm dz
+.Nd
+.Tn DZ-11
+multiplexer device interface
+.Sh SYNOPSIS
+.Cd "device dz0 at uba0 csr 0160100 vector dzrint dzxint"
+.Sh DESCRIPTION
+A
+.Tn DZ-11
+provides 8 communication lines with partial modem control,
+adequate for
+.Tn UNIX
+dialup use.
+.Pp
+An optional argument
+.Ar flags
+may be supplied with the device specification
+in the config file indicating
+that the line corresponding to
+bit number
+.Ar i
+is not properly
+connected, and should be treated as hard-wired with carrier
+always present.  Thus specifying
+.Ql flags 0x04
+for
+.Li dz0
+would cause line
+.Pa tty02
+to be treated in this way.
+.Pp
+Normal I/O
+control parameters for individual lines are managed by
+.Xr ioctl 2
+calls.
+Line speeds may be initiated via
+the
+.Xr ttys 5
+file,
+.Xr stty 1
+or
+.Xr ifconfig 8
+to name a few,
+see
+.Xr tty 4 .
+.Pp
+The
+.Nm dz
+driver monitors the rate of input on each board,
+and switches between the use of character-at-a-time interrupts
+and input silos.
+While the silo is enabled during periods of high-speed input,
+the driver polls for input 30 times per second.
+.Sh FILES
+.Bl -tag -width /dev/tty[0-9][0-9]xx -compact
+.It Pa /dev/tty[0-9][0-9]
+.It Pa /dev/ttyd[0-9a-f]
+dialups
+.El
+.Sh DIAGNOSTICS
+.Bl -diag
+.It dz%d: silo overflow .
+The 64 character input silo overflowed
+before it could be serviced.  This can happen if a hard error occurs
+when the
+.Tn CPU
+is running with elevated priority, as the system will
+then print a message on the console with interrupts disabled.
+It is not serious.
+.El
+.Sh SEE ALSO
+.Xr stty 1 ,
+.Xr tty 4 ,
+.Xr ttys 5 ,
+.Xr getty 8
+.Sh HISTORY
+A
+.Nm
+driver appeared in
+.At 32v .
diff --git a/share/man/man4/man4.vax/ec.4 b/share/man/man4/man4.vax/ec.4
new file mode 100644
index 00000000000..803a97996d8
--- /dev/null
+++ b/share/man/man4/man4.vax/ec.4
@@ -0,0 +1,140 @@
+.\" Copyright (c) 1983, 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: @(#)ec.4	6.7 (Berkeley) 3/27/91
+.\"	$Id: ec.4,v 1.1 1995/10/18 08:44:34 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt EC 4 vax
+.Os BSD 4.2
+.Sh NAME
+.Nm ec
+.Nd 3Com 10 Mb/s Ethernet interface
+.Sh SYNOPSIS
+.Cd "device ec0 at uba0 csr 161000 vector ecrint eccollide ecxint flags 0"
+.Sh DESCRIPTION
+The
+.Nm ec
+interface provides access to a 10 Mb/s Ethernet network through
+a 3com controller.
+.Pp
+The hardware has 32 kilobytes of dual-ported memory on the
+.Tn UNIBUS .
+This memory
+is used for internal buffering by the board, and the interface code reads
+the buffer contents directly through the
+.Tn UNIBUS .
+The address of this memory is given in the
+.Ar flags
+field
+in the configuration file.
+The first interface normally has its memory at Unibus address 0.
+.Pp
+Each of the host's network addresses
+is specified at boot time with an
+.Dv SIOCSIFADDR
+.Xr ioctl 2 .
+The
+.Nm ec
+interface employs the address resolution protocol described in
+.Xr arp 4
+to dynamically map between Internet and Ethernet addresses on the local
+network.
+.Pp
+The interface normally tries to use a
+.Dq trailer
+encapsulation
+to minimize copying data on input and output.
+The use of trailers is negotiated with
+.Tn ARP .
+This negotiation may be disabled, on a per-interface basis,
+by setting the
+.Dv IFF_NOTRAILERS
+flag with an
+.Dv SIOCSIFFLAGS
+.Xr ioctl .
+.Pp
+The interface software implements an exponential backoff algorithm
+when notified of a collision on the cable.  This algorithm utilizes
+a 16-bit mask and the
+.Tn VAX-11 Ns 's
+interval timer in calculating a series
+of random backoff values.  The algorithm is as follows:
+.Bl -enum -offset indent
+.It
+Initialize the mask to be all 1's.
+.It
+If the mask is zero, 16 retries have been made and we give
+up.
+.It
+Shift the mask left one bit and formulate a backoff by
+masking the interval timer with the smaller of the complement of this mask
+and a 5-bit mask, resulting in a pseudo-random number between 0 and 31.
+This produces the number of slot times to delay,
+where a slot is 51 microseconds.
+.It
+Use the value calculated in step 3 to delay before retransmitting
+the packet.
+The delay is done in a software busy loop.
+.El
+.Sh DIAGNOSTICS
+.Bl -diag
+.It ec%d: send error.
+After 16 retransmissions using the
+exponential backoff algorithm described above, the packet
+was dropped.
+.Pp
+.It ec%d: input error (offset=%d).
+The hardware indicated an error
+in reading a packet off the cable or an illegally sized packet.
+The buffer offset value is printed for debugging purposes.
+.Pp
+.It ec%d: can't handle af%d.
+The interface was handed
+a message with addresses formatted in an unsuitable address
+family; the packet was dropped.
+.El
+.Sh SEE ALSO
+.Xr netintro 4 ,
+.Xr inet 4 ,
+.Xr arp 4
+.Sh HISTORY
+The
+.Nm
+driver appeared in
+.Bx 4.2 .
+.Sh BUGS
+The hardware is not capable of talking to itself.  The software
+implements local sending and broadcast by sending such packets to the
+loop interface.  This is a kludge.
+.Pp
+Backoff delays are done in a software busy loop.  This can degrade the
+system if the network experiences frequent collisions.
diff --git a/share/man/man4/man4.vax/en.4 b/share/man/man4/man4.vax/en.4
new file mode 100644
index 00000000000..2e513c6ce33
--- /dev/null
+++ b/share/man/man4/man4.vax/en.4
@@ -0,0 +1,147 @@
+.\" Copyright (c) 1983, 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: @(#)en.4	6.5 (Berkeley) 3/27/91
+.\"	$Id: en.4,v 1.1 1995/10/18 08:44:34 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt EN 4 vax
+.Os BSD 4.2
+.Sh NAME
+.Nm en
+.Nd Xerox 3 Mb/s Ethernet interface
+.Sh SYNOPSIS
+.Cd "device en0 at uba0 csr 161000 vector enrint enxint encollide"
+.Sh DESCRIPTION
+The
+.Nm en
+interface provides access to a 3 Mb/s Ethernet network.
+Due to limitations in the hardware,
+.Tn DMA
+transfers
+to and from the network must take place in the lower 64K bytes
+of the
+.Tn UNIBUS
+address space, and thus this must be among the first
+.Tn UNIBUS
+devices enabled after boot.
+.Pp
+Each of the host's network addresses
+is specified at boot time with an
+.Dv SIOCSIFADDR
+.Xr ioctl 2 .
+The station address is discovered by probing the on-board Ethernet
+address register, and is used to verify the protocol addresses.
+No packets will be sent or accepted until 
+a network address is supplied.
+.Pp
+The interface software implements an exponential backoff algorithm
+when notified of a collision on the cable.  This algorithm utilizes
+a 16-bit mask and the
+.Tn VAX-11 Ns 's
+interval timer in calculating a series
+of random backoff values.  The algorithm is as follows:
+.Pp
+.Bl -enum -offset indent
+.It
+Initialize the mask to be all 1's.
+.It
+If the mask is zero, 16 retries have been made and we give
+up.
+.It
+Shift the mask left one bit and formulate a backoff by
+masking the interval timer with the mask (this is actually
+the two's complement of the value).
+.It
+Use the value calculated in step 3 to delay before retransmitting
+the packet.
+.El
+.Pp
+The interface handles both Internet and
+.Tn NS
+protocol families.
+It normally tries to use a
+.Dq trailer
+encapsulation
+to minimize copying data on input and output.
+The use of trailers is negotiated with
+.Tn ARP .
+This negotiation may be disabled, on a per-interface basis,
+by setting the
+.Dv IFF_NOTRAILERS
+flag with an
+.Dv SIOCSIFFLAGS
+.Xr ioctl .
+.Sh DIAGNOSTICS
+.Bl -diag
+.It en%d: output error.
+The hardware indicated an error on
+the previous transmission.
+.Pp
+.It en%d: send error.
+After 16 retransmissions using the
+exponential backoff algorithm described above, the packet
+was dropped.
+.Pp
+.It en%d: input error.
+The hardware indicated an error
+in reading a packet off the cable.
+.Pp
+.It en%d: can't handle af%d.
+The interface was handed
+a message with addresses formatted in an unsuitable address
+family; the packet was dropped.
+.El
+.Sh SEE ALSO
+.Xr netintro 4 ,
+.Xr inet 4
+.Sh HISTORY
+The
+.Nm
+driver appeared in
+.Bx 4.2 .
+.Sh BUGS
+The device has insufficient buffering to handle back to
+back packets.  This makes use in a production environment
+painful.
+.Pp
+The hardware does word at a time
+.Tn DMA
+without byte swapping.
+To compensate, byte swapping of user data must either be done 
+by the user or by the system.  A kludge to byte swap only
+.Tn IP
+packets is provided if the
+.Dv ENF_SWABIPS
+flag is defined in
+the driver and set at boot time with an 
+.Dv SIOCSIFFLAGS 
+.Xr ioctl .
diff --git a/share/man/man4/man4.vax/ex.4 b/share/man/man4/man4.vax/ex.4
new file mode 100644
index 00000000000..c16d86c66f4
--- /dev/null
+++ b/share/man/man4/man4.vax/ex.4
@@ -0,0 +1,109 @@
+.\" Copyright (c) 1986, 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: @(#)ex.4	6.6 (Berkeley) 3/27/91
+.\"	$Id: ex.4,v 1.1 1995/10/18 08:44:34 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt EX 4 vax
+.Os BSD 4.2
+.Sh NAME
+.Nm ex
+.Nd Excelan 10 Mb/s Ethernet interface
+.Sh SYNOPSIS
+.Cd "device ex0 at uba0 csr 164000 vector excdint"
+.Sh DESCRIPTION
+The
+.Nm ex
+interface provides access to a 10 Mb/s Ethernet network through
+an Excelan controller used as a link-layer interface.
+.Pp
+Each of the host's network addresses
+is specified at boot time with an
+.Dv SIOCSIFADDR
+.Xr ioctl 2 .
+The
+.Nm ex
+interface employs the address resolution protocol described in
+.Xr arp 4
+to dynamically map between Internet and Ethernet addresses on the local
+network.
+.Pp
+The interface normally tries to use a
+.Dq trailer
+encapsulation
+to minimize copying data on input and output.
+The use of trailers is negotiated with
+.Tn ARP .
+This negotiation may be disabled, on a per-interface basis,
+by setting the
+.Dv IFF_NOTRAILERS
+flag with an
+.Dv SIOCSIFFLAGS
+.Xr ioctl .
+.Sh DIAGNOSTICS
+.Bl -diag
+.It "ex%d: HW %c.%c, NX %c.%c, hardware address %s."
+This provides firmware revisions levels, and is expected during
+autoconfiguration.
+.Pp
+.It ex%d: can't initialize.
+There was a failure in allocating unibus resources for the device.
+.Pp
+.It "ex%d: configuration failed; cc = %x."
+The hardware indicated an error when trying to initalize itself.
+The error code returned is described at length in the device
+Reference Manual.
+.Pp
+.It ex%d: receive error %b.
+The hardware indicated an error
+in reading a packet from the cable.
+Specific Error bits are provided
+.Pp
+.It ex%d: transmit error %b.
+The hardware indicated an error
+in transmitting a packet to the cable or an illegally sized packet.
+Specific Error bits are provided
+.Pp
+.It ex%d: can't handle af%d.
+The interface was handed
+a message with addresses formatted in an unsuitable address
+family; the packet was dropped.
+.El
+.Sh SEE ALSO
+.Xr netintro 4 ,
+.Xr inet 4 ,
+.Xr arp 4
+.Sh HISTORY
+The
+.Nm
+driver appeared in
+.Bx 4.3 .
diff --git a/share/man/man4/man4.vax/fl.4 b/share/man/man4/man4.vax/fl.4
new file mode 100644
index 00000000000..60e030ac5ee
--- /dev/null
+++ b/share/man/man4/man4.vax/fl.4
@@ -0,0 +1,74 @@
+.\" Copyright (c) 1980, 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: @(#)fl.4	6.3 (Berkeley) 3/27/91
+.\"	$Id: fl.4,v 1.1 1995/10/18 08:44:34 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt FL 4 vax
+.Os BSD 4
+.Sh NAME
+.Nm fl
+.Nd console floppy interface
+.Sh DESCRIPTION
+This is a simple interface to the
+.Tn DEC
+.Tn RX01
+floppy disk unit, which is part of the console
+.Tn LSI-11
+subsystem for
+.Tn VAX-11/780 Ns s .
+Access is given to the entire
+floppy consisting of 77 tracks of 26 sectors of 128 bytes.
+.Pp
+All I/O is raw; the seek addresses in raw transfers should be a multiple
+of 128 bytes and a multiple of 128 bytes should be transferred,
+as in other
+.Dq raw
+disk interfaces.
+.Sh FILES
+.Bl -tag -width /dev/floppy -compact
+.It Pa /dev/floppy
+.El
+.Sh DIAGNOSTICS
+None.
+.Sh SEE ALSO
+.Xr arff 8
+.Sh HISTORY
+The
+.Nm
+driver appeared in
+.Bx 4.0 .
+.Sh BUGS
+Multiple console floppies are not supported.
+.Pp
+If a write is given with a count not a multiple of 128 bytes then
+the trailing portion of the last sector will be zeroed.
diff --git a/share/man/man4/man4.vax/hdh.4 b/share/man/man4/man4.vax/hdh.4
new file mode 100644
index 00000000000..c5413b72f19
--- /dev/null
+++ b/share/man/man4/man4.vax/hdh.4
@@ -0,0 +1,125 @@
+.\" Copyright (c) 1983, 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: @(#)hdh.4	6.4 (Berkeley) 3/27/91
+.\"	$Id: hdh.4,v 1.1 1995/10/18 08:44:34 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt HDH 4 vax
+.Os BSD 4.3
+.Sh NAME
+.Nm hdh
+.Nd
+.Tn ACC
+.Tn IF-11/HDH 
+.Tn IMP
+interface
+.Sh SYNOPSIS
+.Cd "pseudo-device imp"
+.Cd "device hdh0 at uba0 csr 166740 vector hdhintr"
+.Sh DESCRIPTION
+The 
+.Nm hdh
+device provides an
+.Tn HDLC
+Host
+.Pq Tn HDH
+interface to an
+.Tn IMP .
+It is normally used when participating
+in the
+.Tn DARPA
+Internet.  The controller itself is not accessible
+to users, but instead provides the hardware support to the
+.Tn IMP
+interface described in
+.Xr imp 4 .
+The configuration entry for the
+.Tn IMP
+must also include the
+.Em pseudo-device
+as shown above in the
+.Sx SYNOPSIS .
+.Sh DIAGNOSTICS
+.Bl -diag
+.It hdh%d: not alive.
+The initialization routine was entered even though the device
+did not autoconfigure.  This indicates a system problem.
+.Pp
+.It hdh%d: cannot get chan %d uba resources.
+Insufficient
+.Tn UNIBUS
+resources existed to initialize the device.
+This is likely to be a shortage of
+.Tn UNIBUS
+mapping registers.
+.Pp
+.It hdh%d: LINE UP.
+This indicates that both the
+.Tn HDLC
+and
+.Tn HDH
+protocols have declared the
+link to the
+.Tn IMP
+alive.
+.Pp
+.It hdh%d: LINE DOWN.
+This indicates that the link to the
+.Tn IMP
+has died.
+.Pp
+.It hdh%d: TIMEOUT.
+.It hdh%d: HOST DATA ERROR.
+.It hdh%d: IMP SEQUENCE ERROR.
+.It hdh%d: HOST SEQUENCE ERROR.
+These errors indicate that an
+.Tn HDH
+protocol error has been detected.
+.Pp
+.It hdh%d: cannot get supervisor cmnd buffer.
+This error indicates that an
+.Em mbuf
+could not be allocated to send a command to the
+.Tn IF-11/HDH .
+.El
+.Pp
+Any other error message from hdh%d: indicates a serious error
+detected by either the driver or the
+.Tn IF-11/HDH
+firmware.
+.Sh SEE ALSO
+.Xr netintro 4
+.Sh HISTORY
+The
+.Nm
+driver appeared in
+.Bx 4.3 .
diff --git a/share/man/man4/man4.vax/hk.4 b/share/man/man4/man4.vax/hk.4
new file mode 100644
index 00000000000..6a9c2a24308
--- /dev/null
+++ b/share/man/man4/man4.vax/hk.4
@@ -0,0 +1,201 @@
+.\" Copyright (c) 1980, 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: @(#)hk.4	6.4 (Berkeley) 3/27/91
+.\"	$Id: hk.4,v 1.1 1995/10/18 08:44:34 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt HK 4
+.Os BSD 4
+.Sh NAME
+.Nm hk
+.Nd
+.Tn RK6-11 Ns / Tn RK06
+and
+.Tn RK07
+disk interface
+.Sh SYNOPSIS
+.Cd "controller hk0 at uba? csr 0177440 vector rkintr"
+.Cd "disk rk0 at hk0 drive 0"
+.Sh DESCRIPTION
+The
+.Nm hk
+driver
+is a typical block-device disk driver; block device
+.Tn I/O
+is
+described in
+.Xr physio 4 .
+.Pp
+The script
+.Xr MAKEDEV 8
+should be used to create the special files; if a special file
+needs to be created by hand consult
+.Xr mknod 8 .
+.Sh DISK SUPPORT
+Special file names begin with
+.Sq Li hk
+and
+.Sq Li rhk
+for the block and character files respectively. The second
+component of the name, a drive unit number in the range of zero to
+seven, is represented by a
+.Sq Li ?
+in the disk layouts below. The last component is the file system partition
+which is designated
+by a letter from
+.Sq Li a
+to
+.Sq Li h .
+and
+corresponds to a minor device number set: zero to seven,
+eight to 15, 16 to 23 and so forth for drive zero, drive two and drive
+three respectively.
+The location and size (in sectors) of the
+partitions for the
+.Tn RK06
+and
+.Tn RK07
+drives are as follows:
+.Bl -column header diskx undefined length
+.Tn RK07 No partitions:
+.Sy	disk	start	length	cyl
+	hk?a	0	15884	0-240
+	hk?b	15906	10032	241-392
+	hk?c	0	53790	0-814
+	hk?d	25938	15884	393-633
+	hk?f	41844	11792	634-814
+	hk?g	25938	27786	393-813
+
+.Tn RK06 No partitions
+.Sy	disk	start	length	cyl
+	hk?a	0	15884	0-240
+	hk?b	15906	11154	241-409
+	hk?c	0	27126	0-410
+.El
+.Pp
+On a dual
+.Tn RK-07
+system
+partition hk?a is used
+for the root for one drive
+and partition hk?g for the /usr file system.
+If large jobs are to be run using
+hk?b on both drives as swap area provides a 10Mbyte paging area.
+Otherwise
+partition hk?c on the other drive
+is used as a single large file system.
+.Sh FILES
+.Bl -tag -width /dev/rhk[0-7][a-h] -compact
+.It Pa /dev/hk[0-7][a-h]
+block files
+.It Pa /dev/rhk[0-7][a-h]
+raw files
+.El
+.Sh DIAGNOSTICS
+.Bl -diag
+.It "hk%d%c: hard error %sing fsbn %d[-%d] cs2=%b ds=%b er=%b."
+An unrecoverable error occurred during transfer of the specified
+filesystem block number(s),
+which are logical block numbers on the indicated partition.
+The contents of the cs2, ds and er registers are printed
+in octal and symbolically with bits decoded.
+The error was either unrecoverable, or a large number of retry attempts
+(including offset positioning and drive recalibration) could not
+recover the error.
+.Pp
+.It rk%d: write locked.
+The write protect switch was set on the drive
+when a write was attempted.  The write operation is not recoverable.
+.Pp
+.It rk%d: not ready.
+The drive was spun down or off line when it was
+accessed.  The i/o operation is not recoverable.
+.Pp
+.It rk%d: not ready (came back!).
+The drive was not ready, but after
+printing the message about being not ready (which takes a fraction
+of a second) was ready.  The operation is recovered if no further
+errors occur.
+.Pp
+.It rk%d%c: soft ecc reading fsbn %d[-%d].
+A recoverable
+.Tn ECC
+error occurred on the
+specified sector(s) in the specified disk partition. 
+This happens normally
+a few times a week.  If it happens more frequently than
+this the sectors where the errors are occurring should be checked to see
+if certain cylinders on the pack, spots on the carriage of the drive
+or heads are indicated.
+.Pp
+.It hk%d: lost interrupt.
+A timer watching the controller detected
+no interrupt for an extended period while an operation was outstanding.
+This indicates a hardware or software failure.  There is currently a
+hardware/software problem with spinning down drives while they are
+being accessed which causes this error to occur.
+The error causes a
+.Tn UNIBUS
+reset, and retry of the pending operations.
+If the controller continues to lose interrupts, this error will recur
+a few seconds later.
+.El
+.Sh SEE ALSO
+.Xr hp 4 ,
+.Xr uda 4 ,
+.Xr up 4 ,
+.Xr syslogd 8
+.Sh HISTORY
+The
+.Nm
+driver appeared in
+.Bx 4.1 .
+.Sh BUGS
+The
+.Xr write
+function
+scribbles on the tail of incomplete blocks.
+.Pp
+.Tn DEC Ns -standard
+error logging should be supported.
+.Pp
+A program to analyze the logged error information (even in its
+present reduced form) is needed.
+.Pp
+The partition tables for the file systems should be read off of each
+pack, as they are never quite what any single installation would prefer,
+and this would make packs more portable.
+.Pp
+The
+.Tn RK07
+g partition size in rk.c disagrees with that in
+.Pa /etc/disktab.
diff --git a/share/man/man4/man4.vax/hp.4 b/share/man/man4/man4.vax/hp.4
new file mode 100644
index 00000000000..e3d2909b5f4
--- /dev/null
+++ b/share/man/man4/man4.vax/hp.4
@@ -0,0 +1,380 @@
+.\" Copyright (c) 1980,1988, 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: @(#)hp.4	6.5 (Berkeley) 3/27/91
+.\"	$Id: hp.4,v 1.1 1995/10/18 08:44:34 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt HP 4 vax
+.Os BSD 4
+.Sh NAME
+.Nm hp
+.Nd
+.Tn MASSBUS
+disk interface
+.Sh SYNOPSIS
+.Cd "disk hp0 at mba0 drive 0"
+.Sh DESCRIPTION
+The
+.Nm hp
+driver
+is a generic Massbus disk driver which handles both the standard
+.Tn DEC
+controllers and the Emulex
+.Tn SC750
+and
+.Tn SC780
+controllers.
+It is typical of a block-device disk driver; block
+.Tn I/O
+is
+described in
+.Xr physio 4 .
+.Pp
+The script
+.Xr MAKEDEV 8
+should be used to create the special files; if a special file
+needs to be created by hand consult
+.Xr mknod 8 .
+It is recommended as a security precaution to not create special files
+for devices which may never be installed.
+.Pp
+The first sector of each disk contains both a first-stage bootstrap program
+and a disk label containing geometry information and partition layouts (see
+.Xr disklabel 5 .
+This sector is normally write-protected, and disk-to-disk copies should
+avoid copying this sector.
+The label may be updated with
+.Xr disklabel 8 ,
+which can also be used to write-enable and write-disable the sector.
+The next 15 sectors contain a second-stage bootstrap program.
+.Sh DISK SUPPORT
+This driver handles both standard
+.Tn DEC
+controllers and Emulex
+.Tn SC750
+and
+.Tn SC780
+controllers.
+During autoconfiguration or whenever a drive comes on line for the first time,
+or when a drive is opened after all partitions are closed,
+the first sector of the drive is examined for a disk label.
+If a label is found, the geometry of the drive and the partition tables
+are taken from it.
+If no label is found,
+standard
+.Tn DEC
+drive types are
+recognized according to the
+.Tn MASSBUS
+drive type register,
+and default partitions are used.
+For the Emulex controller the drive type register should be configured
+to indicate the drive is an
+.Tn RM02 .
+When this is encountered,
+the driver checks the holding register to find out
+the disk geometry and, based on this information, decides what
+the drive type is.
+.Pp
+Special file names begin with
+.Sq Li hp
+and
+.Sq Li rhp
+for the block and character files respectively. The second
+component of the name, a drive unit number in the range of zero to
+seven, is represented by a
+.Sq Li ?
+in the disk layouts below.
+The last component is the file system partition
+designated
+by a letter from
+.Sq Li a
+to
+.Sq Li h
+and also corresponds to a minor device number set: zero to seven,
+eight to 15, 16 to 23 and so forth for drive zero, drive two and drive
+three respectively.
+The following disks are supported:
+.Tn RM03 ,
+.Tn RM05 ,
+.Tn RP06 ,
+.Tn RM80 ,
+.Tn RP05 ,
+.Tn RP07 ,
+.Tn ML11A ,
+.Tn ML11B ,
+.Tn CDC 9775 ,
+.Tn CDC 9730 ,
+.Tn AMPEX
+Capricorn (32 sectors/track),
+.Tn FUJITSU
+Eagle (48 sectors/track),
+.Tn FUJITSU 2361, 
+and
+.Tn AMPEX
+9300.  The default layout and size (in sectors) of the
+partitions for these drives:
+.Bl -column header diskx undefined length
+.Tn RM03 No partitions
+.Sy	disk	start	length	cyls
+	hp?a	0	15884	0-99
+	hp?b	16000	33440	100-309
+	hp?c	0	131680	0-822
+	hp?d	49600	15884	309-408
+	hp?e	65440	55936	409-758
+	hp?f	121440	10080	759-822
+	hp?g	49600	82080	309-822
+
+.Tn RM05 No partitions
+.Sy	disk	start	length	cyls
+	hp?a	0	15884	0-26
+	hp?b	16416	33440	27-81
+	hp?c	0	500384	0-822
+	hp?d	341696	15884	562-588
+	hp?e	358112	55936	589-680
+	hp?f	414048	86176	681-822
+	hp?g	341696	158528	562-822
+	hp?h	49856	291346	82-561
+
+.Tn RP06 No partitions
+.Sy	disk	start	length	cyls
+	hp?a	0	15884	0-37
+	hp?b	15884	33440	38-117
+	hp?c	0	340670	0-814
+	hp?d	49324	15884	118-155
+	hp?e	65208	55936	156-289
+	hp?f	121220	219296	290-814
+	hp?g	49324	291192	118-814	
+
+.Tn RM80 No partitions
+.Sy	disk	start	length	cyls
+	hp?a	0	15884	0-36
+	hp?b	16058	33440	37-114
+	hp?c	0	242606	0-558
+	hp?d	49910	15884	115-151
+	hp?e	68096	55936	152-280
+	hp?f	125888	120466	281-558
+	hp?g	49910	192510	115-558
+
+.Tn RP05 No partitions
+.Sy	disk	start	length	cyls
+	hp?a	0	15884	0-37
+	hp?b	15884	33440	38-117
+	hp?c	0	171798	0-410
+	hp?d	2242	15884	118-155
+	hp?e	65208	55936	156-289
+	hp?f	121220	50424	290-410
+	hp?g	2242	122320	118-410
+
+.Tn RP07 No partitions
+.Sy	disk	start	length	cyls
+	hp?a	0	15884	0-9
+	hp?b	16000	66880	10-51
+	hp?c	0	1008000	0-629
+	hp?d	376000	15884	235-244
+	hp?e	392000	307200	245-436
+	hp?f	699200	308600	437-629
+	hp?g	376000	631800	235-629
+	hp?h	83200	291346	52-234
+
+.Tn CDC No 9775 partitions
+.Sy	disk	start	length	cyls
+	hp?a	0	15884	0-12
+	hp?b	16640	66880	13-65
+	hp?c	0	1077760	0-841
+	hp?d	376320	15884	294-306
+	hp?e	392960	307200	307-546
+	hp?f	700160	377440	547-841
+	hp?g	376320	701280	294-841
+	hp?h	84480	291346	66-293
+
+.Tn CDC No 9730 partitions
+.Sy	disk	start	length	cyls
+	hp?a	0	15884	0-49
+	hp?b	16000	33440	50-154
+	hp?c	0	263360	0-822
+	hp?d	49600	15884	155-204
+	hp?e	65600	55936	205-379
+	hp?f	121600	141600	380-822
+	hp?g	49600	213600	155-822
+
+.Tn AMPEX No Capricorn partitions
+.Sy	disk	start	length	cyls
+	hp?a	0	15884	0-31
+	hp?b	16384	33440	32-97
+	hp?c	0	524288	0-1023
+	hp?d	342016	15884	668-699
+	hp?e	358400	55936	700-809
+	hp?f	414720	109408	810-1023
+	hp?g	342016	182112	668-1023
+	hp?h	50176	291346	98-667
+
+.Tn FUJITSU No Eagle partitions
+.Sy	disk	start	length	cyls
+	hp?a	0	15884	0-16
+	hp?b	16320	66880	17-86
+	hp?c	0	808320	0-841
+	hp?d	375360	15884	391-407
+	hp?e	391680	55936	408-727
+	hp?f	698880	109248	728-841
+	hp?g	375360	432768	391-841
+	hp?h	83520	291346	87-390
+
+.Tn FUJITSU No 2361 partitions
+.Sy	disk	start	length	cyls
+	hp?a	0	15884	0-12
+	hp?b	16640	66880	13-65
+	hp?c	0	1077760	0-841
+	hp?d	376320	15884	294-306
+	hp?e	392960	307200	307-546
+	hp?f	700160	377408	547-841
+	hp?g	363520	701248	294-841
+	hp?h	84480	291346	66-293
+
+.Tn AMPEX No 9300 partitions
+.Sy	disk	start	length	cyl
+	hp?a	0	15884	0-26
+	hp?b	16416	33440	27-81
+	hp?c	0	495520	0-814
+	hp?d	341696	15884	562-588
+	hp?e	358112	55936	589-680
+	hp?f	414048	81312	681-814
+	hp?g	341696	153664	562-814
+	hp?h	49856	291346	82-561
+.El
+.Pp
+The hp?a partition is normally used for the root file system,
+the hp?b partition as a paging area,
+and the hp?c partition for pack-pack copying (it maps the entire disk).
+On disks larger than about 205 Megabytes, the hp?h partition
+is inserted prior to the hp?d or hp?g partition;
+the hp?g partition then maps the remainder of the pack.
+All disk partition tables are calculated using the
+.Xr diskpart 8
+program.
+.Pp
+.Sh FILES
+.Bl -tag -width /dev/rhp[0-7][a-h] -compact
+.It Pa /dev/hp[0-7][a-h]
+block files
+.It Pa /dev/rhp[0-7][a-h]
+raw files
+.El
+.Sh DIAGNOSTICS
+.Bl -diag
+.It "hp%d%c: hard error %sing fsbn %d [of %d-%d] (hp%d bn %d cn %d tn %d sn %d) mbsr=%b er1=%b er2=%b."
+An unrecoverable error occurred during transfer of the specified
+filesystem block number,
+which is a logical block number on the indicated partition.
+If the transfer involved multiple blocks, the block range is printed as well.
+The parenthesized fields list the actual disk sector number
+relative to the beginning of the drive,
+as well as the cylinder, track and sector number of the block.
+The
+.Tn MASSBUS
+status register is printed in hexadecimal and
+with the error bits decoded if any error bits other than
+.Tn MBEXC
+and
+.Tn DTABT
+are set.  In any case the contents of the two error registers are also printed
+in octal and symbolically with bits decoded.
+(Note that er2 is what old
+.Tn RP06
+manuals would call
+.Tn RPER3 ;
+the terminology
+is that of the
+.Tn RM
+disks).
+The error was either unrecoverable, or a large number of retry attempts
+(including offset positioning and drive recalibration) could not
+recover the error.
+.Pp
+.It hp%d: write locked.
+The write protect switch was set on the drive
+when a write was attempted.  The write operation is not recoverable.
+.Pp
+.It hp%d: not ready .
+The drive was spun down or off line when it was
+accessed.  The
+.Tn I/O
+operation is not recoverable.
+.Pp
+.It "hp%d%c: soft ecc reading fsbn %d [of %d-%d] (hp%d bn %d cn %d tn %d sn %d)."
+A recoverable
+.Tn ECC
+error occurred on the
+specified sector of the specified disk partition. 
+If the transfer involved multiple blocks, the block range is printed as well.
+The parenthesized fields list the actual disk sector number
+relative to the beginning of the drive,
+as well as the cylinder, track and sector number of the block.
+This happens normally
+a few times a week.  If it happens more frequently than
+this the sectors where the errors are occurring should be checked to see
+if certain cylinders on the pack, spots on the carriage of the drive
+or heads are indicated.
+.Pp
+.It hp%d: 9775 (direct).
+.It hp%d: 9730 (direct).
+.It hp%d: 9300.
+.It hp%d: 9762.
+.It hp%d: capricorn.
+.It hp%d: eagle.
+.It hp%d: 2361.
+.It hp%d: ntracks %d, nsectors %d: unknown device.
+During autoconfiguration one of the above messages may appear
+on the console indicating the appropriate drive type was recognized.
+The last message indicates the drive is of a unknown type.
+In this case, the correct geometry is set, and one partition is created
+that contains the entire drive.
+.Pp
+.El
+.Sh SEE ALSO
+.Xr physio 4 ,
+.Xr up 4 ,
+.Xr disklabel 5 ,
+.Xr MAKEDEV 8
+.Xr disklabel 8
+.Xr mknod 8
+.Sh HISTORY
+The
+.Nm
+driver appeared in
+.Bx 4.0 .
+.Sh BUGS
+.Tn DEC Ns -standard
+error logging should be supported.
+.Pp
+A program to analyze the logged error information (even in its
+present reduced form) is needed.
diff --git a/share/man/man4/man4.vax/ht.4 b/share/man/man4/man4.vax/ht.4
new file mode 100644
index 00000000000..f5ebb9fb905
--- /dev/null
+++ b/share/man/man4/man4.vax/ht.4
@@ -0,0 +1,113 @@
+.\" Copyright (c) 1980, 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: @(#)ht.4	6.3 (Berkeley) 3/27/91
+.\"	$Id: ht.4,v 1.1 1995/10/18 08:44:34 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt HT 4 vax
+.Os BSD 4
+.Sh NAME
+.Nm ht
+.Nd
+.Tn TM-03 Ns / Tn TE-16 ,
+.Tn TU-45 ,
+.Tn TU-77
+.Tn MASSBUS
+magtape device interface:
+.Sh SYNOPSIS
+.Cd "master ht0 at mba? drive ?"
+.Cd "tape tu0 at ht0 slave 0"
+.Sh DESCRIPTION
+The
+.Tn TM-03
+transport combination provides a standard tape drive
+interface as described in
+.Xr mtio 4 .
+All drives provide both 800 and 1600
+.Tn BPI ;
+the
+.Tn TE-16
+runs at 45
+.Tn IPS ,
+the
+.Tn TU-45
+at 75
+.Tn IPS ,
+while the
+.Tn TU-77
+runs at 125
+.Tn IPS
+and autoloads tapes.
+.Sh DIAGNOSTICS
+.Bl -diag
+.It tu%d: no write ring.
+An attempt was made to write on the tape drive
+when no write ring was present; this message is written on the terminal of
+the user who tried to access the tape.
+.Pp
+.It tu%d: not online.
+An attempt was made to access the tape while it
+was offline; this message is written on the terminal of the user
+who tried to access the tape.
+.Pp
+.It tu%d: can't change density in mid-tape.
+An attempt was made to write
+on a tape at a different density than is already recorded on the tape.
+This message is written on the terminal of the user who tried to switch
+the density.
+.Pp
+.It "tu%d: hard error bn%d mbsr=%b er=%b ds=%b."
+A tape error occurred
+at block
+.Em bn ;
+the ht error register and drive status register are
+printed in octal with the bits symbolically decoded.  Any error is
+fatal on non-raw tape; when possible the driver will have retried
+the operation which failed several times before reporting the error.
+.El
+.Sh SEE ALSO
+.Xr mt 1 ,
+.Xr tar 1 ,
+.Xr tp 1 ,
+.Xr mtio 4 ,
+.Xr mt 4 ,
+.Xr physio 4 ,
+.Xr tm 4 ,
+.Xr ts 4 ,
+.Xr ut 4
+.Sh HISTORY
+An
+.Nm
+driver appeared in
+.At v6 .
+.Sh BUGS
+May hang if physical (non-data) errors occur.
diff --git a/share/man/man4/man4.vax/hy.4 b/share/man/man4/man4.vax/hy.4
new file mode 100644
index 00000000000..eb92737f945
--- /dev/null
+++ b/share/man/man4/man4.vax/hy.4
@@ -0,0 +1,137 @@
+.\" Copyright (c) 1983, 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: @(#)hy.4	6.4 (Berkeley) 3/27/91
+.\"	$Id: hy.4,v 1.1 1995/10/18 08:44:35 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt HY 4 vax
+.Os BSD 4.2
+.Sh NAME
+.Nm hy
+.Nd Network Systems Hyperchannel interface
+.Sh SYNOPSIS
+.Cd "device hy0 at uba0 csr 0172410 vector hyint"
+.Sh DESCRIPTION
+The
+.Nm hy
+interface provides access to a Network
+Systems Corporation Hyperchannel Adapter.
+.Pp
+The network to which the interface is attached
+is specified at boot time with an
+.Dv SIOCSIFADDR
+.Xr ioctl 2 .  
+The host's address is discovered by reading the adapter status
+register.  The interface will not transmit or receive
+packets until the network number is known.
+.Sh DIAGNOSTICS
+.Bl -diag
+.It "hy%d: unit number 0x%x port %d type %x microcode level 0x%x."
+Identifies the device during autoconfiguration.
+.Pp
+.It hy%d: can't handle af%d.
+The interface was handed
+a message with addresses formatted in an unsuitable address
+family; the packet was dropped.
+.Pp
+.It hy%d: can't initialize.
+The interface was unable to allocate
+.Tn UNIBUS
+resources. This
+is usually due to having too many network devices on an 11/750
+where there are only 3 buffered data paths.
+.Pp
+.It hy%d: NEX - Non Existent Memory.
+Non existent memory error returned from hardware.
+.Pp
+.It hy%d:  BAR overflow.
+Bus address register
+overflow error returned from hardware.
+.Pp
+.It hy%d: Power Off bit set, trying to reset.
+Adapter has lost power, driver will reset the bit
+and see if power is still out in the adapter.
+.Pp
+.It hy%d: Power Off Error, network shutdown.
+Power was really off in the adapter, network
+connections are dropped.
+Software does not shut down the network unless
+power has been off for a while.
+.Pp
+.It hy%d: RECVD MP > MPSIZE (%d).
+A message proper was received that is too big.
+Probable a driver bug.
+Shouldn't happen.
+.Pp
+.It "hy%d: xmit error \- len > hy_olen [%d > %d]."
+Probable driver error.
+Shouldn't happen.
+.Pp
+.It hy%d: DRIVER BUG \- INVALID STATE %d.
+The driver state machine reached a non-existent state.
+Definite driver bug.
+.Pp
+.It hy%d: watchdog timer expired.
+A command in the adapter has taken too long to complete.
+Driver will abort and retry the command.
+.Pp
+.It hy%d: adapter power restored.
+Software was able to reset the power off bit,
+indicating that the power has been restored.
+.El
+.Sh SEE ALSO
+.Xr netintro 4 ,
+.Xr inet 4
+.Sh HISTORY
+The
+.Nm
+interface appeared in
+.Bx 4.2 .
+.Sh BUGS
+If the adapter does not respond to the status command
+issued during autoconfigure, the adapter is assumed down.
+A reboot is required to recognize it.
+.Pp
+The adapter power fail interrupt seems to occur
+sporadically when power has, in fact, not failed.
+The driver will believe that power has failed
+only if it can not reset the power fail latch after
+a
+.Dq reasonable
+time interval.
+These seem to appear about 2-4 times a day on some machines.
+There seems to be no correlation with adapter
+rev level, number of ports used etc. and whether a
+machine will get these
+.Dq bogus powerfails .
+They don't seem to cause any real problems so they have
+been ignored.
diff --git a/share/man/man4/man4.vax/ik.4 b/share/man/man4/man4.vax/ik.4
new file mode 100644
index 00000000000..af06fd3898e
--- /dev/null
+++ b/share/man/man4/man4.vax/ik.4
@@ -0,0 +1,89 @@
+.\" 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. 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: @(#)ik.4	6.2 (Berkeley) 3/27/91
+.\"	$Id: ik.4,v 1.1 1995/10/18 08:44:35 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt IK 4 vax
+.Os BSD 4.2
+.Sh NAME
+.Nm ik
+.Nd "Ikonas frame buffer, graphics device interface"
+.Sh SYNOPSIS
+.Cd "device ik0 at uba? csr 0172460 vector ikintr"
+.Sh DESCRIPTION
+The
+.Nm ik
+driver
+provides an interface to an Ikonas frame buffer graphics device.
+Each minor device is a different frame buffer interface board.
+When the device is opened, its interface registers are mapped,
+via virtual memory, into the user processes address space.
+This allows the user process very high bandwidth to the frame buffer
+with no system call overhead.
+.Pp
+Bytes written or read from the device are
+.Tn DMA Ns 'ed
+from or to the interface.
+The frame buffer
+.Tn XY
+address, its addressing mode, etc. must be set up by the
+user process before calling write or read.
+.Pp
+Other communication with the driver is via ioctls.
+The
+.Dv IK_GETADDR
+.Xr ioctl 2
+returns the virtual address where the user process can
+find the interface registers.
+The
+.Dv IK_WAITINT
+.Xr ioctl
+suspends the user process until the ikonas device
+has interrupted (for whatever reason \(em the user process has to set
+the interrupt enables).
+.Sh FILES
+.Bl -tag -width /dev/ikxx -compact
+.It Pa /dev/ik
+.El
+.Sh DIAGNOSTICS
+None.
+.Sh HISTORY
+The
+.Nm
+driver appeared in
+.Bx 4.2 .
+.Sh BUGS
+An invalid access (e.g., longword) to a mapped interface register
+can cause the system to crash with a machine check.
+A user process could possibly cause infinite interrupts hence
+bringing things to a crawl.
diff --git a/share/man/man4/man4.vax/il.4 b/share/man/man4/man4.vax/il.4
new file mode 100644
index 00000000000..b0bf769cf9a
--- /dev/null
+++ b/share/man/man4/man4.vax/il.4
@@ -0,0 +1,110 @@
+.\" Copyright (c) 1983, 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: @(#)il.4	6.7 (Berkeley) 3/27/91
+.\"	$Id: il.4,v 1.1 1995/10/18 08:44:35 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt IL 4 vax
+.Os BSD 4.2
+.Sh NAME
+.Nm il
+.Nd Interlan NI1010 10 Mb/s Ethernet interface
+.Sh SYNOPSIS
+.Cd "device il0 at uba0 csr 164000 vector ilrint ilcint"
+.Sh DESCRIPTION
+The
+.Nm il
+interface provides access to a 10 Mb/s Ethernet network through
+an Interlan 1010 or 1010A controller.
+.Pp
+Each of the host's network addresses
+is specified at boot time with an
+.Dv SIOCSIFADDR
+.Xr ioctl 2 .
+The
+.Nm il
+interface employs the address resolution protocol described in
+.Xr arp 4
+to dynamically map between Internet and Ethernet addresses on the local
+network.
+.Pp
+The interface normally tries to use a ``trailer'' encapsulation
+to minimize copying data on input and output.
+The use of trailers is negotiated with
+.Tn ARP .
+This negotiation may be disabled, on a per-interface basis,
+by setting the
+.Dv IFF_NOTRAILERS
+flag with an
+.Dv SIOCSIFFLAGS
+.Xr ioctl .
+.Sh DIAGNOSTICS
+.Bl -diag
+.It il%d: input error.
+The hardware indicated an error
+in reading a packet off the cable or an illegally sized packet.
+.Pp
+.It il%d: can't handle af%d.
+The interface was handed
+a message with addresses formatted in an unsuitable address
+family; the packet was dropped.
+.Pp
+.It il%d: setaddr didn't work.
+The interface was unable to reprogram
+its physical ethernet address.
+This may happen with very early models of the interface.
+This facility is used only when
+the controller is not the first network interface configured for
+.Tn XNS .
+The oldest interface tested (2.7.1.0.1.45) has never failed in this way.
+.Pp
+.It il%d: reset failed, csr=%b.
+.It il%d: status failed, csr=%b.
+.It il%d: hardware diag failed, csr=%b.
+.It il%d: verifying setaddr, csr=%b.
+.It il%d: stray xmit interrupt, csr=%b.
+.It il%d: can't initialize.
+The above messages indicate a probable hardware error performing
+the indicated operation during autoconfiguration or initialization.
+The status field in the control and status register (the low-order four bits)
+should indicate the nature of the failure.
+See the hardware manual for details.
+.El
+.Sh SEE ALSO
+.Xr netintro 4 ,
+.Xr inet 4 ,
+.Xr arp 4
+.Sh HISTORY
+The
+.Nm
+interface appeared in
+.Bx 4.2 .
diff --git a/share/man/man4/man4.vax/intro.4 b/share/man/man4/man4.vax/intro.4
new file mode 100644
index 00000000000..f77853d25c8
--- /dev/null
+++ b/share/man/man4/man4.vax/intro.4
@@ -0,0 +1,183 @@
+.\" Copyright (c) 1980, 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: @(#)intro.4	6.6 (Berkeley) 3/27/91
+.\"	$Id: intro.4,v 1.1 1995/10/18 08:44:35 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt INTRO 4 vax
+.Os BSD 4
+.Sh NAME
+.Nm intro
+.Nd introduction to special files and hardware support
+.Sh DESCRIPTION
+This section describes the special files, related driver functions,
+and networking support
+available in the system.
+In this part of the manual, the
+.Tn SYNOPSIS
+section of
+each configurable device gives a sample specification
+for use in constructing a system description for the
+.Xr config 8
+program.
+The
+.Tn DIAGNOSTICS
+section lists messages which may appear on the console
+and/or in the system error log
+.Pa /var/log/messages
+due to errors in device operation;
+see
+.Xr syslogd 8
+for more information.
+.Sh VAX DEVICE SUPPORT
+This section describes the hardware supported on the
+.Tn DEC
+.Tn VAX-11 .
+Software support for these devices comes in two forms.  A hardware
+device may be supported with a character or block
+.Em device driver ,
+or it may be used within the networking subsystem and have a
+.Em network interface driver .
+Block and character devices are accessed through files in the file
+system of a special type; see
+.Xr physio 4
+and
+.Xr mknod 8 .
+Network interfaces are indirectly accessed through the interprocess
+communication facilities provided by the system; see
+.Xr socket 2 .
+.Pp
+A hardware device is identified to the system at configuration time
+and the appropriate device or network interface driver is then compiled
+into the system.  When the resultant system is booted, the
+autoconfiguration facilities in the system probe for the device
+on either the
+.Tn UNIBUS
+(or
+.Tn Q-bus )
+or
+.Tn MASSBUS
+and, if found, enable the software
+support for it.  If a
+.Tn UNIBUS
+device does not respond at autoconfiguration
+time it is not accessible at any time afterwards.  To
+enable a
+.Tn UNIBUS
+device which did not autoconfigure, the system will have to
+be rebooted.  If a
+.Tn MASSBUS
+device comes
+.Dq on-line
+after the autoconfiguration sequence
+it will be dynamically autoconfigured into the running system.
+.Pp
+The autoconfiguration system is described in
+.Xr autoconf 4 .
+A list of the supported devices is given below.
+.Sh SEE ALSO
+.Xr intro 4 ,
+.Xr netintro 4 ,
+.Xr autoconf 4 ,
+.Xr config 8 .
+.Rs
+.%T "Building 4.3 BSD UNIX Systems with Config"
+.%B SMM
+.%N 2
+.Re
+.Sh LIST OF DEVICES
+The devices listed below are supported in this incarnation of
+the system.  Pseudo-devices are not listed.
+Devices are indicated by their functional interface.
+If second vendor products provide functionally identical interfaces
+they should be usable with the supplied software.
+.Bf -symbolic
+Beware,
+however, that we promise the software works
+ONLY with the hardware indicated on the appropriate manual page.
+.Ef
+Occasionally, new devices of a similar type may be added
+simply by creating appropriate table entries in the driver.
+.Pp
+.Bl -column tmscp -offset indent
+acc	ACC LH/DH IMP communications interface
+ad	Data translation A/D interface
+css	DEC IMP-11A communications interface
+crl	VAX 8600, 8650 console RL02 disk
+ct	C/A/T or APS phototypesetter
+ddn	ACC ACP625 DDN Standard Mode X.25 IMP interface
+de	DEC DEUNA 10Mb/s Ethernet controller
+dh	DH-11 emulators, terminal multiplexor
+dhu	DHU-11 terminal multiplexor
+dmc	DEC DMC-11/DMR-11 point-to-point communications device
+dmf	DEC DMF-32 terminal multiplexor and parallel printer interface
+dmz	DEC DMZ-32 terminal multiplexor
+dn	DEC DN-11 autodialer interface
+dz	DZ-11 terminal multiplexor
+ec	3Com 10Mb/s Ethernet controller
+en	Xerox 3Mb/s Ethernet controller (obsolete)
+ex	Excelan 10Mb/s Ethernet controller
+fl	VAX-11/780 console floppy interface
+hdh	ACC IF-11/HDH IMP interface
+hk	RK6-11/RK06 and RK07 moving head disk
+hp	MASSBUS disk interface (with RP06, RM03, RM05, etc.)
+ht	TM03 MASSBUS tape drive interface (with TE-16, TU-45, TU-77)
+hy	DR-11B or GI-13 interface to an NSC Hyperchannel
+ik	Ikonas frame buffer graphics device interface
+il	Interlan 1010, 1010A 10Mb/s Ethernet controller
+ix	Interlan NP-100 10Mb/s Ethernet controller
+kg	KL-11/DL-11W line clock
+lp	LP-11 parallel line printer interface
+mt	TM78 MASSBUS tape drive interface
+np	Interlan NP-100 10Mb/s Ethernet controller (intelligent mode)
+pcl	DEC PCL-11 communications interface
+ps	Evans and Sutherland Picture System 2 graphics interface
+qe	DEC DEQNA Q-bus 10 Mb/s Ethernet interface
+rx	DEC RX02 floppy interface
+tm	TM-11/TE-10 tape drive interface
+tmscp	TMSCP-compatible tape controllers (e.g., TU81, TK50)
+ts	TS-11 tape drive interface
+tu	VAX-11/730 TU58 console cassette interface
+uda	DEC UDA-50 disk controller
+un	DR-11W interface to Ungermann-Bass
+up	Emulex SC-21V, SC-31 UNIBUS disk controller
+ut	UNIBUS TU-45 tape drive interface
+uu	TU58 dual cassette drive interface (DL11)
+va	Benson-Varian printer/plotter interface
+vp	Versatec printer/plotter interface
+vv	Proteon proNET 10Mb/s and 80Mb/s ring network interface
+.El
+.Sh HISTORY
+The section 4
+.Nm intro
+appeared in
+.Bx 4.1 .
diff --git a/share/man/man4/man4.vax/ix.4 b/share/man/man4/man4.vax/ix.4
new file mode 100644
index 00000000000..a58d2bcd63a
--- /dev/null
+++ b/share/man/man4/man4.vax/ix.4
@@ -0,0 +1,134 @@
+.\" Copyright (c) 1986, 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: @(#)ix.4	6.5 (Berkeley) 3/27/91
+.\"	$Id: ix.4,v 1.1 1995/10/18 08:44:35 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt IX 4 vax
+.Os BSD 4.2
+.Sh NAME
+.Nm ix
+.Nd Interlan Np100 10 Mb/s Ethernet interface
+.Sh SYNOPSIS
+.Cd "device np0 at uba0 csr 166000 vector npintr"
+.Sh DESCRIPTION
+The
+.Nm ix
+interface provides access to a 10 Mb/s Ethernet network through
+an Interlan Np100 controller used as a link-layer interface.
+.Pp
+This interface is unusual in that it requires loading firmware
+into the controller before it may be used as a network interface.
+This is accomplished by opening a character special device,
+and writing data to it.
+A program to load the image is provided in
+.Pa /usr/src/new/np100 .
+The sequence of commands would be:
+.Bd -literal -offset indent
+# ./npload np.image [/dev/np<board #> if other than np00]
+# sleep 10
+# ifconfig ix0 ...
+.Ed
+.Pp
+Each of the host's network addresses
+is specified at boot time with an
+.Dv SIOCSIFADDR
+.Xr ioctl 2 .
+The
+.Nm ix
+interface employs the address resolution protocol described in
+.Xr arp 4
+to dynamically map between Internet and Ethernet addresses on the local
+network.
+.Pp
+The interface normally tries to use a
+.Dq trailer
+encapsulation
+to minimize copying data on input and output.
+The use of trailers is negotiated with
+.Tn ARP .
+This negotiation may be disabled, on a per-interface basis,
+by setting the
+.Dv IFF_NOTRAILERS
+flag with an 
+.Dv SIOCSIFFLAGS 
+.Xr ioctl .
+.Sh DIAGNOSTICS
+.Bl -diag
+.It "ix%d: Req failed, cmd %x, stat %x, ust error %x,%x."
+The firmware in the controller refused to honor a request from
+.Tn UNIX
+in initializing packet level communications.
+The board may need to be reset and reloaded.
+Or, you may not have allowed enough time between loading the board
+and issuing the request to begin unix network operation.
+.Pp
+.It ix%d: can't initialize.
+The interface was unable to obtain unibus resources required for operation.
+.Pp
+.It ix%d: failed to reinitialize DLA module.
+The interface got sick after attempting to reprogram its physical
+ethernet address.  Try reloading the firmware.
+The attempt is made only when this interfaces is not the first
+one configured for
+.Tn XNS .
+.Pp
+.It ix%d: can't handle af%d.
+The interface was handed
+a message with addresses formatted in an unsuitable address
+family; the packet was dropped.
+.Pp
+.It ix%d: stray xmit interrupt, npreq=%x.
+This may happen if the board is reloaded while network processes are still
+running.
+.Pp
+.It ixrint: cqe error %x, %x, %x.
+This will result if an 
+.Xr ifconfig 8
+request is made at an inopportune time, such as not allowing
+enough time after loading the firmware.
+After 100 such errors are logged, the unix network driver will
+shut itself down, saying:
+.Pp
+.It ixrint: shutting down unix dla.
+The recourse is to reload the firmware and allow more time.
+.El
+.Sh SEE ALSO
+.Xr netintro 4 ,
+.Xr inet 4 ,
+.Xr arp 4 ,
+.Xr np 4 .
+.Sh HISTORY
+The
+.Nm
+driver appeared in
+.Bx 4.3 .
diff --git a/share/man/man4/man4.vax/kg.4 b/share/man/man4/man4.vax/kg.4
new file mode 100644
index 00000000000..b4c502f040c
--- /dev/null
+++ b/share/man/man4/man4.vax/kg.4
@@ -0,0 +1,70 @@
+.\" 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. 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: @(#)kg.4	6.2 (Berkeley) 3/27/91
+.\"	$Id: kg.4,v 1.1 1995/10/18 08:44:35 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt KG 4 vax
+.Os BSD 4.2
+.Sh NAME
+.Nm kg
+.Nd
+.Tn KL-11 Ns / Tn DL-11W
+line clock
+.Sh SYNOPSIS
+.Cd "device kg0 at uba0 csr 0176500 vector kglock"
+.Sh DESCRIPTION
+A
+.Tn KL-11
+or
+.Tn DL-11W
+can be used as an alternate real
+time clock
+source.  When configured, certain system
+statistics and, optionally, system profiling work
+will be collected each time the clock interrupts.  For
+optimum accuracy in profiling, the
+.Tn DL-11W
+should be
+configured to interrupt at the highest possible priority
+level.  The 
+.Nm kg
+device driver automatically calibrates itself to the
+line clock frequency.
+.Sh SEE ALSO
+.Xr kgmon 8 ,
+.Xr config 8
+.Sh HISTORY
+The
+.Nm
+driver appeared in
+.Bx 4.2 .
diff --git a/share/man/man4/man4.vax/lp.4 b/share/man/man4/man4.vax/lp.4
new file mode 100644
index 00000000000..7c0607c1b82
--- /dev/null
+++ b/share/man/man4/man4.vax/lp.4
@@ -0,0 +1,86 @@
+.\" Copyright (c) 1980, 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: @(#)lp.4	6.2 (Berkeley) 3/27/91
+.\"	$Id: lp.4,v 1.1 1995/10/18 08:44:35 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt LP 4 vax
+.Os BSD 4
+.Sh NAME
+.Nm lp
+.Nd line printer
+.Sh SYNOPSIS
+.Cd "device lp0 at uba0 csr 0177514 vector lpintr"
+.Sh DESCRIPTION
+The
+.Nm lp
+device
+supports
+.Tn DEC
+and
+.Tn DEC
+compatible printers
+on the
+.Tn LP-11
+parallel interface.
+.Pp
+The unit number of the printer is specified by the minor device
+after removing the low 3 bits, which act as per-device parameters.
+Currently only the lowest of the low three bits is interpreted:
+if it is set, the device is assumed to have a 64-character set or
+.Pf half Tn -ASCII
+mode,
+rather than a full 96-character set.
+.Pp
+If the 64-character set is assumed,
+any lower case characters are mapped to upper case; left curly and
+right curly braces are mapped to left and right parentheses over
+laid with a hyphen; grave accents are mapped to acute accents
+with overlaid with a hyphen; the pipe bar character is mapped
+to an exclamation sign overlaid with a hyphen; and the tilde
+character is mapped to a carat overlaid with a hyphen.
+.Pp
+The default page width is 132 columns; longer lines are
+truncated.
+This may be overridden by specifying, for example,
+.Ql flags 256 .
+.Sh FILES
+.Bl -tag -width Pa -compact
+.It Pa /dev/lp
+.El
+.Sh SEE ALSO
+.Xr lpr 1
+.Sh HISTORY
+A
+.Nm
+driver appeared in
+.At v6 .
diff --git a/share/man/man4/man4.vax/mem.4 b/share/man/man4/man4.vax/mem.4
new file mode 100644
index 00000000000..af4fd39a993
--- /dev/null
+++ b/share/man/man4/man4.vax/mem.4
@@ -0,0 +1,105 @@
+.\" Copyright (c) 1980, 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: @(#)mem.4	6.3 (Berkeley) 3/27/91
+.\"	$Id: mem.4,v 1.1 1995/10/18 08:44:35 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt MEM 4 vax
+.Os BSD 4
+.Sh NAME
+.Nm mem ,
+.Nm kmem ,
+.Nm kUmem
+.Nd memory files
+.Sh DESCRIPTION
+The special file
+.Nm /dev/mem
+is an interface to the physical memory of the computer.
+Byte offsets in this file are interpreted as physical memory addresses.
+Reading and writing this file is equivalent to reading and writing
+memory itself.
+Only offsets within the bounds of
+.Nm /dev/mem
+are allowed.
+.Pp
+Kernel virtual memory is accessed through the interface
+.Nm /dev/kmem
+in the same manner as
+.Nm /dev/mem .
+Only kernel virtual addresses that are currently mapped to memory are allowed.
+.Pp
+The file
+.Nm /dev/kUmem
+also refers to kernel virtual memory,
+but may be used to access areas mapped to
+.Tn UNIBUS
+address space
+and other
+.Tn I/O
+areas.
+It forces all accesses to use word (short integer) accesses.
+.Pp
+On the
+.Tn VAX
+11/780,
+the
+.Tn I/O
+space base address is
+20000000(16);
+on an 11/750
+the
+.Tn I/O space addresses are of the form fxxxxx(16).
+On all
+.Tn VAX Ns 'en
+the
+per-process data
+size
+for the current process
+is
+.Dv UPAGES
+long and ends at the virtual address 80000000(16).
+.Sh FILES
+.Bl -tag -width Pa -compact
+.It Pa /dev/mem
+.It Pa /dev/kmem
+.It Pa /dev/kUmem
+.El
+.Sh HISTORY
+The
+.Nm mem ,
+.Nm kmem
+files appeared in
+.At v6 .
+The file
+.Nm kUmem
+appeared in
+.Bx 3.0 .
diff --git a/share/man/man4/man4.vax/mt.4 b/share/man/man4/man4.vax/mt.4
new file mode 100644
index 00000000000..da79ab4179a
--- /dev/null
+++ b/share/man/man4/man4.vax/mt.4
@@ -0,0 +1,117 @@
+.\" Copyright (c) 1980, 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: @(#)mt.4	6.4 (Berkeley) 3/27/91
+.\"	$Id: mt.4,v 1.1 1995/10/18 08:44:35 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt MT 4 vax
+.Os BSD 4
+.Sh NAME
+.Nm mt
+.Nd
+.Tn TM78 Ns / Tn TU-78
+.Tn MASSBUS
+magtape interface
+.Sh SYNOPSIS
+.Cd "master mt0 at mba? drive ? tape mu0 at mt0 slave 0"
+.Sh DESCRIPTION
+The
+.Tn TM78 Ns / Tn TU-78
+combination provides a standard tape drive
+interface as described in
+.Xr mtio 4 .
+Only 1600 and 6250
+.Tn BPI
+are supported; the
+.Tn TU-78
+runs at 125
+.Tn IPS
+and autoloads tapes.
+.Sh DIAGNOSTICS
+.Bl -diag
+.It mu%d: no write ring.
+An attempt was made to write on the tape drive
+when no write ring was present; this message is written on the terminal of
+the user who tried to access the tape.
+.Pp
+.It mu%d: not online.
+An attempt was made to access the tape while it
+was offline; this message is written on the terminal of the user
+who tried to access the tape.
+.Pp
+.It "mu%d: can't change density in mid-tape."
+An attempt was made to write
+on a tape at a different density than is already recorded on the tape.
+This message is written on the terminal of the user who tried to switch
+the density.
+.Pp
+.It "mu%d: hard error bn%d mbsr=%b er=%x ds=%b."
+A tape error occurred
+at block
+.Em bn ;
+the mt error register and drive status register are
+printed in octal with the bits symbolically decoded.  Any error is
+fatal on non-raw tape; when possible the driver will have retried
+the operation which failed several times before reporting the error.
+.Pp
+.It mu%d: blank tape.
+An attempt was made to read a blank tape (a tape without even
+end-of-file marks).
+.Pp
+.It mu%d: offline.
+During an i/o operation the device was set offline.  If a
+non-raw tape was used in the access it is closed.
+.El
+.Sh SEE ALSO
+.Xr mt 1 ,
+.Xr tar 1 ,
+.Xr tp 1 ,
+.Xr mtio 4 ,
+.Xr tm 4 ,
+.Xr ts 4 ,
+.Xr ut 4
+.Sh HISTORY
+The
+.Nm
+driver appeared in
+.Bx 4.1 .
+.Sh BUGS
+If a physical error (non-data) occurs,
+.Nm
+may hang ungracefully.
+.Pp
+Because 800
+.Tn BPI
+tapes are not supported, the numbering of minor devices
+is inconsistent with triple-density tape units.
+Unit 0 is drive 0, 1600
+.Tn BPI.
diff --git a/share/man/man4/man4.vax/mtio.4 b/share/man/man4/man4.vax/mtio.4
new file mode 100644
index 00000000000..369d2b73078
--- /dev/null
+++ b/share/man/man4/man4.vax/mtio.4
@@ -0,0 +1,235 @@
+.\" Copyright (c) 1983, 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: @(#)mtio.4	6.5 (Berkeley) 3/27/91
+.\"	$Id: mtio.4,v 1.1 1995/10/18 08:44:35 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt MTIO 4 vax
+.Os BSD 4.2
+.Sh NAME
+.Nm mtio
+.Nd
+.Tn UNIX
+magtape interface
+.Sh DESCRIPTION
+The special files
+named
+.Pa /dev/mt0
+and
+.Pa /dev/rmt0
+through
+.Pa /dev/mt23
+and
+.Pa /dev/rmt23
+refer to
+.Tn UNIX
+magtape drives,
+which may be on the
+.Tn MASSBUS
+using the
+.Tn TM03
+formatter
+.Xr ht 4 ,
+or
+.Tn TM78
+formatter,
+.Xr mt 4 ,
+or on the
+.Tn UNIBUS
+using either the
+.Tn TM11
+or
+.Tn TS11
+formatters
+.Xr tm 4 ,
+.Tn TU45
+compatible formatters,
+.Xr ut 4 ,
+or
+.Xr ts 4 .
+These devices are typical tape block devices,
+see
+.Xr physio 4 .
+.Pp
+The following table of the converntional device names
+is applicable to any of the transport/controller pairs.
+(But note that only 1600
+.Tn BPI
+is available with the
+.Tn TS11 . )
+.Bl -column "no-rewindxxx" "or lowest densityxx" "or lowest densityxx" "or lowest densityxx" -offset indent
+	      800 BPI	      1600 BPI	      6500 BPI
+.Em	or lowest density	or second density	or third density
+
+Rewind	     mt0/rmt0	      mt8/rmt8	       mt16/rmt16
+Rewind	     mt1/rmt1	      mt9/rmt9	       mt17/rmt17
+Rewind	     mt2/rmt2	      mt10/rmt10	       mt18/rmt18
+Rewind	     mt3/rmt3	      mt11/rmt11	       mt19/rmt19
+No-rewind	    nmt4/nrmt4	    nmt12/nrmt12	    nmt20/nrmt20
+No-rewind	    nmt5/nrmt5	    nmt13/nrmt13	    nmt21/nrmt21
+No-rewind	    nmt6/nrmt6	    nmt14/nrmt14	    nmt22/nrmt22
+No-rewind	    nmt7/nrmt7	    nmt15/nrmt15	    nmt23/nrmt32
+.El
+.Pp
+The rewind devices automatically rewind
+when the last requested read, write or seek has finished, or the end of the tape
+has been reached. The letter
+.Ql n
+is usually prepended to
+the name of the no-rewind devices.
+.Pp
+Unix tapes are written in multiples of 1024 byte block
+records. Two end-of-file markers mark the end of a tape, and
+one end-of-file marker marks the end of a tape file.
+If the tape is not to be rewound it is positioned with the
+head in between the two tape marks, where the next write
+will over write the second end-of-file marker.
+.Pp
+All of the magtape devices may be manipulated with the
+.Xr mt 1
+command.
+.Pp
+A number of
+.Xr ioctl 2
+operations are available
+on raw magnetic tape.
+The following definitions are from
+.Aq Pa sys/mtio.h :
+.Bd  -literal
+/*
+ * Structures and definitions for mag tape io control commands
+ */
+
+/* structure for MTIOCTOP - mag tape op command */
+struct	mtop	{
+	short	mt_op;		/* operations defined below */
+	daddr_t	mt_count;	/* how many of them */
+};
+
+/* operations */
+#define MTWEOF	0	/* write an end-of-file record */
+#define MTFSF	1	/* forward space file */
+#define MTBSF	2	/* backward space file */
+#define MTFSR	3	/* forward space record */
+#define MTBSR	4	/* backward space record */
+#define MTREW	5	/* rewind */
+#define MTOFFL	6	/* rewind and put the drive offline */
+#define MTNOP	7	/* no operation, sets status only */
+#define MTCACHE 8	/* enable controller cache */
+#define MTNOCACHE 9	/* disable controller cache */
+
+/* structure for MTIOCGET - mag tape get status command */
+
+struct	mtget	{
+	short	mt_type;	/* type of magtape device */
+/* the following two registers are grossly device dependent */
+	short	mt_dsreg;	/* ``drive status'' register */
+	short	mt_erreg;	/* ``error'' register */
+/* end device-dependent registers */
+	short	mt_resid;	/* residual count */
+/* the following two are not yet implemented */
+	daddr_t	mt_fileno;	/* file number of current position */
+	daddr_t	mt_blkno;	/* block number of current position */
+/* end not yet implemented */
+};
+
+/*
+ * Constants for mt_type byte.  These are the same
+ * for controllers compatible with the types listed.
+ */
+#define	MT_ISTS		0x01		/* TS-11 */
+#define	MT_ISHT		0x02		/* TM03 Massbus: TE16, TU45, TU77 */
+#define	MT_ISTM		0x03		/* TM11/TE10 Unibus */
+#define	MT_ISMT		0x04		/* TM78/TU78 Massbus */
+#define	MT_ISUT		0x05		/* SI TU-45 emulation on Unibus */
+#define	MT_ISCPC	0x06		/* SUN */
+#define	MT_ISAR		0x07		/* SUN */
+#define	MT_ISTMSCP	0x08		/* DEC TMSCP protocol (TU81, TK50) */
+#define MT_ISCY 	0x09		/* CCI Cipher */
+#define MT_ISCT 	0x0a		/* HP 1/4 tape */
+#define MT_ISFHP	0x0b		/* HP 7980 1/2 tape */
+#define MT_ISEXABYTE	0x0c		/* Exabyte */
+#define MT_ISEXA8200	0x0c		/* Exabyte EXB-8200 */
+#define MT_ISEXA8500	0x0d		/* Exabyte EXB-8500 */
+#define MT_ISVIPER1	0x0e		/* Archive Viper-150 */
+#define MT_ISPYTHON	0x0f		/* Archive Python (DAT) */
+#define MT_ISHPDAT	0x10		/* HP 35450A DAT drive */
+
+/* mag tape io control commands */
+#define	MTIOCTOP	_IOW('m', 1, struct mtop)	/* do a mag tape op */
+#define	MTIOCGET	_IOR('m', 2, struct mtget)	/* get tape status */
+#define MTIOCIEOT	_IO('m', 3)			/* ignore EOT error */
+#define MTIOCEEOT	_IO('m', 4)			/* enable EOT error */
+
+#ifndef KERNEL
+#define	DEFTAPE	"/dev/rmt12"
+#endif
+
+#ifdef	KERNEL
+/*
+ * minor device number
+ */
+
+#define	T_UNIT		003		/* unit selection */
+#define	T_NOREWIND	004		/* no rewind on close */
+#define	T_DENSEL	030		/* density select */
+#define	T_800BPI	000		/* select  800 bpi */
+#define	T_1600BPI	010		/* select 1600 bpi */
+#define	T_6250BPI	020		/* select 6250 bpi */
+#define	T_BADBPI	030		/* undefined selection */
+#endif
+.Ed
+.Pp
+.Sh FILES
+.Bl -tag -width /dev/rmt? -compact
+.It Pa /dev/mt?
+.It Pa /dev/rmt?
+.El
+.Sh SEE ALSO
+.Xr mt 1 ,
+.Xr tar 1 ,
+.Xr tp 1 ,
+.Xr ht 4 ,
+.Xr tm 4 ,
+.Xr ts 4 ,
+.Xr mt 4 ,
+.Xr ut 4
+.Sh HISTORY
+The
+.Nm mtio
+manual appeared in
+.Bx 4.2 .
+.Sh BUGS
+The status should be returned in a device independent format.
+.Pp
+The special file naming should be redone in a more consistent and
+understandable manner.
diff --git a/share/man/man4/man4.vax/np.4 b/share/man/man4/man4.vax/np.4
new file mode 100644
index 00000000000..237e954ddbf
--- /dev/null
+++ b/share/man/man4/man4.vax/np.4
@@ -0,0 +1,136 @@
+.\" Copyright (c) 1986, 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: @(#)np.4	6.6 (Berkeley) 3/27/91
+.\"	$Id: np.4,v 1.1 1995/10/18 08:44:35 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt NP 4 vax
+.Os BSD 4.2
+.Sh NAME
+.Nm np
+.Nd Interlan Np100 10 Mb/s Ethernet interface
+.Sh SYNOPSIS
+.Cd "device np0 at uba0 csr 166000 vector npintr"
+.Sh DESCRIPTION
+The
+.Nm np
+device provides access to an Interlan Np100 Ethernet interface
+for control functions.
+.Pp
+This interface is unusual in that it requires loading firmware
+into the controller before it may be used as a network link-level interface.
+This is accomplished by opening a character special device,
+and writing data to it.
+It is also possible to do post-mortem debugging of firmware failures
+by reading the local memory of the device.
+.\" .Pp
+.\" A program to load the image is provided in
+.\" .Pa /usr/src/new/np100 .
+.\" The sequence of commands would be:
+.\" .Bd -literal -offset indent
+.\" # ./npload np.image [/dev/np00]
+.\" # sleep 10
+.\" # ifconfig ix0 ...
+.\" .Ed
+.Pp
+Multiple control processes are allowed by opening separate
+minor devices; secondary interfaces are specified by shifting
+the interface number by 4 bits.
+.Pp
+The device also responds to commands passed through the driver
+by the following
+.Xr ioctl 2 Ns s :
+.Bl -tag -width NPNETBOOT
+.It Dv NPRESET
+kills off all active network processes.
+.It Dv NPSTART
+begins execution of the board at the specified address (usually
+.Li 0x400 ) .
+.It Dv NPNETBOOT
+downloads the image from a server on the network.
+[Contact
+.Tn MICOM-INTERLAN
+for details.]
+.El
+.Sh DIAGNOSTICS
+.Bl -diag
+.It np%d: Bad Maintenance command: %x!
+An invalid
+.Xr ioctl
+was passed to the np driver.
+.Pp
+.It np%d: Panic NP100 bad buffer chain.
+An error occurred in an read or write operation causing it to
+run out of buffers before it finished the operation.
+This indicates a kernel failure rather than a device failure.
+.Pp
+.It NP100 unit %d not found!
+A failure occurred during initialization, such that the unibus
+address expected for the board was found to be bad.
+Probably indicates hardware problems with the board, as do the following:
+.Pp
+.Bd -filled -offset indent -compact
+.It NP100 Unit %d timed out!
+.It NP100 Unit %d Failed diagnostics!
+.It Status from CSR0: %x.
+.Ed
+.Pp
+.It "Panic from NP100 unit %d!"
+.It "Panic Message: %s."
+An occurrence on the board was deemed serious enough
+to have the vax print it out.  
+.Pp
+.It NP100 unit #%d available!
+The board was successfully loaded and started.
+.Pp
+.It np%d: Bad Req: %x.
+The board made a maintenance request to the vax that it did not
+understand.
+.Pp
+.It np%d: No more room on Command Queue!
+The np driver allowed an internal resource to be exhausted.
+This should never happen.
+.El
+.Pp
+There are 110 other diagnostic messages that can be enabled
+by setting bits in a debugging mask.
+Consult the driver for details.
+.Sh SEE ALSO
+.Xr netintro 4 ,
+.Xr inet 4 ,
+.Xr arp 4 ,
+.Xr ix 4
+.Sh HISTORY
+The
+.Nm
+driver appeared in
+.Bx 4.3 .
diff --git a/share/man/man4/man4.vax/pcl.4 b/share/man/man4/man4.vax/pcl.4
new file mode 100644
index 00000000000..3ecbc532c02
--- /dev/null
+++ b/share/man/man4/man4.vax/pcl.4
@@ -0,0 +1,133 @@
+.\" 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. 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: @(#)pcl.4	6.3 (Berkeley) 3/27/91
+.\"	$Id: pcl.4,v 1.1 1995/10/18 08:44:35 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt PCL 4 vax
+.Os BSD 4.2
+.Sh NAME
+.Nm pcl
+.Nd
+.Tn DEC CSS
+.Tn PCL-11 B
+Network Interface
+.Sh SYNOPSIS
+.Cd "device pcl0 at uba? csr 164200 vector pclxint pclrint"
+.Sh DESCRIPTION
+The 
+.Nm pcl
+device provides an
+.Tn IP Ns -only
+interface to the
+.Tn DEC CSS
+.Tn PCL-11
+time division multiplexed network bus.
+The controller itself is not accessible to users.
+.Pp
+The hosts's address is specified with the
+.Dv SIOCSIFADDR
+.Xr ioctl 2 .
+The interface will not transmit or receive any data before
+its address is defined.
+.Pp
+As the
+.Tn PCL-11
+hardware is only capable of having 15 interfaces per network,
+a single-byte host-on-network number is used, with range [1..15] to match
+the
+.Tn TDM
+bus addresses of the interfaces.
+.Pp
+The interface currently only supports the Internet protocol family
+and only provides
+.Dq natural
+(header) encapsulation.
+.Sh DIAGNOSTICS
+.Bl -diag
+.It pcl%d: can't init.
+Insufficient
+.Tn UNIBUS
+resources existed to initialize the device.
+This is likely to occur when the device is run on a buffered
+data path on an 11/750 and other network interfaces are also
+configured to use buffered data paths, or when it is configured
+to use buffered data paths on an 11/730 (which has none).
+.Pp
+.It pcl%d: can't handle af%d.
+The interface was handed a message with addresses formatted in an
+unsuitable address family;  the packet was dropped.
+.Pp
+.It pcl%d: stray xmit interrupt.
+An interrupt occurred when no output had previously been started.
+.Pp
+.It pcl%d: master.
+The
+.Tn TDM
+bus had no station providing ``bus master'' timing signals,
+so this interface has assumed the ``master'' role.  This message should
+only appear at most once per
+.Tn UNIBUS INIT
+on a single system.
+Unless there is a hardware failure, only one station may be master at at time.
+.Pp
+.It pcl%d: send error, tcr=%b, tsr=%b.
+The device indicated a problem sending data on output.
+If a ``receiver offline'' error is detected, it is not normally logged
+unless the option
+.Dv PCL_TESTING
+has been selected, as this causes a lot
+of console chatter when sending to a down machine.  However, this option
+is quite useful when debugging problems with the
+.Tn PCL
+interfaces.
+.Pp
+.It pcl%d: rcv error, rcr=%b rsr=%b.
+The device indicated a problem receiving data on input.
+.Pp
+.It pcl%d: bad len=%d.
+An input operation resulted in a data transfer of less than
+0 or more than 1008 bytes of
+data into memory (according to the word count register).
+This should never happen as the maximum size of a
+.Tn PCL
+message
+has been agreed upon to be 1008 bytes (same as ArpaNet message).
+.El
+.Sh SEE ALSO
+.Xr intro 4 ,
+.Xr inet 4
+.Sh HISTORY
+The
+.Nm
+interface appeared in
+.Bx 4.2 .
diff --git a/share/man/man4/man4.vax/ps.4 b/share/man/man4/man4.vax/ps.4
new file mode 100644
index 00000000000..50af2c15a84
--- /dev/null
+++ b/share/man/man4/man4.vax/ps.4
@@ -0,0 +1,153 @@
+.\" 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. 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: @(#)ps.4	6.4 (Berkeley) 3/27/91
+.\"	$Id: ps.4,v 1.1 1995/10/18 08:44:35 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt PS 4 vax
+.Os BSD 4.2
+.Sh NAME
+.Nm ps
+.Nd Evans and Sutherland Picture System 2 graphics device interface
+.Sh SYNOPSIS
+.Cd "device ps0 at uba? csr 0172460 vector psclockintr pssystemintr"
+.Sh DESCRIPTION
+The
+.Nm ps
+driver provides access
+to an Evans and
+Sutherland Picture System 2 graphics device.
+Each minor device is a new
+.Tn PS2 .
+When the device is opened, its interface registers are mapped,
+via virtual memory, into a user process's address space.
+This allows the user process very high bandwidth to the device
+with no system call overhead.
+.Pp
+.Tn DMA
+to and from the
+.Tn PS2
+is not supported. All read and write
+system calls will fail.
+All data is moved to and from the
+.Tn PS2
+via programmed
+.Tn I/O
+using
+the device's interface registers.
+.Pp
+Commands are fed to and from the driver using the following
+.Xr ioctl 2 Ns s :
+.Bl -tag -width PSIOSINGLEREFRESH
+.It Dv PSIOGETADDR
+Returns the virtual address through which the user process can access
+the device's interface registers.
+.It Dv PSIOAUTOREFRESH
+Start auto refreshing the screen.
+The argument is an address in user space where the following data resides.
+The first longword is a
+.Em count
+of the number of static refresh buffers.
+The next
+.Em count
+longwords are the addresses in refresh memory where
+the refresh buffers lie.
+The driver will cycle through these refresh buffers displaying them one by one
+on the screen.
+.It Dv PSIOAUTOMAP
+Start automatically passing the display file through the matrix processor and
+into the refresh buffer.
+The argument is an address in user memory where the following data resides.
+The first longword is a
+.Em count
+of the number of display files to operate on.
+The next
+.Em count
+longwords are the address of these display files.
+The final longword is the address in refresh buffer memory where transformed
+coordinates are to be placed if the driver is not in double buffer mode (see
+below).
+.It Dv PSIODOUBLEBUFFER
+Cause the driver to double buffer the output from the map that
+is going to the refresh buffer.
+The argument is again a user space address where the real arguments are stored.
+The first argument is the starting address of refresh memory where the two
+double buffers are located.
+The second argument is the length of each double buffer.
+The refresh mechanism displays the current double buffer, in addition
+to its static refresh lists, when in double buffer mode.
+.It Dv PSIOSINGLEREFRESH
+Single step the refresh process. That is, the driver does not continually
+refresh the screen.
+.It Dv PSIOSINGLEMAP
+Single step the matrix process.
+The driver does not automatically feed display files through the matrix unit.
+.It Dv PSIOSINGLEBUFFER
+Turn off double buffering.
+.It Dv PSIOTIMEREFRESH
+The argument is a count of the number of refresh interrupts to take
+before turning off the screen.  This is used to do time exposures.
+.It Dv PSIOWAITREFRESH
+Suspend the user process until a refresh interrupt has occurred.
+If in
+.Dv TIMEREFRESH
+mode, suspend until count refreshes have occurred.
+.It Dv PSIOSTOPREFRESH
+Wait for the next refresh, stop all refreshes, and then return to user process.
+.It Dv PSIOWAITMAP
+Wait until a map done interrupt has occurred.
+.It Dv PSIOSTOPMAP
+Wait for a map done interrupt, do not restart the map, and then
+return to the user.
+.El
+.Sh FILES
+.Bl -tag -width /dev/psxx
+.It Pa /dev/ps
+.El
+.Sh DIAGNOSTICS
+.Bl -diag
+.It ps device intr.
+.It ps dma intr.
+An interrupt was received from the device. 
+This shouldn't happen,
+check your device configuration for overlapping interrupt vectors.
+.El
+.Sh HISTORY
+The
+.Nm
+driver appeared in
+.Bx 4.2 .
+.Sh BUGS
+An invalid access (e.g., longword) to a mapped interface register
+can cause the system to crash with a machine check.
+A user process could possibly cause infinite interrupts hence
+bringing things to a crawl.
diff --git a/share/man/man4/man4.vax/qe.4 b/share/man/man4/man4.vax/qe.4
new file mode 100644
index 00000000000..19082537133
--- /dev/null
+++ b/share/man/man4/man4.vax/qe.4
@@ -0,0 +1,86 @@
+.\" Copyright (c) 1983, 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: @(#)qe.4	6.4 (Berkeley) 3/27/91
+.\"	$Id: qe.4,v 1.1 1995/10/18 08:44:35 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt QE 4 vax
+.Os BSD 4.3
+.Sh NAME
+.Nm qe
+.Nd
+.Tn DEC DEQNA
+.Tn Q-bus
+10 Mb/s Ethernet interface
+.Sh SYNOPSIS
+.Cd "device qe0 at uba? csr 174440 vector qeintr"
+.Sh DESCRIPTION
+The
+.Nm qe
+interface provides access to a 10 Mb/s Ethernet network through
+the
+.Tn DEC DEQNA
+.Tn Q-bus
+controller.
+.Pp
+Each of the host's network addresses
+is specified at boot time with an
+.Dv SIOCSIFADDR
+.Xr ioctl 2 .
+The
+.Nm qe
+interface employs the address resolution protocol described in
+.Xr arp 4
+to map dynamically  between Internet and Ethernet addresses on the local
+network.
+.Pp
+The interface normally tries to use a
+.Dq trailer
+encapsulation
+to minimize copying data on input and output.
+The use of trailers is negotiated with
+.Tn ARP .
+This negotiation may be disabled, on a per-interface basis,
+by setting the
+.Dv IFF_NOTRAILERS
+flag with an
+.Dv SIOCSIFFLAGS
+.Xr ioctl .
+.Sh SEE ALSO
+.Xr netintro 4 ,
+.Xr inet 4 ,
+.Xr arp 4
+.Sh HISTORY
+The
+.Nm
+driver appeared in
+.Bx 4.3 .
diff --git a/share/man/man4/man4.vax/rx.4 b/share/man/man4/man4.vax/rx.4
new file mode 100644
index 00000000000..af45611f673
--- /dev/null
+++ b/share/man/man4/man4.vax/rx.4
@@ -0,0 +1,255 @@
+.\" 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. 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: @(#)rx.4	6.2 (Berkeley) 3/27/91
+.\"	$Id: rx.4,v 1.1 1995/10/18 08:44:35 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt RX 4 vax
+.Os BSD 4.2
+.Sh NAME
+.Nm rx
+.Nd
+.Tn DEC
+.Tn RX02
+floppy disk interface
+.Sh SYNOPSIS
+.Cd "controller fx0 at uba0 csr 0177170  vector rxintr"
+.Cd "disk rx0 at fx0 drive 0"
+.Cd "disk rx1 at fx0 drive 1"
+.Sh DESCRIPTION
+The
+.Nm rx
+device provides access to a
+.Tn DEC
+.Tn RX02
+floppy disk
+unit with M8256 interface module
+.Pf ( Tn RX211
+configuration). 
+The
+.Tn RX02
+uses 8-inch, single-sided, soft-sectored floppy
+disks (with pre-formatted industry-standard headers) in
+either single or double density.
+.Pp
+Floppy disks handled by the
+.Tn RX02
+contain 77 tracks, each with 26
+sectors (for a total of 2,002 sectors).  The sector size is 128
+bytes for single density, 256 bytes for double density.  Single 
+density disks are compatible with the
+.Tn RX01
+floppy disk unit and with
+.Tn IBM
+3740 Series Diskette 1 systems.  
+.Pp
+In addition to normal (`block' and `raw')
+.Tn I/O ,
+the driver supports
+formatting of disks for either density and
+the ability to invoke a 2 for 1 interleaved sector mapping
+compatible with the
+.Tn DEC
+operating system
+.Tn RT-11 .
+.Pp
+The minor device number is interpreted as follows:
+.Pp
+.Bl -column Otherx -offset indent
+.Sy Bit	Description
+0	Sector interleaving  (1 disables interleaving)
+1	Logical sector 1 is on track 1 (0 no, 1 yes)
+2	Not used, reserved
+Other	Drive number
+.El
+.Pp
+The two drives in a single
+.Tn RX02
+unit are treated as
+two disks attached to a single controller.  Thus, if there are two
+.Tn RX02 Ns 's
+on a system, the drives on the first
+.Tn RX02
+are
+.Dq Li rx0
+and
+.Dq Li rx1 ,
+while the drives on the second are
+.Dq Li rx2
+and
+.Dq Li rx3 . 
+.Pp
+When the device is opened, the density of the disk
+currently in the drive is automatically determined. If there
+is no floppy in the device, open will fail.
+.Pp
+The interleaving parameters are represented in raw device
+names by the letters
+.Ql a
+through
+.Ql d .
+Thus, unit 0, drive 0 is
+called by one of the following names:
+.Pp
+.Bl -column interleavedxx "Device namexx" "Starting Track" -offset indent
+.Sy Mapping	Device name	Starting track
+interleaved	/dev/rrx0a	0
+direct	/dev/rrx0b	0
+interleaved	/dev/rrx0c	1
+direct	/dev/rrx0d	1
+.El
+.Pp
+The mapping used on the
+.Ql c
+device is compatible with the
+.Tn DEC
+operating system
+.Tn RT-11 .
+The
+.Ql b
+device accesses the
+sectors of the disk in strictly sequential order.  
+The
+.Ql a
+device is the most efficient for disk-to-disk copying.
+This mapping is always used by the block device.
+.Pp
+.Tn I/O
+requests must start on a sector boundary, involve an integral
+number of complete sectors, and not go off the end of the disk.
+.Sh NOTES
+Even though the storage capacity on a floppy disk is quite
+small, it is possible to make filesystems on 
+double density disks. 
+For example, the command
+.Bd -literal -offset indent
+% mkfs /dev/rx0 1001 13 1 4096 512 32 0 4
+.Ed
+.Pp
+makes a file system on the double density disk in rx0 with 
+436 kbytes available for file storage.
+Using
+.Xr tar 1
+gives a more efficient utilization of the available
+space for file storage.
+Single density diskettes do not provide sufficient storage capacity to
+hold file systems.
+.Pp
+A number of
+.Xr ioctl 2
+calls apply to the rx devices, and
+have the form
+.Bd -literal -offset indent
+#include <vaxuba/rxreg.h>
+ioctl(fildes, code, arg)
+int *arg;
+.Ed
+.Pp
+The applicable codes are:
+.Bl -tag -width RXIOC_GETDENS
+.It Dv RXIOC_FORMAT
+Format the diskette. The density to use is specified
+by the 
+.Ar arg
+argument, zero gives single density while non-zero
+gives double density.
+.It Dv RXIOC_GETDENS
+Return the density of the diskette (zero or non-zero as above).
+.It Dv RXIOC_WDDMK
+On the next write, include a
+.Em deleted data address mark
+in 
+the header of the first sector.
+.It Dv RXIOC_RDDMK
+Return non-zero if the last sector read contained a
+.Em deleted data address mark
+in its header, otherwise
+return 0.
+.El
+.Sh FILES
+.Bl -tag -width /dev/rx?xx -compact
+.It Pa /dev/rx?
+.It Pa /dev/rrx?[a-d]
+.El
+.Sh DIAGNOSTICS
+.Bl -diag
+.It "rx%d: hard error, trk %d psec %d cs=%b, db=%b, err=%x, %x, %x, %x."
+An unrecoverable error was encountered.  The 
+track and physical sector numbers, the device registers and the 
+extended error status are displayed.
+.Pp
+.It rx%d: state %d (reset).
+The driver entered a bogus state.  This should not happen.
+.El
+.Sh ERRORS
+The following errors may be returned by the driver:
+.Bl -tag -width [ENODEV]
+.It Bq Er ENODEV
+Drive not ready; usually because no disk is in the drive or
+the drive door is open.
+.It Bq Er ENXIO
+Nonexistent drive (on open); 
+offset is too large or not on a sector boundary or
+byte count is not a multiple of the sector size (on read or write);
+or bad (undefined) ioctl code.
+.It Bq Er EIO
+A physical error other than ``not ready'', probably bad media or 
+unknown format.
+.It Bq Er EBUSY
+Drive has been opened for exclusive access.
+.It Bq Er EBADF
+No write access (on format), or wrong density; the latter
+can only happen if the disk is changed without 
+.Em closing
+the device
+(i.e., calling
+.Xr close 2 ) .
+.El
+.Sh SEE ALSO
+.Xr rxformat 8 ,
+.Xr newfs 8 ,
+.Xr mkfs 8 ,
+.Xr tar 1 ,
+.Xr arff 8
+.Sh HISTORY
+The
+.Nm
+driver appeared in
+.Bx 4.2 .
+.Sh BUGS
+A floppy may not be formatted if the
+header info on sector 1, track 0 has been damaged.  Hence, it is not
+possible to format completely degaussed disks or disks with other
+formats than the two known by the hardware. 
+.Pp
+If the drive subsystem is powered down when the machine is booted, the
+controller won't interrupt.
diff --git a/share/man/man4/man4.vax/tm.4 b/share/man/man4/man4.vax/tm.4
new file mode 100644
index 00000000000..0fd0728e86c
--- /dev/null
+++ b/share/man/man4/man4.vax/tm.4
@@ -0,0 +1,110 @@
+.\" Copyright (c) 1980, 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: @(#)tm.4	6.3 (Berkeley) 3/27/91
+.\"	$Id: tm.4,v 1.1 1995/10/18 08:44:35 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt TM 4 vax
+.Os BSD 4
+.Sh NAME
+.Nm tm
+.Nd
+.Tn TM-11 Ns / Tn TE-10
+magtape device interface
+.Sh SYNOPSIS
+.Sy "controller tm0 at uba? csr 0172520 vector tmintr"
+.Sy "tape te0 at tm0 drive 0"
+.Sh DESCRIPTION
+The
+.Tn TM-11 Ns / Tn TE-10
+combination provides a standard tape drive
+interface as described in
+.Xr mtio 4 .
+Hardware implementing this on the
+.Tn VAX
+is typified by the Emulex
+.Tn TC-11
+controller operating with a Kennedy model 9300 tape transport,
+providing 800 and 1600
+.Tn BPI operation at 125
+.Tn IPS .
+.Sh DIAGNOSTICS
+.Bl -diag
+.It te%d: no write ring.
+An attempt was made to write on the tape drive
+when no write ring was present; this message is written on the terminal of
+the user who tried to access the tape.
+.Pp
+.It te%d: not online.
+An attempt was made to access the tape while it
+was offline; this message is written on the terminal of the user
+who tried to access the tape.
+.Pp
+.It te%d: can't change density in mid-tape.
+An attempt was made to write
+on a tape at a different density than is already recorded on the tape.
+This message is written on the terminal of the user who tried to switch
+the density.
+.Pp
+.It te%d: hard error bn%d er=%b.
+A tape error occurred
+at block
+.Em bn ;
+the tm error register is
+printed in octal with the bits symbolically decoded.  Any error is
+fatal on non-raw tape; when possible the driver will have retried
+the operation which failed several times before reporting the error.
+.Pp
+.It te%d: lost interrupt.
+A tape operation did not complete
+within a reasonable time, most likely because the tape was taken
+off-line during rewind or lost vacuum.  The controller should, but does not,
+give an interrupt in these cases.  The device will be made available
+again after this message, but any current open reference to the device
+will return an error as the operation in progress aborts.
+.El
+.Sh SEE ALSO
+.Xr mt 1 ,
+.Xr tar 1 ,
+.Xr tp 1 ,
+.Xr mt 4 ,
+.Xr mtio 4 ,
+.Xr ht 4 ,
+.Xr ts 4 ,
+.Xr ut 4
+.Sh HISTORY
+A
+.Nm
+driver appeared in
+.At v6 .
+.Sh BUGS
+May hang if a physical (non-data) error occurs.
diff --git a/share/man/man4/man4.vax/tmscp.4 b/share/man/man4/man4.vax/tmscp.4
new file mode 100644
index 00000000000..b34af1b8648
--- /dev/null
+++ b/share/man/man4/man4.vax/tmscp.4
@@ -0,0 +1,132 @@
+.\" 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. 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: @(#)tmscp.4	6.2 (Berkeley) 3/27/91
+.\"	$Id: tmscp.4,v 1.1 1995/10/18 08:44:35 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt TMSCP 4 vax
+.Os BSD 4.3
+.Sh NAME
+.Nm tmscp
+.Nd
+.Tn DEC TMSCP
+magtape interface
+.Sh SYNOPSIS
+.Cd "controller tmscp0 at uba? csr 0174500 vector tmscpintr"
+.Cd "tape tms0 at tmscp0 drive 0"
+.Sh DESCRIPTION
+Tape controllers compatible with the
+.Tn DEC
+Tape Mass Storage Control Protocol
+.Pq Tn TMSCP
+architecture
+such as the
+.Tn TU81
+and the
+.Tn TK50
+provide a standard tape drive interface 
+as described in
+.Xr mtio 4 .
+The controller communicates with the host through a packet
+oriented protocol.
+Consult the file
+.Aq Pa vax/tmscp.h
+for a detailed 
+description of this protocol.
+.Sh DIAGNOSTICS
+.Bl -diag
+.It tmscp controller failed to init.
+The controller initialization procedure failed.
+This probably indicates a hardware problem.
+.Pp
+.It tmscp%d: sa 0%o, state %d.
+(Additional status information given after a hard
+.Tn I/O
+error.)
+The values of the controller status register and the internal
+driver state are printed.
+.Pp
+.It tmscp%d: random interrupt ignored.
+An unexpected interrupt was received (e.g. when no
+.Tn I/O
+was
+pending).  The interrupt is ignored.
+.Pp
+.It tmscp%d:  interrupt in unknown state %d ignored.
+An interrupt was received when the driver was in an unknown
+internal state.  Indicates a hardware problem or a driver bug.
+.Pp
+.It tmscp%d:  fatal error (0%o).
+The controller detected a ``fatal error'' in the status returned
+to the host.  The contents of the status register are displayed.
+.Pp
+.It OFFLINE.
+(Additional status information given after a hard
+.Tn I/O
+error.)
+A hard
+.Tn I/O
+error occurred because the drive was not on-line.
+.Pp
+.It tmscp%d: hard error
+.It tmscp%d: soft error.
+These errors precede an interpretation of a
+.Tn TMSCP
+error message
+returned by the controller to the host.
+.Tn TMSCP
+errors may be:
+.Pp
+.Bd -filled -offset indent -compact
+.It controller error, event 0%o.
+.It host memory access error, event 0%o, addr 0%o.
+.It tape transfer error, unit %d, grp 0x%x, event 0%o.
+.It STI error, unit %d, event 0%o.
+.It STI Drive Error Log, unit %d, event 0%o.
+.It STI Formatter Error Log, unit %d, event 0%o.
+.It unknown error, unit %d, format 0%o, event 0%o.
+.Ed
+.El
+.Sh SEE ALSO
+.Xr mt 1 ,
+.Xr tar 1 ,
+.Xr tp 1 ,
+.Xr mtio 4 ,
+.Xr tm 4 ,
+.Xr ts 4 ,
+.Xr ut 4 ,
+.Xr dmesg 8
+.Sh HISTORY
+The
+.Nm
+driver appeared in
+.Bx 4.3 .
diff --git a/share/man/man4/man4.vax/ts.4 b/share/man/man4/man4.vax/ts.4
new file mode 100644
index 00000000000..2cad0bfa519
--- /dev/null
+++ b/share/man/man4/man4.vax/ts.4
@@ -0,0 +1,110 @@
+.\" Copyright (c) 1980, 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: @(#)ts.4	6.2 (Berkeley) 3/27/91
+.\"	$Id: ts.4,v 1.1 1995/10/18 08:44:36 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt TS 4 vax
+.Os BSD 4
+.Sh NAME
+.Nm ts
+.Nd
+.Tn TS-11
+magtape interface
+.Sh SYNOPSIS
+.Cd "controller zs0 at uba? csr 0172520 vector tsintr"
+.Cd "tape ts0 at zs0 drive 0"
+.Sh DESCRIPTION
+The
+.Tn TS-11
+combination provides a standard tape drive
+interface as described in
+.Xr mtio 4 .
+The
+.Tn TS-11
+operates only at 1600
+.Tn BPI ,
+and only one transport
+is possible per controller.
+.Sh DIAGNOSTICS
+.Bl -diag
+.It ts%d: no write ring.
+An attempt was made to write on the tape drive
+when no write ring was present; this message is written on the terminal of
+the user who tried to access the tape.
+.Pp
+.It ts%d: not online.
+An attempt was made to access the tape while it
+was offline; this message is written on the terminal of the user
+who tried to access the tape.
+.Pp
+.It ts%d: hard error bn%d xs0=%b.
+A hard error occurred on the tape
+at block
+.Em bn ;
+status register 0 is printed in octal and symbolically
+decoded as bits.
+.El
+.Sh SEE ALSO
+.Xr mt 1 ,
+.Xr tar 1 ,
+.Xr tp 1 ,
+.Xr mtio 4 ,
+.Xr ht 4 ,
+.Xr tm 4 ,
+.Xr mt 4 ,
+.Xr ut 4
+.Sh HISTORY
+The
+.Nm
+driver appeared in
+.Bx 4.1 .
+.Sh BUGS
+May hang ungracefully if a physical error (non-data) occurs.
+.Pp
+The device lives at the same address as a
+.Tn TM-11
+.Pq Xr tm 4 ;
+as it is very difficult to get this device to interrupt, a generic
+system assumes that a
+.Nm ts
+is present whenever no
+.Tn TM-11
+exists but
+the
+.Tn CSR
+responds and a
+.Tn TS-11
+is configured.
+This does no harm as long as a non-existent
+.Tn TS-11
+is not accessed.
diff --git a/share/man/man4/man4.vax/tu.4 b/share/man/man4/man4.vax/tu.4
new file mode 100644
index 00000000000..c5bd721187f
--- /dev/null
+++ b/share/man/man4/man4.vax/tu.4
@@ -0,0 +1,166 @@
+.\" Copyright (c) 1980, 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: @(#)tu.4	6.2 (Berkeley) 3/27/91
+.\"	$Id: tu.4,v 1.1 1995/10/18 08:44:36 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt TU 4 vax
+.Os BSD 4
+.Sh NAME
+.Nm tu
+.Nd
+.Tn VAX-11/730
+and
+.Tn VAX-11/750
+.Tn TU58
+console cassette interface
+.Sh SYNOPSIS
+.Cd "options MRSP"
+(for
+.Tn VAX-11/750 Ns 's
+with an
+.Tn MRSP
+prom)
+.Sh DESCRIPTION
+The
+.Nm tu
+interface provides access to the
+.Tn VAX
+11/730 and 11/750
+.Tn TU58
+console
+cassette drive(s).  
+.Pp
+The interface supports only block
+.Tn I/O
+to the
+.Tn TU58
+cassettes.
+The devices are normally manipulated with the 
+.Xr arff 8
+program using the ``f'' and ``m'' options.
+.Pp
+The device driver is automatically included when a
+system is configured to run on an 11/730 or 11/750.
+.Pp
+The
+.Tn TU58
+on an 11/750 uses the Radial Serial Protocol
+.Pq Tn RSP
+to communicate with the cpu over a serial line.  This 
+protocol is inherently unreliable as it has no flow
+control measures built in.  On an 11/730 the Modified
+Radial Serial Protocol is used.  This protocol incorporates
+flow control measures which insure reliable data transfer
+between the cpu and the device.  Certain 11/750's have
+been modified to use the
+.Tn MRSP
+prom used in the 11/730.
+To reliably use the console
+.Tn TU58
+on an 11/750 under
+.Tn UNIX ,
+the
+.Tn MRSP
+prom is required.  For those 11/750's without
+an
+.Tn MRSP
+prom, an unreliable but often
+useable interface has been developed.
+This interface uses an assembly language ``pseudo-dma'' routine
+to minimize the receiver interrupt service latency.
+To include this code in
+the system, the configuration must
+.Em not
+specify the
+system will run on an 11/730 or use an
+.Tn MRSP
+prom.
+This unfortunately makes it impossible to configure a
+single system which will properly handle
+.Tn TU58 Ns 's
+on both an 11/750
+and an 11/730 (unless both machines have
+.Tn MRSP
+proms).
+.Sh FILES
+.Bl -tag -width /dev/tu0xx -compact
+.It Pa /dev/tu0
+.It Pa /dev/tu1
+(only on a
+.Tn VAX Ns \-11/730)
+.El
+.Sh DIAGNOSTICS
+.Bl -diag
+.It tu%d: no bp, active %d.
+A transmission complete interrupt was received with no outstanding
+.Tn I/O
+request.  This indicates a hardware problem.
+.Pp
+.It "tu%d protocol error, state=%s, op=%x, cnt=%d, block=%d."
+The driver entered an illegal state.  The information printed
+indicates the illegal state, operation currently being executed,
+the
+.Tn I/O
+count, and the block number on the cassette.
+.Pp
+.It "tu%d receive state error, state=%s, byte=%x."
+The driver entered an illegal state in the receiver finite
+state machine.  The state is shown along with the control
+byte of the received packet.
+.Pp
+.It tu%d: read stalled.
+A timer watching the controller detected no interrupt for
+an extended period while an operation was outstanding.
+This usually indicates that one or more receiver interrupts
+were lost and the transfer is restarted (11/750 only).
+.Pp
+.It tu%d: hard error bn%d, pk_mod %o.
+The device returned a status code indicating a hard error. The
+actual error code is shown in octal. No retries are attempted
+by the driver.
+.El
+.Sh SEE ALSO
+.Xr arff 8
+.Sh HISTORY
+The
+.Nm
+driver appeared in
+.Bx 4.1 .
+.Sh BUGS
+The
+.Tn VAX Ns \-11/750
+console interface without
+.Tn MRSP
+prom is unuseable
+while the system is multi-user; it should be used only with
+the system running single-user and, even then, with caution.
diff --git a/share/man/man4/man4.vax/uda.4 b/share/man/man4/man4.vax/uda.4
new file mode 100644
index 00000000000..a3960c3df78
--- /dev/null
+++ b/share/man/man4/man4.vax/uda.4
@@ -0,0 +1,616 @@
+.\" Copyright (c) 1980, 1987, 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: @(#)uda.4	6.6 (Berkeley) 3/27/91
+.\"	$Id: uda.4,v 1.1 1995/10/18 08:44:36 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt UDA 4 vax
+.Os BSD 4
+.Sh NAME
+.Nm uda
+.Nd
+.Tn UDA50
+disk controller interface
+.Sh SYNOPSIS
+.Cd "controller uda0 at uba0 csr 0172150 vector udaintr"
+.Cd "disk ra0 at uda0 drive 0"
+.Cd "options MSCP_PARANOIA"
+.Sh DESCRIPTION
+This is a driver for the
+.Tn DEC UDA50
+disk controller and other
+compatible controllers.  The
+.Tn UDA50
+communicates with the host through
+a packet protocol known as the Mass Storage Control Protocol
+.Pq Tn MSCP .
+Consult the file
+.Aq Pa vax/mscp.h
+for a detailed description of this protocol.
+.Pp
+The
+.Nm uda
+driver
+is a typical block-device disk driver; see
+.Xr physio 4
+for a description of block
+.Tn I/O .
+The script
+.Xr MAKEDEV 8
+should be used to create the
+.Nm uda
+special files; should a special
+file need to be created by hand, consult
+.Xr mknod 8 .
+.Pp
+The
+.Dv MSCP_PARANOIA
+option enables runtime checking on all transfer completion responses
+from the controller.  This increases disk
+.Tn I/O
+overhead and may
+be undesirable on slow machines, but is otherwise recommended.
+.Pp
+The first sector of each disk contains both a first-stage bootstrap program
+and a disk label containing geometry information and partition layouts (see
+.Xr disklabel 5 ) .
+This sector is normally write-protected, and disk-to-disk copies should
+avoid copying this sector.
+The label may be updated with
+.Xr disklabel 8 ,
+which can also be used to write-enable and write-disable the sector.
+The next 15 sectors contain a second-stage bootstrap program.
+.Sh DISK SUPPORT
+During autoconfiguration,
+as well as when a drive is opened after all partitions are closed,
+the first sector of the drive is examined for a disk label.
+If a label is found, the geometry of the drive and the partition tables
+are taken from it.
+If no label is found,
+the driver configures the type of each drive when it is first
+encountered.  A default partition table in the driver is used for each type
+of disk when a pack is not labelled.  The origin and size
+(in sectors) of the default pseudo-disks on each
+drive are shown below.  Not all partitions begin on cylinder
+boundaries, as on other drives, because previous drivers used one
+partition table for all drive types.  Variants of the partition tables
+are common; check the driver and the file
+.Pa /etc/disktab
+.Pq Xr disktab 5
+for other possibilities.
+.Pp
+Special file names begin with
+.Sq Li ra
+and
+.Sq Li rra
+for the block and character files respectively. The second
+component of the name, a drive unit number in the range of zero to
+seven, is represented by a
+.Sq Li ?
+in the disk layouts below. The last component of the name is the
+file system partition
+designated
+by a letter from
+.Sq Li a
+to
+.Sq Li h
+and which corresponds to a minor device number set: zero to seven,
+eight to 15, 16 to 23 and so forth for drive zero, drive two and drive
+three respectively, (see
+.Xr physio 4) .
+The location and size (in sectors) of the partitions:
+.Bl -column header diskx undefined length
+.Tn RA60 No partitions
+.Sy	disk	start	length
+	ra?a	0	15884
+	ra?b	15884	33440
+	ra?c	0	400176
+	ra?d	49324	82080	same as 4.2BSD ra?g
+	ra?e	131404	268772	same as 4.2BSD ra?h
+	ra?f	49324	350852
+	ra?g	242606	157570
+	ra?h	49324	193282
+
+.Tn RA70 No partitions
+.Sy	disk	start	length
+	ra?a	0	15884
+	ra?b	15972	33440
+	ra?c	0	547041
+	ra?d	34122	15884
+	ra?e	357192	55936
+	ra?f	413457	133584
+	ra?g	341220	205821
+	ra?h	49731	29136
+
+.Tn RA80 No partitions
+.Sy	disk	start	length
+	ra?a	0	15884
+	ra?b	15884	33440
+	ra?c	0	242606
+	ra?e	49324	193282	same as old Berkeley ra?g
+	ra?f	49324	82080	same as 4.2BSD ra?g
+	ra?g	49910	192696
+	ra?h	131404	111202	same as 4.2BSD
+
+.Tn RA81 No partitions
+.Sy	disk	start	length
+	ra?a	0	15884
+	ra?b	16422	66880
+	ra?c	0	891072
+	ra?d	375564	15884
+	ra?e	391986	307200
+	ra?f	699720	191352
+	ra?g	375564	515508
+	ra?h	83538	291346
+
+.Tn RA81 No partitions with 4.2BSD-compatible partitions
+.Sy	disk	start	length
+	ra?a	0	15884
+	ra?b	16422	66880
+	ra?c	0	891072
+	ra?d	49324	82080	same as 4.2BSD ra?g
+	ra?e	131404	759668	same as 4.2BSD ra?h
+	ra?f	412490	478582	same as 4.2BSD ra?f
+	ra?g	375564	515508
+	ra?h	83538	291346
+
+.Tn RA82 No partitions
+.Sy	disk	start	length
+	ra?a	0	15884
+	ra?b	16245	66880
+	ra?c	0	1135554
+	ra?d	375345	15884
+	ra?e	391590	307200
+	ra?f	669390	466164
+	ra?g	375345	760209
+	ra?h	83790	291346
+.El
+.Pp
+The ra?a partition is normally used for the root file system, the ra?b
+partition as a paging area, and the ra?c partition for pack-pack
+copying (it maps the entire disk).
+.Sh FILES
+.Bl -tag -width /dev/rra[0-9][a-f] -compact
+.It Pa /dev/ra[0-9][a-f]
+.It Pa /dev/rra[0-9][a-f]
+.El
+.Sh DIAGNOSTICS
+.Bl -diag
+.It "panic: udaslave"
+No command packets were available while the driver was looking
+for disk drives.  The controller is not extending enough credits
+to use the drives.
+.Pp
+.It "uda%d: no response to Get Unit Status request"
+A disk drive was found, but did not respond to a status request.
+This is either a hardware problem or someone pulling unit number
+plugs very fast.
+.Pp
+.It "uda%d: unit %d off line"
+While searching for drives, the controller found one that
+seems to be manually disabled.  It is ignored.
+.Pp
+.It "uda%d: unable to get unit status"
+Something went wrong while trying to determine the status of
+a disk drive.  This is followed by an error detail.
+.Pp
+.It uda%d: unit %d, next %d
+This probably never happens, but I wanted to know if it did.  I
+have no idea what one should do about it.
+.Pp
+.It "uda%d: cannot handle unit number %d (max is %d)"
+The controller found a drive whose unit number is too large.
+Valid unit numbers are those in the range [0..7].
+.Pp
+.It "ra%d: don't have a partition table for %s; using (s,t,c)=(%d,%d,%d)"
+The controller found a drive whose media identifier (e.g. `RA 25')
+does not have a default partition table.  A temporary partition
+table containing only an `a' partition has been created covering
+the entire disk, which has the indicated numbers of sectors per
+track (s), tracks per cylinder (t), and total cylinders (c).
+Give the pack a label with the
+.Xr disklabel
+utility.
+.Pp
+.It "uda%d: uballoc map failed"
+Unibus resource map allocation failed during initialisation.  This
+can only happen if you have 496 devices on a Unibus.
+.Pp
+.It uda%d: timeout during init
+The controller did not initialise within ten seconds.  A hardware
+problem, but it sometimes goes away if you try again.
+.Pp
+.It uda%d: init failed, sa=%b
+The controller refused to initalise.
+.Pp
+.It uda%d: controller hung
+The controller never finished initialisation.  Retrying may sometimes
+fix it.
+.Pp
+.It ra%d: drive will not come on line
+The drive will not come on line, probably because it is spun down.
+This should be preceded by a message giving details as to why the
+drive stayed off line.
+.Pp
+.It uda%d: still hung
+When the controller hangs, the driver occasionally tries to reinitialise
+it.  This means it just tried, without success.
+.Pp
+.It panic: udastart: bp==NULL
+A bug in the driver has put an empty drive queue on a controller queue.
+.Pp
+.It uda%d: command ring too small
+If you increase
+.Dv NCMDL2 ,
+you may see a performance improvement.
+(See
+.Pa /sys/vaxuba/uda.c . )
+.Pp
+.It panic: udastart
+A drive was found marked for status or on-line functions while performing
+status or on-line functions.  This indicates a bug in the driver.
+.Pp
+.It "uda%d: controller error, sa=0%o (%s)"
+The controller reported an error.  The error code is printed in
+octal, along with a short description if the code is known (see the
+.%T UDA50 Maintenance Guide ,
+.Tn DEC
+part number
+.Tn AA-M185B-TC ,
+pp. 18-22).
+If this occurs during normal
+operation, the driver will reset it and retry pending
+.Tn I/O .
+If
+it occurs during configuration, the controller may be ignored.
+.Pp
+.It uda%d: stray intr
+The controller interrupted when it should have stayed quiet.  The
+interrupt has been ignored.
+.Pp
+.It "uda%d: init step %d failed, sa=%b"
+The controller reported an error during the named initialisation step.
+The driver will retry initialisation later.
+.Pp
+.It uda%d: version %d model %d
+An informational message giving the revision level of the controller.
+.Pp
+.It uda%d: DMA burst size set to %d
+An informational message showing the
+.Tn DMA
+burst size, in words.
+.Pp
+.It panic: udaintr
+Indicates a bug in the generic
+.Tn MSCP
+code.
+.Pp
+.It uda%d: driver bug, state %d
+The driver has a bogus value for the controller state.  Something
+is quite wrong.  This is immediately followed by a `panic: udastate'.
+.Pp
+.It uda%d: purge bdp %d
+A benign message tracing BDP purges.  I have been trying to figure
+out what BDP purges are for.  You might want to comment out this
+call to log() in /sys/vaxuba/uda.c.
+.Pp
+.It uda%d: SETCTLRC failed:  `detail'
+The Set Controller Characteristics command (the last part of the
+controller initialisation sequence) failed.  The
+.Em detail
+message tells why.
+.Pp
+.It "uda%d: attempt to bring ra%d on line failed:  `detail'"
+The drive could not be brought on line.  The
+.Em detail
+message tells why.
+.Pp
+.It uda%d: ra%d: unknown type %d
+The type index of the named drive is not known to the driver, so the
+drive will be ignored.
+.Pp
+.It "ra%d: changed types! was %d now %d"
+A drive somehow changed from one kind to another, e.g., from an
+.Tn RA80
+to an
+.Tn RA60 .
+The numbers printed are the encoded media identifiers (see
+.Ao Pa vax/mscp.h Ac
+for the encoding).
+The driver believes the new type.
+.Pp
+.It "ra%d: uda%d, unit %d, size = %d sectors"
+The named drive is on the indicated controller as the given unit,
+and has that many sectors of user-file area.  This is printed
+during configuration.
+.Pp
+.It "uda%d: attempt to get status for ra%d failed:  `detail'"
+A status request failed.  The
+.Em detail
+message should tell why.
+.Pp
+.It ra%d: bad block report: %d
+The drive has reported the given block as bad.  If there are multiple
+bad blocks, the drive will report only the first; in this case this
+message will be followed by `+ others'.  Get
+.Tn DEC
+to forward the
+block with
+.Tn EVRLK .
+.Pp
+.It ra%d: serious exception reported
+I have no idea what this really means.
+.Pp
+.It panic: udareplace
+The controller reported completion of a
+.Tn REPLACE
+operation.  The
+driver never issues any
+.Tn REPLACE Ns s ,
+so something is wrong.
+.Pp
+.It panic: udabb
+The controller reported completion of bad block related
+.Tn I/O .
+The
+driver never issues any such, so something is wrong.
+.Pp
+.It uda%d: lost interrupt
+The controller has gone out to lunch, and is being reset to try to bring
+it back.
+.Pp
+.It panic: mscp_go: AEB_MAX_BP too small
+You defined
+.Dv AVOID_EMULEX_BUG
+and increased
+.Dv NCMDL2
+and Emulex has
+new firmware.  Raise
+.Dv AEB_MAX_BP
+or turn off
+.Dv AVOID_EMULEX_BUG .
+.Pp
+.It "uda%d: unit %d: unknown message type 0x%x ignored"
+The controller responded with a mysterious message type. See
+.Pa /sys/vax/mscp.h
+for a list of known message types.  This is probably
+a controller hardware problem.
+.Pp
+.It "uda%d: unit %d out of range"
+The disk drive unit number (the unit plug) is higher than the
+maximum number the driver allows (currently 7).
+.Pp
+.It "uda%d: unit %d not configured, message ignored"
+The named disk drive has announced its presence to the controller,
+but was not, or cannot now be, configured into the running system.
+.Em Message
+is one of `available attention' (an `I am here' message) or
+`stray response op 0x%x status 0x%x' (anything else).
+.Pp
+.It ra%d: bad lbn (%d)?
+The drive has reported an invalid command error, probably due to an
+invalid block number.  If the lbn value is very much greater than the
+size reported by the drive, this is the problem.  It is probably due to
+an improperly configured partition table.  Other invalid commands
+indicate a bug in the driver, or hardware trouble.
+.Pp
+.It ra%d: duplicate ONLINE ignored
+The drive has come on-line while already on-line.  This condition
+can probably be ignored (and has been).
+.Pp
+.It ra%d: io done, but no buffer?
+Hardware trouble, or a bug; the drive has finished an
+.Tn I/O
+request,
+but the response has an invalid (zero) command reference number.
+.Pp
+.It "Emulex SC41/MS screwup: uda%d, got %d correct, then changed 0x%x to 0x%x"
+You turned on
+.Dv AVOID_EMULEX_BUG ,
+and the driver successfully
+avoided the bug.  The number of correctly-handled requests is
+reported, along with the expected and actual values relating to
+the bug being avoided.
+.Pp
+.It panic: unrecoverable Emulex screwup
+You turned on
+.Dv AVOID_EMULEX_BUG ,
+but Emulex was too clever and
+avoided the avoidance.  Try turning on
+.Dv MSCP_PARANOIA
+instead.
+.Pp
+.It uda%d: bad response packet ignored
+You turned on
+.Dv MSCP_PARANOIA ,
+and the driver caught the controller in
+a lie.  The lie has been ignored, and the controller will soon be
+reset (after a `lost' interrupt).  This is followed by a hex dump of
+the offending packet.
+.Pp
+.It ra%d: bogus REPLACE end
+The drive has reported finishing a bad sector replacement, but the
+driver never issues bad sector replacement commands.  The report
+is ignored.  This is likely a hardware problem.
+.Pp
+.It "ra%d: unknown opcode 0x%x status 0x%x ignored"
+The drive has reported something that the driver cannot understand.
+Perhaps
+.Tn DEC
+has been inventive, or perhaps your hardware is ill.
+This is followed by a hex dump of the offending packet.
+.Pp
+.It "ra%d%c: hard error %sing fsbn %d [of %d-%d] (ra%d bn %d cn %d tn %d sn %d)."
+An unrecoverable error occurred during transfer of the specified
+filesystem block number(s),
+which are logical block numbers on the indicated partition.
+If the transfer involved multiple blocks, the block range is printed as well.
+The parenthesized fields list the actual disk sector number
+relative to the beginning of the drive,
+as well as the cylinder, track and sector number of the block.
+.Pp
+.It uda%d: %s error datagram
+The controller has reported some kind of error, either `hard'
+(unrecoverable) or `soft' (recoverable).  If the controller is going on
+(attempting to fix the problem), this message includes the remark
+`(continuing)'.  Emulex controllers wrongly claim that all soft errors
+are hard errors.  This message may be followed by
+one of the following 5 messages, depending on its type, and will always
+be followed by a failure detail message (also listed below).
+.Bd -filled -offset indent
+.It memory addr 0x%x
+A host memory access error; this is the address that could not be
+read.
+.Pp
+.It "unit %d: level %d retry %d, %s %d"
+A typical disk error; the retry count and error recovery levels are
+printed, along with the block type (`lbn', or logical block; or `rbn',
+or replacement block) and number.  If the string is something else,
+.Tn DEC
+has been clever, or your hardware has gone to Australia for vacation
+(unless you live there; then it might be in New Zealand, or Brazil).
+.Pp
+.It unit %d: %s %d
+Also a disk error, but an `SDI' error, whatever that is.  (I doubt
+it has anything to do with Ronald Reagan.)  This lists the block
+type (`lbn' or `rbn') and number.  This is followed by a second
+message indicating a microprocessor error code and a front panel
+code.  These latter codes are drive-specific, and are intended to
+be used by field service as an aid in locating failing hardware.
+The codes for RA81s can be found in the
+.%T RA81 Maintenance Guide ,
+DEC order number AA-M879A-TC, in appendices E and F.
+.Pp
+.It "unit %d: small disk error, cyl %d"
+Yet another kind of disk error, but for small disks.  (`That's what
+it says, guv'nor.  Dunnask me what it means.')
+.Pp
+.It "unit %d: unknown error, format 0x%x"
+A mysterious error: the given format code is not known.
+.Ed
+.Pp
+The detail messages are as follows:
+.Bd -filled -offset indent
+.It success (%s) (code 0, subcode %d)
+Everything worked, but the controller thought it would let you know
+that something went wrong.  No matter what subcode, this can probably
+be ignored.
+.Pp
+.It "invalid command (%s) (code 1, subcode %d)"
+This probably cannot occur unless the hardware is out; %s should be
+`invalid msg length', meaning some command was too short or too long.
+.Pp
+.It "command aborted (unknown subcode) (code 2, subcode %d)"
+This should never occur, as the driver never aborts commands.
+.Pp
+.It "unit offline (%s) (code 3, subcode %d)"
+The drive is offline, either because it is not around (`unknown
+drive'), stopped (`not mounted'), out of order (`inoperative'), has the
+same unit number as some other drive (`duplicate'), or has been
+disabled for diagnostics (`in diagnosis').
+.Pp
+.It "unit available (unknown subcode) (code 4, subcode %d)"
+The controller has decided to report a perfectly normal event as
+an error.  (Why?)
+.Pp
+.It "media format error (%s) (code 5, subcode %d)"
+The drive cannot be used without reformatting.  The Format Control
+Table cannot be read (`fct unread - edc'), there is a bad sector
+header (`invalid sector header'), the drive is not set for 512-byte
+sectors (`not 512 sectors'), the drive is not formatted (`not formatted'),
+or the
+.Tn FCT
+has an uncorrectable
+.Tn ECC
+error (`fct ecc').
+.Pp
+.It "write protected (%s) (code 6, subcode %d)"
+The drive is write protected, either by the front panel switch
+(`hardware') or via the driver (`software').  The driver never
+sets software write protect.
+.Pp
+.It "compare error (unknown subcode) (code 7, subcode %d)"
+A compare operation showed some sort of difference.  The driver
+never uses compare operations.
+.Pp
+.It "data error (%s) (code 7, subcode %d)"
+Something went wrong reading or writing a data sector.  A `forced
+error' is a software-asserted error used to mark a sector that contains
+suspect data.  Rewriting the sector will clear the forced error.  This
+is normally set only during bad block replacment, and the driver does
+no bad block replacement, so these should not occur.  A `header
+compare' error probably means the block is shot.  A `sync timeout'
+presumably has something to do with sector synchronisation.
+An `uncorrectable ecc' error is an ordinary data error that cannot
+be fixed via
+.Tn ECC
+logic.  A `%d symbol ecc' error is a data error
+that can be (and presumably has been) corrected by the
+.Tn ECC
+logic.
+It might indicate a sector that is imperfect but usable, or that
+is starting to go bad.  If any of these errors recur, the sector
+may need to be replaced.
+.Pp
+.It "host buffer access error (%s) (code %d, subcode %d)"
+Something went wrong while trying to copy data to or from the host
+(Vax).  The subcode is one of `odd xfer addr', `odd xfer count',
+`non-exist. memory', or `memory parity'.  The first two could be a
+software glitch; the last two indicate hardware problems.
+.It controller error (%s) (code %d, subcode %d)
+The controller has detected a hardware error in itself.  A
+`serdes overrun' is a serialiser / deserialiser overrun; `edc'
+probably stands for `error detection code'; and `inconsistent
+internal data struct' is obvious.
+.Pp
+.It "drive error (%s) (code %d, subcode %d)"
+Either the controller or the drive has detected a hardware error
+in the drive.  I am not sure what an `sdi command timeout' is, but
+these seem to occur benignly on occasion.  A `ctlr detected protocol'
+error means that the controller and drive do not agree on a protocol;
+this could be a cabling problem, or a version mismatch.  A `positioner'
+error means the drive seek hardware is ailing; `lost rd/wr ready'
+means the drive read/write logic is sick; and `drive clock dropout'
+means that the drive clock logic is bad, or the media is hopelessly
+scrambled.  I have no idea what `lost recvr ready' means.  A `drive 
+detected error' is a catch-all for drive hardware trouble; `ctlr
+detected pulse or parity' errors are often caused by cabling problems.
+.Ed
+.El
+.Sh SEE ALSO
+.Xr disklabel 5 ,
+.Xr disklabel 8
+.Sh HISTORY
+The
+.Nm
+driver appeared in
+.Bx 4.2 .
diff --git a/share/man/man4/man4.vax/up.4 b/share/man/man4/man4.vax/up.4
new file mode 100644
index 00000000000..f68b4f43369
--- /dev/null
+++ b/share/man/man4/man4.vax/up.4
@@ -0,0 +1,258 @@
+.\" Copyright (c) 1980,1988, 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: @(#)up.4	6.4 (Berkeley) 3/27/91
+.\"	$Id: up.4,v 1.1 1995/10/18 08:44:36 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt UP 4 vax
+.Os BSD 4
+.Sh NAME
+.Nm up
+.Nd unibus storage module controller/drives
+.Sh SYNOPSIS
+.Cd "controller sc0 at uba? csr 0176700 vector upintr
+.Cd "disk up0 at sc0 drive 0"
+.Sh DESCRIPTION
+This is a generic
+.Tn UNIBUS
+storage module disk driver.
+It is specifically designed to work with the
+Emulex
+.Tn SC-21
+and
+.Tn SC-31
+controllers.
+It can be easily
+adapted to other controllers (although bootstrapping will
+not necessarily be directly possible.) 
+.Pp
+The script
+.Xr MAKEDEV 8
+should be used to create the
+.Nm up
+special files; consult
+.Xr mknod 8
+if a special file needs to be made manually.
+It is recommended as a security precaution to not create special files
+for devices which may never be installed.
+.Sh DISK SUPPORT
+The driver interrogates the controller's holding register
+to determine the type of drive attached.  The driver recognizes
+seven different drives:
+.Tn CDC
+9762,
+.Tn CDC
+9766,
+.Tn AMPEX DM Ns 980 ,
+.Tn AMPEX
+9300,
+.Tn AMPEX
+Capricorn,
+.Tn FUJITSU
+160, and
+.Tn FUJITSU
+Eagle
+(the Eagle is not supported by the SC-21).
+.Pp
+Special file names begin with
+.Sq Li up
+and
+.Sq Li rup
+for the block and character files respectively. The second
+component of the name, a drive unit number in the range of zero to
+seven, is represented by a
+.Sq Li ?
+in the disk layouts below. The last component of the name, the
+file system partition, is
+designated by a letter from
+.Sq Li a
+to
+.Sq Li h
+which also corresponds to a minor device number set: zero to seven,
+eight to 15, 16 to 23 and so forth for drive zero, drive two and drive
+three respectively (see
+.Xr physio 4 ) .
+The location and size (in 512 byte sectors) of the
+partitions for the above drives:
+.Bl -column header diskx undefined length
+.Tn CDC No 9762 partitions
+.Sy	disk	start	length	cyls
+	hp?a	0	15884	0-99
+	hp?b	16000	33440	100-309
+	hp?c	0	131680	0-822
+	hp?d	49600	15884	309-408
+	hp?e	65440	55936	409-758
+	hp?f	121440	10080	759-822
+	hp?g	49600	82080	309-822
+
+.Tn CDC No 9766 300M drive partitions:
+.Sy	disk	start	length	cyl
+	up?a	0	15884	0-26
+	up?b	16416	33440	27-81
+	up?c	0	500384	0-822
+	up?d	341696	15884	562-588
+	up?e	358112	55936	589-680
+	up?f	414048	861760	681-822
+	up?g	341696	158528	562-822
+	up?h	49856	291346	82-561
+
+.Tn AMPEX DM Ns No 980 partitions
+.Sy	disk	start	length	cyls
+	hp?a	0	15884	0-99
+	hp?b	16000	33440	100-309
+	hp?c	0	131680	0-822
+	hp?d	49600	15884	309-408
+	hp?e	65440	55936	409-758
+	hp?f	121440	10080	759-822
+	hp?g	49600	82080	309-822
+
+.Tn AMPEX No 9300 300M drive partitions:
+.Sy	disk	start	length	cyl
+	up?a	0	15884	0-26
+	up?b	16416	33440	27-81
+	up?c	0	495520	0-814
+	up?d	341696	15884	562-588
+	up?e	358112	55936	589-680
+	up?f	414048	81312	681-814
+	up?g	341696	153664	562-814
+	up?h	49856	291346	82-561
+
+.Tn AMPEX No Capricorn 330M drive partitions:
+.Sy	disk	start	length	cyl
+	hp?a	0	15884	0-31
+	hp?b	16384	33440	32-97
+	hp?c	0	524288	0-1023
+	hp?d	342016	15884	668-699
+	hp?e	358400	55936	700-809
+	hp?f	414720	109408	810-1023
+	hp?g	342016	182112	668-1023
+	hp?h	50176	291346	98-667
+
+.Tn FUJITSU No 160M drive partitions:
+.Sy	disk	start	length	cyl
+	up?a	0	15884	0-49
+	up?b	16000	33440	50-154
+	up?c	0	263360	0-822
+	up?d	49600	15884	155-204
+	up?e	65600	55936	205-379
+	up?f	121600	141600	380-822
+	up?g	49600	213600	155-822
+
+.Tn FUJITSU No Eagle partitions
+.Sy	disk	start	length	cyls
+	hp?a	0	15884	0-16
+	hp?b	16320	66880	17-86
+	hp?c	0	808320	0-841
+	hp?d	375360	15884	391-407
+	hp?e	391680	55936	408-727
+	hp?f	698880	109248	728-841
+	hp?g	375360	432768	391-841
+	hp?h	83520	291346	87-390
+.El
+.Pp
+The up?a partition is normally used for the root file system,
+the up?b partition as a paging area,
+and the up?c partition for pack-pack copying (it maps the entire disk).
+On 160M drives the up?g partition maps the rest of the pack.
+On other drives both up?g and up?h are used to map the
+remaining cylinders.
+.Sh FILES
+.Bl -tag -width Pa -compact
+.It Pa /dev/up[0-7][a-h]
+block files
+.It Pa /dev/rup[0-7][a-h]
+raw files
+.El
+.Sh DIAGNOSTICS
+.Bl -diag
+.It "up%d%c: hard error %sing fsbn %d[-%d] cs2=%b er1=%b er2=%b."
+An unrecoverable error occurred during transfer of the specified
+filesystem block number(s),
+which are logical block numbers on the indicated partition.
+The contents of the cs2, er1 and er2 registers are printed
+in octal and symbolically with bits decoded.
+The error was either unrecoverable, or a large number of retry attempts
+(including offset positioning and drive recalibration) could not
+recover the error.
+.Pp
+.It "up%d: write locked."
+The write protect switch was set on the drive
+when a write was attempted.  The write operation is not recoverable.
+.Pp
+.It "up%d: not ready."
+The drive was spun down or off line when it was
+accessed.  The i/o operation is not recoverable.
+.Pp
+.It "up%d: not ready (flakey)."
+The drive was not ready, but after
+printing the message about being not ready (which takes a fraction
+of a second) was ready.  The operation is recovered if no further
+errors occur.
+.Pp
+.It "up%d%c: soft ecc reading fsbn %d[-%d]."
+A recoverable ECC error occurred on the
+specified sector of the specified disk partition.
+This happens normally
+a few times a week.  If it happens more frequently than
+this the sectors where the errors are occurring should be checked to see
+if certain cylinders on the pack, spots on the carriage of the drive
+or heads are indicated.
+.Pp
+.It "sc%d: lost interrupt."
+A timer watching the controller detecting
+no interrupt for an extended period while an operation was outstanding.
+This indicates a hardware or software failure.  There is currently a
+hardware/software problem with spinning down drives while they are
+being accessed which causes this error to occur.
+The error causes a
+.Tn UNIBUS
+reset, and retry of the pending operations.
+If the controller continues to lose interrupts, this error will recur
+a few seconds later.
+.El
+.Sh SEE ALSO
+.Xr hk 4 ,
+.Xr hp 4 ,
+.Xr uda 4
+.Sh HISTORY
+The
+.Nm up
+driver appeared in
+.Bx 4.0 .
+.Sh BUGS
+.Pp
+A program to analyze the logged error information (even in its
+present reduced form) is needed.
+.Pp
+The partition tables for the file systems should be read off of each
+pack, as they are never quite what any single installation would prefer,
+and this would make packs more portable.
diff --git a/share/man/man4/man4.vax/ut.4 b/share/man/man4/man4.vax/ut.4
new file mode 100644
index 00000000000..e59f8325b5c
--- /dev/null
+++ b/share/man/man4/man4.vax/ut.4
@@ -0,0 +1,108 @@
+.\" 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. 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: @(#)ut.4	6.2 (Berkeley) 3/27/91
+.\"	$Id: ut.4,v 1.1 1995/10/18 08:44:36 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt UT 4 vax
+.Os BSD 4.2
+.Sh NAME
+.Nm ut
+.Nd
+.Tn UNIBUS TU45
+tri-density tape drive interface
+.Sh SYNOPSIS
+.Cd "controller ut0 at uba0 csr 0172440 vector utintr"
+.Cd "tape tj0 at ut0 drive 0"
+.Sh DESCRIPTION
+The 
+.Nm ut
+interface provides access to a standard tape drive interface as
+describe in 
+.Xr mtio 4 .
+Hardware implementing this on the
+.Tn VAX
+is typified by the System
+Industries
+.Tn SI
+9700 tape subsystem.  Tapes may be read or written
+at 800, 1600, and 6250
+.Tn BPI .
+.Sh DIAGNOSTICS
+.Bl -diag
+.It tj%d: no write ring.
+An attempt was made to write on the tape drive
+when no write ring was present; this message is written on the terminal of
+the user who tried to access the tape.
+.Pp
+.It tj%d: not online.
+An attempt was made to access the tape while it
+was offline; this message is written on the terminal of the user
+who tried to access the tape.
+.Pp
+.It tj%d: can't change density in mid-tape.
+An attempt was made to write
+on a tape at a different density than is already recorded on the tape.
+This message is written on the terminal of the user who tried to switch
+the density.
+.Pp
+.It "ut%d: soft error bn%d cs1=%b er=%b cs2=%b ds=%b."
+The formatter indicated a corrected error at a density other
+than 800bpi.  The data transferred is assumed to be correct.
+.Pp
+.It "ut%d: hard error bn%d cs1=%b er=%b cs2=%b ds=%b."
+A tape error occurred
+at block
+.Pp
+.It bn.
+Any error is
+fatal on non-raw tape; when possible the driver will have retried
+the operation which failed several times before reporting the error.
+.Pp
+.It tj%d: lost interrupt.
+A tape operation did not complete
+within a reasonable time, most likely because the tape was taken
+off-line during rewind or lost vacuum.  The controller should, but does not,
+give an interrupt in these cases.  The device will be made available
+again after this message, but any current open reference to the device
+will return an error as the operation in progress aborts.
+.El
+.Sh SEE ALSO
+.Xr mt 1 ,
+.Xr mtio 4
+.Sh HISTORY
+The
+.Nm
+driver appeared in
+.Bx 4.2 .
+.Sh BUGS
+May hang if a physical error (non-data) occurs.
diff --git a/share/man/man4/man4.vax/uu.4 b/share/man/man4/man4.vax/uu.4
new file mode 100644
index 00000000000..48bcfee570d
--- /dev/null
+++ b/share/man/man4/man4.vax/uu.4
@@ -0,0 +1,157 @@
+.\" 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. 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: @(#)uu.4	6.2 (Berkeley) 3/27/91
+.\"	$Id: uu.4,v 1.1 1995/10/18 08:44:36 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt UU 4 vax
+.Os BSD 4.2
+.Sh NAME
+.Nm uu
+.Nd
+.Tn TU58 Ns / Tn DECtape II UNIBUS
+cassette interface 
+.Sh SYNOPSIS
+.Cd "options UUDMA"
+.Cd "device uu0 at uba0 csr 0176500 vector uurintr uuxintr"
+.Sh DESCRIPTION
+The
+.Nm uu
+device provides access to dual
+.Tn DEC
+.Tn TU58
+tape cartridge drives
+connected to the
+.Tn UNIBUS
+via a
+.Tn DL11-W
+interface module.
+.Pp
+The interface supports only block
+.Tn I/O
+to the
+.Tn TU58
+cassettes (see
+.Xr physio 4 ) .
+The drives are normally manipulated with the
+.Xr arff 8
+program using the ``m'' and ``f'' options.
+.Pp
+The driver provides for an optional write and verify 
+(read after write) mode that is activated by specifying the
+``a'' device.
+.Pp
+The
+.Tn TU58
+is treated as a single device by the system even
+though it has two separate drives,
+.Sq Li uu0
+and
+.Sq Li uu1 .
+If there is 
+more than one
+.Tn TU58
+unit on a system, the extra drives
+are named
+.Sq Li uu2 ,
+.Sq Li uu3
+etc.
+.Sh NOTES
+Assembly language code to assist the driver in handling
+the receipt of data (using a pseudo-dma approach) should
+be included when using this driver; specify
+.Sq Li options UUDMA
+in the configuration file.
+.Sh FILES
+.Bl -tag -width /dev/uu?a -compact
+.It Pa /dev/uu?
+.It Pa /dev/uu?a
+.El
+.Sh DIAGNOSTICS
+.Bl -diag
+.It uu%d: no bp, active %d.
+A transmission complete interrupt was received with no outstanding
+.Tn I/O
+request. This indicates a hardware problem.
+.Pp
+.It uu%d protocol error, state=%s, op=%x, cnt=%d, block=%d.
+The driver entered an illegal state.  The information printed
+indicates the illegal state, the 
+operation currently being executed,
+the
+.Tn I/O
+count, and the block number on the cassette.
+.Pp
+.It uu%d: break received, transfer restarted.
+The
+.Tn TU58
+was sending a continuous break signal and had
+to be reset. This may indicate a hardware problem, but
+the driver will attempt to recover from the error.
+.Pp
+.It uu%d receive state error, state=%s, byte=%x.
+The driver entered an illegal state in the receiver finite
+state machine.  The state is shown along with the control
+byte of the received packet.
+.Pp
+.It uu%d: read stalled.
+A timer watching the controller detected no interrupt for
+an extended period while an operation was outstanding.
+This usually indicates that one or more receiver interrupts
+were lost and the transfer is restarted.
+.Pp
+.It uu%d: hard error bn%d, pk_mod %o.
+The device returned a status code indicating a hard error. The
+actual error code is shown in octal. No retries are attempted
+by the driver.
+.El
+.Sh ERRORS
+The following errors may be returned:
+.Bl -tag -width [ENXIO]
+.It Bq Er ENXIO
+Nonexistent drive (on open); 
+offset is too large or bad (undefined)
+.Xr ioctl 2
+code.
+.It Bq Er EIO
+Open failed, the device could not be reset.
+.It Bq Er EBUSY
+Drive in use.
+.El
+.Sh SEE ALSO
+.Xr tu 4 ,
+.Xr arff 8
+.Sh HISTORY
+The
+.Nm
+driver appeared in
+.Bx 4.2 .
diff --git a/share/man/man4/man4.vax/va.4 b/share/man/man4/man4.vax/va.4
new file mode 100644
index 00000000000..b064e4238c8
--- /dev/null
+++ b/share/man/man4/man4.vax/va.4
@@ -0,0 +1,174 @@
+.\" Copyright (c) 1980, 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: @(#)va.4	6.3 (Berkeley) 3/27/91
+.\"	$Id: va.4,v 1.1 1995/10/18 08:44:36 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt VA 4 vax
+.Os BSD 4
+.Sh NAME
+.Nm va
+.Nd Benson-Varian interface
+.Sh SYNOPSIS
+.Cd "controller va0 at uba0 csr 0164000 vector vaintr"
+.Cd "disk vz0 at va0 drive 0"
+.Sh DESCRIPTION
+.Bf -symbolic
+(NOTE: the configuration description, while counter-intuitive,
+is actually as shown above.)
+.Ef
+.Pp
+The Benson-Varian printer/plotter in normally used with the line printer
+system.
+This description is designed for those who wish to drive the Benson-Varian
+directly.
+.Pp
+In print mode, the Benson-Varian uses a modified
+.Tn ASCII
+character set.
+Most control characters print various non-
+.Tn ASCII
+graphics such as daggers,
+sigmas, copyright symbols, etc.
+Only
+.Tn LF
+and
+.Tn FF
+are used as format effectors.
+.Tn LF
+acts as a newline,
+advancing to the beginning of the next line, and
+.Tn FF
+advances to the top of
+the next page.
+.Pp
+In plot mode, the Benson-Varian prints one raster line at a time.
+An entire raster line of bits (2112 bits = 264 bytes) is sent, and
+then the Benson-Varian advances to the next raster line.
+.Pp
+.Em Note :
+The Benson-Varian must be sent an even number of bytes.
+If an odd number is sent, the last byte will be lost.
+Nulls can be used in print mode to pad to an even number of bytes.
+.Pp
+To use the Benson-Varian yourself,
+you must realize that you cannot open the device,
+.Pa /dev/va0
+if there is an daemon active.
+You can see if there is an active daemon by doing a
+.Xr lpq 1
+and seeing if there are any files being printed.
+Printing should be turned off using
+.Xr lpc 8 .
+.Pp
+To set the Benson-Varian into plot mode include the file
+.Aq Pa sys/vcmd.h
+and use the following
+.Xr ioctl 2
+call
+.Bd -literal -offset indent
+ioctl(fileno(va), VSETSTATE, plotmd);
+.Ed
+.Pp
+where
+.Ar plotmd
+is defined to be
+.Bd -literal -offset indent
+int plotmd[] = { VPLOT, 0, 0 };
+.Ed
+.Pp
+and
+.Ar va
+is the result of a call to
+.Xr fopen
+on stdio.
+When you finish using the Benson-Varian in plot mode you should advance to
+a new page
+by sending it a
+.Tn FF
+after putting it back into print mode, i.e. by
+.Bd -literal -offset indent
+int prtmd[] = { VPRINT, 0, 0 };
+\&...
+fflush(va);
+ioctl(fileno(va), VSETSTATE, prtmd);
+write(fileno(va), "\ef\e0", 2);
+.Ed
+.Sh FILES
+.Bl -tag -width /dev/va0xx -compact
+.It Pa /dev/va0
+.El
+.Sh DIAGNOSTICS
+The following error numbers are significant at the
+time the device is opened.
+.Bl -tag -width ENXIOxx
+.It Bq Er ENXIO
+The device is already in use.
+.It Bq Er EIO
+The device is offline.
+.El
+.Pp
+The following message may be printed on the console.
+.Pp
+.Bl -diag
+.It va%d: npr timeout.
+The device was not able to get data from
+the
+.Tn UNIBUS
+within the timeout period, most likely because some other
+device was hogging the bus.  (But see
+.Sx BUGS
+below).
+.El
+.Sh SEE ALSO
+.Xr vfont 5 ,
+.Xr lpr 1 ,
+.Xr lpd 8 ,
+.Xr vp 4
+.Sh HISTORY
+The
+.Nm
+driver appeared in
+.Bx 4.0 .
+.Sh BUGS
+The 1's (one's) and l's (lower-case el's) in the Benson-Varian's
+standard character set look very similar; caution is advised.
+.Pp
+The interface hardware is rumored to have problems which can
+play havoc with the
+.Tn UNIBUS .
+We have intermittent minor problems on the
+.Tn UNIBUS
+where our
+.Xr va
+lives, but haven't ever been able to pin them down
+completely.
diff --git a/share/man/man4/man4.vax/vp.4 b/share/man/man4/man4.vax/vp.4
new file mode 100644
index 00000000000..01b924cdd34
--- /dev/null
+++ b/share/man/man4/man4.vax/vp.4
@@ -0,0 +1,122 @@
+.\" Copyright (c) 1980, 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: @(#)vp.4	6.3 (Berkeley) 3/27/91
+.\"	$Id: vp.4,v 1.1 1995/10/18 08:44:36 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt VP 4 vax
+.Os BSD 4
+.Sh NAME
+.Nm vp
+.Nd Versatec interface
+.Sh SYNOPSIS
+.Cd "device vp0 at uba0 csr 0177510 vector vpintr vpintr"
+.Sh DESCRIPTION
+The Versatec printer/plotter is normally used with the
+line printer system.
+This description is designed for those who wish to drive the Versatec directly.
+.Pp
+To use the Versatec yourself, you must realize that you cannot open the
+device,
+.Pa /dev/vp0
+if there is a daemon active.
+You can see if there is a daemon active by doing a
+.Xr lpq 1 ,
+and seeing if there are any files being sent.
+Printing should be turned off using
+.Xr lpc 8 .
+.Pp
+To set the Versatec into plot mode you should include
+.Aq Pa sys/vcmd.h
+and use the
+.Xr ioctl 2
+call
+.Bd -literal -offset indent
+ioctl(fileno(vp), VSETSTATE, plotmd);
+.Ed
+.Pp
+where
+.Em plotmd
+is defined to be
+.Bd -literal -offset indent
+int plotmd[] = { VPLOT, 0, 0 };
+.Ed
+.Pp
+and
+.Em vp
+is the result of a call to
+.Xr fopen
+on stdio.
+When you finish using the Versatec in plot mode you should eject paper
+by sending it a
+.Tn EOT
+after putting it back into print mode, i.e. by
+.Bd -literal -offset indent
+int prtmd[] = { VPRINT, 0, 0 };
+\&...
+fflush(vp);
+ioctl(fileno(vp), VSETSTATE, prtmd);
+write(fileno(vp), "\e04", 1);
+.Ed
+.Sh FILES
+.Bl -tag -width /dev/vp0xx -compact
+.It Pa /dev/vp0
+.El
+.Sh DIAGNOSTICS
+The following error numbers are significant at the
+time the device is opened.
+.Bl -tag -width [ENXIO]
+.It Bq Er ENXIO
+The device is already in use.
+.It Bq Er EIO
+The device is offline.
+.El
+.Sh SEE ALSO
+.Xr lpr 1 ,
+.Xr vtroff 1 ,
+.Xr va 4
+.Xr font 5 ,
+.Xr lpd 8 ,
+.Sh HISTORY
+A
+.Nm
+driver appeared in
+.At v7 .
+.Sh BUGS
+The configuration part of the driver assumes that the device is set up to
+vector print mode through 0174 and plot mode through 0200.
+As the configuration program can't be sure
+which vector interrupted at boot time,
+we specify that it has two interrupt vectors,
+and if an interrupt comes through 0200 it is reset to 0174.
+This is safe for devices with one or two vectors at these two addresses.
+Other configurations with 2 vectors may require changes in the driver.
diff --git a/share/man/man4/man4.vax/vv.4 b/share/man/man4/man4.vax/vv.4
new file mode 100644
index 00000000000..fdd271ad2c4
--- /dev/null
+++ b/share/man/man4/man4.vax/vv.4
@@ -0,0 +1,140 @@
+.\" Copyright (c) 1983, 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: @(#)vv.4	6.5 (Berkeley) 3/27/91
+.\"	$Id: vv.4,v 1.1 1995/10/18 08:44:36 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt VV 4 vax
+.Os BSD 4.2
+.Sh NAME
+.Nm vv
+.Nd Proteon proNET 10 Megabit ring
+.Sh SYNOPSIS
+.Cd "device vv0 at uba0 csr 0161000 vector vvrint vvxint"
+.Sh DESCRIPTION
+The
+.Nm vv
+interface provides access to a 10 Mb/s Proteon
+.Tn proNET
+ring network.
+.Pp
+The network address of the interface must be specified with an
+an
+.Dv SIOCSIFADDR
+.Xr ioctl 2
+before data can be transmitted or received.
+It is only permissible to change the network address while the
+interface is marked
+.Dq down .
+.Pp
+The host's hardware address is discovered by putting the interface in
+digital loopback mode (not joining the ring) and sending a broadcast
+packet from which the hardware address is extracted.
+.Pp
+Transmit timeouts are detected through use of a watchdog routine.
+Lost input interrupts are checked for when packets are sent out.
+.Pp
+If the installation is running
+.Tn CTL
+boards which use the old broadcast
+address of
+.Ql 0
+instead of the new address of
+.Ql 0xff ,
+the define
+.Dv OLD_BROADCAST
+should be specified in the driver.
+.Pp
+The driver can use
+.Dq trailer
+encapsulation to minimize copying
+data on input and output.
+This may be disabled, on a per-interface basis,
+by setting the
+.Dv IFF_NOTRAILERS
+flag with an
+.Dv SIOCSIFFLAGS 
+.Xr ioctl .
+.Sh DIAGNOSTICS
+.Bl -diag
+.It vv%d: host %d.
+The software announces the host
+address discovered during autoconfiguration.
+.Pp
+.It vv%d: can't initialize.
+The software was unable to
+discover the address of this interface, so it deemed
+"dead" will not be enabled.
+.Pp
+.It vv%d: error vvocsr=%b.
+The hardware indicated an error on
+the previous transmission.
+.Pp
+.It vv%d: output timeout.
+The token timer has fired and the
+token will be recreated.
+.Pp
+.It vv%d: error vvicsr=%b.
+The hardware indicated an error
+in reading a packet off the ring.
+.Pp
+.It en%d: can't handle af%d.
+The interface was handed
+a message with addresses formatted in an unsuitable address
+family; the packet was dropped.
+.Pp
+.It vv%d: vs_olen=%d.
+The ring output routine has been
+handed a message with a preposterous length.  This results in
+an immediate 
+.Em panic: vs_olen .
+.El
+.Sh SEE ALSO
+.Xr netintro 4 ,
+.Xr inet 4
+.Sh HISTORY
+The
+.Nm
+driver appeared in
+.Bx 4.2 .
+.Sh BUGS
+The encapsulation of trailer packets in the
+.Bx 4.2
+version of this driver
+was incorrect (the packet type was in
+.Tn VAX
+byte order).
+As a result, the trailer encapsulation in this version is not compatible
+with the
+.Bx 4.2
+.Tn VAX
+version.