initial import of NetBSD tree

188 files changed, 25779 insertions, 0 deletions

diff --git a/share/man/man4/Makefile b/share/man/man4/Makefile
new file mode 100644
index 00000000000..b8d981c0bbe
--- /dev/null
+++ b/share/man/man4/Makefile
@@ -0,0 +1,12 @@
+#	$NetBSD: Makefile,v 1.18 1995/08/08 20:20:58 gwr Exp $
+#	@(#)Makefile	8.1 (Berkeley) 6/18/93
+
+MAN=	bpf.4 ccd.4 clnp.4 cltp.4 ddb.4 drum.4 esis.4 fd.4 icmp.4 idp.4 imp.4 \
+	inet.4 ip.4 iso.4 lkm.4 lo.4 netintro.4 ns.4 nsip.4 null.4 pty.4 \
+	route.4 spp.4 tb.4 tcp.4 termios.4 tty.4 tp.4 udp.4 unix.4
+MLINKS+=fd.4 stderr.4 fd.4 stdin.4 fd.4 stdout.4
+MLINKS+=netintro.4 networking.4
+SUBDIR=	man4.amiga man4.hp300 man4.i386 man4.mac68k man4.pc532 man4.sparc \
+	man4.sun3 man4.tahoe man4.vax
+
+.include <bsd.prog.mk>
diff --git a/share/man/man4/bpf.4 b/share/man/man4/bpf.4
new file mode 100644
index 00000000000..01c2401402c
--- /dev/null
+++ b/share/man/man4/bpf.4
@@ -0,0 +1,722 @@
+.\" -*- nroff -*-
+.\"
+.\"	$NetBSD: bpf.4,v 1.7 1995/09/27 18:31:50 thorpej Exp $
+.\"
+.\" Copyright (c) 1990 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: (1) source code distributions
+.\" retain the above copyright notice and this paragraph in its entirety, (2)
+.\" distributions including binary code include the above copyright notice and
+.\" this paragraph in its entirety in the documentation or other materials
+.\" provided with the distribution, and (3) all advertising materials mentioning
+.\" features or use of this software display the following acknowledgement:
+.\" ``This product includes software developed by the University of California,
+.\" Lawrence Berkeley Laboratory and its contributors.'' 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 ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED
+.\" WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
+.\" MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
+.\"
+.\" This document is derived in part from the enet man page (enet.4)
+.\" distributed with 4.3BSD Unix.
+.\"
+.TH BPF 4  "23 May 1991"
+.SH NAME
+bpf \- Berkeley Packet Filter
+.SH SYNOPSIS
+.B "pseudo-device bpfilter 16"
+.SH DESCRIPTION
+The Berkeley Packet Filter
+provides a raw interface to data link layers in a protocol 
+independent fashion.
+All packets on the network, even those destined for other hosts,
+are accessible through this mechanism.
+.PP
+The packet filter appears as a character special device,
+.I /dev/bpf0, /dev/bpf1,
+etc.
+After opening the device, the file descriptor must be bound to a 
+specific network interface with the BIOSETIF ioctl.
+A given interface can be shared be multiple listeners, and the filter
+underlying each descriptor will see an identical packet stream.
+The total number of open 
+files is limited to the value given in the kernel configuration; the
+example given in the SYNOPSIS above sets the limit to 16.
+.PP
+A separate device file is required for each minor device.  
+If a file is in use, the open will fail and 
+.I errno
+will be set to EBUSY.
+.PP
+Associated with each open instance of a
+.I bpf
+file is a user-settable packet filter.
+Whenever a packet is received by an interface, 
+all file descriptors listening on that interface apply their filter.
+Each descriptor that accepts the packet receives its own copy.
+.PP
+Reads from these files return the next group of packets
+that have matched the filter.
+To improve performance, the buffer passed to read must be
+the same size as the buffers used internally by 
+.I bpf.
+This size is returned by the BIOCGBLEN ioctl (see below), and under
+BSD, can be set with BIOCSBLEN.
+Note that an individual packet larger than this size is necessarily
+truncated.
+.PP
+The packet filter will support any link level protocol that has fixed length
+headers.  Currently, only Ethernet, SLIP and PPP drivers have been
+modified to interact with
+.I bpf.
+.PP
+Since packet data is in network byte order, applications should use the
+.I byteorder(3n)
+macros to extract multi-byte values.
+.PP
+A packet can be sent out on the network by writing to a 
+.I bpf
+file descriptor.  The writes are unbuffered, meaning only one
+packet can be processed per write.
+Currently, only writes to Ethernets and SLIP links are supported.
+.SH IOCTLS
+The 
+.I ioctl
+command codes below are defined in <net/bpf.h>.  All commands require
+these includes:
+.ft B
+.nf
+
+	#include <sys/types.h>
+	#include <sys/time.h>
+	#include <sys/ioctl.h>
+	#include <net/bpf.h>
+
+.fi
+.ft R
+Additionally, BIOCGETIF and BIOCSETIF require \fB<net/if.h>\fR.
+
+The (third) argument to the 
+.I ioctl
+should be a pointer to the type indicated.
+.TP 10
+.B BIOCGBLEN (u_int)
+Returns the required buffer length for reads on
+.I bpf
+files.
+.TP 10
+.B BIOCSBLEN (u_int)
+Sets the buffer length for reads on 
+.I bpf
+files.  The buffer must be set before the file is attached to an interface
+with BIOCSETIF.
+If the requested buffer size cannot be accomodated, the closest
+allowable size will be set and returned in the argument.
+A read call will result in EIO if it is passed a buffer that is not this size.
+.TP 10
+.B BIOCGDLT (u_int)
+Returns the type of the data link layer underyling the attached interface.
+EINVAL is returned if no interface has been specified.
+The device types, prefixed with ``DLT_'', are defined in <net/bpf.h>.
+.TP 10
+.B BIOCPROMISC
+Forces the interface into promiscuous mode.
+All packets, not just those destined for the local host, are processed.
+Since more than one file can be listening on a given interface,
+a listener that opened its interface non-promiscuously may receive
+packets promiscuously.  This problem can be remedied with an 
+appropriate filter.
+.IP
+The interface remains in promiscuous mode until all files listening 
+promiscuously are closed.
+.TP 10
+.B BIOCFLUSH
+Flushes the buffer of incoming packets,
+and resets the statistics that are returned by BIOCGSTATS.
+.TP 10
+.B BIOCGETIF (struct ifreq)
+Returns the name of the hardware interface that the file is listening on.
+The name is returned in the if_name field of 
+.I ifr.
+All other fields are undefined.
+.TP 10
+.B BIOCSETIF (struct ifreq)
+Sets the hardware interface associate with the file.  This
+command must be performed before any packets can be read.
+The device is indicated by name using the
+.I if_name
+field of the 
+.I ifreq.
+Additionally, performs the actions of BIOCFLUSH.
+.TP 10
+.B BIOCSRTIMEOUT, BIOCGRTIMEOUT (struct timeval)
+Set or get the read timeout parameter.
+The 
+.I timeval 
+specifies the length of time to wait before timing
+out on a read request.
+This parameter is initialized to zero by
+.IR open(2),
+indicating no timeout.
+.TP 10
+.B BIOCGSTATS (struct bpf_stat)
+Returns the following structure of packet statistics:
+.ft B
+.nf
+
+struct bpf_stat {
+	u_int bs_recv;
+	u_int bs_drop;
+};
+.fi
+.ft R
+.IP
+The fields are:
+.RS
+.TP 15
+.I bs_recv
+the number of packets received by the descriptor since opened or reset
+(including any buffered since the last read call);
+and
+.TP
+.I bs_drop
+the number of packets which were accepted by the filter but dropped by the 
+kernel because of buffer overflows
+(i.e., the application's reads aren't keeping up with the packet traffic).
+.RE
+.TP 10
+.B BIOCIMMEDIATE (u_int)
+Enable or disable ``immediate mode'', based on the truth value of the argument.
+When immediate mode is enabled, reads return immediately upon packet 
+reception.  Otherwise, a read will block until either the kernel buffer
+becomes full or a timeout occurs.
+This is useful for programs like
+.I rarpd(8c),
+which must respond to messages in real time.
+The default for a new file is off.
+.TP 10
+.B BIOCSETF (struct bpf_program)
+Sets the filter program used by the kernel to discard uninteresting 
+packets.  An array of instructions and its length is passed in using
+the following structure:
+.ft B
+.nf
+
+struct bpf_program {
+	int bf_len;
+	struct bpf_insn *bf_insns;
+};
+.fi
+.ft R
+.IP
+The filter program is pointed to by the
+.I bf_insns
+field while its length in units of `struct bpf_insn' is given by the
+.I bf_len
+field.
+Also, the actions of BIOCFLUSH are performed.
+.IP
+See section \fBFILTER MACHINE\fP for an explanation of the filter language.
+.TP 10
+.B BIOCVERSION (struct bpf_version)
+Returns the major and minor version numbers of the filter languange currently
+recognized by the kernel.  Before installing a filter, applications must check
+that the current version is compatible with the running kernel.  Version
+numbers are compatible if the major numbers match and the application minor
+is less than or equal to the kernel minor.  The kernel version number is
+returned in the following structure:
+.ft B
+.nf
+
+struct bpf_version {
+	u_short bv_major;
+	u_short bv_minor;
+};
+.fi
+.ft R
+.IP
+The current version numbers are given by 
+.B BPF_MAJOR_VERSION
+and 
+.B BPF_MINOR_VERSION
+from <net/bpf.h>.
+An incompatible filter
+may result in undefined behavior (most likely, an error returned by
+.I ioctl()
+or haphazard packet matching).
+.TP 10
+.B BIOCSRSIG BIOCGRSIG (u_int signal)
+Set or get the receive signal.  This signal will be sent to the process or process group
+specified by FIOSETOWN.  It defaults to SIGIO.
+.SH STANDARD IOCTLS
+.I bpf
+now supports several standard
+.I ioctls
+which allow the user to do async and/or non-blocking I/O to an open
+.I bpf
+file descriptor.
+.TP 10
+.B FIONREAD (int)
+Returns the number of bytes that are immediately available for reading.
+.TP 10
+.B SIOCGIFADDR (struct ifreq)
+Returns the address associated with the interface.
+.TP 10
+.B FIONBIO (int)
+Set or clear non-blocking I/O.  If arg is non-zero, then doing a
+.I read
+when no data is available will return -1 and
+.I errno
+will be set to EWOULDBLOCK.
+If arg is zero, non-blocking I/O is disabled.  Note:  setting this
+overrides the timeout set by BIOCSRTIMEOUT.
+.TP 10
+.B FIOASYNC (int)
+Enable or disable async I/O.  When enabled (arg is non-zero), the process or
+process group specified by FIOSETOWN will start receiving SIGIO's when packets
+arrive.  Note that you must do an FIOSETOWN in order for this to take affect, as
+the system will not default this for you.
+The signal may be changed via BIOCSRSIG.
+.TP 10
+.B FIOSETOWN FIOGETOWN (int)
+Set or get the process or process group (if negative) that should receive SIGIO
+when packets are available.  The signal may be changed using BIOCSRSIG (see above).
+.SH BPF HEADER
+The following structure is prepended to each packet returned by 
+.I read(2):
+.in 15
+.ft B
+.nf
+
+struct bpf_hdr {
+	struct timeval bh_tstamp;
+	u_long bh_caplen;
+	u_long bh_datalen;
+	u_short bh_hdrlen;
+};
+.fi
+.ft R
+.in -15
+.PP
+The fields, whose values are stored in host order, and are:
+.TP 15
+.I bh_tstamp
+The time at which the packet was processed by the packet filter.
+.TP
+.I bh_caplen
+The length of the captured portion of the packet.  This is the minimum of
+the truncation amount specified by the filter and the length of the packet.
+.TP
+.I bh_datalen
+The length of the packet off the wire.
+This value is independent of the truncation amount specified by the filter.
+.TP
+.I bh_hdrlen
+The length of the BPF header, which may not be equal to
+.I sizeof(struct bpf_hdr).
+.RE
+.PP
+The 
+.I bh_hdrlen
+field exists to account for
+padding between the header and the link level protocol.
+The purpose here is to guarantee proper alignment of the packet
+data structures, which is required on alignment sensitive 
+architectures and and improves performance on many other architectures.
+The packet filter insures that the 
+.I bpf_hdr
+and the \fInetwork layer\fR header will be word aligned.  Suitable precautions
+must be taken when accessing the link layer protocol fields on alignment
+restricted machines.  (This isn't a problem on an Ethernet, since
+the type field is a short falling on an even offset,
+and the addresses are probably accessed in a bytewise fashion).
+.PP
+Additionally, individual packets are padded so that each starts
+on a word boundary.  This requires that an application
+has some knowledge of how to get from packet to packet.
+The macro BPF_WORDALIGN is defined in <net/bpf.h> to facilitate
+this process.  It rounds up its argument
+to the nearest word aligned value (where a word is BPF_ALIGNMENT bytes wide).
+.PP
+For example, if `p' points to the start of a packet, this expression
+will advance it to the next packet:
+.sp
+.RS
+.ce 1
+.nf
+p = (char *)p + BPF_WORDALIGN(p->bh_hdrlen + p->bh_caplen)
+.fi
+.RE
+.PP
+For the alignment mechanisms to work properly, the
+buffer passed to 
+.I read(2)
+must itself be word aligned.  
+.I malloc(3)
+will always return an aligned buffer.
+.ft R
+.SH FILTER MACHINE
+A filter program is an array of instructions, with all branches forwardly
+directed, terminated by a \fBreturn\fP instruction.
+Each instruction performs some action on the pseudo-machine state,
+which consists of an accumulator, index register, scratch memory store,
+and implicit program counter.
+
+The following structure defines the instruction format:
+.RS
+.ft B
+.nf
+
+struct bpf_insn {
+	u_short	code;
+	u_char 	jt;
+	u_char 	jf;
+	long k;
+};
+.fi
+.ft R
+.RE
+
+The \fIk\fP field is used in differnet ways by different insutructions, 
+and the \fIjt\fP and \fIjf\fP fields are used as offsets
+by the branch intructions.
+The opcodes are encoded in a semi-hierarchical fashion.
+There are eight classes of intructions: BPF_LD, BPF_LDX, BPF_ST, BPF_STX,
+BPF_ALU, BPF_JMP, BPF_RET, and BPF_MISC.  Various other mode and 
+operator bits are or'd into the class to give the actual instructions.
+The classes and modes are defined in <net/bpf.h>.
+
+Below are the semantics for each defined BPF instruction.
+We use the convention that A is the accumulator, X is the index register,
+P[] packet data, and M[] scratch memory store.
+P[i:n] gives the data at byte offset ``i'' in the packet,
+interpreted as a word (n=4),
+unsigned halfword (n=2), or unsigned byte (n=1).
+M[i] gives the i'th word in the scratch memory store, which is only
+addressed in word units.  The memory store is indexed from 0 to BPF_MEMWORDS-1.
+\fIk\fP, \fIjt\fP, and \fIjf\fP are the corresponding fields in the
+instruction definition.  ``len'' refers to the length of the packet.
+
+.TP 10
+.B BPF_LD
+These instructions copy a value into the accumulator.  The type of the
+source operand is specified by an ``addressing mode'' and can be 
+a constant (\fBBPF_IMM\fP), packet data at a fixed offset (\fBBPF_ABS\fP), 
+packet data at a variable offset (\fBBPF_IND\fP), the packet length
+(\fBBPF_LEN\fP),
+or a word in the scratch memory store (\fBBPF_MEM\fP).
+For \fBBPF_IND\fP and \fBBPF_ABS\fP, the data size must be specified as a word
+(\fBBPF_W\fP), halfword (\fBBPF_H\fP), or byte (\fBBPF_B\fP).
+The semantics of all the recognized BPF_LD instructions follow.
+
+.RS
+.TP 30
+.B BPF_LD+BPF_W+BPF_ABS
+A <- P[k:4]
+.TP
+.B BPF_LD+BPF_H+BPF_ABS
+A <- P[k:2]
+.TP
+.B BPF_LD+BPF_B+BPF_ABS
+A <- P[k:1]
+.TP
+.B BPF_LD+BPF_W+BPF_IND
+A <- P[X+k:4]
+.TP
+.B BPF_LD+BPF_H+BPF_IND
+A <- P[X+k:2]
+.TP
+.B BPF_LD+BPF_B+BPF_IND
+A <- P[X+k:1]
+.TP
+.B BPF_LD+BPF_W+BPF_LEN
+A <- len
+.TP
+.B BPF_LD+BPF_IMM
+A <- k
+.TP
+.B BPF_LD+BPF_MEM
+A <- M[k]
+.RE
+
+.TP 10
+.B BPF_LDX
+These instructions load a value into the index register.  Note that
+the addressing modes are more retricted than those of the accumulator loads,
+but they include
+.B BPF_MSH,
+a hack for efficiently loading the IP header length.
+.RS
+.TP 30
+.B BPF_LDX+BPF_W+BPF_IMM
+X <- k
+.TP
+.B BPF_LDX+BPF_W+BPF_MEM
+X <- M[k]
+.TP
+.B BPF_LDX+BPF_W+BPF_LEN
+X <- len
+.TP
+.B BPF_LDX+BPF_B+BPF_MSH
+X <- 4*(P[k:1]&0xf)
+.RE
+
+.TP 10
+.B BPF_ST
+This instruction stores the accumulator into the scratch memory.
+We do not need an addressing mode since there is only one possibility
+for the destination.
+.RS
+.TP 30
+.B BPF_ST
+M[k] <- A
+.RE
+
+.TP 10
+.B BPF_STX
+This instruction stores the index register in the scratch memory store.
+.RS
+.TP 30
+.B BPF_STX
+M[k] <- X
+.RE
+
+.TP 10
+.B BPF_ALU
+The alu instructions perform operations between the accumulator and
+index register or constant, and store the result back in the accumulator.
+For binary operations, a source mode is required (\fBBPF_K\fP or 
+\fBBPF_X\fP).
+.RS
+.TP 30
+.B BPF_ALU+BPF_ADD+BPF_K
+A <- A + k
+.TP
+.B BPF_ALU+BPF_SUB+BPF_K
+A <- A - k
+.TP
+.B BPF_ALU+BPF_MUL+BPF_K
+A <- A * k
+.TP
+.B BPF_ALU+BPF_DIV+BPF_K
+A <- A / k
+.TP
+.B BPF_ALU+BPF_AND+BPF_K
+A <- A & k
+.TP
+.B BPF_ALU+BPF_OR+BPF_K
+A <- A | k
+.TP
+.B BPF_ALU+BPF_LSH+BPF_K
+A <- A << k
+.TP
+.B BPF_ALU+BPF_RSH+BPF_K
+A <- A >> k
+.TP
+.B BPF_ALU+BPF_ADD+BPF_X
+A <- A + X
+.TP
+.B BPF_ALU+BPF_SUB+BPF_X
+A <- A - X
+.TP
+.B BPF_ALU+BPF_MUL+BPF_X
+A <- A * X
+.TP
+.B BPF_ALU+BPF_DIV+BPF_X
+A <- A / X
+.TP
+.B BPF_ALU+BPF_AND+BPF_X
+A <- A & X
+.TP
+.B BPF_ALU+BPF_OR+BPF_X
+A <- A | X
+.TP
+.B BPF_ALU+BPF_LSH+BPF_X
+A <- A << X
+.TP
+.B BPF_ALU+BPF_RSH+BPF_X
+A <- A >> X
+.TP
+.B BPF_ALU+BPF_NEG
+A <- -A
+.RE
+
+.TP 10
+.B BPF_JMP
+The jump instructions alter flow of control.  Conditional jumps
+compare the accumulator against a constant (\fBBPF_K\fP) or 
+the index register (\fBBPF_X\fP).  If the result is true (or non-zero),
+the true branch is taken, otherwise the false branch is taken.
+Jump offsets are encoded in 8 bits so the longest jump is 256 instructions.
+However, the jump always (\fBBPF_JA\fP) opcode uses the 32 bit \fIk\fP 
+field as the offset, allowing arbitrarily distant destinations.
+All conditionals use unsigned comparison conventions.
+.RS
+.TP 30
+.B BPF_JMP+BPF_JA
+pc += k
+.TP
+.B BPF_JMP+BPF_JGT+BPF_K
+pc += (A > k) ? jt : jf
+.TP
+.B BPF_JMP+BPF_JGE+BPF_K
+pc += (A >= k) ? jt : jf
+.TP
+.B BPF_JMP+BPF_JEQ+BPF_K
+pc += (A == k) ? jt : jf
+.TP
+.B BPF_JMP+BPF_JSET+BPF_K
+pc += (A & k) ? jt : jf
+.TP
+.B BPF_JMP+BPF_JGT+BPF_X
+pc += (A > X) ? jt : jf
+.TP
+.B BPF_JMP+BPF_JGE+BPF_X
+pc += (A >= X) ? jt : jf
+.TP
+.B BPF_JMP+BPF_JEQ+BPF_X
+pc += (A == X) ? jt : jf
+.TP
+.B BPF_JMP+BPF_JSET+BPF_X
+pc += (A & X) ? jt : jf
+.RE
+.TP 10
+.B BPF_RET
+The return instructions terminate the filter program and specify the amount
+of packet to accept (i.e., they return the truncation amount).  A return
+value of zero indicates that the packet should be ignored.
+The return value is either a constant (\fBBPF_K\fP) or the accumulator
+(\fBBPF_A\fP).
+.RS
+.TP 30
+.B BPF_RET+BPF_A
+accept A bytes
+.TP
+.B BPF_RET+BPF_K
+accept k bytes
+.RE
+.TP 10
+.B BPF_MISC
+The miscellaneous category was created for anything that doesn't
+fit into the above classes, and for any new instructions that might need to
+be added.  Currently, these are the register transfer intructions
+that copy the index register to the accumulator or vice versa.
+.RS
+.TP 30
+.B BPF_MISC+BPF_TAX
+X <- A
+.TP
+.B BPF_MISC+BPF_TXA
+A <- X
+.RE
+.PP
+The BPF interface provides the following macros to facilitate 
+array initializers:
+.RS
+\fBBPF_STMT\fI(opcode, operand)\fR
+.br
+and 
+.br
+\fBBPF_JUMP\fI(opcode, operand, true_offset, false_offset)\fR
+.RE
+.PP
+.SH EXAMPLES
+The following filter is taken from the Reverse ARP Daemon.  It accepts
+only Reverse ARP requests.
+.RS
+.nf
+
+struct bpf_insn insns[] = {
+	BPF_STMT(BPF_LD+BPF_H+BPF_ABS, 12),
+	BPF_JUMP(BPF_JMP+BPF_JEQ+BPF_K, ETHERTYPE_REVARP, 0, 3),
+	BPF_STMT(BPF_LD+BPF_H+BPF_ABS, 20),
+	BPF_JUMP(BPF_JMP+BPF_JEQ+BPF_K, REVARP_REQUEST, 0, 1),
+	BPF_STMT(BPF_RET+BPF_K, sizeof(struct ether_arp) + 
+		 sizeof(struct ether_header)),
+	BPF_STMT(BPF_RET+BPF_K, 0),
+};
+.fi
+.RE
+.PP
+This filter accepts only IP packets between host 128.3.112.15 and
+128.3.112.35.
+.RS
+.nf
+
+struct bpf_insn insns[] = {
+	BPF_STMT(BPF_LD+BPF_H+BPF_ABS, 12),
+	BPF_JUMP(BPF_JMP+BPF_JEQ+BPF_K, ETHERTYPE_IP, 0, 8),
+	BPF_STMT(BPF_LD+BPF_W+BPF_ABS, 26),
+	BPF_JUMP(BPF_JMP+BPF_JEQ+BPF_K, 0x8003700f, 0, 2),
+	BPF_STMT(BPF_LD+BPF_W+BPF_ABS, 30),
+	BPF_JUMP(BPF_JMP+BPF_JEQ+BPF_K, 0x80037023, 3, 4),
+	BPF_JUMP(BPF_JMP+BPF_JEQ+BPF_K, 0x80037023, 0, 3),
+	BPF_STMT(BPF_LD+BPF_W+BPF_ABS, 30),
+	BPF_JUMP(BPF_JMP+BPF_JEQ+BPF_K, 0x8003700f, 0, 1),
+	BPF_STMT(BPF_RET+BPF_K, (u_int)-1),
+	BPF_STMT(BPF_RET+BPF_K, 0),
+};
+.fi
+.RE
+.PP
+Finally, this filter returns only TCP finger packets.  We must parse
+the IP header to reach the TCP header.  The \fBBPF_JSET\fP instruction
+checks that the IP fragment offset is 0 so we are sure
+that we have a TCP header.
+.RS
+.nf
+
+struct bpf_insn insns[] = {
+	BPF_STMT(BPF_LD+BPF_H+BPF_ABS, 12),
+	BPF_JUMP(BPF_JMP+BPF_JEQ+BPF_K, ETHERTYPE_IP, 0, 10),
+	BPF_STMT(BPF_LD+BPF_B+BPF_ABS, 23),
+	BPF_JUMP(BPF_JMP+BPF_JEQ+BPF_K, IPPROTO_TCP, 0, 8),
+	BPF_STMT(BPF_LD+BPF_H+BPF_ABS, 20),
+	BPF_JUMP(BPF_JMP+BPF_JSET+BPF_K, 0x1fff, 6, 0),
+	BPF_STMT(BPF_LDX+BPF_B+BPF_MSH, 14),
+	BPF_STMT(BPF_LD+BPF_H+BPF_IND, 14),
+	BPF_JUMP(BPF_JMP+BPF_JEQ+BPF_K, 79, 2, 0),
+	BPF_STMT(BPF_LD+BPF_H+BPF_IND, 16),
+	BPF_JUMP(BPF_JMP+BPF_JEQ+BPF_K, 79, 0, 1),
+	BPF_STMT(BPF_RET+BPF_K, (u_int)-1),
+	BPF_STMT(BPF_RET+BPF_K, 0),
+};
+.fi
+.RE
+.SH SEE ALSO
+tcpdump(8), signal(3), ioctl(2), read(2), select(2), filio(2)
+.LP
+McCanne, S., Jacobson V.,
+.RI ` "An efficient, extensible, and portable network monitor" '
+.SH FILES
+/dev/bpf0, /dev/bpf1, ...
+.SH BUGS
+The read buffer must be of a fixed size (returned by the BIOCGBLEN ioctl).
+.PP
+A file that does not request promiscuous mode may receive promiscuously
+received packets as a side effect of another file requesting this
+mode on the same hardware interface.  This could be fixed in the kernel
+with additional processing overhead.  However, we favor the model where 
+all files must assume that the interface is promiscuous, and if 
+so desired, must utilize a filter to reject foreign packets.
+.PP
+Data link protocols with variable length headers are not currently supported.
+.PP
+Under SunOS, if a BPF application reads more than 2^31 bytes of
+data, read will fail in EINVAL.  You can either fix the bug in SunOS,
+or lseek to 0 when read fails for this reason.
+.SH HISTORY
+.PP
+The Enet packet filter was created in 1980 by Mike Accetta and
+Rick Rashid at Carnegie-Mellon University.  Jeffrey Mogul, at
+Stanford, ported the code to BSD and continued its development from 
+1983 on.  Since then, it has evolved into the Ultrix Packet Filter
+at DEC, a STREAMS NIT module under SunOS 4.1, and BPF.
+.SH AUTHORS
+.PP
+Steven McCanne, of Lawrence Berkeley Laboratory, implemented BPF in
+Summer 1990.  Much of the design is due to Van Jacobson.
diff --git a/share/man/man4/ccd.4 b/share/man/man4/ccd.4
new file mode 100644
index 00000000000..a292bf98360
--- /dev/null
+++ b/share/man/man4/ccd.4
@@ -0,0 +1,115 @@
+.\"	$NetBSD: ccd.4,v 1.5 1995/10/09 06:09:09 thorpej Exp $
+.\"
+.\" Copyright (c) 1994 Jason Downs.
+.\" Copyright (c) 1994, 1995 Jason R. Thorpe.
+.\" All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed for the NetBSD Project
+.\"	by Jason Downs and Jason R. Thorpe.
+.\" 4. Neither the name of the author 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 AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
+.\" BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+.\" LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
+.\" AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+.\" OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.Dd August 9, 1995
+.Dt CCD 4
+.Os NetBSD
+.Sh NAME
+.Nm ccd
+.Nd Concatenated Disk Driver
+.Sh SYNOPSIS
+.Cd "pseudo-device ccd 4"
+.Sh DESCRIPTION
+The
+.Nm
+driver provides the capability of combining one or more disks/partitions
+into one virtual disk.
+.Pp
+This document assumes that you're familiar with how to generate kernels,
+how to properly configure disks and pseudo-devices in a kernel
+configuration file, and how to partition disks.
+.Pp
+Note that the
+.Sq raw
+partitions of the disks
+.Pa should not
+be combined.  Each component partition should be offset at least one
+cylinder from the beginning of the component disk.  This avoids potential
+conflicts between the compoent disk's disklabel and the
+.Nm ccd's
+disklabel.  The kernel will only allow component partitions of type FS_BSDFFS.
+.Pp
+In order to compile in support for the ccd, you must add a line similar
+to the following to your kernel configuration file:
+.Bd -unfilled -offset indent
+pseudo-device	ccd	4	# concatenated disk devices
+.Ed
+.Pp
+The count argument is how many
+.Nm ccds
+memory is allocated for a boot time.  In this example, no more than 4
+.Nm ccds
+may be configured.
+.Pp
+A
+.Nm ccd
+may be either serially concatenated or interleaved.  If a
+.Nm ccd
+is interleaved correctly, a
+.Dq striping
+effect is achieved, which can increase performance.  The optimum interleave
+factor is typically the size of a track.  Since the interleave factor
+is expressed in units of DEV_BSIZE, one must account for sector sizes
+other than DEV_BSIZE in order to calculate the correct interleave.
+The kernel will not allow an interleave factor less than the size
+of the largest component sector divided by DEV_BSIZE.
+.Pp
+Note that best performance is achieved if all compent disks have the same
+geometery and size.  Optimum striping cannot occur with different
+disk types.
+.Pp
+There is a run-time utility that is used for configuring
+.Nm ccds .
+See
+.Xr ccdconfig 8
+for more information.
+.Sh WARNINGS
+If just one (or more) of the disks in a
+.Nm ccd
+fails, the entire
+file system will be lost.
+.Sh FILES
+/dev/{,r}ccd* - ccd device special files.
+.Pp
+.Sh HISTORY
+The concatenated disk driver was originally written at the University of
+Utah.
+.Sh SEE ALSO
+.Xr MAKEDEV 8 ,
+.Xr ccdconfig 8 ,
+.Xr config 8 ,
+.Xr config.old 8 ,
+.Xr fsck 8 ,
+.Xr mount 8 ,
+.Xr newfs 8 .
diff --git a/share/man/man4/clnp.4 b/share/man/man4/clnp.4
new file mode 100644
index 00000000000..9c2bed61a6b
--- /dev/null
+++ b/share/man/man4/clnp.4
@@ -0,0 +1,169 @@
+.\"	$NetBSD: clnp.4,v 1.4 1994/11/30 16:22:07 jtc Exp $
+.\"
+.\" Copyright (c) 1990, 1991, 1993
+.\"	The Regents of the University of California.  All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     @(#)clnp.4	8.2 (Berkeley) 4/2/94
+.\"
+.Dd April 2, 1994
+.Dt CLNP 4
+.Os
+.Sh NAME
+.Nm clnp
+.Nd Connectionless-Mode Network Protocol
+.Sh SYNOPSIS
+.Fd #include <sys/socket.h>
+.Fd #include <netiso/iso.h>
+.Fd #include <netiso/clnp.h>
+.Ft int
+.Fn socket AF_ISO SOCK_RAW 0
+.Sh DESCRIPTION
+.Tn CLNP
+is the connectionless-mode network protocol used by the 
+connectionless-mode network service. This protocol is specified in
+.Tn ISO
+8473.
+It may be accessed
+through a
+.Dq raw socket
+for debugging purposes only.
+.Tn CLNP
+sockets are connectionless,
+and are normally used with the
+.Xr sendto
+and
+.Xr recvfrom
+calls, though the
+.Xr connect 2
+call may also be used to fix the destination for future
+packets (in which case the 
+.Xr read 2
+or
+.Xr recv 2
+and 
+.Xr write 2
+or
+.Xr send 2
+system calls may be used).
+.Pp
+Outgoing packets automatically have a
+.Tn CLNP
+header prepended to
+them. Incoming packets received by the user contain the full
+.Tn CLNP
+header.
+The following
+.Xr setsockopt
+options apply to
+.Tn CLNP :
+.Bl -tag -width CLNPOPT_FLAGS
+.It Dv CLNPOPT_FLAGS
+Sets the flags which are passed to clnp when sending a datagram.
+Valid flags are:
+.Pp
+.Bl -tag -width "CLNP_NO_CKSUM" -offset indent -compact
+.It Dv CLNP_NO_SEG
+Do not allow segmentation
+.It Dv CLNP_NO_ER
+Suppress ER pdus
+.It Dv CLNP_NO_CKSUM
+Do not generate the
+.Tn CLNP
+checksum
+.El
+.Pp
+.It Dv CLNPOPT_OPTS
+Sets
+.Tn CLNP
+options. The options must be formatted exactly as specified by
+.Tn ISO
+8473, section 7.5
+.Dq Options Part.
+Once an option has been set, it will
+be sent on all packets until a different option is set.
+.El
+.Sh CONGESTION EXPERIENCE BIT
+Whenever a packet is transmitted, the globally unique quality of
+service option is added to the packet. The sequencing preferred bit and
+the low transit delay bit are set in this option.
+.Pp
+If a packet is forwarded containing the globally unique quality of
+service option, and the interface through which the packet will be 
+transmitted has a queue length greater than
+.Em congest_threshold ,
+then the congestion experienced bit is set in the quality of service option.
+.Pp
+The threshold value stored in
+.Em congest_threshold
+may be tuned.
+.Pp
+When a packet is received with the 
+globally unique quality of service option present, and the
+congestion experienced bit is set, then the transport congestion
+control function is called.
+.Sh DIAGNOSTICS
+A socket operation may fail with one of the following errors returned:
+.Bl -tag -width [EADDRNOTAVAIL]
+.It Bq Er EISCONN
+When trying to establish a connection on a socket which
+already has one, or when trying to send a datagram with the destination
+address specified and the socket is already connected;
+.It Bq Er ENOTCONN
+When trying to send a datagram, but
+no destination address is specified, and the socket hasn't been
+connected;
+.It Bq Er ENOBUFS
+When the system runs out of memory for
+an internal data structure;
+.It Bq Er EADDRNOTAVAIL
+When an attempt is made to create a 
+socket with a network address for which no network interface
+exists;
+.It Bq Er EHOSTUNREACH
+When trying to send a datagram, but no route to the destination
+address exists.
+.It Bq Er EINVAL
+When specifying unsupported options.
+.El
+.Sh SEE ALSO
+.Xr send 2 ,
+.Xr recv 2 ,
+.Xr intro 4 ,
+.Xr iso 4
+.Sh BUGS
+Packets are sent with the type code of 0x1d (technically an invalid
+packet type) for lack of a better way to identify raw
+.Tn CLNP
+packets.
+.Pp
+No more than
+.Dv MLEN
+bytes of options can be specified.
diff --git a/share/man/man4/cltp.4 b/share/man/man4/cltp.4
new file mode 100644
index 00000000000..672088210b4
--- /dev/null
+++ b/share/man/man4/cltp.4
@@ -0,0 +1,129 @@
+.\"	$NetBSD: cltp.4,v 1.3 1994/11/30 16:22:08 jtc Exp $
+.\"
+.\" Copyright (c) 1990, 1991, 1993
+.\"	The Regents of the University of California.  All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     @(#)cltp.4	8.1 (Berkeley) 6/9/93
+.\"
+.Dd June 9, 1993
+.Dt CLTP 4
+.Os
+.Sh NAME
+.Nm cltp
+.Nd
+.Tn ISO
+Connectionless Transport Protocol
+.Sh SYNOPSIS
+.Fd #include <sys/socket.h>
+.Fd #include <netiso/iso.h>
+.Ft int
+.Fn socket AF_ISO SOCK_DGRAM 0
+.Sh DESCRIPTION
+.Tn CLTP
+is a simple, unreliable datagram protocol which is accessed
+via the
+.Dv SOCK_DGRAM
+abstraction for the
+.Tn ISO
+protocol family.
+.Tn CLTP
+sockets are connectionless, and are
+normally used with the
+.Xr sendto
+and
+.Xr recvfrom
+calls, though the
+.Xr connect 2
+call may also be used to fix the destination for future
+packets (in which case the 
+.Xr recv 2
+or
+.Xr read 2
+and 
+.Xr send 2
+or
+.Xr write 2
+system calls may be used).
+.Pp
+.Tn CLTP
+address formats are identical to those used by TP.
+In particular
+.Tn CLTP
+provides a service selector in addition
+to the normal
+.Tn ISO NSAP .
+Note that the
+.Tn CLTP
+selector
+space is separate from the TP selector space (i.e. a
+.Tn CLTP
+selector
+may not be
+.Dq connected
+to a TP selector).
+.Pp
+Options at the
+.Tn CLNP
+network level may be used with
+.Tn CLTP ;
+see
+.Xr clnp 4 .
+.Sh DIAGNOSTICS
+A socket operation may fail with one of the following errors returned:
+.Bl -tag -width [EADDRNOTAVAIL]
+.It Bq Er EISCONN
+when trying to establish a connection on a socket which
+already has one, or when trying to send a datagram with the destination
+address specified and the socket is already connected;
+.It Bq Er ENOTCONN
+when trying to send a datagram, but
+no destination address is specified, and the socket hasn't been
+connected;
+.It Bq Er ENOBUFS
+when the system runs out of memory for
+an internal data structure;
+.It Bq Er EADDRINUSE
+when an attempt
+is made to create a socket with a selector which has already been
+allocated;
+.It Bq Er EADDRNOTAVAIL
+when an attempt is made to create a 
+socket with a network address for which no network interface
+exists.
+.El
+.Sh SEE ALSO
+.Xr getsockopt 2 ,
+.Xr recv 2 ,
+.Xr send 2 ,
+.Xr socket 2 ,
+.Xr intro 4 ,
+.Xr iso 4 ,
+.Xr clnp 4
diff --git a/share/man/man4/ddb.4 b/share/man/man4/ddb.4
new file mode 100644
index 00000000000..c616bf066e0
--- /dev/null
+++ b/share/man/man4/ddb.4
@@ -0,0 +1,371 @@
+.\" -*- nroff -*-
+.\" 
+.\"	$NetBSD: ddb.4,v 1.5 1994/11/30 16:22:09 jtc Exp $
+.\"
+.\" Mach Operating System
+.\" Copyright (c) 1991,1990 Carnegie Mellon University
+.\" All Rights Reserved.
+.\" 
+.\" Permission to use, copy, modify and distribute this software and its
+.\" documentation is hereby granted, provided that both the copyright
+.\" notice and this permission notice appear in all copies of the
+.\" software, derivative works or modified versions, and any portions
+.\" thereof, and that both notices appear in supporting documentation.
+.\" 
+.\" CARNEGIE MELLON ALLOWS FREE USE OF THIS SOFTWARE IN ITS "AS IS"
+.\" CONDITION.  CARNEGIE MELLON DISCLAIMS ANY LIABILITY OF ANY KIND FOR
+.\" ANY DAMAGES WHATSOEVER RESULTING FROM THE USE OF THIS SOFTWARE.
+.\" 
+.\" Carnegie Mellon requests users of this software to return to
+.\" 
+.\"  Software Distribution Coordinator  or  Software.Distribution@CS.CMU.EDU
+.\"  School of Computer Science
+.\"  Carnegie Mellon University
+.\"  Pittsburgh PA 15213-3890
+.\" 
+.\" any improvements or extensions that they make and grant Carnegie Mellon
+.\" the rights to redistribute these changes.
+.\" 
+.TH ddb 4
+.SH NAME
+ddb \- kernel debugger
+.de XX
+.sp
+.ti -4n
+\\$1
+.br
+.sp
+..
+.de XS
+.nr )R +\\$1
+..
+.de XE
+.nr )R -\\$1
+..
+.SH DESCRIPTION
+.br
+.sp
+The kernel debugger has most of the features of the old kdb,
+but with a more rational (gdb-like) syntax.
+.sp
+The current location is called 'dot'.  The 'dot' is displayed with
+a hexadecimal format at a prompt.
+Examine and write commands update 'dot' to the address of the last line
+examined or the last location modified, and set 'next' to the address of
+the next location to be examined or changed.
+Other commands don't change 'dot', and set 'next' to be the same as 'dot'.
+.sp
+The general command syntax is:
+.sp
+.ti +4n
+\fIcommand[/modifier] address [,count]\fR
+.sp
+A blank line repeats from the address 'next' with count 1 and no modifiers.
+Specifying 'address' sets 'dot' to the address.
+Omitting 'address' uses 'dot'.
+A missing 'count' is taken to be 1 for printing commands or infinity
+for stack traces.
+.sp
+"\fBddb\fR" has a feature like a command "\fBmore\fR"
+for the output.  If an output line exceeds the number set in the $lines
+variable, it displays "\fI--db_more--\fR"
+and waits for a response.
+The valid responses for it are:
+.XS 4n
+.IP \fI\<space>\fR 10n
+one more page
+.IP \fI\<return>\fR 10n
+one more line
+.IP \fB\q\fR 10n
+abort the current command, and return to the command input mode.
+.LP
+.sp
+.XE 4n
+.LP
+.B COMMANDS
+.sp
+.XS 4n
+.LP
+.XX "\fBexamine(x) \fI[/<modifier>] <addr>[,<count>]\fR"
+Display the addressed locations according to the formats in the modifier.
+Multiple modifier formats display multiple locations.
+If no format is specified, the last formats specified for this command
+is used.
+.br
+The format characters are
+.sp
+.LP
+.XS 2n
+.IP b 5n
+look at by bytes(8 bits)
+.IP h 5n
+look at by half words(16 bits)
+.IP l 5n
+look at by long words(32 bits)
+.IP a 5n
+print the location being displayed
+.IP A 5n
+print the location with a line number if possible
+.IP x 5n
+display in unsigned hex
+.IP z 5n
+display in signed hex
+.IP o 5n
+display in unsigned octal
+.IP d 5n
+display in signed decimal
+.IP u 5n
+display in unsigned decimal
+.IP r 5n
+display in current radix, signed
+.IP c 5n
+display low 8 bits as a character.
+Non-printing characters are displayed as an octal escape code (e.g. '\\000').
+.IP s 5n
+display the null-terminated string at the location.
+Non-printing characters are displayed as octal escapes.
+.IP m 5n
+display in unsigned hex with character dump at the end of each line.
+The location is also displayed in hex at the beginning of each line.
+.IP i 5n
+display as an instruction
+.IP I 5n
+display as an instruction with possible alternate formats depending on the
+machine:
+.XE 2n
+.LP
+.XS 5n
+.LP
+.IP vax 6n
+don't assume that each external label is a procedure entry mask
+.IP i386 6n
+don't round to the next long word boundary
+.IP mips 6n
+print register contents
+.LP
+.XE 5n
+.LP
+.XX xf
+Examine forward.
+It executes an examine command with the last specified parameters to it
+except that the next address displayed by it is used as the start address.
+.XX xb
+Examine backward.
+It executes an examine command with the last specified parameters to it
+except that the last start address subtracted by the size displayed by it
+is used as the start address.
+.XX "\fBprint[/axzodurc] \fI<addr1> [ <addr2> ... ]\fR"
+Print 'addr's according to the modifier character.
+Valid formats are: a x z o d u r c.
+If no modifier is specified, the last one specified to it is used.  'addr'
+can be a string, and it is printed as it is.  For example,
+.br
+.sp
+.ti +4n
+print/x "eax = " $eax "\\necx = " $ecx "\\n"
+.br
+.sp
+will print like
+.sp
+.in +4n
+eax = xxxxxx
+.br
+ecx = yyyyyy
+.in -4n
+.sp
+.br
+.XX "\fBwrite[/bhl] \fI<addr> <expr1> [ <expr2> ... ]\fR"
+Write the expressions at succeeding locations.
+The write unit size can be specified in the modifier with a letter
+b (byte), h (half word) or l(long word) respectively.  If omitted,
+long word is assumed.
+.br
+Warning: since there is no delimiter between expressions, strange
+things may happen.
+It's best to enclose each expression in parentheses.
+.XX "\fBset \fI$<variable> [=] <expr>\fR"
+Set the named variable or register with the value of 'expr'.
+Valid variable names are described below.
+.XX "\fBbreak[/u] \fI<addr>[,<count>]\fR"
+Set a break point at 'addr'.
+If count is supplied, continues (count-1) times before stopping at the
+break point.  If the break point is set, a break point number is
+printed with '#'.  This number can be used in deleting the break point
+or adding conditions to it.
+.LP
+.XS 2n
+.IP u 5n
+Set a break point in user space address. Without 'u' option,
+the address is considered in the kernel space, and wrong space address
+is rejected with an error message.
+This option can be used only if it is supported by machine dependent
+routines.
+.LP
+.XE 2n
+Warning: if a user text is shadowed by a normal user space debugger,
+user space break points may not work correctly.  Setting a break
+point at the low-level code paths may also cause strange behavior.
+.XX "\fBdelete \fI<addr>|#<number>\fR"
+Delete the break point.  The target break point can be specified by a
+break point number with '#', or by 'addr' like specified in 'break'
+command.
+.XX "\fBstep[/p] \fI[,<count>]\fR"
+Single step 'count' times.
+If 'p' option is specified, print each instruction at each step.
+Otherwise, only print the last instruction.
+.br
+.sp
+Warning: depending on machine type, it may not be possible to
+single-step through some low-level code paths or user space code.
+On machines with software-emulated single-stepping (e.g., pmax),
+stepping through code executed by interrupt handlers will probably
+do the wrong thing.
+.XX "\fBcontinue[/c]\fR"
+Continue execution until a breakpoint or watchpoint.
+If /c, count instructions while executing.
+Some machines (e.g., pmax) also count loads and stores.
+.br
+.sp
+Warning: when counting, the debugger is really silently single-stepping.
+This means that single-stepping on low-level code may cause strange
+behavior.
+.XX "\fBuntil[/p]\fR"
+Stop at the next call or return instruction.
+If 'p' option is specified, print the call nesting depth and the
+cumulative instruction count at each call or return.  Otherwise,
+only print when the matching return is hit.
+.XX "\fBnext[/p]\fR"
+Stop at the matching return instruction.
+If 'p' option is specified, print the call nesting depth and the
+cumulative instruction count at each call or return.  Otherwise,
+only print when the matching return is hit.
+.XX "\fBmatch[/p]\fR"
+A synonym for 'next'.
+.XX "\fBtrace[/u] \fI[ <frame_addr> ][,<count>]\fR"
+Stack trace.  'u' option traces user space; if omitted, only traces
+kernel space. 'count' is the number of frames to be traced. 
+If the 'count' is omitted, all frames are printed.
+.br
+.sp
+Warning: User space stack trace is valid
+only if the machine dependent code supports it.
+.XX "\fBsearch[/bhl] \fI<addr> <value> [<mask>] [,<count>]\fR"
+Search memory for a value. This command might fail in interesting
+ways if it doesn't find the searched-for value.  This is because
+ddb doesn't always recover from touching bad memory.  The optional
+count argument limits the search.
+.XX "\fBshow all procs[/m]\fR"
+Display all process information.
+This version of "\fBddb\fR"
+prints more information than previous one.
+It shows UNIX process information like "ps".
+The UNIX process information may not be shown if it is not
+supported in the machine, or the bottom of the stack of the
+target process is not in the main memory at that time.
+The 'm' options will alter the 'ps' display to show vm_map
+addresses for the process and not show other info.
+.br
+.XX "\fBps[/m]\fR"
+A synonym for 'show all procs'.
+.XX "\fBshow registers\fR"
+Display the register set.
+If 'u' option is specified, it displays user registers instead of
+kernel or currently saved one.
+.br
+.sp
+Warning: The support of 'u' option depends on the machine.  If
+not supported, incorrect information will be displayed.
+.XX "\fBshow map[/f] \fI<addr>\fR"
+Prints the vm_map at 'addr'. If the 'f' option is specified the
+complete map is printed.
+.XX "\fBshow object[/f]  \fI<addr>\fR"
+Prints the vm_object at 'addr'. If the 'f' option is specified the
+complete object is printed.
+.XX "\fBshow watches\fR"
+Displays all watchpoints.
+.XX "\fBwatch \fI<addr>,<size>\fR"
+Set a watchpoint for a region.  Execution stops
+when an attempt to modify the region occurs.
+The 'size' argument defaults to 4.
+.br
+If you specify a wrong space address, the request is rejected
+with an error message.
+.br
+.sp
+Warning: Attempts to watch wired kernel memory
+may cause unrecoverable error in some systems such as i386.
+Watchpoints on user addresses work best.
+.br
+.LP
+.XE 4n
+.LP
+.sp
+.B VARIABLES
+.sp
+The debugger accesses registers and variables as
+.I $<name>.
+Register names are as in the "\fBshow registers\fR"
+command.
+Some variables are suffixed with numbers, and may have some modifier
+following a colon immediately after the variable name.
+For example, register variables can have 'u' modifier to indicate
+user register (e.g. $eax:u).
+.br
+.sp
+Built-in variables currently supported are:
+.sp
+.IP radix 12n
+Input and output radix
+.IP maxoff 12n
+Addresses are printed as 'symbol'+offset unless offset is greater than maxoff.
+.IP maxwidth 12n
+The width of the displayed line.
+.IP lines 12n
+The number of lines.  It is used by "more" feature.
+.IP tabstops 12n
+Tab stop width.
+.IP work\fIxx\fR
+Work variable.
+.I 'xx'
+can be 0 to 31.
+.LP
+.LP
+.sp
+.B EXPRESSIONS
+.sp
+Almost all expression operators in C are supported except '~', '^',
+and unary '&'.
+Special rules in "\fBddb\fR"
+are:
+.br
+.IP "<identifier>" 15n
+name of a symbol.  It is translated to the address(or value) of it.  '.'
+and ':' can be used in the identifier.  If supported by an object format
+dependent routine,
+[\fI<file_name>\fR:]\fI<func>\fR[:\fI<line_number>\fR]
+[\fI<file_name>\fR:]\fI<variable>\fR, and
+\fI<file_name>\fR[:\fI<line_number>\fR]
+can be accepted as a symbol.
+The symbol may be prefixed with '\fI<symbol_table_name>\fR::'
+like 'emulator::mach_msg_trap' to specify other than kernel symbols.
+.IP "<number>" 15n
+radix is determined by the first two letters:
+0x: hex, 0o: octal, 0t: decimal, otherwise, follow current radix.
+.IP \. 15n
+\'dot'
+.IP \+ 15n
+\'next'
+.IP \.. 15n
+address of the start of the last line examined.
+Unlike 'dot' or 'next', this is only changed by "examine" or
+"write" command.
+.IP \' 15n
+last address explicitly specified.
+.IP "$<variable>" 15n
+register name or variable.  It is translated to the value of it.
+It may be followed by a ':' and modifiers as described above.
+.IP \# 15n
+a binary operator which rounds up the left hand side to the next
+multiple of right hand side.
+.IP "*<expr>" 15n
+indirection.  It may be followed by a ':' and  modifiers as described above.
diff --git a/share/man/man4/drum.4 b/share/man/man4/drum.4
new file mode 100644
index 00000000000..f0e9a800f4e
--- /dev/null
+++ b/share/man/man4/drum.4
@@ -0,0 +1,61 @@
+.\"	$NetBSD: drum.4,v 1.3 1994/11/30 16:22:11 jtc Exp $
+.\"
+.\" Copyright (c) 1980, 1991, 1993
+.\"	The Regents of the University of California.  All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     @(#)drum.4	8.1 (Berkeley) 6/5/93
+.\"
+.Dd June 5, 1993
+.Dt DRUM 4
+.Os BSD 4
+.Sh NAME
+.Nm drum
+.Nd paging device
+.Sh DESCRIPTION
+This file refers to the paging device in use by the system.
+This may actually be a subdevice of one of the disk drivers, but in
+a system with paging interleaved across multiple disk drives
+it provides an indirect driver for the multiple drives.
+.Sh FILES
+.Bl -tag -width /dev/drum
+.It Pa /dev/drum
+.El
+.Sh HISTORY
+The
+.Nm
+special file appeared in
+.Bx 3.0 .
+.Sh BUGS
+Reads from the drum are not allowed across the interleaving boundaries.
+Since these only occur every .5Mbytes
+or so,
+and since the system never allocates blocks across the boundary,
+this is usually not a problem.
diff --git a/share/man/man4/esis.4 b/share/man/man4/esis.4
new file mode 100644
index 00000000000..84cf4c42e20
--- /dev/null
+++ b/share/man/man4/esis.4
@@ -0,0 +1,217 @@
+.\"	$NetBSD: esis.4,v 1.3 1994/11/30 16:22:12 jtc Exp $
+.\"
+.\" Copyright (c) 1990, 1991, 1993
+.\"	The Regents of the University of California.  All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     @(#)esis.4	8.2 (Berkeley) 11/30/93
+.\"
+.Dd November 30, 1993
+.Dt ESIS 4
+.Os
+.Sh NAME
+.Nm es-is
+.Nd End System to Intermediate System Routing Protocol
+.Sh SYNOPSIS
+.Sy pseudo-device
+.Nm ether
+.Sh DESCRIPTION
+The
+.Nm ES-IS
+routing protocol is used to dynamically map between
+.Tn ISO NSAP
+addresses and
+.Tn ISO SNPA
+addresses; to permit End and Intermediate Systems
+to learn of each other's existence; and to allow Intermediate Systems
+to inform End Systems of (potentially) better routes to use when 
+forwarding
+.Tn NPDU Ns s
+to a particular destination.
+.Pp
+The mapping between
+.Tn NSAP
+addresses and
+.Tn SNPA
+addresses is accomplished by
+transmitting hello
+.Tn PDU Ns s
+between the cooperating Systems. These
+.Tn PDU Ns s
+are transmitted whenever the
+.Em configuration
+timer expires.
+When a hello
+.Tn PDU
+is received, the
+.Tn SNPA
+address that it conveys is stored in the routing table for as long as the
+.Em holding time
+in the
+.Tn PDU
+suggests. The default
+.Em holding time
+(120 seconds) placed in the hello
+.Tn PDU ,
+the configuration timer value,
+and the system type (End System or Intermediate System) may be changed by
+issuing an
+.Dv SIOCSSTYPE
+.Xr ioctl 2 ,
+which is defined in
+.Pa /sys/netiso/iso_snpac.h.
+.Pp
+The protocol behaves differently depending on whether the System is
+configured as an End System or an Intermediate System.
+.Sh END SYSTEM OPERATION
+When an interface requests a mapping for an address not in the cache,
+the
+.Tn SNPA
+of any known Intermediate System is returned. If an Intermediate
+System is not known, then the
+.Em all end systems
+multicast address
+is returned. It is assumed that the intended recipient of the NPDU will
+immediately transmit a hello
+.Tn PDU
+back to the originator of the
+.Tn NPDU .
+.Pp
+If an
+.Tn NPDU
+is forwarded by the End System, a redirect
+.Tn PDU
+will not be
+generated.
+However, redirect
+.Tn PDU Ns s
+received will be processed. This processing
+consists of adding an entry in the routing table. If the
+redirect is towards an Intermediate System, then an entry is made in the
+routing table as well.
+The entry in the routing table will mark the
+.Tn NSAP
+address contained in the redirect
+.Tn PDU
+as the gateway for the destination
+system (if an NET is supplied), or will create a route with
+the NSAP address as the
+destination and the
+.Tn SNPA
+address (embodied as a link-level sockaddr) as the
+gateway.
+.Pp
+If the System is configured as an End System, it will report all the
+.Tn NSAP Ns s
+that have been configured using the ifconfig command, and no others.
+It is possible to have more than one
+.Tn NSAP
+assigned to a given interface,
+and it is also possible to have the same
+.Tn NSAP
+assigned to multiple
+interfaces.
+However, any
+.Tn NSAP
+containing an NSEL that is consistent with the
+nsellength option (default one) of any interface will be accepted as
+an
+.Tn NSAP
+for this System.
+.Sh INTERMEDIATE SYSTEM OPERATION
+When an interface requests a mapping for an address not in the routing table,
+an error is returned.
+.Pp
+When an
+.Tn NPDU
+is forwarded out on the same interface that the
+.Tn NPDU
+arrived upon,
+a redirect
+.Tn PDU
+is generated.
+.Sh MANUAL ROUTING TABLE MODIFICATION
+.Pp
+To facilitate communications with systems which do not use
+.Nm ES-IS,
+one may add a route whose destination is a sockaddr_iso containing
+the
+.Tn NSAP
+in question, and the gateway being a link-level sockaddr,
+either by writing a special purpose program, or using the
+.Xr route 8
+command e.g.:
+.Bd -literal
+route add -iface -osi 49.0.4.8.0.2b.b.83.bf \
+	-link qe0:8.0.2b.b.83.bf
+.Ed
+.Pp
+If the
+System is configured as an End System and has a single network interface
+which does not support multicast reception,
+it is necessary to manually configure the location of an
+.Tn IS ,
+using the route command in a similar way.
+There, the destination address should be
+.Dq default
+(spelled 
+out literally as 7
+.Tn ASCII
+characters), and the gateway should be
+once again be a link-level sockaddr specifying the
+.Tn SNPA
+of the
+.Tn IS .
+.Sh SEE ALSO
+.Xr un 4 ,
+.Xr iso 4 ,
+.Xr route 8 ,
+.Xr ifconfig 8
+.Rs
+.%T "End system to Intermediate system routing exchange protocol for use in conjunction with the Protocol for providing the connectionless-mode network service"
+.%R ISO
+.%N 9542
+.Re
+.Sh BUGS
+Redirect
+.Tn PDU Ns s
+do not contain options from the forwarded
+.Tn NPDU
+which generated
+the redirect. The multicast address used on the 802.3 network is taken from
+the
+.Tn NBS
+December 1987 agreements. This multicast address is not compatible
+with the 802.5 (Token Ring) multicast addresses format. Therefore, broadcast
+addresses are used on the 802.5 subnetwork.
+Researchers at the University of Wisconsin are constructing an implementation
+of the
+.Tn IS-IS
+routing protocol.
diff --git a/share/man/man4/fd.4 b/share/man/man4/fd.4
new file mode 100644
index 00000000000..7ab5ab196ad
--- /dev/null
+++ b/share/man/man4/fd.4
@@ -0,0 +1,93 @@
+.\"	$NetBSD: fd.4,v 1.3 1994/11/30 16:22:13 jtc Exp $
+.\"
+.\" Copyright (c) 1990, 1991, 1993
+.\"	The Regents of the University of California.  All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     @(#)fd.4	8.1 (Berkeley) 6/9/93
+.\"
+.Dd June 9, 1993
+.Dt FD 4
+.Os
+.Sh NAME
+.Nm fd ,
+.Nm stdin ,
+.Nm stdout ,
+.Nm stderr
+.Nd file descriptor files
+.Sh DESCRIPTION
+The files
+.Pa /dev/fd/0
+through
+.Pa /dev/fd/#
+refer to file descriptors which can be accessed through the file
+system.
+If the file descriptor is open and the mode the file is being opened
+with is a subset of the mode of the existing descriptor, the call:
+.Bd -literal -offset indent
+fd = open("/dev/fd/0", mode);
+.Ed
+.Pp
+and the call:
+.Bd -literal -offset indent
+fd = fcntl(0, F_DUPFD, 0);
+.Ed
+.Pp
+are equivalent.
+.Pp
+Opening the files
+.Pa /dev/stdin ,
+.Pa /dev/stdout
+and
+.Pa /dev/stderr
+is equivalent to the following calls:
+.Bd -literal -offset indent
+fd = fcntl(STDIN_FILENO,  F_DUPFD, 0);
+fd = fcntl(STDOUT_FILENO, F_DUPFD, 0);
+fd = fcntl(STDERR_FILENO, F_DUPFD, 0);
+.Ed
+.Pp
+Flags to the
+.Xr open 2
+call other than
+.Dv O_RDONLY , 
+.Dv O_WRONLY
+and
+.Dv O_RDWR
+are ignored.
+.Sh FILES
+.Bl -tag -width /dev/stderr -compact
+.It Pa /dev/fd/#
+.It Pa /dev/stdin
+.It Pa /dev/stdout
+.It Pa /dev/stderr
+.El
+.Sh SEE ALSO
+.Xr tty 4
diff --git a/share/man/man4/icmp.4 b/share/man/man4/icmp.4
new file mode 100644
index 00000000000..988902428d6
--- /dev/null
+++ b/share/man/man4/icmp.4
@@ -0,0 +1,119 @@
+.\"	$NetBSD: icmp.4,v 1.3 1994/11/30 16:22:14 jtc Exp $
+.\"
+.\" Copyright (c) 1986, 1991, 1993
+.\"	The Regents of the University of California.  All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     @(#)icmp.4	8.1 (Berkeley) 6/5/93
+.\"
+.Dd June 5, 1993
+.Dt ICMP 4
+.Os BSD 4.3
+.Sh NAME
+.Nm icmp
+.Nd Internet Control Message Protocol
+.Sh SYNOPSIS
+.Fd #include <sys/socket.h>
+.Fd #include <netinet/in.h>
+.Ft int
+.Fn socket AF_INET SOCK_RAW proto
+.Sh DESCRIPTION
+.Tn ICMP
+is the error and control message protocol used
+by
+.Tn IP
+and the Internet protocol family.  It may be accessed
+through a
+.Dq raw socket
+for network monitoring
+and diagnostic functions.
+The
+.Fa proto
+parameter to the socket call to create an
+.Tn ICMP
+socket
+is obtained from
+.Xr getprotobyname 3 .
+.Tn ICMP
+sockets are connectionless,
+and are normally used with the
+.Xr sendto
+and
+.Xr recvfrom
+calls, though the
+.Xr connect 2
+call may also be used to fix the destination for future
+packets (in which case the 
+.Xr read 2
+or
+.Xr recv 2
+and 
+.Xr write 2
+or
+.Xr send 2
+system calls may be used).
+.Pp
+Outgoing packets automatically have an
+.Tn IP
+header prepended to
+them (based on the destination address).
+Incoming packets are received with the
+.Tn IP
+header and options intact.
+.Sh DIAGNOSTICS
+A socket operation may fail with one of the following errors returned:
+.Bl -tag -width [EADDRNOTAVAIL]
+.It Bq Er EISCONN
+when trying to establish a connection on a socket which
+already has one, or when trying to send a datagram with the destination
+address specified and the socket is already connected;
+.It Bq Er ENOTCONN
+when trying to send a datagram, but
+no destination address is specified, and the socket hasn't been
+connected;
+.It Bq Er ENOBUFS
+when the system runs out of memory for
+an internal data structure;
+.It Bq Er EADDRNOTAVAIL
+when an attempt is made to create a 
+socket with a network address for which no network interface
+exists.
+.El
+.Sh SEE ALSO
+.Xr send 2 ,
+.Xr recv 2 ,
+.Xr intro 4 ,
+.Xr inet 4 ,
+.Xr ip 4
+.Sh HISTORY
+The
+.Nm
+protocol appeared in
+.Bx 4.3 .
diff --git a/share/man/man4/idp.4 b/share/man/man4/idp.4
new file mode 100644
index 00000000000..8bc5d181edd
--- /dev/null
+++ b/share/man/man4/idp.4
@@ -0,0 +1,187 @@
+.\"	$NetBSD: idp.4,v 1.3 1994/11/30 16:22:15 jtc Exp $
+.\"
+.\" Copyright (c) 1985, 1991, 1993
+.\"	The Regents of the University of California.  All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     @(#)idp.4	8.1 (Berkeley) 6/5/93
+.\"
+.Dd June 5, 1993
+.Dt IDP 4
+.Os BSD 4.3
+.Sh NAME
+.Nm idp
+.Nd Xerox Internet Datagram Protocol
+.Sh SYNOPSIS
+.Fd #include <sys/socket.h>
+.Fd #include <netns/ns.h>
+.Fd #include <netns/idp.h>
+.Ft int
+.Fn socket AF_NS SOCK_DGRAM 0
+.Sh DESCRIPTION
+.Tn IDP
+is a simple, unreliable datagram protocol which is used
+to support the
+.Dv SOCK_DGRAM
+abstraction for the Internet
+protocol family.
+.Tn IDP
+sockets are connectionless, and are
+normally used with the
+.Xr sendto
+and
+.Xr recvfrom
+calls, though the
+.Xr connect 2
+call may also be used to fix the destination for future
+packets (in which case the 
+.Xr recv 2
+or
+.Xr read 2
+and 
+.Xr send 2
+or
+.Xr write 2
+system calls may be used).
+.Pp
+Xerox protocols are built vertically on top of
+.Tn IDP .
+Thus,
+.Tn IDP
+address formats are identical to those used by
+.Tn SPP .
+Note that the
+.Tn IDP
+port
+space is the same as the
+.Tn SPP
+port space (i.e. a
+.Tn IDP
+port
+may be
+.Dq connected
+to a
+.Tn SPP
+port, with certain
+options enabled below).
+In addition broadcast packets may be sent
+(assuming the underlying network supports
+this) by using a reserved
+.Dq broadcast address ;
+this address
+is network interface dependent.
+.Sh DIAGNOSTICS
+A socket operation may fail with one of the following errors returned:
+.Bl -tag -width [EADDRNOTAVAIL]
+.It Bq Er EISCONN
+when trying to establish a connection on a socket which
+already has one, or when trying to send a datagram with the destination
+address specified and the socket is already connected;
+.It Bq Er ENOTCONN
+when trying to send a datagram, but
+no destination address is specified, and the socket hasn't been
+connected;
+.It Bq Er ENOBUFS
+when the system runs out of memory for
+an internal data structure;
+.It Bq Er EADDRINUSE
+when an attempt
+is made to create a socket with a port which has already been
+allocated;
+.It Bq Er EADDRNOTAVAIL
+when an attempt is made to create a 
+socket with a network address for which no network interface
+exists.
+.El
+.Sh SOCKET OPTIONS
+.Bl -tag -width [SO_HEADERS_ON_OUTPUT]
+.It Bq Dv SO_ALL_PACKETS
+When set, this option defeats automatic processing of Error packets,
+and Sequence Protocol packets.
+.It Bq Dv SO_DEFAULT_HEADERS
+The user provides the kernel an
+.Tn IDP
+header, from which
+it gleans the Packet Type.
+When requested, the kernel will provide an
+.Tn IDP
+header, showing
+the default packet type, and local and foreign addresses, if
+connected.
+.It Bq Dv SO_HEADERS_ON_INPUT
+When set, the first 30 bytes of any data returned from a read
+or recv from will be the initial 30 bytes of the
+.Tn IDP
+packet,
+as described by
+.Bd -literal -offset indent
+struct idp {
+	u_short		idp_sum;
+	u_short		idp_len;
+	u_char		idp_tc;
+	u_char		idp_pt;
+	struct ns_addr	idp_dna;
+	struct ns_addr	idp_sna;
+};
+.Ed
+.Pp
+This allows the user to determine the packet type, and whether
+the packet was a multi-cast packet or directed specifically at
+the local host.
+When requested, gives the current state of the option,
+.Pf ( Dv NSP_RAWIN
+or 0).
+.It Bq Dv SO_HEADERS_ON_OUTPUT
+When set, the first 30 bytes of any data sent
+will be the initial 30 bytes of the
+.Tn IDP
+packet.
+This allows the user to determine the packet type, and whether
+the packet should be multi-cast packet or directed specifically at
+the local host.
+You can also misrepresent the sender of the packet.
+When requested, gives the current state of the option.
+.Pf ( Dv NSP_RAWOUT
+or 0).
+.It Bq Dv SO_SEQNO
+When requested, this returns a sequence number which is not likely
+to be repeated until the machine crashes or a very long time has passed.
+It is useful in constructing Packet Exchange Protocol packets.
+.El
+.Sh SEE ALSO
+.Xr send 2 ,
+.Xr recv 2 ,
+.Xr intro 4 ,
+.Xr ns 4
+.Sh HISTORY
+The
+.Nm
+protocol appeared in
+.Bx 4.3 .
diff --git a/share/man/man4/imp.4 b/share/man/man4/imp.4
new file mode 100644
index 00000000000..b60d957fa80
--- /dev/null
+++ b/share/man/man4/imp.4
@@ -0,0 +1,111 @@
+.\"	$NetBSD: imp.4,v 1.3 1994/11/30 16:22:16 jtc Exp $
+.\"
+.\" 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.
+.\"
+.\"     @(#)imp.4	6.5 (Berkeley) 3/28/91
+.\"
+.Dd March 28, 1991
+.Dt IMP 4
+.Os BSD 4.2
+.Sh NAME
+.Nm imp
+.Nd
+.Tn IMP
+raw socket interface
+.Sh SYNOPSIS
+.Fd #include <sys/socket.h>
+.Fd #include <netinet/in.h>
+.Fd #include <netimp/if_imp.h>
+.Ft int
+.Fn socket AF_IMPLINK SOCK_RAW proto
+.Sh DESCRIPTION
+The raw imp socket provides direct access to the
+.Nm imp
+network interface.  Users send packets through
+the interface using the 
+.Xr send 2
+calls, and receive packets with the
+.Xr recv 2 ,
+calls.  All outgoing packets must have an 1822 96-bit
+leader on the front.  Likewise, packets received
+by the user will have this leader on the front.  The
+1822 leader and the legal values for the various fields
+are defined in the include file
+.Aq Pa netimp/if_imp.h .
+The raw imp interface automatically installs the length
+and destination address in the 1822 leader of all
+outgoing packets; these need not be filled in by the user.
+.Pp
+If the protocol selected,
+.Fa proto ,
+is zero,
+the socket will receive
+all
+.Tn IMP
+messages except RFNM and incompletes
+which are not input data for a kernel protocol.
+If
+.Fa proto
+is non-zero,
+only messages for the specified link type will be received.
+.Sh DIAGNOSTICS
+An operation on a socket may fail with one of the following
+errors:
+.Bl -tag -width [EADDRNOTAVAIL]
+.It Bq Er EISCONN
+when trying to establish a connection on a socket which
+already has one, or when trying to send a datagram with the destination
+address specified and the socket is already connected;
+.It Bq Er ENOTCONN
+when trying to send a datagram, but
+no destination address is specified, and the socket hasn't been
+connected;
+.It Bq Er ENOBUFS
+when the system runs out of memory for
+an internal data structure;
+.It Bq Er ENOBUFS
+eight messages to the destination host are outstanding,
+and another eight are already queued for output;
+.It Bq Er EADDRNOTAVAIL
+when an attempt is made to create a 
+socket with a network address for which no network interface
+exists.
+.El
+.Sh SEE ALSO
+.Xr intro 4 ,
+.Xr inet 4 ,
+.Xr imp 4
+.Sh HISTORY
+The
+.Nm
+driver appeared in
+.Bx 4.2 .
diff --git a/share/man/man4/inet.4 b/share/man/man4/inet.4
new file mode 100644
index 00000000000..5d70e315d71
--- /dev/null
+++ b/share/man/man4/inet.4
@@ -0,0 +1,184 @@
+.\"	$NetBSD: inet.4,v 1.3 1994/11/30 16:22:18 jtc Exp $
+.\"
+.\" Copyright (c) 1983, 1991, 1993
+.\"	The Regents of the University of California.  All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     @(#)inet.4	8.1 (Berkeley) 6/5/93
+.\"
+.Dd June 5, 1993
+.Dt INET 4
+.Os BSD 4.2
+.Sh NAME
+.Nm inet
+.Nd Internet protocol family
+.Sh SYNOPSIS
+.Fd #include <sys/types.h>
+.Fd #include <netinet/in.h>
+.Sh DESCRIPTION
+The Internet protocol family is a collection of protocols
+layered atop the
+.Em Internet  Protocol
+.Pq Tn IP
+transport layer, and utilizing the Internet address format.
+The Internet family provides protocol support for the
+.Dv SOCK_STREAM , SOCK_DGRAM ,
+and
+.Dv SOCK_RAW
+socket types; the
+.Dv SOCK_RAW
+interface provides access to the
+.Tn IP
+protocol.
+.Sh ADDRESSING
+Internet addresses are four byte quantities, stored in
+network standard format (on the
+.Tn VAX
+these are word and byte
+reversed).  The include file
+.Aq Pa netinet/in.h
+defines this address
+as a discriminated union.
+.Pp
+Sockets bound to the Internet protocol family utilize
+the following addressing structure,
+.Bd -literal -offset indent
+struct sockaddr_in {
+	short	sin_family;
+	u_short	sin_port;
+	struct	in_addr sin_addr;
+	char	sin_zero[8];
+};
+.Ed
+.Pp
+Sockets may be created with the local address
+.Dv INADDR_ANY
+to effect
+.Dq wildcard
+matching on incoming messages. 
+The address in a
+.Xr connect 2
+or
+.Xr sendto 2
+call may be given as
+.Dv INADDR_ANY
+to mean
+.Dq this host .
+The distinguished address
+.Dv INADDR_BROADCAST
+is allowed as a shorthand for the broadcast address on the primary
+network if the first network configured supports broadcast.
+.Sh PROTOCOLS
+The Internet protocol family is comprised of
+the
+.Tn IP
+transport protocol, Internet Control
+Message Protocol
+.Pq Tn ICMP ,
+Transmission Control
+Protocol
+.Pq Tn TCP ,
+and User Datagram Protocol
+.Pq Tn UDP .
+.Tn TCP
+is used to support the
+.Dv SOCK_STREAM
+abstraction while
+.Tn UDP
+is used to support the
+.Dv SOCK_DGRAM
+abstraction.  A raw interface to
+.Tn IP
+is available
+by creating an Internet socket of type
+.Dv SOCK_RAW .
+The
+.Tn ICMP
+message protocol is accessible from a raw socket.
+.Pp
+The 32-bit Internet address contains both network and host parts.
+It is frequency-encoded; the most-significant bit is clear
+in Class A addresses, in which the high-order 8 bits are the network
+number.
+Class B addresses use the high-order 16 bits as the network field,
+and Class C addresses have a 24-bit network part.
+Sites with a cluster of local networks and a connection to the
+Internet may chose to use a single network number for the cluster;
+this is done by using subnet addressing.
+The local (host) portion of the address is further subdivided
+into subnet and host parts.
+Within a subnet, each subnet appears to be an individual network;
+externally, the entire cluster appears to be a single, uniform
+network requiring only a single routing entry.
+Subnet addressing is enabled and examined by the following
+.Xr ioctl 2
+commands on a datagram socket in the Internet domain;
+they have the same form as the
+.Dv SIOCIFADDR
+command (see
+.Xr intro 4 ) .
+.Pp
+.Bl -tag -width SIOCSIFNETMASK
+.It Dv SIOCSIFNETMASK
+Set interface network mask.
+The network mask defines the network part of the address;
+if it contains more of the address than the address type would indicate,
+then subnets are in use.
+.It Dv SIOCGIFNETMASK
+Get interface network mask.
+.El
+.Sh SEE ALSO
+.Xr ioctl 2 ,
+.Xr socket 2 ,
+.Xr intro 4 ,
+.Xr tcp 4 ,
+.Xr udp 4 ,
+.Xr ip 4 ,
+.Xr icmp 4
+.Rs
+.%T "An Introductory 4.3 BSD Interprocess Communication Tutorial"
+.%B PS1
+.%N 7
+.Re
+.Rs
+.%T "An Advanced 4.3 BSD Interprocess Communication Tutorial"
+.%B PS1
+.%N 8
+.Re
+.Sh CAVEAT
+The Internet protocol support is subject to change as
+the Internet protocols develop.  Users should not depend
+on details of the current implementation, but rather
+the services exported.
+.Sh HISTORY
+The
+.Nm
+protocol interface appeared in
+.Bx 4.2 .
diff --git a/share/man/man4/ip.4 b/share/man/man4/ip.4
new file mode 100644
index 00000000000..cfb7cfdf7c7
--- /dev/null
+++ b/share/man/man4/ip.4
@@ -0,0 +1,380 @@
+.\"	$NetBSD: ip.4,v 1.3 1994/11/30 16:22:19 jtc Exp $
+.\"
+.\" Copyright (c) 1983, 1991, 1993
+.\"	The Regents of the University of California.  All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     @(#)ip.4	8.2 (Berkeley) 11/30/93
+.\"
+.Dd November 30, 1993
+.Dt IP 4
+.Os BSD 4.2
+.Sh NAME
+.Nm ip
+.Nd Internet Protocol
+.Sh SYNOPSIS
+.Fd #include <sys/socket.h>
+.Fd #include <netinet/in.h>
+.Ft int
+.Fn socket AF_INET SOCK_RAW proto
+.Sh DESCRIPTION
+.Tn IP 
+is the transport layer protocol used
+by the Internet protocol family.
+Options may be set at the
+.Tn IP
+level
+when using higher-level protocols that are based on
+.Tn IP
+(such as
+.Tn TCP
+and
+.Tn UDP ) .
+It may also be accessed
+through a
+.Dq raw socket
+when developing new protocols, or
+special-purpose applications.
+.Pp
+There are several
+.Tn IP-level
+.Xr setsockopt 2 / Ns
+.Xr getsockopt 2
+options.
+.Dv IP_OPTIONS 
+may be used to provide
+.Tn IP
+options to be transmitted in the
+.Tn IP
+header of each outgoing packet
+or to examine the header options on incoming packets.
+.Tn IP
+options may be used with any socket type in the Internet family.
+The format of
+.Tn IP
+options to be sent is that specified by the
+.Tn IP 
+protocol specification (RFC-791), with one exception:
+the list of addresses for Source Route options must include the first-hop
+gateway at the beginning of the list of gateways.
+The first-hop gateway address will be extracted from the option list
+and the size adjusted accordingly before use.
+To disable previously specified options,
+use a zero-length buffer:
+.Bd -literal
+setsockopt(s, IPPROTO_IP, IP_OPTIONS, NULL, 0);
+.Ed
+.Pp
+.Dv IP_TOS 
+and 
+.Dv IP_TTL 
+may be used to set the type-of-service and time-to-live
+fields in the 
+.Tn IP 
+header for 
+.Dv SOCK_STREAM 
+and 
+.Dv SOCK_DGRAM 
+sockets. For example,
+.Bd -literal
+int tos = IPTOS_LOWDELAY;       /* see <netinet/in.h> */
+setsockopt(s, IPPROTO_IP, IP_TOS, &tos, sizeof(tos));
+
+int ttl = 60;                   /* max = 255 */
+setsockopt(s, IPPROTO_IP, IP_TTL, &ttl, sizeof(ttl));
+.Ed
+.Pp
+If the 
+.Dv IP_RECVDSTADDR 
+option is enabled on a 
+.Dv SOCK_DGRAM 
+socket,
+the
+.Xr recvmsg
+call will return the destination 
+.Tn IP 
+address for a 
+.Tn UDP 
+datagram. 
+The msg_control field in the msghdr structure points to a buffer 
+that contains a cmsghdr structure followed by the 
+.Tn IP 
+address. 
+The cmsghdr fields have the following values:
+.Bd -literal
+cmsg_len = sizeof(struct in_addr)
+cmsg_level = IPPROTO_IP
+cmsg_type = IP_RECVDSTADDR
+.Ed
+.Ss "Multicast Options"
+.Pp
+.Tn IP 
+multicasting is supported only on 
+.Dv AF_INET 
+sockets of type
+.Dv SOCK_DGRAM 
+and 
+.Dv SOCK_RAW,
+and only on networks where the interface
+driver supports multicasting.
+.Pp
+The 
+.Dv IP_MULTICAST_TTL 
+option changes the time-to-live (TTL)
+for outgoing multicast datagrams
+in order to control the scope of the multicasts:
+.Bd -literal
+u_char ttl;	/* range: 0 to 255, default = 1 */
+setsockopt(s, IPPROTO_IP, IP_MULTICAST_TTL, &ttl, sizeof(ttl));
+.Ed
+.sp
+Datagrams with a TTL of 1 are not forwarded beyond the local network.
+Multicast datagrams with a TTL of 0 will not be transmitted on any network,
+but may be delivered locally if the sending host belongs to the destination
+group and if multicast loopback has not been disabled on the sending socket
+(see below).  Multicast datagrams with TTL greater than 1 may be forwarded
+to other networks if a multicast router is attached to the local network.
+.Pp
+For hosts with multiple interfaces, each multicast transmission is 
+sent from the primary network interface.
+The 
+.Dv IP_MULTICAST_IF 
+option overrides the default for 
+subsequent transmissions from a given socket:
+.Bd -literal
+struct in_addr addr;
+setsockopt(s, IPPROTO_IP, IP_MULTICAST_IF, &addr, sizeof(addr));
+.Ed
+.sp
+where "addr" is the local 
+.Tn IP 
+address of the desired interface or
+.Dv INADDR_ANY 
+to specify the default interface.
+An interface's local IP address and multicast capability can 
+be obtained via the 
+.Dv SIOCGIFCONF 
+and 
+.Dv SIOCGIFFLAGS 
+ioctls. 
+Normal applications should not need to use this option.
+.Pp
+If a multicast datagram is sent to a group to which the sending host itself
+belongs (on the outgoing interface), a copy of the datagram is, by default,
+looped back by the IP layer for local delivery. 
+The 
+.Dv IP_MULTICAST_LOOP 
+option gives the sender explicit control 
+over whether or not subsequent datagrams are looped back:
+.Bd -literal
+u_char loop;	/* 0 = disable, 1 = enable (default) */
+setsockopt(s, IPPROTO_IP, IP_MULTICAST_LOOP, &loop, sizeof(loop));
+.Ed
+.sp
+This option
+improves performance for applications that may have no more than one
+instance on a single host (such as a router demon), by eliminating
+the overhead of receiving their own transmissions.  It should generally not
+be used by applications for which there may be more than one instance on a
+single host (such as a conferencing program) or for which the sender does
+not belong to the destination group (such as a time querying program).
+.Pp
+A multicast datagram sent with an initial TTL greater than 1 may be delivered
+to the sending host on a different interface from that on which it was sent,
+if the host belongs to the destination group on that other interface.  The
+loopback control option has no effect on such delivery.
+.Pp
+A host must become a member of a multicast group before it can receive 
+datagrams sent to the group.  To join a multicast group, use the 
+.Dv IP_ADD_MEMBERSHIP 
+option:
+.Bd -literal
+struct ip_mreq mreq;
+setsockopt(s, IPPROTO_IP, IP_ADD_MEMBERSHIP, &mreq, sizeof(mreq));
+.Ed
+.sp
+where 
+.Fa mreq
+is the following structure:
+.Bd -literal
+struct ip_mreq {
+    struct in_addr imr_multiaddr; /* multicast group to join */
+    struct in_addr imr_interface; /* interface to join on */
+}
+.Ed
+.sp
+.Dv imr_interface 
+should
+be 
+.Dv INADDR_ANY 
+to choose the default multicast interface, 
+or the 
+.Tn IP 
+address of a particular multicast-capable interface if
+the host is multihomed.
+Membership is associated with a single interface; 
+programs running on multihomed hosts may need to 
+join the same group on more than one interface.  
+Up to 
+.Dv IP_MAX_MEMBERSHIPS 
+(currently 20) memberships may be added on a
+single socket.
+.Pp
+To drop a membership, use:
+.Bd -literal
+struct ip_mreq mreq;
+setsockopt(s, IPPROTO_IP, IP_DROP_MEMBERSHIP, &mreq, sizeof(mreq));
+.Ed
+.sp
+where 
+.Fa mreq
+contains the same values as used to add the membership. 
+Memberships are dropped when the socket is closed or the process exits.  
+.\"-----------------------
+.Ss "Raw IP Sockets"
+.Pp
+Raw
+.Tn IP
+sockets are connectionless,
+and are normally used with the
+.Xr sendto
+and
+.Xr recvfrom
+calls, though the
+.Xr connect 2
+call may also be used to fix the destination for future
+packets (in which case the 
+.Xr read 2
+or
+.Xr recv 2
+and 
+.Xr write 2
+or
+.Xr send 2
+system calls may be used).
+.Pp
+If
+.Fa proto
+is 0, the default protocol
+.Dv IPPROTO_RAW
+is used for outgoing
+packets, and only incoming packets destined for that protocol
+are received.
+If
+.Fa proto
+is non-zero, that protocol number will be used on outgoing packets
+and to filter incoming packets.
+.Pp
+Outgoing packets automatically have an
+.Tn IP
+header prepended to
+them (based on the destination address and the protocol
+number the socket is created with),
+unless the 
+.Dv IP_HDRINCL 
+option has been set.
+Incoming packets are received with
+.Tn IP
+header and options intact.
+.Pp
+.Dv IP_HDRINCL 
+indicates the complete IP header is included with the data
+and may be used only with the 
+.Dv SOCK_RAW 
+type.
+.Bd -literal
+#include <netinet/ip.h>
+
+int hincl = 1;                  /* 1 = on, 0 = off */
+setsockopt(s, IPPROTO_IP, IP_HDRINCL, &hincl, sizeof(hincl));
+.Ed
+.sp
+Unlike previous 
+.Tn BSD 
+releases, the program must set all
+the fields of the IP header, including the following:
+.Bd -literal
+ip->ip_v = IPVERSION;
+ip->ip_hl = hlen >> 2;
+ip->ip_id = 0;  /* 0 means kernel set appropriate value */
+ip->ip_off = offset;
+.Ed
+.sp .5
+If the header source address is set to 
+.Dv INADDR_ANY,
+the kernel will choose an appropriate address.
+.Sh DIAGNOSTICS
+A socket operation may fail with one of the following errors returned:
+.Bl -tag -width [EADDRNOTAVAIL]
+.It Bq Er EISCONN
+when trying to establish a connection on a socket which
+already has one, or when trying to send a datagram with the destination
+address specified and the socket is already connected;
+.It Bq Er ENOTCONN
+when trying to send a datagram, but
+no destination address is specified, and the socket hasn't been
+connected;
+.It Bq Er ENOBUFS
+when the system runs out of memory for
+an internal data structure;
+.It Bq Er EADDRNOTAVAIL
+when an attempt is made to create a 
+socket with a network address for which no network interface
+exists.
+.It Bq Er EACESS
+when an attempt is made to create
+a raw IP socket by a non-privileged process.
+.El
+.Pp
+The following errors specific to
+.Tn IP
+may occur when setting or getting
+.Tn IP
+options:
+.Bl -tag -width EADDRNOTAVAILxx
+.It Bq Er EINVAL
+An unknown socket option name was given.
+.It Bq Er EINVAL
+The IP option field was improperly formed;
+an option field was shorter than the minimum value
+or longer than the option buffer provided.
+.El
+.Sh SEE ALSO
+.Xr getsockopt 2 ,
+.Xr send 2 ,
+.Xr recv 2 ,
+.Xr intro 4 ,
+.Xr icmp 4 ,
+.Xr inet 4
+.Sh HISTORY
+The
+.Nm
+protocol appeared in
+.Bx 4.2 .
diff --git a/share/man/man4/iso.4 b/share/man/man4/iso.4
new file mode 100644
index 00000000000..cd5f3f8aa8f
--- /dev/null
+++ b/share/man/man4/iso.4
@@ -0,0 +1,188 @@
+.\"	$NetBSD: iso.4,v 1.3 1994/11/30 16:22:20 jtc Exp $
+.\"
+.\" Copyright (c) 1990, 1991, 1993
+.\"	The Regents of the University of California.  All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     @(#)iso.4	8.2 (Berkeley) 11/30/93
+.\"
+.Dd November 30, 1993
+.Dt ISO 4
+.Os
+.Sh NAME
+.Nm iso
+.Nd
+.Tn ISO
+protocol family
+.Sh SYNOPSIS
+.Fd #include <sys/types.h>
+.Fd #include <netiso/iso.h>
+.Sh DESCRIPTION
+The
+.Tn ISO
+protocol family is a collection of protocols
+that uses the
+.Tn ISO
+address format.
+The
+.Tn ISO
+family provides protocol support for the
+.Dv SOCK_SEQPACKET
+abstraction through the
+.Tn TP
+protocol
+.Pf ( Tn ISO
+8073), 
+for the
+.Dv SOCK_DGRAM
+abstraction through the connectionless transport
+protocol
+.Pf ( Tn ISO
+8602),
+and for the
+.Dv SOCK_RAW
+abstraction
+by providing direct access (for debugging) to the
+.Tn CLNP 
+.Pf ( Tn ISO
+8473) network layer protocol.
+.Sh ADDRESSING
+.Tn ISO
+addresses are based upon
+.Tn ISO
+8348/AD2, 
+.%T "Addendum to the Network Service Definition Covering Network Layer Addressing."
+.Pp
+Sockets bound to the OSI protocol family use
+the following address structure:
+.Bd -literal
+struct iso_addr {
+     u_char    isoa_len;  /* length, not including this byte */
+     char      isoa_genaddr[20];  /* general opaque address */
+};
+
+struct sockaddr_iso {
+     u_char    siso_len;      /* size of this sockaddr */
+     u_char    siso_family;   /* addressing domain, AF_ISO */
+     u_char    siso_plen;     /* presentation selector length */
+     u_char    siso_slen;     /* session selector length */
+     u_char    siso_tlen;     /* transport selector length */
+     struct    iso_addr siso_addr; /* network address */
+     u_char    siso_pad[6];    /* space for gosip v2 SELs */
+};
+#define siso_nlen siso_addr.isoa_len
+#define siso_data siso_addr.isoa_genaddr
+.Ed
+.Pp
+The fields of this structure are:
+.Bl -tag -width Ds
+.It Ar siso_len:
+Length of the entire address structure, in bytes, which may grow to
+be longer than the 32 bytes shown above.
+.It Ar siso_family:
+Identifies the domain:
+.Dv AF_ISO .
+.It Ar siso_tlen:
+Length of the transport selector.
+.It Ar siso_slen:
+Length of the session selector.
+This is not currently supported by the kernel and is provided as
+a convenience for user level programs.
+.It Ar siso_plen:
+Length of the presentation selector.
+This is not currently supported by the kernel and is provided as
+a convenience for user level programs.
+.It Ar siso_addr:
+The network part of the address, described below.
+.El
+.Sh TRANSPORT ADDRESSING
+.Pp
+An
+.Tn ISO
+transport address is similar to an Internet address in that
+it contains a network-address portion and a portion that the
+transport layer uses to multiplex its services among clients.
+In the Internet domain, this portion of the address is called a
+.Em port .
+In the
+.Tn ISO
+domain, this is called a
+.Em transport selector
+(also known at one time as a
+.Em transport suffix ) .
+While ports are always 16 bits, 
+transport selectors may be
+of (almost) arbitrary size.
+.Pp
+Since the C language does not provide convenient variable
+length structures, we have separated the selector lengths
+from the data themselves.
+The network address and various selectors are stored contiguously,
+with the network address first, then the transport selector, and so
+on.  Thus, if you had a nework address of less then 20 bytes,
+the transport selector would encroach on space normally reserved
+for the network address.
+.Pp
+.Sh NETWORK ADDRESSING.
+.Tn ISO
+network addresses are limited to 20 bytes in length.
+.Tn ISO
+network addresses can take any format.
+.Sh PROTOCOLS
+The
+.Tn ARGO
+1.0 implementation of the 
+.Tn ISO
+protocol family comprises
+the Connectionless-Mode Network Protocol
+.Pq Tn CLNP , 
+and the Transport Protocol
+.Pq Tn TP ,
+classes 4 and 0,
+and
+.Tn X.25 .
+.Tn TP
+is used to support the
+.Dv SOCK_SEQPACKET
+abstraction.
+A raw interface to
+.Tn CLNP
+is available
+by creating an
+.Tn ISO
+socket of type
+.Dv SOCK_RAW .
+This is used for
+.Tn CLNP
+debugging only.
+.Sh SEE ALSO
+.Xr tp 4 ,
+.Xr clnp 4 ,
+.Xr cltp 4
diff --git a/share/man/man4/lkm.4 b/share/man/man4/lkm.4
new file mode 100644
index 00000000000..b3debde3227
--- /dev/null
+++ b/share/man/man4/lkm.4
@@ -0,0 +1,146 @@
+.\"	$NetBSD: lkm.4,v 1.4 1994/11/30 16:22:22 jtc Exp $
+.\"
+.\" Copyright (c) 1993 Christopher G. Demetriou
+.\" All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.Dd September 4, 1993
+.Dt LKM 4
+.Os NetBSD 0.9a
+.Sh NAME
+.Nm LKM
+.Nd Loadable Kernel Modules interface
+.Sh SYNOPSIS
+.Cd "options LKM"
+.Sh DESCRIPTION
+Loadable kernel modules allow the system administrator to
+dynamically add and remove functionality from a running system.
+This ability also helps software developers to develop
+new parts of the kernel without constantly rebooting to
+test their changes.
+.Pp
+Various types of modules can be loaded into the sytem.
+There are several defined module types, listed below, which can
+be added to the system in a predefined way.  In addition, there
+is a generic type, for which the module itself handles loading and
+unloading.
+.Pp
+The
+.Nm
+interface is used by performing
+.Xr ioctl 2
+calls on the
+.Pa /dev/lkm
+device.  Normally all operations involving
+Loadable Kernel Modules are handled by the
+.Xr modload 8 ,
+.Xr modunload 8 ,
+and
+.Xr modstat 8
+programs.  Users should never have to interact with
+.Pa /dev/lkm
+directly.
+.Sh "MODULE TYPES"
+.Bl -tag -width indent
+.It System Call modules
+System calls may be replaced by loading
+new ones via the
+.Nm
+interface.  All system calls may be
+replaced, but special care should
+be taken with the
+.Xr ioctl 2
+system call, as it is used to load and
+unload modules.
+.Pp
+When a system call module is unloaded,
+the system call which
+was replaced by the loadable module
+is returned to its rightful place
+in the system call table.
+.It Virtual File System modules
+Virtual file systems may be added
+via the
+.Nm
+interface.  At this time, only
+file systems which are already
+known to the system can be added,
+because of the way the
+.Xr mount 2
+system call is implemented.
+.It Device Driver modules
+New block and character device
+drivers may be loaded into the system with
+.Nm LKM .
+The major problem with loading
+a device driver is that the driver's
+device nodes must be exist for the
+devices to be accessed.  They are usually
+created by instructing
+.Xr modload 8
+to run an appropriate program when
+the driver has been successfully loaded.
+.It Execution Interpreters
+Execution interpreters allow
+the loading and execution of
+binaries which are normally not
+usable by the operating system.
+.It Miscellaneous modules
+Miscellaneous modules are modules
+for which there are not currently
+well-defined or well-used interfaces
+for extension.  The user is expected
+to write their own loader to manipulate
+whatever kernel data structures necessary
+to enable and disable the new module
+when it is loaded and unloaded.
+.El
+.Sh FILES
+.Bl -tag -width /usr/include/sys/lkm.h -compact
+.It Pa /dev/lkm
+.Nm
+interface device
+.It Pa /usr/include/sys/lkm.h
+file containing defitions of module types
+.It Pa /usr/share/lkm
+example source code implementing several of the modules types
+.Sh SEE ALSO
+.Xr modload 8 ,
+.Xr modunload 8 ,
+.Xr modstat 8
+.Sh HISTORY
+The
+.Nm
+facility was designed to be similar in functionality
+to the loadable kernel modules facility provided by
+.Tn "SunOS 4.1.3" .
+.Sh AUTHOR
+.Bl -tag
+Terrence R. Lambert, terry@cs.weber.edu
+.El
+.Sh BUGS
+Loading a bogus module is likely to kill your machine.
+.Pp
+Loadable streams modules should and will be implemented
+when a streams implementation is written.
diff --git a/share/man/man4/lo.4 b/share/man/man4/lo.4
new file mode 100644
index 00000000000..0491936b493
--- /dev/null
+++ b/share/man/man4/lo.4
@@ -0,0 +1,83 @@
+.\"	$NetBSD: lo.4,v 1.3 1994/11/30 16:22:23 jtc Exp $
+.\"
+.\" Copyright (c) 1983, 1991, 1993
+.\"	The Regents of the University of California.  All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     @(#)lo.4	8.1 (Berkeley) 6/5/93
+.\"
+.Dd June 5, 1993
+.Dt LO 4
+.Os BSD 4.2
+.Sh NAME
+.Nm lo
+.Nd software loopback network interface
+.Sh SYNOPSIS
+.Sy pseudo-device
+.Nm loop
+.Sh DESCRIPTION
+The
+.Nm loop
+interface is a software loopback mechanism which may be
+used for performance analysis, software testing, and/or local
+communication.
+As with other network interfaces, the loopback interface must have
+network addresses assigned for each address family with which it is to be used.
+These addresses
+may be set or changed with the
+.Dv SIOCSIFADDR
+.Xr ioctl 2 .
+The loopback interface should be the last interface configured,
+as protocols may use the order of configuration as an indication of priority.
+The loopback should
+.Em never
+be configured first unless no hardware
+interfaces exist.
+.Sh DIAGNOSTICS
+.Bl -diag
+.It lo%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 intro 4 ,
+.Xr inet 4 ,
+.Xr ns 4
+.Sh HISTORY
+The
+.Nm
+device appeared in
+.Bx 4.2 .
+.Sh BUGS
+Previous versions of the system enabled the loopback interface
+automatically, using a nonstandard Internet address (127.1).
+Use of that address is now discouraged; a reserved host address
+for the local network should be used instead.
diff --git a/share/man/man4/man4.amiga/Makefile b/share/man/man4/man4.amiga/Makefile
new file mode 100644
index 00000000000..8b2a58270ad
--- /dev/null
+++ b/share/man/man4/man4.amiga/Makefile
@@ -0,0 +1,9 @@
+# 	from: @(#)Makefile	8.2 (Berkeley) 2/16/94
+#	$Id: Makefile,v 1.1 1995/10/18 08:44:26 deraadt Exp $
+
+MAN=	ae.4 afsc.4 ahsc.4 atzsc.4 autoconf.4 console.4 bah.4 ed.4 es.4 gtsc.4 \
+	intro.4 ite.4 le.4 mem.4 mfcs.4 mgnsc.4 qn.4 ser.4 wesc.4 zssc.4
+MLINKS=	mem.4 kmem.4
+MANSUBDIR=/amiga
+
+.include <bsd.prog.mk>
diff --git a/share/man/man4/man4.amiga/ae.4 b/share/man/man4/man4.amiga/ae.4
new file mode 100644
index 00000000000..fd3cd367536
--- /dev/null
+++ b/share/man/man4/man4.amiga/ae.4
@@ -0,0 +1,118 @@
+.\"	$NetBSD: ae.4,v 1.3 1995/10/07 18:09:11 chopps Exp $
+.\"
+.\" Copyright (c) 1995 Bernd Ernesti and Klaus Burkert. All rights reserved.
+.\" Copyright (c) 1992, 1993
+.\" 	The Regents of the University of California. All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" Ralph Campbell and Rick Macklem.
+.\"
+.\" 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 Klaus Burkert,by Bernd
+.\"	Ernesti, by Michael van Elst, and by the University of California,
+.\"	Berkeley and its contributors.
+.\" 4. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.\" 	This is based on the original LANCE files, as the PCnet-ISA used on
+.\" 	the Ariadne is a LANCE-descendant optimized for the PC-ISA bus.
+.\" 	This causes some modifications, all data that is to go into registers
+.\" 	or to structures (buffer-descriptors, init-block) has to be
+.\" 	byte-swapped. In addition ALL write accesses to the board have to be
+.\" 	WORD or LONG, BYTE-access is prohibited!!
+.\"
+.\" The following requests are required for all man pages.
+.Dd Aug 1, 1995
+.Os NetBSD 1.0
+.Dt AE 4 amiga
+.Sh NAME
+.Nm ae
+.Nd Ethernet driver for AMD 79C960 LANCE based boards
+.Sh SYNOPSIS
+.Cd "ae* at zbus0"
+.Sh DESCRIPTION
+The 
+.Nm
+interface provides access to the 10 Mb/s Ethernet network via the
+.Tn AMD
+79C960
+.Tn LANCE
+Ethernet chip set.
+.Pp
+Each of the host's network addresses
+is specified at boot time with an
+.Dv SIOCSIFADDR
+.Xr ioctl .
+The
+.Nm
+interface employs the address resolution protocol described in
+.Xr arp 4
+to dynamically map between Internet and Ethernet addresses on the local
+network.
+.Pp
+This card come with two different assortment of connectors:
+.Pp
+.Bl -tag -width xxxxxxxxxxxxxxxxxxxx
+.It 10Base2
+BNC, also known as thin-net
+.It 10BaseT
+UTP, also known as twisted pair
+.El
+.Pp
+The card uses an autoselect between UTP and BNC, so it uses UTP when an
+active UTP line is connected or otherwise BNC.
+To choose an alternate port, use the following flag combinations with
+.Xr ifconfig 8
+or in your /etc/hostname.ae? file.
+.Pp
+.Bl -tag -width xxxxxxxxxxxxxxxxxxxx
+.It -link0
+Use the autoselect between UTP and BNC (default).
+.It \ link0 -link1
+Use the BNC port.
+.It \ link0 \ link1
+Use the UTP port.
+.El
+.Pp
+.Sh HARDWARE
+The
+.Nm
+interface supports the following Zorro II expansion cards:
+.Bl -tag -width "ARIADNE" -offset indent
+.It Em ARIADNE
+Village Tronic's ethernet card, manufacturer\ 2167, product\ 201
+.El
+.Pp
+.Sh NOTES
+Multicasting needs to be tested.
+.Pp
+.Sh HISTORY
+The
+.Nm
+interface first appeared in
+.Nx 1.0a
+.Sh SEE ALSO
+.Xr arp 4 ,
+.Xr ifconfig 8 ,
+.Xr inet 4 ,
+.Xr intro 4
diff --git a/share/man/man4/man4.amiga/afsc.4 b/share/man/man4/man4.amiga/afsc.4
new file mode 100644
index 00000000000..1d583bd7363
--- /dev/null
+++ b/share/man/man4/man4.amiga/afsc.4
@@ -0,0 +1,89 @@
+.\"
+.\" Copyright (c) 1994 Christian E. Hopps
+.\" 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 Christian E. Hopps.
+.\" 3. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.\"	$Id: afsc.4,v 1.1 1995/10/18 08:44:26 deraadt Exp $
+.\"
+.Dd July 23, 1995
+.Os NetBSD 1.0a
+.Dt AFSC 4 amiga
+.Sh NAME
+.Nm afsc
+.Nd A4091 low level SCSI interface
+.Sh SYNOPSIS
+.Cd "afsc0 at zbus0"
+.Sh DESCRIPTION
+The
+.Tn Amiga
+architecture uses a common machine independent scsi sub-system
+provided in the kernel source.  The machine independent 
+drivers that use this code access the hardware through a
+common interface. (see
+.Xr scsibus 4 )
+This common interface interacts with a machine dependent interface,
+such as
+.Nm afsc ,
+which then handles the hardware specific issues.
+.Pp
+The
+.Nm 
+interface handles things such as DMA and interrupts as well as
+actually sending commands, negotiating synchronous or asynchronous
+transfers and handling disconnect/reconnect of SCSI targets.
+The hardware that 
+.Nm
+uses is based on the NCR53c710 SCSI chip.
+.Sh HARDWARE
+The
+.Nm
+interface supports the following Zorro III expansion cards:
+.Bl -tag -width "A4091" -offset indent
+.It Em A4091
+Commodore SCSI adapter, manufacturer\ 514, product\ 84
+.El
+.Sh DIAGNOSTICS
+.Bl -diag
+.It afsc%s: abort %s: dstat %02x, sstat0 %02x sbcl %02x
+The scsi operation %s was aborted due to error.  Dstat, sstat and
+sbcl are registers within the NCR53c710 SCSI chip.
+.It siop id %d reset\n"
+The NCR53c710 SCSI chip has been reset and configure at id %d.
+.It SIOP interrupt: %x sts %x msg %x sbcl %x
+The NCR53c710 SCSI chip has interrupted unexpectedly.
+.It SIOP: SCSI Gross Error
+The NCR53c710 SCSI chip has indicated that it is confused.
+.It SIOP: Parity Error
+The NCR53c710 SCSI chip has indicated that it has detected a
+parity error on the SCSI bus.
+.Sh SEE ALSO
+.Xr scsibus 4
+.Sh HISTORY
+The
+.Nm 
+interface first appeared in
+.Nx 1.0
diff --git a/share/man/man4/man4.amiga/ahsc.4 b/share/man/man4/man4.amiga/ahsc.4
new file mode 100644
index 00000000000..2f3f7bfe968
--- /dev/null
+++ b/share/man/man4/man4.amiga/ahsc.4
@@ -0,0 +1,90 @@
+.\"
+.\" Copyright (c) 1994 Christian E. Hopps
+.\" 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 Christian E. Hopps.
+.\" 3. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.\"	$Id: ahsc.4,v 1.1 1995/10/18 08:44:26 deraadt Exp $
+.\"
+.Dd August 31, 1994
+.Os NetBSD 1.0
+.Dt AHSC 4 amiga
+.Sh NAME
+.Nm ahsc
+.Nd A3000 low level SCSI interface
+.Sh SYNOPSIS
+.Cd "ahsc0 at mainbus0"
+.Sh DESCRIPTION
+The
+.Tn Amiga
+architecture uses a common machine independent scsi sub-system
+provided in the kernel source.  The machine independent 
+drivers that use this code access the hardware through a
+common interface. (see
+.Xr scsibus 4 )
+This common interface interacts with a machine dependent interface,
+such as
+.Nm ahsc ,
+which then handles the hardware specific issues.
+.Pp
+The
+.Nm 
+interface handles things such as DMA and interrupts as well as
+actually sending commands, negotiating synchronous or asynchronous
+transfers and handling disconnect/reconnect of SCSI targets.
+The hardware that 
+.Nm
+uses is based on the WD33c93 SCSI chip.
+.Sh DIAGNOSTICS
+.Bl -diag
+.It sbicwait TIMEO @%d with asr=x%x csr=x%x
+The 33c93 code (sbic) has been waiting too long for a SCSI chip
+operation to complete. %d is the line in the source file
+.Pa amiga/dev/sbic.c
+at which the SCSI chip timed-out.  Asr and csr are status registers
+withing the SCSI chip.
+.It ahsc%d: abort %s: csr = 0x%02x, asr = 0x%02x
+A SCSI operation %s was aborted due to an error.
+.It ahsc%d: csr == 0x%02i
+A error has occured within the SCSI chip code.
+.It ahsc%d: unexpected phase %d in icmd from %d
+The target described by
+.Sq from %d
+has taken the SCSI bus into a phase which is not
+expected durring polled IO.
+.It ahsc%d: unexpected phase %d in icmd from %d
+The target described by
+.Sq from %d
+has taken the SCSI bus into a phase which is not
+expected durring DMA IO setup.
+.El
+.Sh SEE ALSO
+.Xr scsibus 4
+.Sh HISTORY
+The
+.Nm 
+interface first appeared in
+.Nx 0.9a
diff --git a/share/man/man4/man4.amiga/atzsc.4 b/share/man/man4/man4.amiga/atzsc.4
new file mode 100644
index 00000000000..e0a06a0c87c
--- /dev/null
+++ b/share/man/man4/man4.amiga/atzsc.4
@@ -0,0 +1,98 @@
+.\"
+.\" Copyright (c) 1994 Christian E. Hopps
+.\" 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 Christian E. Hopps.
+.\" 3. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.\"	$Id: atzsc.4,v 1.1 1995/10/18 08:44:26 deraadt Exp $
+.\"
+.Dd August 31, 1994
+.Os NetBSD 1.0
+.Dt ATZSC 4 amiga
+.Sh NAME
+.Nm atzsc
+.Nd A2091 low level SCSI interface
+.Sh SYNOPSIS
+.Cd "atzsc0 at zbus0"
+.Sh DESCRIPTION
+The
+.Tn Amiga
+architecture uses a common machine independent scsi sub-system
+provided in the kernel source.  The machine independent 
+drivers that use this code access the hardware through a
+common interface. (see
+.Xr scsibus 4 )
+This common interface interacts with a machine dependent interface,
+such as
+.Nm atzsc ,
+which then handles the hardware specific issues.
+.Pp
+The
+.Nm 
+interface handles things such as DMA and interrupts as well as
+actually sending commands, negotiating synchronous or asynchronous
+transfers and handling disconnect/reconnect of SCSI targets.
+The hardware that 
+.Nm
+uses is based on the WD33c93 SCSI chip.
+.Sh HARDWARE
+The
+.Nm
+interface supports the following Zorro II expansion cards:
+.Bl -tag -width "A2091" -offset indent
+.It Em A2091
+Commodore SCSI adapter, manufacturer\ 514, product\ 2 or product\ 3
+.El
+.Sh DIAGNOSTICS
+.Bl -diag
+.It sbicwait TIMEO @%d with asr=x%x csr=x%x
+The 33c93 code (sbic) has been waiting too long for a SCSI chip
+operation to complete. %d is the line in the source file
+.Pa amiga/dev/sbic.c
+at which the SCSI chip timed-out.  Asr and csr are status registers
+withing the SCSI chip.
+.It atzsc%d: abort %s: csr = 0x%02x, asr = 0x%02x
+A SCSI operation %s was aborted due to an error.
+.It atzsc%d: csr == 0x%02i
+A error has occured within the SCSI chip code.
+.It atzsc%d: unexpected phase %d in icmd from %d
+The target described by
+.Sq from %d
+has taken the SCSI bus into a phase which is not
+expected durring polled IO.
+.It atzsc%d: unexpected phase %d in icmd from %d
+The target described by
+.Sq from %d
+has taken the SCSI bus into a phase which is not
+expected durring DMA IO setup.
+.El
+.Sh SEE ALSO
+.Xr scsibus 4
+.Sh HISTORY
+The
+.Nm 
+interface first appeared in
+.Nx 0.9a
diff --git a/share/man/man4/man4.amiga/autoconf.4 b/share/man/man4/man4.amiga/autoconf.4
new file mode 100644
index 00000000000..e14acee218d
--- /dev/null
+++ b/share/man/man4/man4.amiga/autoconf.4
@@ -0,0 +1,95 @@
+.\"
+.\" Copyright (c) 1990, 1991 Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"      This product includes software developed by Christopher G. Demetriou.
+.\" 3. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.\"	$Id: autoconf.4,v 1.1 1995/10/18 08:44:26 deraadt Exp $
+.\"
+.Dd
+.Dt AUTOCONF 4 amiga
+.Os
+.Sh NAME
+.Nm autoconf
+.Nd diagnostics from the autoconfiguration code
+.Sh DESCRIPTION
+When
+.Tn NetBSD
+bootstraps it probes the innards of the machine
+on which it is running
+and locates controllers, drives, and other devices, printing out
+what it finds on the console.  This procedure is driven by a system
+configuration table which is processed by
+.Xr config 8
+and compiled into each kernel.
+Devices which exist in the machine but are not configured into the
+kernel are not detected.
+.Sh DIAGNOSTICS
+.Bl -diag
+.It CPU class not configured.
+You tried to boot
+.Tn NetBSD
+on a class of
+.Tn CPU
+type which it doesn't
+(or at least this compiled version of
+.Tn NetBSD
+doesn't) understand.
+.Pp
+.It %s at mainbus0.
+An Amiga internal device
+.Ql %s
+was configured
+.Pp  not configured.
+If this line follows the
+.Qlfd0 at fdc0
+configuration line, this diagnostic
+indicates that a second floppy drive was detected, but was not configured
+into the kernel.
+.Pp
+.It zbus0 at mainbus0 [mem 0x%x-0x%x].
+The kernel is configuring AutoConfigured expansion boards.  If any Zorro
+II memory was detected, the virtual address of the space reserved for
+DMA bounce buffers is printed.
+.Pp
+.It %s at zbus0: rom 0x%x man/prod %d/%d.
+A Zorro expansion board was configured.
+.Ql Rom 0x%0x
+is the physical address the board was configured at.
+.Ql Man/prod &d/%d
+is the manufacturer/product codes.
+.Pp
+.It %s at zbus0: rom 0x%x man/prod %d/%d not configured.
+A Zorro expansion board located at
+.Ql rom 0x%0x
+with a manufacturer/product code
+.Ql %d/%d
+was found that is not configured into the kernel.
+.El
+.Sh SEE ALSO
+.Xr intro 4 ,
+.Xr boot 8 ,
+.Xr config 8
diff --git a/share/man/man4/man4.amiga/bah.4 b/share/man/man4/man4.amiga/bah.4
new file mode 100644
index 00000000000..af4d2b64b21
--- /dev/null
+++ b/share/man/man4/man4.amiga/bah.4
@@ -0,0 +1,108 @@
+.\"	$NetBSD: bah.4,v 1.2 1995/06/06 23:41:37 cgd Exp $
+.\"
+.\" Copyright (c) 1995 Ignatios Souvatzis
+.\" 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 Ignatios Souvatzis
+.\"      for the NetBSD project.
+.\" 4. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+
+.\" The following requests are required for all man pages.
+.Dd May 31, 1995
+.Os NetBSD 1.0
+.Dt BAH 4 amiga
+.Sh NAME
+.Nm bah
+.Nd ARCnet driver for SMC COM90C26 based boards
+.Sh SYNOPSIS
+.Cd "bah* at zbus0"
+.Sh DESCRIPTION
+The 
+.Nm
+interface provides access to the 2.5 Mb/s ARCnet network via the
+.Tn SMC
+COM90C26
+ARCnet chip set.
+.Pp
+Each of the host's network addresses
+is specified at boot time with an
+.Dv SIOCSIFADDR
+.Xr ioctl .
+The
+.Nm
+interface does not employ the address resolution protocol described in
+.Xr arp 4
+to dynamically map between Internet and Ethernet addresses on the local
+network. Instead, it uses the least significant 8 bits of the IP address
+as hardware address, as described in
+.Xr RFC 1051
+and
+.Xr RFC 1201
+as one option.
+.Pp
+With the IFF_LINK0 flag cleared, IP encoding is done according to the
+deprecated, but popular among Amiga users, RFC 1051 encoding (that
+is, with simple header, packet type 240), and the MTU is 507.
+.Pp 
+With the IFF_LINK0 flag set, IP encoding is done according to RFC 1201 (that 
+is, with Packet Header Definition Standard header and packet type 212). The MTU
+is normally 1500.
+.Pp
+When switching between the two modes, do a 
+.Cd ifconfig interfacename down up
+to switch the mtu.
+.Pp
+.Sh HARDWARE
+The
+.Nm
+interface supports the following Zorro II expansion cards:
+.Bl -tag -width "AMERISTAR" -offset indent
+.It Em A2060
+Commodore's arcnet card, manufacturer\ 514, product\ 9
+.It Em AMERISTAR
+Ameristar's arcnet card, manufacturer\ 1053, product\ 9
+.El
+.Sh SEE ALSO
+.Xr arp 4 ,
+.Xr ifconfig 8 ,
+.Xr inet 4 ,
+.Xr intro 4 ,
+.Xr RFC1051 
+,
+.Xr RFC1201
+.br
+ARCnet Packet Header Definition Standard, Novell Inc., 1989
+.Sh STANDARDS
+RFC 1051 / RFC1201 without ARP, using direct mapping of lower 8 IP
+address bits instead.
+.Sh HISTORY
+The
+.Tn Amiga
+.Nm
+interface first appeared in
+.Nx 1.0a
+.Sh AUTHOR
+Ignatios Souvatzis
diff --git a/share/man/man4/man4.amiga/console.4 b/share/man/man4/man4.amiga/console.4
new file mode 100644
index 00000000000..7eb1c94ab78
--- /dev/null
+++ b/share/man/man4/man4.amiga/console.4
@@ -0,0 +1,79 @@
+.\" Copyright (c) 1990, 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" the Systems Programming Group of the University of Utah Computer
+.\" Science Department.
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)cons.4	5.2 (Berkeley) 3/27/91
+.\"	$Id: console.4,v 1.1 1995/10/18 08:44:26 deraadt Exp $
+.\"
+.Dd August 30, 1994
+.Dt CONSOLE 4 amiga
+.Os NetBSD 1.0
+.Sh NAME
+.Nm console
+.Nd
+.Tn amiga
+console interface
+.Sh DESCRIPTION
+This release supports a
+.Dq virtual
+console device used for
+.Em kernel printf
+messages and accessed in user mode via
+.Pa /dev/console .
+It is virtual in the sense that it is attached to a hardware interface
+at boot time.
+Currently the choices are limited to:
+a bit-mapped display acting as an
+.Em internal terminal emulator
+.Dq Tn ITE ,
+the builtin serial interface
+.Xr ser 4 ,
+or a
+.Xr null 4
+console in that order.
+.Sh FILES
+.Bl -tag -width /dev/console
+.It Pa /dev/console
+.El
+.Sh HISTORY
+The
+.Nm
+device is
+.Ud
+.Sh SEE ALSO
+.Xr tty 4 ,
+.Xr reboot 8
+.Sh BUGS
+You should be able to specify potential console devices at
+.Xr config.new 8
+time.
diff --git a/share/man/man4/man4.amiga/ed.4 b/share/man/man4/man4.amiga/ed.4
new file mode 100644
index 00000000000..3df0865e1e6
--- /dev/null
+++ b/share/man/man4/man4.amiga/ed.4
@@ -0,0 +1,76 @@
+.\"
+.\" Copyright (c) 1994 Christopher G. Demetriou
+.\" All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"      This product includes software developed by Christopher G. Demetriou.
+.\" 3. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.\"	$Id: ed.4,v 1.1 1995/10/18 08:44:26 deraadt Exp $
+.\"
+.Dd August 30, 1994
+.Dt ED 4 amiga
+.Os NetBSD 1.0
+.Sh NAME
+.Nm ed
+.Nd Ethernet driver for DP8390-based ethernet boards
+.Sh SYNOPSIS
+.Cd "ed* at zbus0"
+.Sh DESCRIPTION
+The
+.Nm
+interface provides access to a 10 Mb/s Ethernet network via the
+DP8390 Ethernet chip set.
+.Pp
+Each of the host's network addresses
+is specified at boot time with an
+.Dv SIOCSIFADDR
+.Xr ioctl .
+The
+.Nm
+interface employs the address resolution protocol described in
+.Xr arp 4
+to dynamically map between Internet and Ethernet addresses on the local
+network.
+.Sh HARDWARE
+The
+.Nm
+interface supports the following Zorro II expansion cards:
+.Bl -tag -width "LAN ROVER" -offset indent
+.It Em AMIGANET
+Hydra Systems' ethernet card, manufacturer\ 2121, product\ 1
+.\" support ready but not in yet
+.\" .It Em LAN ROVER
+.\" ASDG's ethernet card, manufacturer\ 1023, product\ 254
+.El
+.Sh HISTORY
+The
+.Nm
+interface first appeared in
+.Nx 0.9a
+.Sh SEE ALSO
+.Xr arp 4 ,
+.Xr ifconfig 8 ,
+.Xr inet 4 ,
+.Xr intro 4
diff --git a/share/man/man4/man4.amiga/es.4 b/share/man/man4/man4.amiga/es.4
new file mode 100644
index 00000000000..38beb80dbf9
--- /dev/null
+++ b/share/man/man4/man4.amiga/es.4
@@ -0,0 +1,73 @@
+.\"
+.\" Copyright (c) 1994 Christopher G. Demetriou
+.\" All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"      This product includes software developed by Christopher G. Demetriou.
+.\" 3. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.\"	$Id: es.4,v 1.1 1995/10/18 08:44:26 deraadt Exp $
+.\"
+.Dd August 30, 1994
+.Dt ES 4 amiga
+.Os NetBSD 1.0
+.Sh NAME
+.Nm es
+.Nd Ethernet driver for SMC91C90-based ethernet boards
+.Sh SYNOPSIS
+.Cd "es* at zbus0"
+.Sh DESCRIPTION
+The
+.Nm
+interface provides access to a 10 Mb/s Ethernet network via the
+SMC91C90 Ethernet chip set.
+.Pp
+Each of the host's network addresses
+is specified at boot time with an
+.Dv SIOCSIFADDR
+.Xr ioctl .
+The
+.Nm
+interface employs the address resolution protocol described in
+.Xr arp 4
+to dynamically map between Internet and Ethernet addresses on the local
+network.
+.Sh HARDWARE
+The
+.Nm
+interface supports the following Zorro II expansion cards:
+.Bl -tag -width "EthernetPLUS" -offset indent
+.It Em EthernetPLUS
+CEI A4066 EthernetPLUS ethernet card, manufacturer\ 1053, product\ 10
+.El
+.Sh HISTORY
+The
+.Nm
+interface first appeared in
+.Nx 1.0a
+.Sh SEE ALSO
+.Xr arp 4 ,
+.Xr ifconfig 8 ,
+.Xr inet 4 ,
+.Xr intro 4
diff --git a/share/man/man4/man4.amiga/gtsc.4 b/share/man/man4/man4.amiga/gtsc.4
new file mode 100644
index 00000000000..233a63adf64
--- /dev/null
+++ b/share/man/man4/man4.amiga/gtsc.4
@@ -0,0 +1,90 @@
+.\"
+.\" Copyright (c) 1994 Christian E. Hopps
+.\" 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 Christian E. Hopps.
+.\" 3. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.\"	$Id: gtsc.4,v 1.1 1995/10/18 08:44:26 deraadt Exp $
+.\"
+.Dd August 31, 1994
+.Os NetBSD 1.0
+.Dt GTSC 4 amiga
+.Sh NAME
+.Nm gtsc
+.Nd GVP low level SCSI interface
+.Sh SYNOPSIS
+.Cd "gtsc0 at gvpbus0"
+.Sh DESCRIPTION
+The
+.Tn Amiga
+architecture uses a common machine independent scsi sub-system
+provided in the kernel source.  The machine independent 
+drivers that use this code access the hardware through a
+common interface. (see
+.Xr scsibus 4 )
+This common interface interacts with a machine dependent interface,
+such as
+.Nm gtsc ,
+which then handles the hardware specific issues.
+.Pp
+The
+.Nm 
+interface handles things such as DMA and interrupts as well as
+actually sending commands, negotiating synchronous or asynchronous
+transfers and handling disconnect/reconnect of SCSI targets.
+The hardware that 
+.Nm
+uses is based on the WD33c93 SCSI chip.
+.Sh DIAGNOSTICS
+.Bl -diag
+.It sbicwait TIMEO @%d with asr=x%x csr=x%x
+The 33c93 code (sbic) has been waiting too long for a SCSI chip
+operation to complete. %d is the line in the source file
+.Pa amiga/dev/sbic.c
+at which the SCSI chip timed-out.  Asr and csr are status registers
+withing the SCSI chip.
+.It gtsc%d: abort %s: csr = 0x%02x, asr = 0x%02x
+A SCSI operation %s was aborted due to an error.
+.It gtsc%d: csr == 0x%02i
+A error has occured within the SCSI chip code.
+.It gtsc%d: unexpected phase %d in icmd from %d
+The target described by
+.Sq from %d
+has taken the SCSI bus into a phase which is not
+expected durring polled IO.
+.It gtsc%d: unexpected phase %d in icmd from %d
+The target described by
+.Sq from %d
+has taken the SCSI bus into a phase which is not
+expected durring DMA IO setup.
+.El
+.Sh SEE ALSO
+.Xr scsibus 4
+.Sh HISTORY
+The
+.Nm 
+interface first appeared in
+.Nx 0.9a
diff --git a/share/man/man4/man4.amiga/intro.4 b/share/man/man4/man4.amiga/intro.4
new file mode 100644
index 00000000000..538e9c6b901
--- /dev/null
+++ b/share/man/man4/man4.amiga/intro.4
@@ -0,0 +1,160 @@
+.\" Copyright (c) 1990, 1991 Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)intro.4	5.2 (Berkeley) 3/27/91
+.\"	$Id: intro.4,v 1.1 1995/10/18 08:44:26 deraadt Exp $
+.\"
+.Dd August 30, 1994
+.Dt INTRO 4 amiga
+.Os NetBSD 1.0
+.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.
+.Pp
+This section contains both devices
+which may be configured into the system
+and network related information.
+The networking support is introduced in
+.Xr netintro 4 .
+.Sh AMIGA DEVICE SUPPORT
+This section describes the hardware supported on the
+.Tn Amiga .
+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 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
+and, if found, enable the software support for it.
+If a device does not respond at autoconfiguration
+time it is not accessible at any time afterwards.
+To enable a device which did not autoconfigure,
+the system will have to be rebooted.
+.Pp
+The autoconfiguration system is described in
+.Xr autoconf 4 .
+A list of the supported devices is given below.
+.Sh HISTORY
+The
+.Tn Amiga
+.Nm intro
+man page first appeared in
+.Nx 1.0a
+.Sh SEE ALSO
+.Xr intro 4 ,
+.Xr autoconf 4 ,
+.Xr config 8 .
+.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.
+.Bl -tag -width "zbus" -compact -offset indent
+.It Em afsc
+A4091 low level SCSI adapter interface
+.It Em ahsc
+A3000 low level SCSI adapter interface
+.It Em atzsc
+A2091 low level SCSI adapter interface
+.It Em ed
+DP8390-based ethernet interface
+.It Em es
+SMC91C90-based ethernet interface
+.It Em fdc
+Floppy disk controller device
+.It Em fd
+Floppy disk device
+.It Em grf
+Custom Chips/Retina/Retina ZIII frame buffer
+.It Em gtsc
+GVP low level SCSI adapter interface
+.It Em gvpbus
+GVP custom bus
+.It Em kbd
+Amiga Keyboard device
+.It Em kmem
+kernel virtual memory
+.It Em ite
+Amiga Internal Terminal Emulator
+.It Em ivsc
+IVS low level SCSI adapter interface
+.It Em le
+AMD 7990 Lance-based ethernet interface
+.It Em mem
+physical memory
+.It Em mfcs
+MultiFaceCard II/II serial interface
+.It Em mgnsc
+Magnum 40 low level SCSI adapter interface
+.It Em otgsc
+12 Gauge low level SCSI adapter interface
+.It Em par
+8520 built-in parallel interface
+.It Em ser
+8520 built-in serial interface
+.It Em wesc
+Warp Engine low level SCSI adapter interface
+.It Em wstsc
+Wordsync II low level SCSI adapter interface
+.It Em zssc
+Zeus low level SCSI adapter interface
+.It Em zbus
+Amiga Zorro II/III bus
+.El
diff --git a/share/man/man4/man4.amiga/ite.4 b/share/man/man4/man4.amiga/ite.4
new file mode 100644
index 00000000000..17baf64e355
--- /dev/null
+++ b/share/man/man4/man4.amiga/ite.4
@@ -0,0 +1,139 @@
+.\" Copyright (c) 1990, 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" the Systems Programming Group of the University of Utah Computer
+.\" Science Department.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)ite.4	5.2 (Berkeley) 3/27/91
+.\"	$Id: ite.4,v 1.1 1995/10/18 08:44:27 deraadt Exp $
+.\"
+.Dd August 30, 1994
+.Dt ITE 4 amiga
+.Os NetBSD 1.0
+.Sh NAME
+.Nm ite
+.Nd
+.Tn Amiga
+Internal Terminal Emulator
+.Sh SYNOPSIS
+.Cd "ite0 at grf0"
+.Cd "ite1 at grf1"
+.Cd "ite2 at grf2"
+.Sh DESCRIPTION
+.Tn TTY
+special files of the form ``ttye?''
+are interfaces to the
+.Tn Amiga ITE
+for bit-mapped displays.
+An
+.Nm
+is the main system console on most
+.Tn Amiga
+workstations and
+is the mechanism through which a user communicates with the machine.
+If more than one of the supported displays exists on a system,
+any or all can be used as
+.Nm
+.Ns s
+with the limitation that only 
+one will have a keyboard (since only one keyboard is supported) and only
+one of each type can be used.
+.Pp
+.Nm Ite
+devices use the
+.Tn HP-UX
+.Sq Li 300h
+.Xr termcap 5
+entry.
+However, as currently implemented,
+the
+.Nm ite
+does not support the full range of
+.Tn HP-UX
+capabilities for this device.
+Missing are multiple colors, blinking, softkeys,
+programmable tabs, scrolling memory and keyboard arrow keys.
+The keyboard will use the left and right
+.Tn Em Amiga
+keys as meta keys, in that it will set the eighth bit of the character code.
+.Nm Ite
+devices also do a good job at emulating the
+.Sq Li vt100 
+.Xr termcap 5
+entry.
+.Pp
+Upon booting, the kernel will first look for an
+.Nm ite
+device
+to use as the system console
+.Pq Pa /dev/console .
+If a display exists at any hardware address, it will be the console.
+The kernel looks for, in order:
+.Nm ite2 ,
+.Nm ite1
+then
+.Nm ite0
+.Pp
+On most systems,
+a display is used both as an
+.Nm ite
+.Pf ( Pa /dev/ttye?
+aka
+.Pa /dev/console )
+and as a graphics device
+.Pq /dev/grf? .
+In this environment,
+there is some interaction between the two uses that should be noted.
+For example, opening
+.Pa /dev/grf0
+will deactivate the
+.Nm
+that is, write over whatever may be on the
+.Nm
+display.
+When the graphics application is finished and
+.Pa /dev/grf0
+closed,
+the
+.Nm 
+will be reinitialized with the frame buffer cleared
+and the
+old colormap installed.
+.Sh HISTORY
+The
+.Tn Amiga
+.Nm
+first appeared in
+.Nx 0.9a
+.Sh SEE ALSO
+.Xr grf 4 ,
+.Xr kbd 4
diff --git a/share/man/man4/man4.amiga/le.4 b/share/man/man4/man4.amiga/le.4
new file mode 100644
index 00000000000..fcafaadadb5
--- /dev/null
+++ b/share/man/man4/man4.amiga/le.4
@@ -0,0 +1,87 @@
+.\" Copyright (c) 1992, 1993
+.\"	The Regents of the University of California.  All rights reserved.
+.\"
+.\" This software was developed by the Computer Systems Engineering group
+.\" at Lawrence Berkeley Laboratory under DARPA contract BG 91-66 and
+.\" contributed to Berkeley.
+.\"
+.\" 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: Header: le.4,v 1.2 92/10/13 05:31:33 leres Exp
+.\"	from: @(#)le.4	8.1 (Berkeley) 6/9/93
+.\"	$Id: le.4,v 1.1 1995/10/18 08:44:27 deraadt Exp $
+.\"
+.Dd August 30, 1994
+.Dt LE 4 amiga
+.Os NetBSD 1.0
+.Sh NAME
+.Nm le
+.Nd Ethernet driver for AMD7990(LANCE)-based boards 
+.Sh SYNOPSIS
+.Cd "le* at zbus0"
+.Sh DESCRIPTION
+The 
+.Nm
+interface provides access to the 10 Mb/s Ethernet network via the
+.Tn AMD
+7990
+.Tn LANCE
+Ethernet chip set.
+.Pp
+Each of the host's network addresses
+is specified at boot time with an
+.Dv SIOCSIFADDR
+.Xr ioctl .
+The
+.Nm
+interface employs the address resolution protocol described in
+.Xr arp 4
+to dynamically map between Internet and Ethernet addresses on the local
+network.
+.Sh HARDWARE
+The
+.Nm
+interface supports the following Zorro II expansion cards:
+.Bl -tag -width "AMERISTAR" -offset indent
+.It Em A2065
+Commodore's ethernet card, manufacturer\ 514, product\ 112
+.It Em AMERISTAR
+Ameristar's ethernet card, manufacturer\ 1053, product\ 1
+.El
+.Sh HISTORY
+The
+.Tn Amiga
+.Nm
+interface first appeared in
+.Nx 0.9a
+.Sh SEE ALSO
+.Xr arp 4 ,
+.Xr ifconfig 8 ,
+.Xr inet 4 ,
+.Xr intro 4
diff --git a/share/man/man4/man4.amiga/mem.4 b/share/man/man4/man4.amiga/mem.4
new file mode 100644
index 00000000000..7d2d56491ca
--- /dev/null
+++ b/share/man/man4/man4.amiga/mem.4
@@ -0,0 +1,80 @@
+.\" Copyright (c) 1992, 1993
+.\"	The Regents of the University of California.  All rights reserved.
+.\"
+.\" This software was developed by the Computer Systems Engineering group
+.\" at Lawrence Berkeley Laboratory under DARPA contract BG 91-66 and
+.\" contributed to Berkeley.
+.\"
+.\" 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	8.1 (Berkeley) 6/5/93
+.\"	$Id: mem.4,v 1.1 1995/10/18 08:44:27 deraadt Exp $
+.\"
+.Dd June 5, 1993
+.Dt MEM 4 amiga
+.Os NetBSD 1.0
+.Sh NAME
+.Nm mem ,
+.Nm kmem
+.Nd main memory
+.Sh DESCRIPTION
+The 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.
+An error will be returned if an attempt is made to reference
+an offset outside of
+.Nm /dev/mem .
+.Pp
+Kernel virtual memory is accessed via the file
+.Nm /dev/kmem
+in the same manner as
+.Nm /dev/mem .
+Only kernel virtual addresses that are currently mapped to memory are allowed.
+.Pp
+On the
+.Tn Amiga ,
+physical memory may be discontiguous;
+kernel virtual memory begins at
+.Ad 0x00000000 .
+.Sh FILES
+.Bl -tag -width /dev/kmem -compact
+.It Pa /dev/mem
+.It Pa /dev/kmem
+.El
+.Sh HISTORY
+The files
+.Nm mem
+and
+.Nm kmem
+appeared in
+.At v6 .
diff --git a/share/man/man4/man4.amiga/mfcs.4 b/share/man/man4/man4.amiga/mfcs.4
new file mode 100644
index 00000000000..a733dbe285d
--- /dev/null
+++ b/share/man/man4/man4.amiga/mfcs.4
@@ -0,0 +1,89 @@
+.\" Copyright (c) 1990, 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" the Systems Programming Group of the University of Utah Computer
+.\" Science Department.
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)dca.4	5.2 (Berkeley) 3/27/91
+.\"	$Id: mfcs.4,v 1.1 1995/10/18 08:44:27 deraadt Exp $
+.\"
+.Dd July 23, 1995
+.Dt MFCS 4 amiga
+.Os NetBSD 1.0a
+.Sh NAME
+.Nm mfcs
+.Nd
+.Tn BSC/AlfaData MultiFaceCard II/III
+serial communications interface
+.Sh SYNOPSIS
+.Cd "mfc0 at mainbus0"
+.Cd "mfcs0 at mfc0 unit 0"
+.Cd "mfcs1 at mfc0 unit 1"
+.Sh DESCRIPTION
+The
+.Tn MultiFaceCard II/III
+controls, among other things, a dual port
+.Tn EIA
+.Tn RS-232C
+.Pf ( Tn CCITT
+.Tn V.28 )
+communications interface with a multiple character buffer.
+.Pp
+Input and output for each MultiFaceCard III line may set to a maximum baud
+rates of 1152000.  Formula for baud rate:  Baud = 230400 / N with 1 < N < 65536.
+.Pp
+Input and output for each MultiFaceCard II line may set to a maximum baud
+rates of 57600.  Formula for baud rate:  Baud = 115200 / N with 1 < N < 65536.
+.Sh FILES
+.Bl -tag -width Pa
+.It Pa /dev/ttyA?
+.El
+.Sh DIAGNOSTICS
+.Bl -diag
+.It mfcs0: fifo overflow.
+The four-character input
+.Dq fifo
+has overflowed and incoming data has been lost.
+.It mfcs0: %d buffer overflows.
+The software based input ring buffer
+has overflowed %d times and incoming data has been lost.
+.El
+.Sh SEE ALSO
+.Xr tty 4
+.Sh HISTORY
+The
+.Tn Amiga
+.Nm
+device first appeared in
+.Nx 1.0a
+.Sh BUGS
+The MultiFaceCard II/III serial ports use the level 6 interrupt and may
+experience fifo overflows if the LEV6_DEFER option is used.
diff --git a/share/man/man4/man4.amiga/mgnsc.4 b/share/man/man4/man4.amiga/mgnsc.4
new file mode 100644
index 00000000000..3a61eba2307
--- /dev/null
+++ b/share/man/man4/man4.amiga/mgnsc.4
@@ -0,0 +1,81 @@
+.\"
+.\" Copyright (c) 1994 Christian E. Hopps
+.\" 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 Christian E. Hopps.
+.\" 3. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.\"	$Id: mgnsc.4,v 1.1 1995/10/18 08:44:27 deraadt Exp $
+.\"
+.Dd August 31, 1994
+.Os NetBSD 1.0
+.Dt MGNSC 4 amiga
+.Sh NAME
+.Nm mgnsc
+.Nd Magnum low level SCSI interface
+.Sh SYNOPSIS
+.Cd "mgnsc0 at zbus0"
+.Sh DESCRIPTION
+The
+.Tn Amiga
+architecture uses a common machine independent scsi sub-system
+provided in the kernel source.  The machine independent 
+drivers that use this code access the hardware through a
+common interface. (see
+.Xr scsibus 4 )
+This common interface interacts with a machine dependent interface,
+such as
+.Nm mgnsc ,
+which then handles the hardware specific issues.
+.Pp
+The
+.Nm 
+interface handles things such as DMA and interrupts as well as
+actually sending commands, negotiating synchronous or asynchronous
+transfers and handling disconnect/reconnect of SCSI targets.
+The hardware that 
+.Nm
+uses is based on the NCR53c710 SCSI chip.
+.Sh DIAGNOSTICS
+.Bl -diag
+.It mgnsc%s: abort %s: dstat %02x, sstat0 %02x sbcl %02x
+The scsi operation %s was aborted due to error.  Dstat, sstat and
+sbcl are registers within the NCR53c710 SCSI chip.
+.It siop id %d reset\n"
+The NCR53c710 SCSI chip has been reset and configure at id %d.
+.It SIOP interrupt: %x sts %x msg %x sbcl %x
+The NCR53c710 SCSI chip has interrupted unexpectedly.
+.It SIOP: SCSI Gross Error
+The NCR53c710 SCSI chip has indicated that it is confused.
+.It SIOP: Parity Error
+The NCR53c710 SCSI chip has indicated that it has detected a
+parity error on the SCSI bus.
+.Sh SEE ALSO
+.Xr scsibus 4
+.Sh HISTORY
+The
+.Nm 
+interface first appeared in
+.Nx 0.9a
diff --git a/share/man/man4/man4.amiga/qn.4 b/share/man/man4/man4.amiga/qn.4
new file mode 100644
index 00000000000..61a8bb22bc1
--- /dev/null
+++ b/share/man/man4/man4.amiga/qn.4
@@ -0,0 +1,94 @@
+.\"
+.\" Copyright (c) 1995 Mika Kortelainen. All rights reserved.
+.\" Copyright (c) 1995 Bernd Ernesti and Klaus Burkert. All rights reserved.
+.\" Copyright (c) 1992, 1993
+.\" 	The Regents of the University of California. All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by Klaus Burkert,by Bernd
+.\"	Ernesti, by Michael van Elst, and by the University of California,
+.\"	Berkeley and its contributors.
+.\" 4. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.\" Thanks for Aspecs Oy (Finland) for the data book for the NIC used
+.\" in this card and also many thanks for the Resource Management Force
+.\" (QuickNet card manufacturer) and especially Daniel Koch for providing
+.\" me with the necessary 'inside' information to write the driver.
+.\"
+.\" This is partly based on other code:
+.\" - if_ed.c: basic function structure for Ethernet driver
+.\" - if_es.c: used as an example of -current driver
+.\"
+.\" The following requests are required for all man pages.
+.Dd Oct 5, 1995
+.Os NetBSD 1.0
+.Dt QN 4 amiga
+.Sh NAME
+.Nm qn
+.Nd Ethernet driver for Fujitsu MB86950 based boards
+.Sh SYNOPSIS
+.Cd "qn* at zbus0"
+.Sh DESCRIPTION
+The 
+.Nm
+interface provides access to the 10 Mb/s Ethernet network via the
+.Tn Fujitsu
+MB86950
+Ethernet chip set.
+.Pp
+Each of the host's network addresses
+is specified at boot time with an
+.Dv SIOCSIFADDR
+.Xr ioctl .
+The
+.Nm
+interface employs the address resolution protocol described in
+.Xr arp 4
+to dynamically map between Internet and Ethernet addresses on the local
+network.
+.Pp
+.Sh HARDWARE
+The
+.Nm
+interface supports the following Zorro II expansion cards:
+.Bl -tag -width "QuickNet" -offset indent
+.It Em QuickNet
+Resource Management Force's ethernet card, manufacturer\ 2011, product\ 2
+.El
+.Pp
+.Sh NOTES
+Multicasting not done yet. If the driver happens to lock up, you may use
+.Xr ifconfig
+to force the driver down and up again. This usually helps.
+.Pp
+.Sh HISTORY
+The
+.Nm
+interface first appeared in
+.Nx 1.0a
+.Sh SEE ALSO
+.Xr arp 4 ,
+.Xr ifconfig 8 ,
+.Xr inet 4 ,
+.Xr intro 4
diff --git a/share/man/man4/man4.amiga/ser.4 b/share/man/man4/man4.amiga/ser.4
new file mode 100644
index 00000000000..26124f6fdd6
--- /dev/null
+++ b/share/man/man4/man4.amiga/ser.4
@@ -0,0 +1,85 @@
+.\" Copyright (c) 1990, 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" the Systems Programming Group of the University of Utah Computer
+.\" Science Department.
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)dca.4	5.2 (Berkeley) 3/27/91
+.\"	$Id: ser.4,v 1.1 1995/10/18 08:44:27 deraadt Exp $
+.\"
+.Dd August 30, 1994
+.Dt SER 4 amiga
+.Os NetBSD 1.0
+.Sh NAME
+.Nm ser
+.Nd
+.Tn Amiga 8520
+serial communications interface
+.Sh SYNOPSIS
+.Cd "ser0 at mainbus0"
+.Sh DESCRIPTION
+The
+.Tn Amiga 8520
+controls, among other things, a single port
+.Tn EIA
+.Tn RS-232C
+.Pf ( Tn CCITT
+.Tn V.28 )
+communications interface with a single character buffer.
+Such an interface is built-in to all Amiga machines.
+.Pp
+Input and output for each line may set to one of following baud rates;
+50, 75, 110, 134.5, 150, 300, 600, 1200, 1800, 2400, 4800, 9600, 
+19200, 38400, 57600 or 76800.
+.Sh FILES
+.Bl -tag -width Pa
+.It Pa /dev/tty00
+.El
+.Sh DIAGNOSTICS
+.Bl -diag
+.It ser0: silo overflow.
+The single-character input
+.Dq silo
+has overflowed and incoming data has been lost.
+.It ser0: %d ring buffer overflows.
+The software based input ring buffer
+has overflowed %d times and incoming data has been lost.
+.El
+.Sh SEE ALSO
+.Xr tty 4
+.Sh HISTORY
+The
+.Tn Amiga
+.Nm
+device first appeared in
+.Nx 0.9a
+.Sh BUGS
+Data loss is possible on busy systems with baud rates greater than 300.
diff --git a/share/man/man4/man4.amiga/wesc.4 b/share/man/man4/man4.amiga/wesc.4
new file mode 100644
index 00000000000..90addfa8204
--- /dev/null
+++ b/share/man/man4/man4.amiga/wesc.4
@@ -0,0 +1,89 @@
+.\"
+.\" Copyright (c) 1994 Christian E. Hopps
+.\" 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 Christian E. Hopps.
+.\" 3. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.\"	$Id: wesc.4,v 1.1 1995/10/18 08:44:27 deraadt Exp $
+.\"
+.Dd August 31, 1994
+.Os NetBSD 1.0
+.Dt WESC 4 amiga
+.Sh NAME
+.Nm wesc
+.Nd Warp Engine low level SCSI interface
+.Sh SYNOPSIS
+.Cd "wesc0 at zbus0"
+.Sh DESCRIPTION
+The
+.Tn Amiga
+architecture uses a common machine independent scsi sub-system
+provided in the kernel source.  The machine independent 
+drivers that use this code access the hardware through a
+common interface. (see
+.Xr scsibus 4 )
+This common interface interacts with a machine dependent interface,
+such as
+.Nm wesc ,
+which then handles the hardware specific issues.
+.Pp
+The
+.Nm 
+interface handles things such as DMA and interrupts as well as
+actually sending commands, negotiating synchronous or asynchronous
+transfers and handling disconnect/reconnect of SCSI targets.
+The hardware that 
+.Nm
+uses is based on the NCR53c710 SCSI chip.
+.Sh HARDWARE
+The
+.Nm
+interface supports the following Zorro III expansion cards:
+.Bl -tag -width "WARP ENGINE" -offset indent
+.It Em WARP ENGINE
+MacroSystem Development Warp Engine internal SCSI, manufacturer\ 2203, product\ 19
+.El
+.Sh DIAGNOSTICS
+.Bl -diag
+.It wesc%s: abort %s: dstat %02x, sstat0 %02x sbcl %02x
+The scsi operation %s was aborted due to error.  Dstat, sstat and
+sbcl are registers within the NCR53c710 SCSI chip.
+.It siop id %d reset\n"
+The NCR53c710 SCSI chip has been reset and configure at id %d.
+.It SIOP interrupt: %x sts %x msg %x sbcl %x
+The NCR53c710 SCSI chip has interrupted unexpectedly.
+.It SIOP: SCSI Gross Error
+The NCR53c710 SCSI chip has indicated that it is confused.
+.It SIOP: Parity Error
+The NCR53c710 SCSI chip has indicated that it has detected a
+parity error on the SCSI bus.
+.Sh SEE ALSO
+.Xr scsibus 4
+.Sh HISTORY
+The
+.Nm 
+interface first appeared in
+.Nx 0.9a
diff --git a/share/man/man4/man4.amiga/zssc.4 b/share/man/man4/man4.amiga/zssc.4
new file mode 100644
index 00000000000..b3d86c5b84c
--- /dev/null
+++ b/share/man/man4/man4.amiga/zssc.4
@@ -0,0 +1,81 @@
+.\"
+.\" Copyright (c) 1994 Christian E. Hopps
+.\" 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 Christian E. Hopps.
+.\" 3. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.\"	$Id: zssc.4,v 1.1 1995/10/18 08:44:27 deraadt Exp $
+.\"
+.Dd August 31, 1994
+.Os NetBSD 1.0
+.Dt ZSSC 4 amiga
+.Sh NAME
+.Nm zssc
+.Nd Zeus low level SCSI interface
+.Sh SYNOPSIS
+.Cd "zssc0 at zbus0"
+.Sh DESCRIPTION
+The
+.Tn Amiga
+architecture uses a common machine independent scsi sub-system
+provided in the kernel source.  The machine independent 
+drivers that use this code access the hardware through a
+common interface. (see
+.Xr scsibus 4 )
+This common interface interacts with a machine dependent interface,
+such as
+.Nm zssc ,
+which then handles the hardware specific issues.
+.Pp
+The
+.Nm 
+interface handles things such as DMA and interrupts as well as
+actually sending commands, negotiating synchronous or asynchronous
+transfers and handling disconnect/reconnect of SCSI targets.
+The hardware that 
+.Nm
+uses is based on the NCR53c710 SCSI chip.
+.Sh DIAGNOSTICS
+.Bl -diag
+.It zssc%s: abort %s: dstat %02x, sstat0 %02x sbcl %02x
+The scsi operation %s was aborted due to error.  Dstat, sstat and
+sbcl are registers within the NCR53c710 SCSI chip.
+.It siop id %d reset\n"
+The NCR53c710 SCSI chip has been reset and configure at id %d.
+.It SIOP interrupt: %x sts %x msg %x sbcl %x
+The NCR53c710 SCSI chip has interrupted unexpectedly.
+.It SIOP: SCSI Gross Error
+The NCR53c710 SCSI chip has indicated that it is confused.
+.It SIOP: Parity Error
+The NCR53c710 SCSI chip has indicated that it has detected a
+parity error on the SCSI bus.
+.Sh SEE ALSO
+.Xr scsibus 4
+.Sh HISTORY
+The
+.Nm 
+interface first appeared in
+.Nx 0.9a
diff --git a/share/man/man4/man4.hp300/Makefile b/share/man/man4/man4.hp300/Makefile
new file mode 100644
index 00000000000..2d78d5551a7
--- /dev/null
+++ b/share/man/man4/man4.hp300/Makefile
@@ -0,0 +1,9 @@
+#	from: @(#)Makefile	5.1 (Berkeley) 6/29/90
+#	$Id: Makefile,v 1.1 1995/10/18 08:44:27 deraadt Exp $
+
+MAN=	autoconf.4 cons.4 ct.4 dca.4 dcl.4 dcm.4 dv.4 gb.4 grf.4 hil.4 \
+	intro.4 ite.4 le.4 mem.4 ppi.4 rb.4 rd.4 rmp.4 tc.4
+MLINKS=	mem.4 kmem.4
+MANSUBDIR=/hp300
+
+.include <bsd.prog.mk>
diff --git a/share/man/man4/man4.hp300/autoconf.4 b/share/man/man4/man4.hp300/autoconf.4
new file mode 100644
index 00000000000..7314c89f6e2
--- /dev/null
+++ b/share/man/man4/man4.hp300/autoconf.4
@@ -0,0 +1,142 @@
+.\" Copyright (c) 1990, 1991 Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)autoconf.4	5.2 (Berkeley) 3/27/91
+.\"	$Id: autoconf.4,v 1.1 1995/10/18 08:44:27 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt AUTOCONF 4 hp300
+.Os
+.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, printing out
+what it finds 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
+Autoconfiguration on the
+.Tn HP300 Ns s
+is similar to that on the
+.Tn VAX ,
+the primary difference is in the naming conventions.
+On the
+.Tn HP300 ,
+if devices exist which are not configured they will be ignored;
+if devices exist of unsupported type they will be ignored.
+.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 use
+.Sq Li rd0
+if it exists.
+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 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 hpib%d at sc%d, ipl %d.
+An
+.Tn HP-IB
+was found at sc%d (the select code)
+with ipl%d (interrupt priority level).
+.Tn UNIX
+will call it hpib%d.
+.Pp
+.It %s%d: %s.
+.It %s%d at hpib%d, slave %d.
+An
+.Tn HP-IB
+disk or tape controller was found.
+For disks
+.Ql %s%d
+will look like
+.Sq Li rd0 ,
+for tapes like
+.Sq Li ct0 .
+The
+.Ql %s
+in the first line will be a product type like ``7945A'' or ``9144''.
+The slave number comes from the address select switches on the drive.
+.Pp
+.It grf0 csr 0x560000
+.It grf%d at sc%d
+A bit mapped display was found either at the ``internal'' address (first case)
+or at some ``external'' select code (second case).
+If it exists, the internal display will always be unit 0.
+.Pp
+.It %s%d at sc%d, ipl %d flags %d
+Another peripheral controller was found at the indicated select code
+and with indicated interrupt priority level.
+.Ql %s
+will be one of
+.Xr dca 4
+(single-port serial interfaces),
+.Xr dcm 4
+(four-port serial interfaces), or
+.Xr le 4
+.Pf ( Tn LAN
+cards).
+The slave number comes from the address select switches on the interface card.
+.El
+.Sh SEE ALSO
+.Xr intro 4 ,
+.Xr boot 8 ,
+.Xr config 8
+.Rs
+.%T 4.3BSD for the HP300
+.%O in the distribution documentation package
+.Re
+.Sh HISTORY
+The
+.Nm autoconf
+feature
+.Ud -beta
diff --git a/share/man/man4/man4.hp300/cons.4 b/share/man/man4/man4.hp300/cons.4
new file mode 100644
index 00000000000..64a8bdaabf0
--- /dev/null
+++ b/share/man/man4/man4.hp300/cons.4
@@ -0,0 +1,79 @@
+.\" Copyright (c) 1990, 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" the Systems Programming Group of the University of Utah Computer
+.\" Science Department.
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)cons.4	5.2 (Berkeley) 3/27/91
+.\"	$Id: cons.4,v 1.1 1995/10/18 08:44:27 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt CONS 4 hp300
+.Os
+.Sh NAME
+.Nm cons
+.Nd
+.Tn HP300
+console interface
+.Sh DESCRIPTION
+This release supports a
+.Dq virtual
+console device used for
+.Em kernel printf
+messages and accessed in user mode via
+.Pa /dev/console .
+It is virtual in the sense that it is attached to a hardware interface
+at boot time.
+Currently the choices are limited to:
+a bit-mapped display acting as an
+.Em internal terminal emulator
+.Dq Tn ITE ,
+the builtin serial interface
+.Xr dca 4 ,
+or a
+.Xr null 4
+console in that order.
+.Sh FILES
+.Bl -tag -width /dev/console
+.It Pa /dev/console
+.El
+.Sh SEE ALSO
+.Xr tty 4 ,
+.Xr reboot 8
+.Sh HISTORY
+The
+.Nm
+device
+.Ud
+.Sh BUGS
+You should be able to specify potential console devices at
+.Xr config 8
+time.
diff --git a/share/man/man4/man4.hp300/ct.4 b/share/man/man4/man4.hp300/ct.4
new file mode 100644
index 00000000000..43c39844eca
--- /dev/null
+++ b/share/man/man4/man4.hp300/ct.4
@@ -0,0 +1,110 @@
+.\" Copyright (c) 1990, 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" the Systems Programming Group of the University of Utah Computer
+.\" Science Department.
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)ct.4	5.2 (Berkeley) 3/27/91
+.\"	$Id: ct.4,v 1.1 1995/10/18 08:44:27 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt CT 4 hp300
+.Os
+.Sh NAME
+.Nm \&ct
+.Nd
+.Tn CS/80
+cartridge tape interface
+.Sh SYNOPSIS
+.Cd "tape ct0 at hpib? slave ?"
+.Sh DESCRIPTION
+The cartridge tape interface as found in the 7946 and 9144 products
+provides a standard tape drive interface as described in
+.Xr mtio 4
+with the following exceptions:
+.Bl -enum
+.It
+There is only one density.
+.It
+Only the
+.Dq raw
+interface is supported.
+.It
+The
+.Dv MTIOCTOP
+.Xr ioctl 2
+is limited.
+In particular, the command,
+.Dv MTFSR
+is not supported.
+.It
+The
+.Dv MTIOCGET
+.Xr ioctl
+is not supported.
+.It
+The record size for read and write operations must be between
+1K and 64K inclusive.
+.El
+.Pp
+Special files
+.Pa rct0
+through
+.Pa rct3
+refer to rewind on close interfaces to drives 0 to 3.
+Files
+.Pa rct4
+through
+.Pa rct7
+refer to no-rewind interfaces.
+Files
+.Pa rct8
+through
+.Pa rct11
+refer to streaming rewind on close interfaces. (Only 9144 type devices
+can stream.)
+Lastly,
+.Pa rct12
+through
+.Pa rct15
+refer to streaming no-rewind interfaces.
+.Sh SEE ALSO
+.Xr mt 1 ,
+.Xr tar 1 ,
+.Xr tp 1 ,
+.Xr mtio 4 .
+.Sh HISTORY
+The
+.Nm \&ct
+driver
+.Ud
+.Sh BUGS
+Read and writes of less than 1024 bytes will not behave as expected.
diff --git a/share/man/man4/man4.hp300/dca.4 b/share/man/man4/man4.hp300/dca.4
new file mode 100644
index 00000000000..3d6968f416d
--- /dev/null
+++ b/share/man/man4/man4.hp300/dca.4
@@ -0,0 +1,90 @@
+.\" Copyright (c) 1990, 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" the Systems Programming Group of the University of Utah Computer
+.\" Science Department.
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)dca.4	5.2 (Berkeley) 3/27/91
+.\"	$Id: dca.4,v 1.1 1995/10/18 08:44:27 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt DCA 4 hp300
+.Os
+.Sh NAME
+.Nm dca
+.Nd
+.Tn HP 98644A
+communications interface
+.Sh SYNOPSIS
+.Cd "device dca0 at scode9 flags 0x1"
+.Sh DESCRIPTION
+The
+.Tn 98644A
+is a single port
+.Tn EIA
+.Tn RS-232C
+.Pf ( Tn CCITT
+.Tn V.28 )
+communications interface with a single character buffer.
+Such an interface is built-in to all series 300 machines.
+.Pp
+Input and output for each line may set to one of following baud rates;
+50, 75, 110, 134.5, 150, 300, 600, 1200, 1800, 2400, 4800, 9600 or
+19200.
+.Pp
+An optional argument
+.Ar flags
+may be set to 1 if the line should be treated as hard-wired
+with carrier always present or 0 if modem control is desired.
+.Sh FILES
+.Bl -tag -width Pa
+.It Pa /dev/tty0
+.El
+.Sh DIAGNOSTICS
+.Bl -diag
+.It dca%d: silo overflow.
+The single-character input
+.Dq silo
+has overflowed and incoming data has been lost.
+.El
+.Sh SEE ALSO
+.Xr tty 4
+.Sh HISTORY
+The
+.Nm
+driver
+.Ud
+.Sh BUGS
+Data loss is possible on busy systems with baud rates greater than 300.
+The
+.Nm dca
+has never been tested with modem control enabled or on anything but the
+built-in interface.
diff --git a/share/man/man4/man4.hp300/dcl.4 b/share/man/man4/man4.hp300/dcl.4
new file mode 100644
index 00000000000..6883f53522d
--- /dev/null
+++ b/share/man/man4/man4.hp300/dcl.4
@@ -0,0 +1,130 @@
+.\" Copyright (c) 1990, 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" the Systems Programming Group of the University of Utah Computer
+.\" Science Department.
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)dcl.4	5.2 (Berkeley) 3/27/91
+.\"	$Id: dcl.4,v 1.1 1995/10/18 08:44:27 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt DCL 4 hp300
+.Os
+.Sh NAME
+.Nm dcl
+.Nd
+.Tn HP
+98628A communications link
+.Sh SYNOPSIS
+.Cd "device dcl0 at scode? flags 0x1"
+.Sh DESCRIPTION
+The 98628A is a buffered
+.Tn EIA
+.Tn RS-232C
+.Pf ( Tn CCITT
+.Tn V.28 )
+communications interface.
+It has one port with full modem control.
+.Pp
+Input and output for each line may set to one of following baud rates;
+0, 50, 75, 110, 134.5, 150, 200, 300, 600, 1200, 1800, 2400, 4800,
+9600, 19200.
+.Pp
+An optional argument
+.Ar flags
+may be set to 1 if the line should be treated as hard-wired with
+carrier always present, or to 0 if modem control is desired.
+.Pp
+Use
+.Tn HP
+cable "98626 & 98628 opts.002,
+.Tn RS232-C
+.Tn DCE CABLE ,
+5061-4216" to attach non-modem devices.
+Use
+.Tn HP
+cable "98626 & 98628 opts.001,
+.Tn RS232-C
+.Tn DTE CABLE ,
+5061-4215" to attach modems.
+.Pp
+The 98628A has a 256 byte input silo and a 256 output silo. Input interrupts
+happen on a per character basis.
+.Pp
+The high water and low water marks in the kernel tty routines are completely
+inappropriate for a device like this with a large input buffer.  Don't use
+tandem mode if possible.  A fast system can handle input at 19.2K baud without
+receive overflow.
+.Pp
+For output to devices that make heavy use of
+.Tn XON/XOFF
+a write size of less
+then 256 will improve performance marginally.
+.Sh FILES
+.Bl -tag -width /dev/ttyl[0-9] -compact
+.It Pa /dev/ttyl[0-9]
+.El
+.Sh DIAGNOSTICS
+.Bl -diag
+.It dcl%d: error 0x%x RESET CARD.
+Where the errors are encoded:
+.Bd -unfilled -offset indent
+0x06 card failure
+0x0d uart receive overflow
+0x0e receive overflow
+0x0f missing external clock
+0x10 cts false too long
+0x11 lost carrier
+0x12 activity timeout
+0x13 connection not established
+0x19 illegal databits/parity
+0x1a register address out of range
+0x1b register value out of range
+0x-- unknown error
+.Ed
+.El
+.Sh SEE ALSO
+.Xr tty 4
+.Sh HISTORY
+The
+.Nm
+driver
+.Ud
+.Sh BUGS
+Breaks received at a faster rate then 1 break every second will be 
+recognized as a single break.
+.Pp
+Console use is not supported.
+.Pp
+The
+.Tn RS-422/423/499 ,
+.Tn MTS-DSN/DL
+modes of the card are not supported.
diff --git a/share/man/man4/man4.hp300/dcm.4 b/share/man/man4/man4.hp300/dcm.4
new file mode 100644
index 00000000000..291dd44e90d
--- /dev/null
+++ b/share/man/man4/man4.hp300/dcm.4
@@ -0,0 +1,103 @@
+.\" Copyright (c) 1990, 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" the Systems Programming Group of the University of Utah Computer
+.\" Science Department.
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)dcm.4	5.2 (Berkeley) 3/27/91
+.\"	$Id: dcm.4,v 1.1 1995/10/18 08:44:27 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt DCM 4 hp300
+.Os
+.Sh NAME
+.Nm dcm
+.Nd
+.Tn HP
+98642A communications multiplexer
+.Sh SYNOPSIS
+.Cd "device dcm0 at scode? flags 0xe"
+.Sh DESCRIPTION
+The
+.Tn 98642A
+is a four port
+.Tn EIA
+.Tn RS-232C
+.Pf ( Tn CCITT
+.Tn V.28 )
+communications
+multiplexer. The
+.Tn 98642A
+has three direct-connect ports and one port with
+full modem control.
+.Pp
+Input and output for each line may set to one of following baud rates;
+50, 75, 110, 134.5, 150, 300, 600, 1200, 1800, 2400, 4800,
+9600, 19200, 38400.
+.Pp
+.Ar Flags
+is usually specified as 0xe since 3 of the 4 ports (1-3) do not support
+modem control and should be treated as hard-wired with carrier always present.
+If port 0 does not have the need for modem control then flags can be specified
+as
+.Ql 0xf .
+.Pp
+Each port on the
+.Tn 98642A
+has a 128 byte input silo and a 16 byte output silo.
+Interrupts happen on a per character basis unless the interrupt
+rate for the card reaches 70 interrupts per second at which time the
+driver changes to a 16.7ms (60 interrupts per second) polling scheme until 
+the interrupt rate drops.
+.Sh FILES
+.Bl -tag -width /dev/tty0[0-9a-f] -compact
+.It Pa /dev/tty0[0-9a-f]
+.El
+.Sh DIAGNOSTICS
+.Bl -diag
+.It dcm%d port%d: silo overflow
+Input Silo has overflowed and incoming data
+has been lost.
+.Pp
+.It dcm%d port%d: uart overflow
+The 3 character buffer in the uart has
+overflowed.
+.El
+.Sh SEE ALSO
+.Xr tty 4
+.Sh HISTORY
+The
+.Nm
+driver
+.Ud
+.Sh BUGS
+Total throughput per card, all ports together, is limited to 76800 bits per
+second continuous input rate.
diff --git a/share/man/man4/man4.hp300/dv.4 b/share/man/man4/man4.hp300/dv.4
new file mode 100644
index 00000000000..9dc597272ff
--- /dev/null
+++ b/share/man/man4/man4.hp300/dv.4
@@ -0,0 +1,174 @@
+.\" Copyright (c) 1990, 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" the Systems Programming Group of the University of Utah Computer
+.\" Science Department.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)dv.4	5.2 (Berkeley) 3/27/91
+.\"	$Id: dv.4,v 1.1 1995/10/18 08:44:27 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt DV 4 hp300
+.Os
+.Sh NAME
+.Nm dv
+.Nd
+.Tn HP98730
+``DaVinci'' device interface
+.Sh DESCRIPTION
+This driver is for the
+.Tn HP98730
+and 98731 graphics device, also known as
+the DaVinci.  This driver has not been tested with all possible
+combinations of frame buffer boards and scan boards installed in the device.
+The driver merely checks for the existence of the device and does minimal set
+up.
+.Pp
+The DaVinci can be configured at either the ``internal'' address
+(frame buffer address 0x200000, control register space address 0x560000)
+or at an external select code less than 32.
+At the internal address it will be the ``preferred'' console device
+(see
+.Xr cons 4 ) .
+The hardware installation manual describes the procedure for
+setting these values.
+.Pp
+A user process communicates to the device initially by means of
+.Xr ioctl 2
+calls.  For the
+.Tn HP-UX
+.Xr ioctl
+calls supported, refer to
+.Tn HP-UX
+manuals.
+The
+.Bx
+calls supported are:
+.Bl -tag -width indent
+.It Dv GRFIOCGINFO
+Get Graphics Info
+.Pp
+Get info about device, setting the entries in the
+.Ar grfinfo
+structure, as defined in
+.Aq Pa hpdev/grfioctl.h .
+For the standard 98730, the number of planes should be 4.  The number of
+colors would therefore be 15, excluding black.  If one 98732A frame buffer
+board is installed, there will still be 4 planes, with the 4 planes on the
+colormap board becoming overlay planes.  With each additional 98732 frame
+buffer board 4 planes will be added up to a maximum of 32 planes total.
+.It Dv GRFIOCON
+Graphics On
+.Pp
+Turn graphics on by enabling
+.Tn CRT
+output.  The screen will come on, displaying
+whatever is in the frame buffer, using whatever colormap is in place.
+.It Dv GRFIOCOFF
+Graphics Off
+.Pp
+Turn graphics off by disabling output to the
+.Tn CRT .
+The frame buffer contents
+are not affected.
+.It Dv GRFIOCMAP
+Map Device to user space
+.Pp
+Map in control registers and frame buffer space. Once the device file is
+mapped, the frame buffer structure is accessible.  The structure describing
+the 98730 is defined in
+.Aq Pa hpdev/grf_dvreg.h .
+.El
+.Sh EXAMPLE
+This is a short segment of code showing how the device is opened and mapped
+into user process address space assuming that it is
+.Ql grf0 :
+.Bd -literal -offset indent
+struct dvboxfb *dvbox;
+u_char *Addr, frame_buffer;
+struct grfinfo gi;
+int disp_fd;
+
+disp_fd = open("/dev/grf0",1);
+
+if (ioctl (disp_fd, GRFIOCGINFO, &gi) < 0) return -1;
+
+(void) ioctl (disp_fd, GRFIOCON, 0);
+
+Addr = (u_char *) 0;
+if (ioctl (disp_fd, GRFIOCMAP, &Addr) < 0) {
+(void) ioctl (disp_fd, GRFIOCOFF, 0);
+return -1;
+}
+dvbox = (dvboxfb *) Addr;                  /* Control Registers   */
+frame_buffer=(u_char *)Addr+gi.gd_regsize; /* Frame buffer memory */
+.Ed
+.Sh FILES
+.Bl -tag -width /dev/MAKEDEV.hpux -compact
+.It Pa /dev/grf?
+.Bx
+special file
+.It Pa /dev/crt98730
+.It Pa /dev/ocrt98730
+.Tn HP-UX
+.Em starbase
+special files
+.It Pa /dev/MAKEDEV.hpux
+script for creating
+.Tn HP-UX
+special files
+.El
+.Sh DIAGNOSTICS
+None under
+.Bx .
+.Tn HP-UX
+.Tn CE.utilities
+must be used.
+.Sh ERRORS
+.Bl -tag -width [EINVAL]
+.It Bq Er ENODEV
+no such device.
+.It Bq Er EBUSY
+Another process has the device open.
+.It Bq Er EINVAL
+Invalid ioctl specification.
+.El
+.Sh SEE ALSO
+.Xr ioctl 2 ,
+.Xr grf 4 .
+.Sh HISTORY
+The
+.Nm
+driver
+.Ud
+.Sh BUGS
+Not tested for all configurations of scan board and frame buffer memory boards.
diff --git a/share/man/man4/man4.hp300/gb.4 b/share/man/man4/man4.hp300/gb.4
new file mode 100644
index 00000000000..962bc2ea6c9
--- /dev/null
+++ b/share/man/man4/man4.hp300/gb.4
@@ -0,0 +1,185 @@
+.\" Copyright (c) 1990, 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" the Systems Programming Group of the University of Utah Computer
+.\" Science Department.
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)gb.4	5.2 (Berkeley) 3/27/91
+.\"	$Id: gb.4,v 1.1 1995/10/18 08:44:27 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt GB 4 hp300
+.Os
+.Sh NAME
+.Nm gb
+.Nd
+.Tn HP98700
+``Gatorbox'' device interface
+.Sh DESCRIPTION
+This driver is for the
+.Tn HP98700
+and 98710 graphics devices, also known as
+the Gatorbox.  The term ``Gator'' will often be used, and it is not to be
+confused with ``Gator'' used in reference to an
+.Tn HP
+9837 or 200/237 machine.
+Also, the term Gatorbox is used for the 98700 alone, with the 98701 frame
+buffer memory or with the 98710 accelerator installed.  This driver merely
+checks for the existence of the device and does minimal set up, as it is
+expected the applications will initialize the device to their requirements.
+.Pp
+The 98700 can be used as the only graphics device on a system, in which case
+it will be used as the system console.  It can also be installed as a secondary
+display device.  For the first case, the
+.Tn HP
+.Tn 98287A M.A.D.
+interface card
+should be set to internal control space.  This will put the frame buffer at
+the DIO address 0x200000 and the control registers at 0x560000.
+At this address it will be the ``preferred'' console device (see
+.Xr cons 4 ) .
+For use as a secondary device,
+the 98287A should be set to frame buffer address 0x300000,
+and to an external select code.
+.Pp
+It should be noted that this configuration will conflict with the 98547
+display card which has a 2 megabyte frame buffer starting at address 0x200000.
+The 98700 should only be installed as a secondary device in a machine with a
+1 bit 98544 display card or 4 bit 98545 card.
+The
+.%T 98700H Installation Guide
+contains further configuration information.
+.Pp
+The
+.Xr ioctl 2
+calls supported by the
+.Bx
+system for the Gatorbox are:
+.Bl -tag -width indent
+.It Dv GRFIOCGINFO
+Get Graphics Info
+.Pp
+Get info about device, setting the entries in the
+.Em grfinfo
+structure, as defined in
+.Aq Pa hpdev/grfioctl.h .
+For the standard 98700, the number of planes should be 4.  The number of
+colors would therefore be 15, excluding black.  With the 98701 option installed
+there will be another 4 planes for a total of 8, giving 255 colors.
+.It Dv GRFIOCON
+Graphics On
+.Pp
+Turn graphics on by enabling
+.Tn CRT
+output.  The screen will come on, displaying
+whatever is in the frame buffer, using whatever colormap is in place.
+.It Dv GRFIOCOFF
+Graphics Off
+.Pp
+Turn graphics off by disabling output to the
+.Tn CRT .
+The frame buffer contents
+are not affected.
+.It Dv GRFIOCMAP
+Map Device to user space
+.Pp
+Map in control registers and framebuffer space. Once the device file is
+mapped, the frame buffer structure is accessible.
+The frame buffer structure describing the 98700
+is given in
+.Aq Pa hpdev/grf_gbreg.h .
+.It Dv GRFIOCUNMAP
+Unmap Device
+.Pp
+Unmap control registers and framebuffer space.
+.Pp
+For further information about the use of ioctl see the man page.
+.El
+.Sh EXAMPLE
+A small example of opening, mapping and using the device is given below.
+For more examples of the details on the behavior of the device, see the device
+dependent source files for the X Window System, in the
+.Pa /usr/src/new/X/libhp.fb
+directory.
+.Bd -literal -offset indent
+struct gboxfb *gbox;
+u_char *Addr, frame_buffer;
+struct grfinfo gi;
+int disp_fd;
+
+disp_fd = open("/dev/grf0",1);
+
+if (ioctl (disp_fd, GRFIOCGINFO, &gi) < 0) return -1;
+
+(void) ioctl (disp_fd, GRFIOCON, 0);
+
+Addr = (u_char *) 0;
+if (ioctl (disp_fd, GRFIOCMAP, &Addr) < 0) {
+(void) ioctl (disp_fd, GRFIOCOFF, 0);
+return -1;
+}
+gbox = (gboxfb *) Addr;                         /* Control Registers   */
+frame_buffer = (u_char *) Addr + gi.gd_regsize; /* Frame buffer memory */
+.Ed
+.Sh FILES
+.Bl -tag -width /dev/crt98700 -compact
+.It Pa /dev/grf?
+.Bx
+special file
+.It Pa /dev/crt98700
+.Tn HP-UX
+.Em starbase
+special file
+.El
+.Sh DIAGNOSTICS
+None under
+.Bx .
+.Tn HP-UX
+The
+.Tn CE.utilities/Crtadjust
+programs must be used.
+.Sh ERRORS
+.Bl -tag -width [EINVAL]
+.It Bq Er ENODEV
+no such device.
+.It Bq Er EBUSY
+Another process has the device open.
+.It Bq Er EINVAL
+Invalid ioctl specification.
+.El
+.Sh SEE ALSO
+.Xr ioctl 2 ,
+.Xr grf 4
+.Sh HISTORY
+The
+.Nm
+driver
+.Ud
diff --git a/share/man/man4/man4.hp300/grf.4 b/share/man/man4/man4.hp300/grf.4
new file mode 100644
index 00000000000..733de76ac6b
--- /dev/null
+++ b/share/man/man4/man4.hp300/grf.4
@@ -0,0 +1,214 @@
+.\" Copyright (c) 1990, 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" the Systems Programming Group of the University of Utah Computer
+.\" Science Department.
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)grf.4	5.3 (Berkeley) 7/31/91
+.\"	$Id: grf.4,v 1.1 1995/10/18 08:44:28 deraadt Exp $
+.\"
+.Dd July 31, 1991
+.Dt GRF 4 hp300
+.Os
+.Sh NAME
+.Nm grf
+.Nd
+.Tn HP
+graphics frame buffer device interface
+.Sh DESCRIPTION
+This is a generic description of the frame buffer device interface.
+The devices to which this applies are the 98544, 98545 and 98547
+Topcat display cards (also known as
+.Tn HP300H
+devices),
+the 98548, 98549 and 98550
+Catseye display cards,
+the 98700
+Gatorbox graphics box,
+the 98720
+Renaissance graphics box,
+and the 98730
+DaVinci graphics box.
+.Pp
+Use of the devices can be effectively approached from two directions.
+The first is through
+.Tn HP-UX
+.Em Starbase
+routines, the second is by direct control in the
+.Bx
+environment.
+In order to use the Starbase libraries,
+code must be compiled in an
+.Tn HP-UX
+environment, either by doing so on an
+.Tn HP-UX
+machine and transferring the binaries to the
+.Bx
+machine, or by compilation
+with the use of the
+.Xr hpux 1
+command.
+Applications using Starbase libraries have been run successfully
+on
+.Bx
+machines using both of these compilation techniques.
+.Pp
+Direct compilation,
+such as that used for the X Window System servers, has also been successful.
+Examples of some frame buffer operations can be found in
+the device dependent X Window system sources, for example the
+.Pa /usr/src/new/X/libhp.fb
+directory.  These files contain examples of device dependent color map
+initialization, frame buffer operations, bit moving routines etc.
+.Pp
+The basic programming of the
+.Nm grf Ns ?
+devices involves opening the device
+file, mapping the control registers and frame buffer addresses into user
+space, and then manipulating the device as the application requires.
+The address mapping is controlled by an
+.Xr ioctl 2
+call to map the device into user space, and an unmap call when finished.
+The ioctls supported by
+.Bx
+are:
+.Bl -tag -width indent
+.It Dv GRFIOCGINFO
+Get Graphics Info
+.Pp
+Get info about device, setting the entries in the
+.Em grfinfo
+structure, as defined in <hpdev/grfioctl.h>:
+.Bd -literal
+struct	grfinfo {
+	int	gd_id;		/* HPUX identifier */
+	caddr_t	gd_regaddr;	/* control registers physaddr */
+	int	gd_regsize;	/* control registers size */
+	caddr_t	gd_fbaddr;	/* frame buffer physaddr */
+	int	gd_fbsize;	/* frame buffer size */
+	short	gd_colors;	/* number of colors */
+	short	gd_planes;	/* number of planes */
+/* new stuff */
+	int	gd_fbwidth;	/* frame buffer width */
+	int	gd_fbheight;	/* frame buffer height */
+	int	gd_dwidth;	/* displayed part width */
+	int	gd_dheight;	/* displayed part height */
+	int	gd_pad[6];	/* for future expansion */
+};
+.Ed
+.It Dv GRFIOCON
+Graphics On
+.Pp
+Turn graphics on by enabling
+.Tn CRT
+output.  The screen will come on, displaying
+whatever is in the frame buffer, using whatever colormap is in place.
+.It Dv GRFIOCOFF
+Graphics Off
+.Pp
+Turn graphics off by disabling output to the
+.Tn CRT .
+The frame buffer contents
+are not affected.
+.It Dv GRFIOCMAP
+Map Device to user space
+.Pp
+Map in control registers and framebuffer space. Once the device file is
+mapped, the frame buffer structure is accessible.
+.It Dv GRFIOCUNMAP
+Unmap Device
+.Pp
+Unmap control registers and framebuffer space.
+.El
+.Pp
+For further information about the use of ioctl see the man page.
+.Sh EXAMPLE
+This short code fragment is an example of opening some graphics device and
+mapping in the control and frame buffer space:
+.Bd -literal
+#define GRF_DEV <some_graphics_device>  /* /dev/grfN */
+{
+	struct fbstruct *regs;  /*  fbstruct = gboxfb, rboxfb, etc. */
+	u_char *Addr, frame_buffer;
+	struct grfinfo gi;
+	int disp_fd;
+
+	disp_fd = open(GRF_DEV,1);
+	if (ioctl (disp_fd, GRFIOCGINFO, &gi) < 0) return -1;
+	(void) ioctl (disp_fd, GRFIOCON, 0);
+
+	Addr = (u_char *) 0;
+	if (ioctl (disp_fd, GRFIOCMAP, &Addr) < 0) {
+		(void) ioctl (disp_fd, GRFIOCOFF, 0);
+		return -1;
+	}
+	regs = (fbstruct *) Addr;               /* Control Registers   */
+	frame_buffer = (u_char *) Addr + gi.gd_regsize; /* Frame buffer mem */
+}
+.Ed
+.Sh FILES
+.Bl -tag -width /dev/*crt*? -compact
+.It Pa /dev/grf?
+.Bx
+interface special files
+.It Pa /dev/*crt*
+.Tn HP-UX
+.Em starbase
+interface special files
+.El
+.Sh DIAGNOSTICS
+None under
+.Bx .
+.Tn HP-UX
+The
+.Tn CE.utilities/Crtadjust
+programs must be used for each specific device.
+.Sh ERRORS
+.Bl -tag -width [EINVAL]
+.It Bq Er ENODEV
+no such device.
+.It Bq Er EBUSY
+Another process has the device open.
+.It Bq Er EINVAL
+Invalid ioctl specification.
+.El
+.Sh SEE ALSO
+.Xr ioctl 2 ,
+.Xr dv 4 ,
+.Xr gb 4 ,
+.Xr rb 4 ,
+.Xr tc 4 ,
+.Xr hil 4
+.Sh HISTORY
+The
+.Nm
+driver
+.Ud
diff --git a/share/man/man4/man4.hp300/hil.4 b/share/man/man4/man4.hp300/hil.4
new file mode 100644
index 00000000000..ff60307d48c
--- /dev/null
+++ b/share/man/man4/man4.hp300/hil.4
@@ -0,0 +1,380 @@
+.\" Copyright (c) 1990, 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" the Systems Programming Group of the University of Utah Computer
+.\" Science Department.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)hil.4	5.2 (Berkeley) 3/27/91
+.\"	$Id: hil.4,v 1.1 1995/10/18 08:44:28 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt HIL 4 hp300
+.Os
+.Sh NAME
+.Nm hil
+.Nd Human Interface Link device driver
+.Sh DESCRIPTION
+The Human Interface Link
+.Pq Tn HIL
+is the interface used by the Series
+300 computers to connect devices such as keyboards, mice, control knobs,
+and
+.Tn ID
+modules to the machine. 
+.Pp
+Special files
+.Pa /dev/hil[1-7]
+refer to physical
+.Tn HIL
+devices 1 through 7.
+.Pa /dev/hil0
+refers to the ``loop'' pseudo-device and is used for the queue
+allocation commands described below.
+In the current implementation,
+there can only be one keyboard and it must be the first device
+.Pq Li hil1 .
+.Pp
+The device file that corresponds to a particular
+.Tn HIL
+device is determined
+by the order of the devices on the loop. For instance, if the
+.Tn ID
+module
+is the second physical device on the loop, then
+.Pa /dev/hil2
+is the special
+file that should be used for communication with the module.
+.Pp
+Communication with an
+.Tn HIL
+device is begun with an
+.Em open
+system call.
+A process may open a device already opened by another process unless
+the process is operating in
+.Tn HP-UX
+compatibility mode
+in which case it requires exclusive use of the device, or
+another process has the device open and is using
+.Tn HP-UX
+style
+device access (see
+.Dv HILIOCHPUX
+below).
+.Pp
+Input data from a device are obtained in one of two ways.
+Processes may use an
+.Tn HP-UX
+style interface in which the
+.Xr read 2
+system call is used to get fixed-size input packets,
+or they can use a
+.Em shared-queue
+interface.
+The shared-queue interface avoids the system call overhead associated with
+the
+.Tn HP-UX
+read interface by sharing a region of memory between the system
+and a user process.
+This region consists of a circular list of 255 event packets,
+and a header containing the size of the queue, and its head and tail indices.
+The system deposits event data at the tail of the queue,
+a process extracts it from the head.
+Extracting an event is done by copying it from the queue and then updating
+the head appropriately (i.e. head = (head + 1) % qsize).
+It is up to the process to ensure that packets are removed from the
+queue quickly enough to prevent the queue from filling.
+The system, when it determines that the queue is full,
+will ignore future packets from the device.
+Devices are
+.Em mapped
+to queues via an
+.Xr ioctl 2.
+More than one device can be mapped to a single queue and one device can
+be mapped to several queues.
+Queues are implicitly unmapped by a
+.Xr fork 2
+and thus,
+cannot be shared between processes.
+.Pp
+Choosing the type of interface is done on a per device basis using
+an
+.Xr ioctl ,
+but each device can only have one interface at any given time.
+.Pp
+.Em Select
+may be used with either interface to detect when input data are present.
+With the read interface, selecting indicates when there is input for a
+given device.
+With the shared-queue interface, selecting on the loop pseudo-device
+.Pq Li hil0
+indicates when data are present from any device on any queue
+while selecting on an individual device indicates when data are present
+for that device on any queue.
+.Pp
+.Em Close
+shuts down the file descriptor associated with the
+.Tn HIL
+device.
+The last close (system-wide) of any device removes that device
+from all queues it was mapped to while the last close of the loop
+pseudo-device unmaps all devices and deallocates all queues.
+.Pp
+.Xr Ioctl 2
+is used to control the
+.Tn HIL
+device.
+The ioctl commands (see
+.Aq Pa hpdev/hilioctl.h )
+listed below are separated into two groups.
+The first are those which provide functions identical to
+.Tn HP-UX .
+Refer to
+.Xr hil 7
+in the
+.Tn HP-UX
+documentation for more
+complete descriptions of these ioctls.
+The second set of ioctls are specific to this implementation and are
+primarily related to the shared-queue interface.
+.Bl -tag -width HILIOCARO
+.It Dv HILIOCID
+Identify and Describe
+.Pp
+The device will return up to 11 bytes of information describing the
+type and characteristics of the device.
+At the very least, 2 bytes of information,
+the device
+.Tn ID ,
+and the Describe Record Header will be returned.
+Identical to the
+.Tn HP-UX
+.Dv HILID
+ioctl.
+.It Dv HILIOCSC
+Report Security Code
+.Pp
+Request the security code record from a device. The security code can
+vary from 1 byte to 15, and is only supported by some
+.Tn HIL
+devices.
+Identical to the
+.Tn HP-UX
+.Dv HILSC
+ioctl.
+.It Dv HILIOCRN
+Report Name
+.Pp
+An ascii string of up to 15 bytes in length that describes the device
+is returned.
+Identical to the
+.Tn HP-UX
+.Dv HILRN
+ioctl.
+.It Dv HILIOCRS
+Report Status
+.Pp
+An ascii string of up to 15 bytes in length that describes the current
+status of the device is returned.
+Identical to the
+.Tn HP-UX
+.Dv HILRS
+ioctl.
+.It Dv HILIOCED
+Extended Describe
+.Pp
+Additional information of up to 15 bytes is returned describing the device.
+This ioctl is similar to
+.Tn HILIOCID ,
+which must be used first
+to determine if the device supports extended describe.
+Identical to the
+.Tn HP-UX
+.Dv HILED
+ioctl.
+.It Dv HILIOCAROFF
+Disable Auto Repeat
+.Pp
+Turn off auto repeat on the keyboard while it is cooked mode.
+Identical to the
+.Tn HP-UX
+.Dv HILDKR
+ioctl.
+.It Dv HILIOCAR1
+Enable Auto Repeat
+.Pp
+Turn on auto repeat on the keyboard while it is in raw mode.
+The repeat rate is set to 1/30th of a second.
+Identical to the
+.Tn HP-UX
+.Dv HILER1
+ioctl.
+.It Dv HILIOCAR2
+Enable Auto Repeat
+.Pp
+Turn on auto repeat on the keyboard while it is in raw mode.
+The repeat rate is set to 1/60th of a second.
+Identical to the
+.Tn HP-UX
+.Dv HILER2
+ioctl.
+.Pp
+The following ioctls are specific to this implementation:
+.It Dv HILIOCBEEP
+Beep
+.Pp
+Generate a keyboard beep as defined by
+.Ar arg .
+.Ar Arg
+is a pointer to two bytes of information,
+the first is the duration of the beep (microseconds),
+the second is the frequency of the beep.
+.It Dv HILIOCALLOCQ
+Allocate Queue
+.Pp
+Allocate and map into user space,
+an
+.Tn HILQ
+structure as defined in
+.Aq Pa hpdev/hilioctl.h .
+.Ar Arg
+is a pointer to a
+.Ar hilqinfo
+structure (also described in
+.Aq Pa hpdev/hilioctl.h )
+consisting of a
+.Pa qid
+and an
+.Pa addr .
+If
+.Pa addr
+is non-zero it specifies where in the address space to map the queue.
+If zero, the system will select a convenient location and fill in
+.Pa addr .
+.Pa Qid
+is filled in by the system and
+is a small integer used to uniquely identify this queue.
+This ioctl can only be issued to the loop pseudo-device.
+.It Dv HILIOCFREEQ
+Free Queue
+.Pp
+Release a previously allocated
+.Tn HIL
+event queue,
+unmapping it from the user's address space.
+.Ar Arg
+should point to a
+.Ar hilqinfo
+structure which contains the
+.Ar qid
+of the queue to be released.
+All devices that are currently mapped to the queue are unmapped.
+This ioctl can only be issued to the loop pseudo-device.
+.It Dv HILIOCMAPQ
+Map Device to Queue
+.Pp
+Maps this device to a previously allocated
+.Tn HIL
+event queue.
+.Ar Arg
+is a pointer to an integer containing the
+.Ar qid
+of the queue.
+Once a device is mapped to a queue,
+all event information generated by the device will be placed
+into the event queue at the tail.
+.It Dv HILIOCUNMAPQ
+Unmap Device from Queue
+.Pp
+Unmap this device from a previously allocated
+.Tn HIL
+event queue.
+.Ar Arg
+is a pointer to an integer containing the
+.Ar qid
+for the queue.
+Future events from the device are no longer placed on the event queue.
+.It Dv HILIOCHPUX
+Use HP-UX Read Interface
+.Pp
+Use
+.Tn HP-UX
+semantics for gathering data from this device.
+Instead of placing input events for the device on a queue,
+they are placed, in
+.Tn HP-UX
+format, into a buffer from which they
+can be obtained via
+.Xr read 2 .
+This interface is provided for backwards compatibility.
+Refer to the
+.Tn HP-UX
+documentation for a description of the event packet.
+.El
+.Sh FILES
+.Bl -tag -width /dev/hil[2-7] -compact
+.It Pa /dev/hil0
+.Tn HIL
+loop pseudo device.
+.It Pa /dev/hil1
+.Tn HIL
+keyboard device.
+.It Pa /dev/hil[2-7]
+Individual
+.Tn HIL
+loop devices.
+.El
+.Sh ERRORS
+.Bl -tag -width [EINVAL]
+.It Bq Er ENODEV
+no such HIL loop device.
+.It Bq Er ENXIO
+HIL loop is inoperative.
+.It Bq Er EBUSY
+Another HP-UX process has the device open, or another
+.Bx
+process has the
+device open, and is using it in
+.Tn HP-UX
+mode.
+.It Bq Er EINVAL
+Invalid
+.Xr ioctl
+specification.
+.It Bq Er EMFILE
+No more shared queues available.
+.El
+.Sh HISTORY
+The
+.Nm
+interface
+.Ud
diff --git a/share/man/man4/man4.hp300/intro.4 b/share/man/man4/man4.hp300/intro.4
new file mode 100644
index 00000000000..db77f858f29
--- /dev/null
+++ b/share/man/man4/man4.hp300/intro.4
@@ -0,0 +1,139 @@
+.\" Copyright (c) 1990, 1991 Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)intro.4	5.2 (Berkeley) 3/27/91
+.\"	$Id: intro.4,v 1.1 1995/10/18 08:44:28 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt INTRO 4 hp300
+.Os
+.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 /usr/adm/messages
+due to errors in device operation;
+see
+.Xr syslogd 8
+for more information.
+.Pp
+This section contains both devices
+which may be configured into the system
+and network related information.
+The networking support is introduced in
+.Xr netintro 4 .
+.Sh HP DEVICE SUPPORT
+This section describes the hardware supported on the
+.Tn HP
+9000/300 series.
+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 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
+and, if found, enable the software support for it.
+If a device does not respond at autoconfiguration
+time it is not accessible at any time afterwards.
+To enable a device which did not autoconfigure,
+the system will have to be rebooted.
+.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 intro 4 ,
+.Xr autoconf 4 ,
+.Xr config 8 .
+.Rs
+.%T "Building 4.3 BSD UNIX Systems with Config (SMM: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.
+Occasionally, new devices of a similar type may be added
+simply by creating appropriate table entries in the driver;
+for example, new
+.Tn CS/80
+drives.
+.Bl -column grf/ite -offset indent
+ct	7946/9144 CS/80 cartridge tape
+dca	98644 built-in serial interface
+dcl	HP 98628A communications link
+dcm	HP 98642A communications multiplexer
+dma	98620B DMA controller
+dv	HP98730 ``DaVinci'' device interface
+gb	 HP98700 ``Gatorbox'' device interface
+grf/ite	Topcat/Gatorbox/Renaissance frame buffer
+hil	HIL interface
+hpib	Built-in and 98625 HP-IB interface
+ite	HP Internal Terminal Emulator
+le	98643 Lance-based ethernet interface
+mem	main memory
+ppi	HP-IB printer/plotter interface
+rb	HP98720 ``Renaissance'' device interface
+rd	CS/80 disk interface
+rmp	HP Remote Maintenance Protocol family
+st	CCS SCSI tape drive
+tc	HP98544-98550 ``Topcat'' and ``Catseye'' device interface
+.El
+.Sh HISTORY
+The
+.Tn HP300
+.Nm intro
+appeared in
+.Bx 4.3 Reno .
diff --git a/share/man/man4/man4.hp300/ite.4 b/share/man/man4/man4.hp300/ite.4
new file mode 100644
index 00000000000..4ef50690a49
--- /dev/null
+++ b/share/man/man4/man4.hp300/ite.4
@@ -0,0 +1,171 @@
+.\" Copyright (c) 1990, 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" the Systems Programming Group of the University of Utah Computer
+.\" Science Department.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)ite.4	5.2 (Berkeley) 3/27/91
+.\"	$Id: ite.4,v 1.1 1995/10/18 08:44:28 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt ITE 4 hp300
+.Os
+.Sh NAME
+.Nm ite
+.Nd
+.Tn HP
+Internal Terminal Emulator
+.Sh DESCRIPTION
+.Tn TTY
+special files of the form ``ttye?''
+are interfaces to the
+.Tn HP ITE
+for bit-mapped displays as implemented under
+.Bx .
+An
+.Tn ITE
+is the main system console on most
+.Tn HP300
+workstations and
+is the mechanism through which a user communicates with the machine.
+If more than one display exists on a system,
+any or all can be used as
+.Tn ITE Ns s
+with the limitation that only the first
+one opened will have a keyboard (since only one keyboard is supported).
+.Pp
+.Tn ITE
+devices use the
+.Tn HP-UX
+.Sq Li 300h
+.Xr termcap 5
+or
+.Xr terminfo 5
+entries.
+However, as currently implemented,
+the
+.Tn ITE
+does not support the full range of
+.Tn HP-UX
+capabilities for this device.
+Missing are multiple colors, underlining, blinking, softkeys,
+programmable tabs, scrolling memory and keyboard arrow keys.
+The keyboard does not have any of the international character
+support of
+.Tn HP Ns 's
+.Tn NLS
+system.
+It does use the left and right
+.Em extend char
+keys as meta keys, in that it will set the eighth bit of the character code.
+.Pp
+Upon booting, the kernel will first look for an
+.Tn ITE
+device
+to use as the system console
+.Pq Pa /dev/console .
+If a display exists at any hardware address, it will be the console.
+The kernel looks for, in order:
+a 98544, 98545, or 98547 Topcat display,
+a 98700 Gatorbox at a supported address (see
+.Xr gb 4 ) ,
+or a 98720 Renaissance at a supported address (see
+.Xr rb 4 ) .
+Currently there is no
+.Tn ITE
+support for the
+98548, 98549, 98550 and 98556 boards.
+.Pp
+When activated as an
+.Tn ITE
+(special file opened),
+all displays go through a standard initialization sequence.
+The frame buffer is cleared,
+the
+.Tn ROM
+fonts are unpacked and loaded into off-screen storage and
+a cursor appears.
+The
+.Tn ITE
+initialization routine also sets the colormap entry used to white.
+Variable colors are not used, mainly for reasons of simplicity.
+The font pixels are all set to 0xff and the colormap entry corresponding
+to all planes is set to R=255, G=255 and B=255.
+The actual number of planes used to display the characters depends
+on the hardware installed.
+Finally, if the keyboard
+.Tn HIL
+device is not already assigned to another
+.Tn ITE
+device, it is placed in ``cooked'' mode and assigned to this
+.Tn ITE .
+.Pp
+On most systems,
+a display is used both as an
+.Tn ITE
+.Pf ( Pa /dev/ttye?
+aka
+.Pa /dev/console )
+and as a graphics device
+.Pq /dev/grf? .
+In this environment,
+there is some interaction between the two uses that should be noted.
+For example, opening
+.Pa /dev/grf0
+will deactivate the
+.Tn ITE ,
+that is, write over whatever may be on the
+.Tn ITE
+display.
+When the graphics application is finished and
+.Pa /dev/grf0
+closed,
+the
+.Tn ITE
+will be reinitialized with the frame buffer cleared
+and the
+.Tn ITE
+colormap installed.
+.Sh DIAGNOSTICS
+None under
+.Bx .
+.Sh SEE ALSO
+.Xr grf 4 ,
+.Xr hil 4 ,
+.Xr gb 4 ,
+.Xr rb 4 ,
+.Xr tc 4
+.Sh HISTORY
+The
+.Nm
+driver
+.Ud
diff --git a/share/man/man4/man4.hp300/le.4 b/share/man/man4/man4.hp300/le.4
new file mode 100644
index 00000000000..2f5beeb62ed
--- /dev/null
+++ b/share/man/man4/man4.hp300/le.4
@@ -0,0 +1,110 @@
+.\" Copyright (c) 1990, 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" the Systems Programming Group of the University of Utah Computer
+.\" Science Department.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)le.4	5.2 (Berkeley) 3/27/91
+.\"	$Id: le.4,v 1.1 1995/10/18 08:44:28 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt LE 4 hp300
+.Os
+.Sh NAME
+.Nm le
+.Nd
+.Tn HP AMD
+7990
+.Tn LANCE
+Ethernet interface
+.Sh SYNOPSIS
+.Cd "device le0 at scode?"
+.Sh DESCRIPTION
+The
+.Nm le
+interface provides access to a 10 Mb/s Ethernet network via the
+.Tn AMD
+7990
+.Tn LANCE
+Ethernet chip set.
+.Pp
+Each of the host's network addresses
+is specified at boot time with an
+.Dv SIOCSIFADDR
+.Xr ioctl .
+The
+.Xr le
+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 use of ``trailer'' encapsulation to minimize copying data on
+input and output is supported by the interface but offers no advantage
+due to the large
+.Tn HP
+page size.
+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 le%d: hardware address %s.
+This is a normal autoconfiguration message noting the 6 byte physical
+ethernet address of the adapter.
+.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
+The following message indicate a possible hardware error performing
+the indicated operation during autoconfiguration or initialization.
+.Pp
+.It le%d: init timeout, stat = 0x%x.
+The hardware did not respond to an initialize command during reset.
+The reset procedure continues anyway.
+.El
+.Sh SEE ALSO
+.Xr intro 4 ,
+.Xr inet 4 ,
+.Xr arp 4
+.Sh HISTORY
+The
+.Nm le
+driver
+.Ud
diff --git a/share/man/man4/man4.hp300/mem.4 b/share/man/man4/man4.hp300/mem.4
new file mode 100644
index 00000000000..c2163a9b2db
--- /dev/null
+++ b/share/man/man4/man4.hp300/mem.4
@@ -0,0 +1,87 @@
+.\" Copyright (c) 1990, 1991 Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)mem.4	5.2 (Berkeley) 3/27/91
+.\"	$Id: mem.4,v 1.1 1995/10/18 08:44:28 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt MEM 4 hp300
+.Os
+.Sh NAME
+.Nm mem ,
+.Nm kmem
+.Nd main memory
+.Sh DESCRIPTION
+The 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.
+An error will be returned if an attempt is made to reference
+an offset outside of
+.Nm /dev/mem .
+.Pp
+Kernel virtual memory is accessed via the file
+.Nm /dev/kmem
+in the same manner as
+.Nm /dev/mem .
+Only kernel virtual addresses that are currently mapped to memory are allowed.
+.Sh HP300
+On the
+.Tn HP300 ,
+the last byte of physical memory is always
+.Li 0xFFFFFFFF .
+Therefore, on an
+.Tn HP300
+with
+8Mb of memory, physical memory would start
+at
+.Li 0xFF800000 .
+On the
+.Tn HP300 ,
+kernel virtual memory runs from
+.Li 0
+to about
+.Li 0x2400000 .
+.Sh FILES
+.Bl -tag -width /dev/kmem -compact
+.It Pa /dev/mem
+.It Pa /dev/kmem
+.El
+.Sh HISTORY
+The files
+.Nm mem
+and
+.Nm kmem
+appeared in
+.At v6 .
diff --git a/share/man/man4/man4.hp300/ppi.4 b/share/man/man4/man4.hp300/ppi.4
new file mode 100644
index 00000000000..555c4c957c0
--- /dev/null
+++ b/share/man/man4/man4.hp300/ppi.4
@@ -0,0 +1,83 @@
+.\" Copyright (c) 1990, 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" the Systems Programming Group of the University of Utah Computer
+.\" Science Department.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)ppi.4	5.2 (Berkeley) 3/27/91
+.\"	$Id: ppi.4,v 1.1 1995/10/18 08:44:28 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt PPI 4 hp300
+.Os
+.Sh NAME
+.Nm ppi
+.Nd
+.Tn HP-IB
+printer/plotter interface
+.Sh SYNOPSIS
+.Cd "device ppi0 at hpib0 slave 5"
+.Sh DESCRIPTION
+The
+.Nm ppi
+interface provides a means of communication with
+.Tn HP-IB
+printers and plotters.
+.Pp
+Special files
+.Pa ppi0
+through
+.Pa ppi7
+are used to access the devices, with the digit at the end
+of the filename referring to the bus address of the device.
+Current versions of the autoconf code can not probe for these
+devices, so the device entry in the configuration file must be
+fully qualified.
+.Pp
+The device files appear as follows:
+.Bd -literal -offset indent
+"crw-rw-rw-  1 root      11,   0 Dec 21 11:22 /dev/ppi"
+.Ed
+.Sh DIAGNOSTICS
+None.
+.Sh SEE ALSO
+.Xr hpib 4 .
+.Sh HISTORY
+The
+.Nm
+interface
+.Ud
+.Sh BUGS
+This driver is very primitive, it handshakes data out byte by byte.
+It should use
+.Tn DMA
+if possible.
diff --git a/share/man/man4/man4.hp300/rb.4 b/share/man/man4/man4.hp300/rb.4
new file mode 100644
index 00000000000..a476c698857
--- /dev/null
+++ b/share/man/man4/man4.hp300/rb.4
@@ -0,0 +1,177 @@
+.\" Copyright (c) 1990, 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" the Systems Programming Group of the University of Utah Computer
+.\" Science Department.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)rb.4	5.2 (Berkeley) 3/27/91
+.\"	$Id: rb.4,v 1.1 1995/10/18 08:44:28 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt RB 4 hp300
+.Os
+.Sh NAME
+.Nm rb
+.Nd
+.Tn HP98720
+``Renaissance'' device interface
+.Sh DESCRIPTION
+This driver is for the
+.Tn HP98720
+and 98721 graphics device, also known as
+the Renaissance.  This driver has not been tested with all possible
+combinations of frame buffer boards and scan boards installed in the device.
+The driver merely checks for the existence of the device and does minimal set
+up.
+.Pp
+The Renaissance can be configured at either the ``internal'' address
+(frame buffer address 0x200000, control register space address 0x560000)
+or at an external select code less than 32.
+At the internal address it will be the ``preferred'' console device
+(see
+.Xr cons 4 ) .
+The hardware installation manual describes the procedure for
+setting these values.
+.Pp
+A user process communicates to the device initially by means of
+.Xr ioctl 2
+calls.  For the
+.Tn HP-UX
+.Xr ioctl 2
+calls supported, refer to
+.Tn HP-UX
+manuals.
+The
+.Tn BSD
+calls supported are:
+.Bl -tag -width indent
+.It Dv GRFIOCGINFO
+Get Graphics Info
+.Pp
+Get info about device, setting the entries in the
+.Ar grfinfo
+structure, as defined in
+.Aq Pa hpdev/grfioctl.h .
+For the standard 98720, the number of planes should be 4.  The number of
+colors would therefore be 15, excluding black.  If one 98722A frame buffer
+board is installed, there will still be 4 planes, with the 4 planes on the
+colormap board becoming overlay planes.  With each additional 98722 frame
+buffer board 4 planes will be added up to a maximum of 32 planes total.
+.It Dv GRFIOCON
+Graphics On
+.Pp
+Turn graphics on by enabling
+.Tn CRT
+output.  The screen will come on, displaying
+whatever is in the frame buffer, using whatever colormap is in place.
+.It Dv GRFIOCOFF
+Graphics Off
+.Pp
+Turn graphics off by disabling output to the
+.Tn CRT .
+The frame buffer contents
+are not affected.
+.It Dv GRFIOCMAP
+Map Device to user space
+.Pp
+Map in control registers and framebuffer space. Once the device file is
+mapped, the frame buffer structure is accessible.  The structure describing
+the 98720 is defined in
+.Pa hpdev/grf_rbreg.h .
+.El
+.Sh EXAMPLE
+This is a short segment of code showing how the device is opened and mapped
+into user process address space assuming that it is grf0:
+.Bd -literal
+struct rboxfb *rbox;
+u_char *Addr, frame_buffer;
+struct grfinfo gi;
+int disp_fd;
+
+disp_fd = open("/dev/grf0",1);
+
+if (ioctl (disp_fd, GRFIOCGINFO, &gi) < 0) return -1;
+
+(void) ioctl (disp_fd, GRFIOCON, 0);
+
+Addr = (u_char *) 0;
+if (ioctl (disp_fd, GRFIOCMAP, &Addr) < 0) {
+	(void) ioctl (disp_fd, GRFIOCOFF, 0);
+	return -1;
+}
+rbox = (rboxfb *) Addr;                         /* Control Registers   */
+frame_buffer = (u_char *) Addr + gi.gd_regsize; /* Frame buffer memory */
+.Ed
+.Sh FILES
+.Bl -tag -width /dev/MAKEDEV.hpux -compact
+.It Pa /dev/grf?
+.Bx
+special file
+.It Pa /dev/crt98720
+.It Pa /dev/ocrt98720
+.Tn HP-UX
+.Em starbase
+special files
+.It Pa /dev/MAKEDEV.hpux
+script for creating
+.Tn HP-UX
+special files
+.El
+.Sh DIAGNOSTICS
+None under
+.Bx .
+The
+.Tn HP-UX
+.Tn CE.utilities
+must be used.
+.Sh ERRORS
+.Bl -tag -width [EINVAL]
+.It Bq Er ENODEV
+no such device.
+.It Bq Er EBUSY
+Another process has the device open.
+.It Bq Er EINVAL
+Invalid ioctl specification.
+.El
+.Sh SEE ALSO
+.Xr ioctl 2 ,
+.Xr grf 4 .
+.Pp
+For extensive code examples using the
+Renaissance, see the X device dependent source.
+.Sh HISTORY
+The
+.Nm
+interface
+.Ud
+.Sh BUGS
+Not tested for all configurations of scan board and frame buffer memory boards.
diff --git a/share/man/man4/man4.hp300/rd.4 b/share/man/man4/man4.hp300/rd.4
new file mode 100644
index 00000000000..a6a59420c59
--- /dev/null
+++ b/share/man/man4/man4.hp300/rd.4
@@ -0,0 +1,321 @@
+.\" Copyright (c) 1990, 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" the Systems Programming Group of the University of Utah Computer
+.\" Science Department.
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)rd.4	5.2 (Berkeley) 3/27/91
+.\"	$Id: rd.4,v 1.1 1995/10/18 08:44:28 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt RD 4 hp300
+.Os
+.Sh NAME
+.Nm rd
+.Nd
+.Tn CS/80
+disk interface
+.Sh SYNOPSIS
+.Cd "master hpib? at scode?"
+.Cd "disk rd? at hpib? slave?"
+.Sh DESCRIPTION
+This is a generic
+.Tn CS/80
+disk driver.
+Only a small number of possible
+.Tn CS/80
+drives are supported,
+but others can easily be added by adding tables to the driver.
+It is a typical block-device driver; see
+.Xr physio 4 .
+.Pp
+The script
+.Xr MAKEDEV 8
+should be used to create the
+.Nm rd
+special files; consult
+.Xr mknod 8
+if a special file needs to be made manually.
+.Sh DISK SUPPORT
+The driver interrogates the controller
+to determine the type of drive attached.
+The driver recognizes the following drives:
+7912, 7914, 7933, 7936, 7937, 7945,
+.Tn 757A/B ,
+.Tn 7958A/B ,
+.Tn 7959B,
+7962, 7963, 9122, 9134, 7912, 7936,
+and 9122,
+not all of which have been tested.
+Special file names begin with
+.Sq Li rd
+and
+.Sq Li rrd
+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
+and is designated
+by a letter from
+.Sq Li a
+to
+.Sq Li h
+which also corresponds to a minor device number sets: zero to seven,
+eight to 15, 16 to 23 and so forth for drive zero, drive two and drive
+three respectively
+(see physio 4 ) .
+The location and size (in sectors) of the
+partitions for these drives:
+.Bl -column header diskx undefined length
+.Tn 7945/7946 No partitions:
+.Sy	disk	start	length	cyls
+	rd?a	112	15904	1-142
+	rd?b	16016	20160	143-322
+	rd?c	0	108416	0-967
+	rd?d	16016	40320	143-502
+	rd?e	undefined
+	rd?f	undefined
+	rd?g	36176	72240	323-967
+	rd?h	56336	52080	503-967
+
+.Tn 9134D No partitions:
+.Sy	disk	start	length	cyls
+	rd?a	96	15936	1-166
+	rd?b	16032	13056	167-302
+	rd?c	0	29088	0-302
+	rd?d	undefined
+	rd?e	undefined
+	rd?f	undefined
+	rd?g	undefined
+	rd?h	undefined
+
+.Tn 9122S No partitions:
+.Sy	disk	start	length	cyls
+	rd?a	undefined
+	rd?b	undefined
+	rd?c	0	1232	0-76
+	rd?d	undefined
+	rd?e	undefined
+	rd?f	undefined
+	rd?g	undefined
+	rd?h	undefined
+
+.Tn 7912P No partitions:
+.Sy	disk	start	length	cyls
+	rd?a	0	15904	0-70
+	rd?b	16128	22400	72-171
+	rd?c	0	128128	0-571
+	rd?d	16128	42560	72-261
+	rd?e	undefined
+	rd?f	undefined
+	rd?g	38528	89600	172-571
+	rd?h	58688	69440	262-571
+
+.Tn 7914CT/P No partitions:
+.Sy	disk	start	length	cyls
+	rd?a	224	15904	1-71
+	rd?b	16128	40320	72-251
+	rd?c	0	258048	0-1151
+	rd?d	16128	64960	72-361
+	rd?e	81088	98560	362-801
+	rd?f	179648	78400	802-1151
+	rd?g	56448	201600	252-1151
+	rd?h	81088	176960	362-1151
+
+.Tn 7958A No partitions:
+.Sy	disk	start	length	cyls
+	rd?a	252	16128	1-64
+	rd?b	16380	32256	65-192
+	rd?c	0	255276	0-1012
+	rd?d	16380	48384	65-256
+	rd?e	64764	100800	257-656
+	rd?f	165564	89712	657-1012
+	rd?g	48636	206640	193-1012
+	rd?h	64764	190512	257-1012
+
+.Tn 7957A No partitions:
+.Sy	disk	start	length	cyls
+	rd?a	154	16016	1-104
+	rd?b	16170	24640	105-264
+	rd?c	0	159544	0-1035
+	rd?d	16170	42350	105-379
+	rd?e	58520	54824	380-735
+	rd?f	113344	46200	736-1035
+	rd?g	40810	118734	265-1035
+	rd?h	58520	101024	380-1035
+
+.Tn 7933H No partitions:
+.Sy	disk	start	length	cyls
+	rd?a	598	16146	1-27
+	rd?b	16744	66976	28-139
+	rd?c	0	789958	0-1320
+	rd?d	83720	16146	140-166
+	rd?e	99866	165646	167-443
+	rd?f	265512	165646	444-720
+	rd?g	83720	706238	140-1320
+	rd?h	431158	358800	721-1320
+
+.Tn 9134L No partitions:
+.Sy	disk	start	length	cyls
+	rd?a	80	15920	1-199
+	rd?b	16000	20000	200-449
+	rd?c	0	77840	0-972
+	rd?d	16000	32000	200-599
+	rd?e	undefined
+	rd?f	undefined
+	rd?g	36000	41840	450-972
+	rd?h	48000	29840	600-972
+
+.Tn 7936H No partitions:
+.Sy	disk	start	length	cyls
+	rd?a	861	16359	1-19
+	rd?b	17220	67158	20-97
+	rd?c	0	600978	0-697
+	rd?d	84378	16359	98-116
+	rd?e	100737	120540	117-256
+	rd?f	220416	120540	256-395
+	rd?g	84378	516600	98-697
+	rd?h	341817	259161	397-697
+
+.Tn 7937H No partitions:
+.Sy	disk	start	length	cyls
+	rd?a	1599	15990	1-10
+	rd?b	17589	67158	11-52
+	rd?c	0	1116102	0-697
+	rd?d	84747	15990	53-62
+	rd?e	100737	246246	63-216
+	rd?f	346983	246246	217-370
+	rd?g	84747	1031355	53-697
+	rd?h	593229	522873	371-697
+
+.Tn 7957B/7961B No partitions:
+.Sy	disk	start	length	cyls
+	rd?a	126	16002	1-127
+	rd?b	16128	32760	128-387
+	rd?c	0	159894	0-1268
+	rd?d	16128	49140	128-517
+	rd?e	65268	50400	518-917
+	rd?f	115668	44226	918-1268
+	rd?g	48888	111006	388-1268
+	rd?h	65268	94626	518-1268
+
+.Tn 7958B/7962B No partitions:
+.Sy	disk	start	length	cyls
+	rd?a	378	16254	1-43
+	rd?b	16632	32886	44-130
+	rd?c	0	297108	0-785
+	rd?d	16632	49140	44-173
+	rd?e	65772	121716	174-495
+	rd?f	187488	109620	496-785
+	rd?g	49518	247590	131-785
+	rd?h	65772	231336	174-785
+
+.Tn 7959B/7963B No partitions:
+.Sy	disk	start	length	cyls
+	rd?a	378	16254	1-43
+	rd?b	16632	49140	44-173
+	rd?c	0	594216	0-1571
+	rd?d	16632	65772	44-217
+	rd?e	82404	303912	218-1021
+	rd?f	386316	207900	1022-1571
+	rd?g	65772	528444	174-1571
+	rd?h	82404	511812	218-1571
+.El
+.Pp
+The eight partitions as given support four basic, non-overlapping layouts,
+though not all partitions exist on all drive types.
+.Pp
+In the first layout there are three partitions and a ``bootblock'' area.
+The bootblock area is at the beginning of the disk and holds
+the standalone disk boot program.
+The
+.Pa rd?a
+partition is for the root file system,
+.Pa rd?b
+is a paging/swapping area, and
+.Pa rd?g
+is for everything else.
+.Pp
+The second layout is the same idea,
+but has a larger paging/swapping partition
+.Pq Pa rd?d
+and
+a smaller ``everything else'' partition
+.Pq Pa rd?h .
+This layout is better for environments which run many large processes.
+.Pp
+The third layout is a variation of the second,
+but breaks the
+.Pa rd?h
+partition into two partitions,
+.Pa rd?e
+and
+.Pa rd?f .
+.Pp
+The final layout is intended for a large, single file system second disk.
+It is also used when writing out the boot program since it is the only
+partition mapping the bootblock area.
+.Sh FILES
+.Bl -tag -width /dev/rrd[0-7][a-h] -compact
+.It Pa /dev/rd[0-7][a-h]
+block files
+.It Pa /dev/rrd[0-7][a-h]
+raw files
+.El
+.Sh DIAGNOSTICS
+.Bl -diag
+.It "rd%d err: v%d u%d, R0x%x F0x%x A0x%x I0x%x, block %d"
+An unrecoverable data error occurred during transfer of the
+specified block on the specified disk.
+.El
+.Sh HISTORY
+The
+.Nm
+driver
+.Ud
+.Sh BUGS
+The current disk partitioning is totally bogus.
+.Tn CS/80
+drives have 256 byte sectors which are mapped to 512 byte
+``sectors'' by the driver.
+Since some
+.Tn CS/80
+drives have an odd number of sectors per cylinder,
+the disk geometry used is not always accurate.
+.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
+A program to analyze the logged error information (even in its
+present reduced form) is needed.
diff --git a/share/man/man4/man4.hp300/rmp.4 b/share/man/man4/man4.hp300/rmp.4
new file mode 100644
index 00000000000..341a30fb2b8
--- /dev/null
+++ b/share/man/man4/man4.hp300/rmp.4
@@ -0,0 +1,163 @@
+.\" Copyright (c) 1990, 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" the Systems Programming Group of the University of Utah Computer
+.\" Science Department.
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)rmp.4	5.2 (Berkeley) 3/27/91
+.\"	$Id: rmp.4,v 1.1 1995/10/18 08:44:28 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt RMP 4 hp300
+.Os
+.Sh NAME
+.Nm rmp
+.Nd
+.Tn HP
+Remote Maintenance Protocol Family
+.Sh SYNOPSIS
+.Cd "options RMP"
+.Fd #include <sys/types.h>
+.Fd #include <sys/socket.h>
+.Fd #include <netrmp/rmp.h>
+.Fd #include <netrmp/rmp_var.h>
+.Ft int
+.Fn socket AF_RMP SOCK_RAW proto
+.Sh DESCRIPTION
+Hewlett-Packard's Remote Maintenance Protocol family is a collection
+of protocols layered atop
+.Tn IEEE  802.3 .
+The current implementation of the RMP family provides protocol support only
+for the
+.Dv SOCK_RAW
+socket type.
+As a result,
+.Xr sendto 2
+and
+.Xr recvfrom 2
+must be used to send and
+receive
+.Tn RMP
+packets.
+.Pp
+The format of an
+.Tn RMP
+packet is defined in the include file
+.Aq Pa netrmp/rmp_var.h .
+The
+.Tn RMP
+packet arrives encapsulated in an
+.Pf ( Tn HP
+extended)
+.Tn IEEE  802.2
+packet.
+The
+.Tn IEEE  802.2
+packet
+is preceded by the kernel address of an
+.Ar ifnet struct
+which is used to `route' a packet out the same interface it
+arrived on.
+Outgoing packets are encapsulated in a standard
+.Tn IEEE  802.3
+packet, while incoming packets have this information stripped away.
+.Sh ADDRESSING
+.Tn RMP
+.Pf ( Tn IEEE
+802.3) addresses are 6 octets in length (48 bytes).
+Sockets in the Remote Maintenance Protocol family use the following
+addressing structure:
+.Bd -literal -offset indent
+struct sockaddr_rmp {
+	short		srmp_family;
+	u_char		srmp_dhost[6];
+};
+.Ed
+.Sh PROTOCOLS
+The
+.Tn RMP
+protocol family supported by the operating system
+is currently comprised of the Boot Protocol
+.Pq Em proto= Ns Dv RMPPROTO_BOOT .
+Unfortunately, we have no documentation on the Remote Maintenance
+Protocol and only sketchy information about the Boot Protocol.
+.Sh SEE ALSO
+.Xr socket 2 ,
+.Xr bind 2 ,
+.Xr sendto 2 ,
+.Xr recvfrom 2 ,
+.Xr intro 4 ,
+.Xr rbootd 8
+.Rs
+.%T "An Advanced 4.3 BSD Interprocess Communication Tutorial"
+.Re
+.Sh HISTORY
+The
+.Nm
+protocol interface
+.Ud
+.Sh BUGS
+.Bl -bullet
+.It
+The
+.Tn HP ROM
+uses
+.Tn IEEE
+802.3 (as opposed to Ethernet) packets.  While the
+kernel heuristically recognizes these packets, a more general mechanism
+for doing so should be provided.
+.It
+The
+.Tn HP ROM
+uses a multicast address when first trying to locate boot
+servers.  While the Ethernet [sic] board is programmed to recognize
+this particular multicast address (9:0:9:0:0:4), a more general
+mechanism for doing so should be provided.
+.It
+The kernel supports only
+.Tn RAW
+sockets for the
+.Tn RMP
+protocol.
+This is either a bug or a feature, since the kernel is smaller at the
+price of greater complexity in the server.
+.It
+There is no support for
+.Xr bind Ns 'ing
+an address in the
+.Tn RMP
+domain.
+Something like an
+.Dv RMPADDR_ANY
+should be provided to prevent more than one
+.Xr rbootd
+server from running at the same time.
+.El
diff --git a/share/man/man4/man4.hp300/st.4 b/share/man/man4/man4.hp300/st.4
new file mode 100644
index 00000000000..0d6092cbdd4
--- /dev/null
+++ b/share/man/man4/man4.hp300/st.4
@@ -0,0 +1,234 @@
+.\" Copyright (c) 1990, 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" the Systems Programming Group of the University of Utah Computer
+.\" Science Department.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)st.4	5.3 (Berkeley) 7/31/91
+.\"	$Id: st.4,v 1.1 1995/10/18 08:44:28 deraadt Exp $
+.\"
+.Dd July 31, 1991
+.Dt ST 4 hp300
+.Os
+.Sh NAME
+.Nm \&st
+.Nd
+.Tn CCS SCSI
+tape driver
+.Sh SYNOPSIS
+.Cd "tape st0 at scsi? slave ?"
+.Sh DESCRIPTION
+The
+.Nm \&st
+driver was written especially to support the Exabyte
+.Tn EXB-8200 8MM
+Cartridge 
+Tape Subsystem.  It has several extensions specific to the Exabyte,
+but should support other tape drives as long has they follow
+the
+.Tn ANSI SCSI-I
+specification.  Besides extensive use with
+an Exabyte, the driver has been tested with an
+Archive
+.Tn QIC-24
+tape drive.
+The
+.Nm \&st
+tape interface provides a standard tape drive interface 
+as described in
+.Xr mtio 4
+with the following exceptions:
+.Bl -enum
+.It
+Density is dependent on device type.  Current Exabyte hardware has
+only one density. The
+.Tn EXB-8500
+drive, when released, will have a high
+density format of
+.Tn 5.6GB .
+On an Archive
+.Tn QIC-24
+drive the driver reads both
+.Tn QIC-11
+and
+.Tn QIC-24
+formats
+but writes only
+.Tn QIC-24 .
+.It
+Only the ``raw'' interface is supported.
+.El
+.Pp
+Special Exabyte Support:
+.Pp
+The
+.Dv MTIOCGET
+.Xr ioctl 2
+call on an Exabyte returns this structure:
+.Bd -literal
+struct	mtget {
+	short mt_type;   /* type of magtape device */
+	short mt_dsreg;  /* sc_flags */
+	short mt_erreg;  /* high 8 bytes error status */
+	/* low  8 bytes percentage of Rewrites
+	if writing, ECC errors if reading */
+	short mt_resid;  /* Mbyte until end of tape */
+};
+.Ed
+.Pp
+Bit 4 in the minor device number is used
+to select long filemarks or short filemarks. A long filemark occupies
+2.12 MBytes of space on the tape, while a short filemark occupies 488 KBytes.
+A long filemark includes an erase gap while the short filemark does not.
+The tape can be positioned on the
+.Tn BOT
+side of a long filemark allowing
+data to be appended with a write operation.  Since the short filemark does not
+contain an erase gap which would allow writing it is considered to be
+non-erasable.  If either type of filemark is followed by blank tape,
+data may be appended on its
+.Tn EOT
+side.
+.Pp
+Bit 5 in the minor device number selects fixed block mode with a block
+size of 1K.  Variable length records are the default if bit 5 is not
+set.
+.Pp
+For unit 0 here are the effects of minor device bits 2,3,4,5. For other
+units add the
+.Em unit#
+to each of the device names.
+.Bl -column norewind density filemarks -offset indent
+.Em norewind	high	short	fixed
+.Em 	density	filemarks	block mode
+rst0
+nrst0	X
+rst8		X
+nrst8	X	X
+rst16			X
+nrst16	X		X
+rst24		X	X
+nrst24	X	X	X
+rst32				X
+nrst32	X			X
+rst40		X		X
+nrst40	X	X		X
+rst48			X	X
+nrst48	X		X	X
+rst56		X	X	X
+nrst56	X	X	X	X
+.El
+.Sh SEE ALSO
+.Xr mt 1 ,
+.Xr tar 1 ,
+.Xr mtio 4 ,
+.Rs
+.%T EXB-8200 8MM Cartridge Tape Subsystem Interface User Manual.
+.Re
+.Sh HISTORY
+The
+.Nm \&st
+driver
+.Ud
+.Sh BUGS
+The
+.Tn HP
+98268
+.Tn SCSI
+controller hardware can not do odd length
+.Tn DMA
+transfers.  If odd length
+.Tn DMA I/O
+is requested the driver will use the
+"Program Transfer Mode" of the Fujitsu
+.Tn MB87030
+chip. Read requests are
+normally even length for which a
+.Tn DMA
+transfer is used. If, however, the
+driver detects that a odd length read has happened (when a even length
+was requested) it will issue the
+.Dv EIO
+error and the last byte of the read
+data will be 0x00. Odd length read requests must match the size of the
+requested data block on tape.
+.Pp
+The following only applies when using long filemarks. Short filemarks can
+not be overwritten.
+.Bd -filled -offset 4n
+Due to the helical scan and the erase mechanism, there is a writing
+limitation on Exabyte drives.
+.Dq Li tar r
+or
+.Dq Li tar u
+will not work
+.Pf ( Dq Li tar c
+is ok).  One can only start writing at  1) beginning of tape, 2) on the
+end of what was last written, 3) "front" side of a regular (long) filemark.
+Say you have a tape with 3 tar files on it, want to save the first
+file, and want to begin writing over the 2nd file.
+.Pp
+On a normal 1/4" or 1/2" drive you would do:
+.Pp
+.Li "mt fsf 1; tar cf /dev/nrst0 ..."
+.Pp
+but for an Exabyte you need to do:
+.Pp
+.Li "mt fsf 1; mt bsf 1; mt weof 1; tar cf /dev/nrst0 ..."
+.Pp
+The regular long filemark consists of an erased zone 3.8" long
+(needed to begin a write).  In this case, the first filemark is
+rewritten in place, which creates an erased zone
+.Em after
+it, clearing the
+way to write more on the tape.  The erase head is not helical.
+.Pp
+One can position a tape to the end of what was last written by reading
+until a
+.Tn \*qBLANK CHECK\*q
+error is returned.  Writing can be started at this
+point.  (This applies to both long and short filemarks.)  The tape does
+not become positioned somewhere down the "erased" area as does a
+conventional magtape.  One can issue multiple reads at the
+.Tn \*qBLANK CHECK\*q
+error, but the Exabyte stays positioned at the beginning of the
+blank area, ready to accept write commands.  File skip operations do
+not stop at blank tape and will run into old data or run to the end of
+the tape, so you have to be careful not to
+.Dq Li mt fsf too_many .
+.Ed
+.Pp
+Archive support gets confused if asked to moved more filemarks than there are
+on the tape.
+.Pp
+This man page needs some work.  Some of these are not really bugs,
+just unavoidable consequences of the hardware.
diff --git a/share/man/man4/man4.hp300/tc.4 b/share/man/man4/man4.hp300/tc.4
new file mode 100644
index 00000000000..040f3ba2a9d
--- /dev/null
+++ b/share/man/man4/man4.hp300/tc.4
@@ -0,0 +1,182 @@
+.\" Copyright (c) 1990, 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" the Systems Programming Group of the University of Utah Computer
+.\" Science Department.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)tc.4	5.2 (Berkeley) 3/27/91
+.\"	$Id: tc.4,v 1.1 1995/10/18 08:44:28 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt TC 4 hp300
+.Os
+.Sh NAME
+.Nm \&tc
+.Nd
+.Tn HP98544
+98550 ``Topcat'' and ``Catseye'' device interface
+.Sh DESCRIPTION
+This driver is for the
+.Tn HP98544 ,
+98545 and 98547 ``Topcat''
+and
+.Tn HP98548 ,
+98549, and 98550 ``Catseye'' display cards.
+This driver merely checks for the existence of the device
+and does minimal set up, as it is expected the applications will initialize
+the device to their requirements.
+The Topcat and Catseye are nearly identical in common usage and only the
+Topcat will be referred to from now on.
+.Pp
+The Topcat display cards are not user configurable.  If one is present on a
+system, it will always have a frame buffer address of 0x200000 and a control
+register address of 0x560000.  These are the
+.Tn HP
+series 300
+.Tn ITE
+(Internal
+Terminal Emulator) defaults.  The device can also be used as a graphics output
+device.
+.Pp
+The 
+.Xr ioctl 2
+calls supported by the
+.Bx
+system for the Topcat are:
+.Bl -tag -width GRFIOCGINFO
+.It Dv GRFIOCGINFO
+Get Graphics Info
+.Pp
+Get info about device, setting the entries in the
+.Ar grfinfo
+structure, as defined in
+.Aq Pa hpdev/grfioctl.h .
+For the 98544 or 98549,
+the number of planes should be 1, as they are monochrome devices.
+The number of planes for a 98545 is 4, translating to 15 colors,
+excluding black.
+The 98547 and 98548 cards have 6 planes, yielding 63 colors and black.
+The 98550 has 8 planes, yielding 255 colors and black.
+The displayed frame buffer size for the 98549 and 98550 is 2048 x 1024,
+for the others it is 1024 x 768.
+.It Dv GRFIOCON
+Graphics On
+.Pp
+Turn graphics on by enabling
+.Tn CRT
+output.  The screen will come on, displaying
+whatever is in the frame buffer, using whatever colormap is in place.
+.It Dv GRFIOCOFF
+Graphics Off
+.Pp
+Turn graphics off by disabling output to the
+.Tn CRT .
+The frame buffer contents
+are not affected.
+.It Dv GRFIOCMAP
+Map Device to user space
+.Pp
+Map in control registers and framebuffer space. Once the device file is
+mapped, the frame buffer structure is accessible.  The frame buffer structure
+describing Topcat/Catseye devices is defined in
+.Aq Pa hpdev/grf_tcreg.h .
+.El
+.Pp
+For further information about the use of
+.Xr ioctl
+see the man page.
+.Sh EXAMPLE
+A small example of opening, mapping and using the device is given below.
+For more examples of the details on the behavior of the device, see the device
+dependent source files for the X Window System, in the
+.Pa /usr/src/new/X/libhp
+directory.
+.Bd -literal 
+struct tcboxfb *tc;
+u_char *Addr, frame_buffer;
+struct grfinfo gi;
+int disp_fd;
+
+disp_fd = open("/dev/grf0",1);
+
+if (ioctl (disp_fd, GRFIOCGINFO, &gi) < 0) return -1;
+
+(void) ioctl (disp_fd, GRFIOCON, 0);
+
+Addr = (u_char *) 0;
+if (ioctl (disp_fd, GRFIOCMAP, &Addr) < 0) {
+	(void) ioctl (disp_fd, GRFIOCOFF, 0);
+	return -1;
+}
+tc = (tcboxfb *) Addr;                          /* Control Registers   */
+frame_buffer = (u_char *) Addr + gi.gd_regsize; /* Frame buffer memory */
+.Ed
+.Sh FILES
+.Bl -tag -width /dev/MAKEDEV.hpux -compact
+.It Pa /dev/grf?
+.Bx
+special file
+.It Pa /dev/crt9837
+.It Pa /dev/crt98550
+.Tn HP-UX
+.Em starbase
+special files
+.It Pa /dev/MAKEDEV.hpux
+script for creating
+.Tn HP-UX
+special files
+.El
+.Sh DIAGNOSTICS
+None under
+.Bx .
+.Tn HP-UX
+.Tn /usr/CE.utilities/Crtadjust
+programs must be used.
+.Sh ERRORS
+.Bl -tag -width [EINVAL]
+.It Bq Er ENODEV
+no such device.
+.It Bq Er EBUSY
+Another process has the device open.
+.It Bq Er EINVAL
+Invalid
+.Xr ioctl
+specification.
+.El
+.Sh SEE ALSO
+.Xr ioctl 2 ,
+.Xr grf 4
+.Sh HISTORY
+The
+.Nm
+driver
+.Ud
diff --git a/share/man/man4/man4.i386/Makefile b/share/man/man4/man4.i386/Makefile
new file mode 100644
index 00000000000..dce736d37f8
--- /dev/null
+++ b/share/man/man4/man4.i386/Makefile
@@ -0,0 +1,12 @@
+#	from: @(#)Makefile	5.1 (Berkeley) 2/12/91
+#	$Id: Makefile,v 1.1 1995/10/18 08:44:28 deraadt Exp $
+
+MAN=	intro.4 aha.4 ahb.4 aic.4 ast.4 autoconf.4 boca.4 bt.4
+MAN+=	com.4 cy.4 ed.4 ep.4 lms.4 lpt.4 mcd.4 mem.4 mms.4 ncr.4 npx.4 pms.4 
+MAN+=	rtfps.4 sea.4 speaker.4 uha.4 wd.4
+MAN+=	eg.4 el.4 ie.4 le.4 wt.4
+
+MLINKS=	mem.4 kmem.4
+MANSUBDIR=/i386
+
+.include <bsd.prog.mk>
diff --git a/share/man/man4/man4.i386/aha.4 b/share/man/man4/man4.i386/aha.4
new file mode 100644
index 00000000000..702a0f41efb
--- /dev/null
+++ b/share/man/man4/man4.i386/aha.4
@@ -0,0 +1,65 @@
+.\"
+.\" Copyright (c) 1994 James A. Jegers
+.\" 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. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission
+.\" 
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.Dd November 29, 1994
+.Dt AHA 4 i386
+.Os NetBSD 
+.Sh NAME
+.Nm aha
+.Nd Adaptec 154x SCSI adapter driver
+.Sh SYNOPSIS
+.Cd "aha0 at isa? port 0x330 irq ? drq ?"
+.Cd "scsibus* at aha?"
+.Sh DESCRIPTION
+The
+.Nm aha 
+driver provides support for the following SCSI adapters:
+.Pp
+.Bl -tag -width -offset indent -compact
+.It Adaptec AHA-154xA
+.It Adaptec AHA-154xB
+.It Adaptec AHA-154xC
+.It Adaptec AHA-154xCF
+.It Buslogic BT-54x
+.El
+.Sh BUGS
+The
+.Nm
+driver can not be used on systems with more than 16 megabytes of
+memory.
+.Pp
+Due to the 24 bit addressing limitation of the ISA bus, The SCSI
+adapter's onboard DMA controller is unable to access memory with
+addresses greater than 16 megabytes.  
+.Pp
+This restriction can be fixed with "bounce buffers", buffers in low
+memory which are used whenever data to be transfered to or from the
+SCSI adapter is above the 16 megabyte threshold.  The data is copied
+to the bounce buffer, then copied from the bounce buffer to its
+destination.
+.Sh SEE ALSO
+.Xr intro 4 ,
+.Xr sd 4 ,
+.Xr st 4 ,
+.Xr cd 4 ,
+.Xr ch 4
diff --git a/share/man/man4/man4.i386/ahb.4 b/share/man/man4/man4.i386/ahb.4
new file mode 100644
index 00000000000..74f9783d680
--- /dev/null
+++ b/share/man/man4/man4.i386/ahb.4
@@ -0,0 +1,42 @@
+.\"
+.\" Copyright (c) 1994 James A. Jegers
+.\" 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. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission
+.\" 
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.Dd November 29, 1994
+.Dt AHB 4 i386
+.Os NetBSD 
+.Sh NAME
+.Nm ahb
+.Nd Adaptec 1742 SCSI adapter driver
+.Sh SYNOPSIS
+.Cd "ahb0 at eisa? slot ? irq ?"
+.Cd "scsibus* at ahb?"
+.Sh DESCRIPTION
+The
+.Nm ahb 
+driver provide support for the Adaptec AHA-1742 EISA SCSI adapter.
+.Sh SEE ALSO
+.Xr intro 4 ,
+.Xr sd 4 ,
+.Xr st 4 ,
+.Xr cd 4 ,
+.Xr ch 4  
diff --git a/share/man/man4/man4.i386/aic.4 b/share/man/man4/man4.i386/aic.4
new file mode 100644
index 00000000000..c70871271ed
--- /dev/null
+++ b/share/man/man4/man4.i386/aic.4
@@ -0,0 +1,48 @@
+.\"
+.\" Copyright (c) 1994 James A. Jegers
+.\" 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. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission
+.\" 
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.\"
+.Dd November 29, 1994
+.Dt AIC 4 i386
+.Os NetBSD 
+.Sh NAME
+.Nm aic
+.Nd Adaptec AIC-6260 and AIC-6360 SCSI driver
+.Sh SYNOPSIS
+.Cd "aic0 at isa? port 0x340 irq 12"
+.Cd "scsibus* at aic?"
+.Sh DESCRIPTION
+The
+.Nm aic
+driver provides support for the Adaptec AIC-6260 and AIC-6360 SCSI
+controller chips.  This includes the Adaptec 152x and the Creative
+Labs SoundBlaster SCSI host adapter.
+.Pp
+Many systems that use these controller chips do not have a boot ROM
+and therefore cannot be booted from.
+.Sh SEE ALSO
+.Xr intro 4 ,
+.Xr sd 4 ,
+.Xr st 4 ,
+.Xr cd 4 ,
+.Xr ch 4  
diff --git a/share/man/man4/man4.i386/ast.4 b/share/man/man4/man4.i386/ast.4
new file mode 100644
index 00000000000..f109e6882c8
--- /dev/null
+++ b/share/man/man4/man4.i386/ast.4
@@ -0,0 +1,93 @@
+.\"
+.\" Copyright (c) 1990, 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" the Systems Programming Group of the University of Utah Computer
+.\" Science Department.
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)dca.4	5.2 (Berkeley) 3/27/91
+.\"	from: Id: com.4,v 1.1 1993/08/06 11:19:07 cgd Exp
+.\"	$Id: ast.4,v 1.1 1995/10/18 08:44:29 deraadt Exp $
+.\"
+.Dd March 30, 1994
+.Dt AST 4 i386
+.Os NetBSD 0.9a
+.Sh NAME
+.Nm ast
+.Nd
+multiplexing serial communications interface
+.Sh SYNOPSIS
+.Cd "ast0 at isa? port 0x1a0 irq 5"
+.Cd "com2 at ast? slave ? flags 1"
+.Cd "com3 at ast? slave ? flags 1"
+.Cd "com4 at ast? slave ? flags 1"
+.Cd "com5 at ast? slave ? flags 1"
+.Sh DESCRIPTION
+The
+.Nm ast
+driver provides support for boards that multiplex together up to four
+.Tn EIA
+.Tn RS-232C
+.Pf ( Tn CCITT
+.Tn V.28 )
+communications interfaces.  Apparently the original master of hardware
+using this multiplexing protocol was AST.
+.Pp
+Each
+.Nm
+device is the master device for up to four 
+.Nm com
+devices.  The kernel configuration specifies these
+.Nm com
+devices as slave devices of the
+.Nm
+device, as shown in the synopsis.  The slave ID given for each
+.Nm com
+device determines which bit in the interrupt multiplexing register is
+tested to find interrupts for that device.
+The
+.Tn port
+specification for the
+.Nm
+device is used to compute the base addresses for the
+.Nm com
+subdevices and the port for the interrupt multiplexing register.
+.Sh FILES
+.Bl -tag -width Pa
+.It Pa /dev/tty0?
+.El
+.Sh SEE ALSO
+.Xr com 4
+.Sh HISTORY
+The
+.Nm
+driver was written by Roland McGrath and placed into the public
+domain.
diff --git a/share/man/man4/man4.i386/autoconf.4 b/share/man/man4/man4.i386/autoconf.4
new file mode 100644
index 00000000000..b9ea193f6c0
--- /dev/null
+++ b/share/man/man4/man4.i386/autoconf.4
@@ -0,0 +1,65 @@
+.\"
+.\" Copyright (c) 1994 Christopher G. Demetriou
+.\" All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"      This product includes software developed by Christopher G. Demetriou.
+.\" 3. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.\"	$Id: autoconf.4,v 1.1 1995/10/18 08:44:29 deraadt Exp $
+.\"
+.Dd
+.Dt AUTOCONF 4 i386
+.Os
+.Sh NAME
+.Nm autoconf
+.Nd diagnostics from the autoconfiguration code
+.Sh DESCRIPTION
+When
+.Tn NetBSD
+bootstraps it probes the innards of the machine
+on which it is running
+and locates controllers, drives, and other devices, printing out
+what it finds on the console.  This procedure is driven by a system
+configuration table which is processed by
+.Xr config 8
+and compiled into each kernel.
+Devices which exist in the machine but are not configured into the
+kernel are not detected.
+.Sh DIAGNOSTICS
+.Bl -diag
+.It CPU class not configured.
+You tried to boot
+.Tn NetBSD
+on a class of
+.Tn CPU
+type which it doesn't
+(or at least this compiled version of
+.Tn NetBSD
+doesn't) understand.
+.El
+.Sh SEE ALSO
+.Xr intro 4 ,
+.Xr boot 8 ,
+.Xr config 8
diff --git a/share/man/man4/man4.i386/boca.4 b/share/man/man4/man4.i386/boca.4
new file mode 100644
index 00000000000..58a6ceff10e
--- /dev/null
+++ b/share/man/man4/man4.i386/boca.4
@@ -0,0 +1,135 @@
+.\"
+.\" Copyright (c) 1990, 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" the Systems Programming Group of the University of Utah Computer
+.\" Science Department.
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)dca.4	5.2 (Berkeley) 3/27/91
+.\"	from: Id: com.4,v 1.1 1993/08/06 11:19:07 cgd Exp
+.\"	$Id: boca.4,v 1.1 1995/10/18 08:44:29 deraadt Exp $
+.\"
+.Dd January 3, 1995
+.Dt BOCA 4 i386
+.Os NetBSD 1.1
+.Sh NAME
+.Nm boca
+.Nd
+multiplexing serial communications interface
+.Sh SYNOPSIS
+.Pp
+For 4-port BB1004 boards:
+.Pp
+.Cd "boca0 at isa? port 0x100 irq 5"
+.Cd "com2 at boca? slave ?"
+.Cd "com3 at boca? slave ?"
+.Cd "com4 at boca? slave ?"
+.Cd "com5 at boca? slave ?"
+.Pp
+For 8-port BB1008 boards:
+.Pp
+.Cd "boca0 at isa? port 0x100 irq 5"
+.Cd "com2 at boca? slave ?"
+.Cd "com3 at boca? slave ?"
+.Cd "com4 at boca? slave ?"
+.Cd "com5 at boca? slave ?"
+.Cd "com6 at boca? slave ?"
+.Cd "com7 at boca? slave ?"
+.Cd "com8 at boca? slave ?"
+.Cd "com9 at boca? slave ?"
+.Pp
+For 16-port BB2016 boards:
+.Pp
+.Cd "boca0 at isa? port 0x100 irq 5"
+.Cd "com2 at boca? slave ?"
+.Cd "com3 at boca? slave ?"
+.Cd "com4 at boca? slave ?"
+.Cd "com5 at boca? slave ?"
+.Cd "com6 at boca? slave ?"
+.Cd "com7 at boca? slave ?"
+.Cd "com8 at boca? slave ?"
+.Cd "com9 at boca? slave ?"
+.Cd "boca1 at isa? port 0x140 irq 5"
+.Cd "com10 at boca? slave ?"
+.Cd "com11 at boca? slave ?"
+.Cd "com12 at boca? slave ?"
+.Cd "com13 at boca? slave ?"
+.Cd "com14 at boca? slave ?"
+.Cd "com15 at boca? slave ?"
+.Cd "com16 at boca? slave ?"
+.Cd "com17 at boca? slave ?"
+.Pp
+(The BB2016 is functionally equivalent to two BB1008 boards,
+and is configured as such.)
+.Sh DESCRIPTION
+The
+.Nm boca
+driver provides support for BOCA Research BB1004, BB1008 and BB2016
+boards that multiplex together up to four, eight or sixteen
+.Tn EIA
+.Tn RS-232C
+.Pf ( Tn CCITT
+.Tn V.28 )
+communications interfaces.
+.Pp
+Each
+.Nm
+device is the master device for up to eight 
+.Nm com
+devices.  The kernel configuration specifies these
+.Nm com
+devices as slave devices of the
+.Nm
+device, as shown in the synopsis.  The slave ID given for each
+.Nm com
+device determines which bit in the interrupt multiplexing register is
+tested to find interrupts for that device.
+The
+.Tn port
+specification for the
+.Nm
+device is used to compute the base addresses for the
+.Nm com
+subdevices and the port for the interrupt multiplexing register.
+.Sh FILES
+.Bl -tag -width Pa
+.It Pa /dev/tty??
+.El
+.Sh SEE ALSO
+.Xr com 4
+.Sh HISTORY
+The
+.Nm
+driver was written by Charles Hannum, based on the
+.Nm ast
+driver and source code from David Muir Sharnoff.  David wishes to
+acknowledge the assistance of Jason Venner in determining how to use
+the BOCA boards.
diff --git a/share/man/man4/man4.i386/bt.4 b/share/man/man4/man4.i386/bt.4
new file mode 100644
index 00000000000..a3e18297967
--- /dev/null
+++ b/share/man/man4/man4.i386/bt.4
@@ -0,0 +1,48 @@
+.\"
+.\" Copyright (c) 1994 James A. Jegers
+.\" 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. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission
+.\" 
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.Dd November 29, 1994
+.Dt BT 4 i386
+.Os NetBSD 
+.Sh NAME
+.Nm bt
+.Nd Buslogic SCSI adapter driver
+.Sh SYNOPSIS
+.Cd "bt0 at isa? port 0x330 irq ? drq ?"
+.Cd "scsibus* at bt?"
+.Sh DESCRIPTION
+The
+.Nm bt
+driver supports the following Buslogic SCSI adapters:
+.Pp
+.Bl -tag -width -offset indent -compact
+.It Buslogic BT-445
+.It Buslogic BT-74x 
+.It Buslogic BT-9xx 
+.El
+.Sh SEE ALSO
+.Xr intro 4 ,
+.Xr sd 4 ,
+.Xr st 4 ,
+.Xr cd 4 ,
+.Xr ch 4  
diff --git a/share/man/man4/man4.i386/com.4 b/share/man/man4/man4.i386/com.4
new file mode 100644
index 00000000000..d9554b19ea0
--- /dev/null
+++ b/share/man/man4/man4.i386/com.4
@@ -0,0 +1,105 @@
+.\" Copyright (c) 1990, 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" the Systems Programming Group of the University of Utah Computer
+.\" Science Department.
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)dca.4	5.2 (Berkeley) 3/27/91
+.\"	$Id: com.4,v 1.1 1995/10/18 08:44:29 deraadt Exp $
+.\"
+.Dd August 6, 1993
+.Dt COM 4 i386
+.Os NetBSD 0.8a
+.Sh NAME
+.Nm com
+.Nd
+serial communications interface
+.Sh SYNOPSIS
+.Cd "com0 at isa? port" \&"IO_COM1\&" irq 4
+.Cd "com1 at isa? port" \&"IO_COM2\&" irq 3
+.Cd "com2 at ast? slave ? flags 1"
+.Sh DESCRIPTION
+The
+.Nm
+driver provides support for NS8250-, NS16450-, and NS16550-based
+.Tn EIA
+.Tn RS-232C
+.Pf ( Tn CCITT
+.Tn V.28 )
+communications interfaces.  The NS8250 and NS16450 have single character
+buffers, and the NS16550 has a 16 character buffer.
+.Pp
+Input and output for each line may set to one of following baud rates;
+50, 75, 110, 134.5, 150, 300, 600, 1200, 1800, 2400, 4800, 9600,
+19200, 38400, 57600, or 115200, or any other baud rate which is a factor
+of 115200.
+.Pp
+If
+.Dq flags 1
+is specified, the
+.Nm
+driver will not set the MCR_IENABLE bit on the UART.  This is mainly for
+use on AST multiport boards, where the MCR_IENABLE bit is used to control
+whether or not the devices use a shared interrupt.
+.Sh FILES
+.Bl -tag -width Pa
+.It Pa /dev/tty00
+.It Pa /dev/tty01
+.It Pa /dev/tty02
+.El
+.Sh DIAGNOSTICS
+.Bl -diag
+.It com%d: %d silo overflows
+The input
+.Dq silo
+has overflowed and incoming data has been lost.
+.It com%d: weird interrupt: iir=%x
+The device has generated an unexpected interrupt
+with the code listed.
+.El
+.Sh SEE ALSO
+.Xr ast 4 ,
+.Xr rtfps 4 ,
+.Xr tty 4
+.Sh HISTORY
+The
+.Nm
+driver was originally derived from the
+.Nm HP9000/300
+.Nm dca
+driver and is
+.Ud
+.Sh BUGS
+Data loss is possible on busy systems with unbuffered UARTs at high speed.
+.Pp
+The name of this driver and the constants which define the locations
+of the various serial ports are holdovers from
+.Nm DOS .
diff --git a/share/man/man4/man4.i386/cy.4 b/share/man/man4/man4.i386/cy.4
new file mode 100644
index 00000000000..5558ce78e30
--- /dev/null
+++ b/share/man/man4/man4.i386/cy.4
@@ -0,0 +1,96 @@
+.\"
+.\" Copyright (c) 1993 Andrew Herbert.
+.\" 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. The name Andrew Herbert may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.\"	$Id: cy.4,v 1.1 1995/10/18 08:44:29 deraadt Exp $
+.\"
+.Dd 5 October, 1993
+.Dt CY 4 i386
+.Sh NAME
+.Nm cy
+.Nd
+Cyclades Cyclom-{4, 8, 16}Y asynchronous comms board device driver
+.Sh SYNOPSIS
+.Cd "cy0 at isa? tty irq 10 iomem 0xdc000 iosiz 8192 vector cyintr"
+.Sh DESCRIPTION
+This driver provides an interface to Cyclades Cyclom-4Y, Cyclom-8Y and
+Cyclom-16Y asynchronous multiport serial boards.  These boards are based
+around Cirrus Logic CD1400 communication controllers.
+.Pp
+The device minor numbers for this driver are encoded as follows:
+.Pp
+.Bd -literal
+    c c x x u u u u	- bits in the minor device number
+
+    bits    meaning
+    ----    -------
+    uuuu    physical serial line (i.e. unit) to use
+		0-7 on a cyclom-8Y, 0-15 on a cyclom-16Y
+
+    xx      unused
+
+    cc      carrier control mode
+		00      complete hardware carrier control of the tty.
+			DCD must be high for the open(2) to complete.
+		01	reserved
+		10      carrier ignored until a high->low transition
+		11      carrier completed ignored
+.Ed
+.Sh DIAGNOSTICS
+.Bl -diag
+.It "cy%d: tty input queue overflow"
+Incoming characters have been discarded due to a buffer overflow.  This is
+caused by the process in control of the device not read(2)ing characters
+fast enough.
+.It "cy%d: receive fifo overrun"
+Incoming characters have been discarded due to a CD1400 channel overrun.  This
+is caused by interrupts not being serviced sufficiently quickly to prevent
+the 12 byte receive FIFO on a serial channel from overflowing.  Reducing
+the value of the \fIRxFifoThreshold\fR #define from 8 to something smaller may
+help slow machines avoid this problem.  The driver must have been compiled
+with the \fILogOverruns\fR option defined (the default) in order for this
+condition to be logged.
+.Sh SEE ALSO
+.Xr com 4 ,
+.Xr termios 4 ,
+.Xr tty 4
+.Sh AUTHORS
+The driver was written by Andrew Herbert <andrew@werple.apana.org.au>, and
+is still under development (from time to time :-).
+.Sh HISTORY
+Some ideas for the architecture of this driver's two-layer processing model
+were derived from the fas 2.10 driver by Uwe Doering
+<gemini@geminix.in-berlin.de> and the high-performance com driver by Bruce
+Evans <bde@kralizec.zeta.org.au>.
+.Pp
+This work was made possible through the donation of a Cyclom-8Y board by the
+manufacturer, Cyclades Corporation.  However, neither Cyclades nor the author
+make any warranties regarding this software, nor guarantees of support.
+.Sh BUGS
+There is currently no BREAK handling - breaks are ignored.
+There is no support for bad-character reporting, except via PARMRK.
+The Cyclom-[48]Y boards do not listen to the RTS signal for receiver flow
+control.
+FIFO overruns are only logged when the termios IGNPAR setting is enabled.
diff --git a/share/man/man4/man4.i386/ed.4 b/share/man/man4/man4.i386/ed.4
new file mode 100644
index 00000000000..208267afe1f
--- /dev/null
+++ b/share/man/man4/man4.i386/ed.4
@@ -0,0 +1,67 @@
+.\"
+.\" Copyright (c) 1994 Christopher G. Demetriou
+.\" All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"      This product includes software developed by Christopher G. Demetriou.
+.\" 3. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.\"	$Id: ed.4,v 1.1 1995/10/18 08:44:29 deraadt Exp $
+.\"
+.Dd
+.Dt ED 4 i386
+.Os
+.Sh NAME
+.Nm ed
+.Nd Ethernet driver for DP8390- and WD83C690-based ethernet boards
+.Sh SYNOPSIS
+.Cd "ed0 at isa? port 0x280 irq 9 iomem 0xd0000"
+.Cd "ed1 at isa? port 0x250 irq 9 iomem 0xd8000"
+.Cd "ed2 at isa? port 0x300 irq 10 iomem 0xcc000"
+.Sh DESCRIPTION
+The
+.Nm
+interface provides access to a 10 Mb/s Ethernet network via the
+DP8390 and WD83C690 Ethernet chips.  The ethernet cards supported
+by the
+.Nm
+interface are:
+.Pp
+.Bl -tag -width -offset indent -compact
+.It Western Digital 8003 Series
+.It Western Digital 8013 Series
+.It SMC Elite (80x3) Series
+.It SMC Ultra (8216) Series
+.It 3Com 3c503
+.It Novell NE1000
+.It Novell NE2000
+.El
+.Sh SEE ALSO
+.Xr ifconfig 8 ,
+.Xr intro 4 ,
+.Xr eg 4 ,
+.Xr el 4 ,
+.Xr ep 4 ,
+.Xr ie 4 ,
+.Xr le 4
diff --git a/share/man/man4/man4.i386/eg.4 b/share/man/man4/man4.i386/eg.4
new file mode 100644
index 00000000000..39e8308fb3d
--- /dev/null
+++ b/share/man/man4/man4.i386/eg.4
@@ -0,0 +1,44 @@
+.\"
+.\" Copyright (c) 1994 James A. Jegers
+.\" 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. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission
+.\" 
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.Dd July 10, 1995
+.Dt EG 4 i386
+.Os
+.Sh NAME
+.Nm eg
+.Nd Ethernet driver for 3Com 3c505 Ethernet boards
+.Sh SYNOPSIS
+.Cd "eg0 at isa?"
+.Sh DESCRIPTION
+The
+.Nm
+interface provides access to a 10 Mb/s Ethernet network via the
+3Com 3c505 Ethernet board. 
+.Sh SEE ALSO
+.Xr ifconfig 8 ,
+.Xr intro 4 ,
+.Xr ed 4 ,
+.Xr el 4 ,
+.Xr ep 4 ,
+.Xr ie 4 ,
+.Xr le 4 
diff --git a/share/man/man4/man4.i386/el.4 b/share/man/man4/man4.i386/el.4
new file mode 100644
index 00000000000..fb1e4e804d5
--- /dev/null
+++ b/share/man/man4/man4.i386/el.4
@@ -0,0 +1,44 @@
+.\"
+.\" Copyright (c) 1994 James A. Jegers
+.\" 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. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission
+.\" 
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.Dd July 10, 1995
+.Dt EL 4 i386
+.Os
+.Sh NAME
+.Nm el
+.Nd Ethernet driver for 3Com Etherlink 3C501 device driver
+.Sh SYNOPSIS
+.Cd "el0 at isa? port 0x300 irq 9"
+.Sh DESCRIPTION
+The
+.Nm
+interface provides access to a 10 Mb/s Ethernet network via the
+3Com 3c501 Ethernet cards.
+.Sh SEE ALSO
+.Xr ifconfig 8 ,
+.Xr intro 4 ,
+.Xr ed 4 ,
+.Xr eg 4 ,
+.Xr ep 4 ,
+.Xr ie 4 ,
+.Xr le 4
diff --git a/share/man/man4/man4.i386/ep.4 b/share/man/man4/man4.i386/ep.4
new file mode 100644
index 00000000000..130ce29e2d4
--- /dev/null
+++ b/share/man/man4/man4.i386/ep.4
@@ -0,0 +1,123 @@
+.\"
+.\" Copyright (c) 1994 Herb Peyerl
+.\" 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 Herb Peyerl
+.\" 3. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.\"	$Id: ep.4,v 1.1 1995/10/18 08:44:29 deraadt Exp $
+.\"
+.Dd February 04, 1993
+.Dt EP 4
+.Os
+.Sh NAME
+.Nm ep
+.Nd Ethernet driver for 3Com Etherlink III (3c5x9)
+.Sh SYNOPSIS
+.Cd "ep? at isa? port ? irq ?"
+.Sh DESCRIPTION
+The
+.Nm ep
+device driver supports the 3c509 (ISA) and 3c579 (EISA) cards.
+Various models of these cards come with a different assortment of
+connectors:
+.Pp
+.Bl -tag -width xxxxxxxxxxxxxxxxxxxx
+.It AUI/DIX
+Standard 15 pin connector
+.It 10Base2
+BNC, also known as thin-net
+.It 10BaseT
+UTP, also known as twisted pair
+.El
+.Pp
+The default port to use is the BNC. To choose an alternate port,
+use the following flag combinations with
+.Xr ifconfig 8
+or in your /etc/hostname.ep? file.
+.Pp
+.Bl -tag -width xxxxxxxxxxxxxxxxxxxx
+.It -link0
+Use the BNC port (default).
+.It \ link0 -link1
+Use the AUI port.
+.It \ link0 \ link1
+Use the UTP port.
+.El
+.Pp
+If there are multiple cards in the computer, they are searched for
+in the following order:
+The 3c579 EISA cards are searched for first -- they will be found
+in EISA slot# order.
+Next, the 3c509 ISA cards are searched -- they are found in increasing
+ethernet address order.
+This is an example of how they will probe:
+.Pp
+ep0 at isa0 port 0x6000-0x600f irq 10: aui/bnc address 00:60:8c:70:e5:c5
+ep1 at isa0 port 0x300-0x30f irq 3: aui/bnc/utp address 00:20:af:10:62:ab
+.Pp
+You may specify the port and irq numbers that the cards are expected
+to be found at, but it is not necessary.
+The cards are sufficiently intelligent to tell us where they
+actually live on the ISA bus.
+.Pp
+.Sh NOTES
+The 3c509 card has no jumpers to set the address.
+3Com supplies software to set the address of the card in software.
+To find the card on the ISA bus, the kernel performs a complex
+scan operation at IO address 0x100.
+Beware!
+Avoid placing other cards at that address!
+.Pp
+Some models of 3c5x9 have all three connectors on them.
+In the case of these cards; you must configure the transceiver type
+with the 3Com supplied DOS configuration disk before the link0/link1
+flags will operate correctly.
+.Pp
+.Sh DIAGNOSTICS
+ep0: reset (status: %x)
+.in +4
+the driver has encountered a FIFO underrun or overrun. The driver will reset
+the card and the packet will be lost. This is not fatal.
+.in -4
+ep0: eeprom failed to come ready
+.in +4
+The eeprom failed to come ready.  This probably means the card is wedged.
+.in -4
+ep0: 3c509 in test mode. Erase pencil mark!
+.in +4
+This means that someone has scribbled with pencil in the test area on the
+card.  Erase the pencil mark and reboot.  (This is not a joke).
+.in -4
+.Sh SEE ALSO
+.Xr ifconfig 8 ,
+.Xr intro 4 ,
+.Xr ed 4 ,
+.Xr eg 4 ,
+.Xr el 4 ,
+.Xr ie 4 ,
+.Xr le 4
+.Sh STANDARDS
+are great. There's so many to choose from.
diff --git a/share/man/man4/man4.i386/ie.4 b/share/man/man4/man4.i386/ie.4
new file mode 100644
index 00000000000..c905da190e7
--- /dev/null
+++ b/share/man/man4/man4.i386/ie.4
@@ -0,0 +1,53 @@
+.\"
+.\" Copyright (c) 1994 James A. Jegers
+.\" 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. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission
+.\" 
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.Dd July 10, 1995
+.Dt IE 4 i386
+.Os
+.Sh NAME
+.Nm ie 
+.Nd Ethernet driver for Intel 82586 Ethernet chip
+.Sh SYNOPSIS
+.Cd "ie0 at isa? port 0x360 irq 7 iomem 0xd0000"
+.Sh DESCRIPTION
+The
+.Nm
+interface provides access to a 10 Mb/s Ethernet network via the
+Intel 82586 chips.  The Ethernet cards supported by the
+.Nm
+interface are:
+.Pp
+.Bl -tag -width -offset indet -compact
+.It AT&T StarLAN 10
+.It AT&T EN100
+.It AT&T StarLan Fiber
+.It 3Com 3c507
+.El
+.Sh SEE ALSO
+.Xr ifconfig 8 ,
+.Xr intro 4 ,
+.Xr ed 4 ,
+.Xr eg 4 ,
+.Xr el 4 ,
+.Xr ep 4 ,
+.Xr le 4
diff --git a/share/man/man4/man4.i386/intro.4 b/share/man/man4/man4.i386/intro.4
new file mode 100644
index 00000000000..86eedc090c9
--- /dev/null
+++ b/share/man/man4/man4.i386/intro.4
@@ -0,0 +1,169 @@
+.\"
+.\" Copyright (c) 1994 Christopher G. Demetriou
+.\" All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"      This product includes software developed by Christopher G. Demetriou.
+.\" 3. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.\"	$Id: intro.4,v 1.1 1995/10/18 08:44:29 deraadt Exp $
+.\"
+.Dd
+.Dt INTRO 4 i386
+.Os
+.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.
+.Pp
+This section contains both devices
+which may be configured into the system
+and network related information.
+The networking support is introduced in
+.Xr netintro 4 .
+.Sh DEVICE SUPPORT
+This section describes the hardware supported on the i386
+(PC-clone) platform.
+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 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
+and, if found, enable the software support for it.
+If a device does not respond at autoconfiguration
+time it is not accessible at any time afterwards.
+To enable a device which did not autoconfigure,
+the system must be rebooted.
+.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 autoconf 4 ,
+.Xr config 8 .
+.Sh LIST OF DEVICES
+The devices listed below are supported in this incarnation of
+the system.  Devices are indicated by their functional interface.
+Not all supported devices are listed.
+.Pp
+.Bl -tag -width speaker -offset indent -compact
+.It aha
+Adaptec 154x ISA SCSI adapter boards.
+.It ahb
+Adaptec 1742 EISA SCSI adapter boards.
+.It aic
+Adaptec AIC-6260, Adaptec AIC-6360, Adaptec 152x, and SoundBlaster SCSI boards.
+.It ast
+multiplexing serial communications card first made by AST. 
+.It bt
+Buslogic BT-445, BT-74x, and BT-9xx SCSI boards.
+.It com
+NS8250-, NS16450-, and NS16550-based asynchronous serial
+communications device interface
+.It cy
+Cyclades Cyclom-4Y, -8Y, and -16Y asynchronous serial communications
+device interface
+.It ed
+Western Digital/SMC 80x3 and Ultra, 3Com 3c503, and Novell NE1000 and 2000
+Ethernet interface
+.It eg
+3Com 3c505 Ethernet board.
+.It el
+3Com 3c501 Ethernet board.
+.It ep
+3Com Etherlink III (3c5x9) Ethernet interface
+.It ie
+Ethernet driver for the AT&T StarLAN 10, EN100, StarLan Fiber, and 3Com 3c507.
+.It le
+Ethernet driver for BICC Isolan, Novell NE2100, and Digital DEPCA cards.
+.It lms
+Logitech-style bus mouse device interface
+.It lpt
+Parallel port device interface
+.It mcd
+Mitsumi CD-ROM drives.
+.It mem
+Main memory interface
+.It mms
+Microsoft-style bus mouse device interface
+.It ncr
+NCR PCI SCSI adapter boards.
+.It npx
+Numeric Processing Extension coprocessor and emulator
+.It pms
+PS/2 auxiliary port mouse device interface
+.It rtfps
+another multiplexing serial communications card
+.It sb
+Sound Blaster card.
+.It sea
+Seagate/Future Domain SCSI cards.  ST01/02, Future Domain TMC-885, and
+Future Domain TMC-950.
+.It speaker
+console speaker device interface
+.It uha
+Ultrastor ISA and EISA SCSI adapter cards.  Ultrastore 14f, Ultrastore 34f,
+and Ultrastore 24f.
+.It wd
+Standard ISA Western Digital type hard drives.  MFM, RLL, ESDI, and IDE.
+.It wt
+Wangtek and compatible tape drives.  QIC-02 and QIC-36.
+.El
+.Sh HISTORY
+The
+.Tn i386
+.Nm intro
+appeared in
+.Nx 0.9a .
diff --git a/share/man/man4/man4.i386/le.4 b/share/man/man4/man4.i386/le.4
new file mode 100644
index 00000000000..5152d2d2f83
--- /dev/null
+++ b/share/man/man4/man4.i386/le.4
@@ -0,0 +1,51 @@
+.\"
+.\" Copyright (c) 1994 James A. Jegers
+.\" 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. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission
+.\" 
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.Dd July 10, 1995
+.Dt LE 4 i386
+.Os
+.Sh NAME
+.Nm le 
+.Nd Ethernet driver for Lance based Ethernet boards
+.Sh SYNOPSIS
+.Cd "le0 at isa? port 0x320 irq 10 drq 7"
+.Sh DESCRIPTION
+The
+.Nm
+interface provides access to a 10 Mb/s Ethernet network via the
+Lance Ethernet chips.  The Ethernet cards supported by the
+.Nm
+interface are:
+.Pp
+.Bl -tag -width -offset indet -compact
+.It BICC Isolan 
+.It Novell NE2100
+.It Digital DEPCA
+.El
+.Sh SEE ALSO
+.Xr ifconfig 8 ,
+.Xr intro 4 ,
+.Xr ed 4 ,
+.Xr eg 4 ,
+.Xr ep 4 ,
+.Xr ie 4
diff --git a/share/man/man4/man4.i386/lms.4 b/share/man/man4/man4.i386/lms.4
new file mode 100644
index 00000000000..57df4db0ccd
--- /dev/null
+++ b/share/man/man4/man4.i386/lms.4
@@ -0,0 +1,52 @@
+.\"
+.\" Copyright (c) 1993 Christopher G. Demetriou
+.\" All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"      This product includes software developed by Christopher G. Demetriou.
+.\" 3. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.\"	$Id: lms.4,v 1.1 1995/10/18 08:44:29 deraadt Exp $
+.\"
+.Dd August 6, 1993
+.Dt LMS 4 i386
+.Os NetBSD 0.8a
+.Sh NAME
+.Nm lms
+.Nd
+Logitech-style bus mouse driver
+.Sh SYNOPSIS
+.\" XXX this is awful hackery to get it to work right... -- cgd
+.Cd "lms0 at isa? port" \&"IO_BMS1\&" irq 5
+.Cd "lms0 at isa? port" \&"IO_BMS2\&" irq 5
+.Sh DESCRIPTION
+This driver provides an interface to a Logitech-style bus mouse.
+.Sh FILES
+.Bl -tag -width Pa -compact
+.It Pa /dev/lms0
+first Logitech-style bus mouse
+.El
+.Sh SEE ALSO
+.Xr mms 4 ,
+.Xr pms 4
diff --git a/share/man/man4/man4.i386/lpt.4 b/share/man/man4/man4.i386/lpt.4
new file mode 100644
index 00000000000..9467a5a130e
--- /dev/null
+++ b/share/man/man4/man4.i386/lpt.4
@@ -0,0 +1,53 @@
+.\"
+.\" Copyright (c) 1993 Christopher G. Demetriou
+.\" All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"      This product includes software developed by Christopher G. Demetriou.
+.\" 3. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.\"	$Id: lpt.4,v 1.1 1995/10/18 08:44:29 deraadt Exp $
+.\"
+.Dd August 6, 1993
+.Dt LPT 4 i386
+.Os NetBSD 0.8a
+.Sh NAME
+.Nm lpt
+.Nd
+Parallel port driver
+.Sh SYNOPSIS
+.\" XXX this is awful hackery to get it to work right... -- cgd
+.Cd "lpt0 at isa? port" \&"IO_LPT1\&" irq 7
+.Cd "lpt1 at isa? port" \&"IO_LPT2\&"
+.Sh DESCRIPTION
+This driver provides access to parallel ports.  The highest bit in the minor
+number selects whether to do polling or wait for interrupts.  If no IRQ is
+specified in the kernel configuration, only the polling device may be used.
+.Sh FILES
+.Bl -tag -width Pa -compact
+.It Pa /dev/lpt0
+first interrupt-driven parallel port device
+.It Pa /dev/lpa0
+first polled parallel port device
+.El
diff --git a/share/man/man4/man4.i386/mcd.4 b/share/man/man4/man4.i386/mcd.4
new file mode 100644
index 00000000000..eaf0566c015
--- /dev/null
+++ b/share/man/man4/man4.i386/mcd.4
@@ -0,0 +1,42 @@
+.\"
+.\" Copyright (c) 1994 James A. Jegers
+.\" 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. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission
+.\" 
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.\"
+.Dd November 29, 1994
+.Dt MCD 4 i386
+.Os NetBSD 
+.Sh NAME
+.Nm mcd
+.Nd Mitsumi CD-ROM driver
+.Sh SYNOPSIS
+.Cd "mcd0 at isa? port 0x300 irq 10"
+.Sh DESCRIPTION
+The
+.Nm mcd 
+driver provides support for Mitsumi CD-ROM drives and controllers.
+.Pp
+.Sh FILES
+.Xr /dev/mcd*
+.Xr /dev/rmcd*
+.Sh SEE ALSO
+.Xr intro 4
diff --git a/share/man/man4/man4.i386/mem.4 b/share/man/man4/man4.i386/mem.4
new file mode 100644
index 00000000000..47ffeaf3e51
--- /dev/null
+++ b/share/man/man4/man4.i386/mem.4
@@ -0,0 +1,83 @@
+.\" Copyright (c) 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"	from: @(#)mem.4	5.3 (Berkeley) 5/2/91
+.\"	$Id: mem.4,v 1.1 1995/10/18 08:44:29 deraadt Exp $
+.\"
+.Dd May 2, 1991
+.Dt MEM 4 i386
+.Os
+.Sh NAME
+.Nm mem ,
+.Nm kmem
+.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
+On
+.Tn ISA
+the
+.Tn I/O
+memory space begins at physical address 0x000a0000
+and runs to 0x00100000.
+The
+per-process data
+size
+for the current process
+is
+.Dv UPAGES
+long, and ends at virtual
+address 0xfe000000.
+.Sh FILES
+.Bl -tag -width Pa -compact
+.It Pa /dev/mem
+.It Pa /dev/kmem
+.El
+.Sh HISTORY
+The
+.Nm mem ,
+.Nm kmem
+files appeared in
+.At v6 .
diff --git a/share/man/man4/man4.i386/mms.4 b/share/man/man4/man4.i386/mms.4
new file mode 100644
index 00000000000..44cfab83dbd
--- /dev/null
+++ b/share/man/man4/man4.i386/mms.4
@@ -0,0 +1,51 @@
+.\"
+.\" Copyright (c) 1993 Christopher G. Demetriou
+.\" All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"      This product includes software developed by Christopher G. Demetriou.
+.\" 3. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.\"	$Id: mms.4,v 1.1 1995/10/18 08:44:30 deraadt Exp $
+.\"
+.Dd August 6, 1993
+.Dt MMS 4 i386
+.Os NetBSD 0.8a
+.Sh NAME
+.Nm mms
+.Nd
+Microsoft-style bus mouse driver
+.Sh SYNOPSIS
+.\" XXX this is awful hackery to get it to work right... -- cgd
+.Cd "mms0 at isa? port" \&"IO_BMS1\&" irq 5
+.Sh DESCRIPTION
+This driver provides an interface to a Microsoft-style bus mouse.
+.Sh FILES
+.Bl -tag -width Pa -compact
+.It Pa /dev/mms0
+first Microsoft-style bus mouse
+.El
+.Sh SEE ALSO
+.Xr lms 4 ,
+.Xr pms 4
diff --git a/share/man/man4/man4.i386/ncr.4 b/share/man/man4/man4.i386/ncr.4
new file mode 100644
index 00000000000..7a33b1bdeda
--- /dev/null
+++ b/share/man/man4/man4.i386/ncr.4
@@ -0,0 +1,43 @@
+.\"
+.\" Copyright (c) 1994 James A. Jegers
+.\" 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. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission
+.\" 
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.\"
+.Dd November 29, 1994
+.Dt NCR 4 i386
+.Os NetBSD 
+.Sh NAME
+.Nm ncr
+.Nd NCR 53C810 SCSI driver
+.Sh SYNOPSIS
+.Cd "ncr* at pci? bus ? dev ?"
+.Cd "scsibus* at ncr?"
+.Sh DESCRIPTION
+The
+.Nm ncr
+driver provides support for the NCR 53C810 SCSI controller chip.
+.Sh SEE ALSO
+.Xr intro 4 ,
+.Xr sd 4 ,
+.Xr st 4 ,
+.Xr cd 4 ,
+.Xr ch 4  
diff --git a/share/man/man4/man4.i386/npx.4 b/share/man/man4/man4.i386/npx.4
new file mode 100644
index 00000000000..8a4f5f5f24b
--- /dev/null
+++ b/share/man/man4/man4.i386/npx.4
@@ -0,0 +1,76 @@
+.\"
+.\" Copyright (c) 1993 Christopher G. Demetriou
+.\" All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"      This product includes software developed by Christopher G. Demetriou.
+.\" 3. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.\"	$Id: npx.4,v 1.1 1995/10/18 08:44:30 deraadt Exp $
+.\"
+.Dd August 6, 1993
+.Dt NPX 4 i386
+.Os NetBSD 0.8a
+.Sh NAME
+.Nm npx
+.Nd
+Numeric Processing Extension coprocessor and emulator
+.Sh SYNOPSIS
+.Cd "options MATH_EMULATE"
+.\" XXX this is awful hackery to get it to work right... -- cgd
+.Cd "npx0 at isa? port" \&"IO_NPX0\&" irq 13
+.Sh DESCRIPTION
+The
+.Nm npx
+driver enables the use of the system's Numeric Processing Extension
+coprocessor,
+if one is present.  Numeric processing extensions are present in
+systems with
+.Nm 486DX
+CPUs and in systems with
+.Nm 387
+or
+.Nm 487SX
+coprocessors.  The
+.Nm npx
+driver is required for proper system functioning regardless
+of whether or not a NPX is present.
+.Pp
+If there is no NPX present in the system, the "MATH_EMULATE"
+option must be defined in the kernel configuration file.
+It will provide support for the instructions normally executed
+by the NPX.  If there is no NPX in the system and the kernel
+is not built with math emulation, the system will not boot.
+.Sh CAVEATS
+The emulator is much slower than the NPX coprocessor.
+This will result in poor floating-point math performance
+if the emulator must be used.
+.Sh BUGS
+There are lots of them, especially on cheap motherboards.  In particular,
+some motherboards do not have the interrupt lines from the NPX to
+the CPU wired properly.  If this is the case, the emulator must be used
+if consistent system operation is desired.
+.Pp
+Emulation of the transcendental functions instructions is incorrect.
+Emulation of other instructions is suspect.
diff --git a/share/man/man4/man4.i386/pms.4 b/share/man/man4/man4.i386/pms.4
new file mode 100644
index 00000000000..9ac78a0877d
--- /dev/null
+++ b/share/man/man4/man4.i386/pms.4
@@ -0,0 +1,51 @@
+.\"
+.\" Copyright (c) 1993 Christopher G. Demetriou
+.\" All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"      This product includes software developed by Christopher G. Demetriou.
+.\" 3. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.\"	$Id: pms.4,v 1.1 1995/10/18 08:44:30 deraadt Exp $
+.\"
+.Dd August 6, 1993
+.Dt PMS 4 i386
+.Os NetBSD 0.8a
+.Sh NAME
+.Nm pms
+.Nd
+PS/2 auxiliary port mouse driver
+.Sh SYNOPSIS
+.\" XXX this is awful hackery to get it to work right... -- cgd
+.Cd "pms0 at isa? port" \&"IO_KBD\&" irq 12
+.Sh DESCRIPTION
+This driver provides an interface to a PS/2 auxiliary port mice.
+.Sh FILES
+.Bl -tag -width Pa -compact
+.It Pa /dev/pms0
+PS/2 mouse device file
+.El
+.Sh SEE ALSO
+.Xr lms 4 ,
+.Xr mms 4
diff --git a/share/man/man4/man4.i386/rtfps.4 b/share/man/man4/man4.i386/rtfps.4
new file mode 100644
index 00000000000..9e315b2f492
--- /dev/null
+++ b/share/man/man4/man4.i386/rtfps.4
@@ -0,0 +1,103 @@
+.\"
+.\" Copyright (c) 1990, 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" the Systems Programming Group of the University of Utah Computer
+.\" Science Department.
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)dca.4	5.2 (Berkeley) 3/27/91
+.\"	from: Id: com.4,v 1.1 1993/08/06 11:19:07 cgd Exp
+.\"	$Id: rtfps.4,v 1.1 1995/10/18 08:44:30 deraadt Exp $
+.\"
+.Dd August 7, 1994
+.Dt RTFPS 4 i386
+.Os NetBSD 1.0
+.Sh NAME
+.Nm rtfps
+.Nd
+multiplexing serial communications interface
+.Sh SYNOPSIS
+.Cd "rtfps0 at isa? port 0x1230 irq 10"
+.Cd "com2 at rtfps0 slave 0"
+.Cd "com3 at rtfps0 slave 1"
+.Cd "com4 at rtfps0 slave 2"
+.Cd "com5 at rtfps0 slave 3"
+.Sh DESCRIPTION
+The
+.Nm rtfps
+driver provides support for IBM RT PC boards that multiplex together up to four
+.Rn EIA
+.Tn RS-232C
+.Pf ( Tn CCITT
+.Tn V.28 )
+or
+.Tn RS-422A
+communications interfaces.
+.Pp
+Each
+.Nm
+device is the master device for up to four 
+.Nm com
+devices.  The kernel configuration specifies these
+.Nm com
+devices as slave devices of the
+.Nm
+device, as shown in the synopsis.
+The
+.Tn port
+specification for the
+.Nm
+device is used to compute the base addresses for the
+.Nm com
+subdevices.
+.Sh FILES
+.Bl -tag -width Pa
+.It Pa /dev/tty0?
+.El
+.Sh SEE ALSO
+.Xr com 4
+.Sh HISTORY
+The
+.Nm
+driver was written by Charles Hannum, based on the
+.Nm ast
+driver.
+.Sh BUGS
+The
+.Nm
+driver is unlikely to work on non-EISA and non-PCI machines.  The ISA
+bus only asserts 10 I/O address lines, and this is not enough.
+.Pp
+Even on EISA and PCI machines, some address conflicts have been observed.
+On one machine, the second port always conflicted with something (though
+it's not clear what) and caused strange results.  Disabling the second
+port in the kernel config allowed the other three ports to function
+correctly.
diff --git a/share/man/man4/man4.i386/sea.4 b/share/man/man4/man4.i386/sea.4
new file mode 100644
index 00000000000..1e20421bf20
--- /dev/null
+++ b/share/man/man4/man4.i386/sea.4
@@ -0,0 +1,50 @@
+.\"
+.\" Copyright (c) 1994 James A. Jegers
+.\" 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. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission
+.\" 
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.\"
+.Dd November 29, 1994
+.Dt SEA 4 i386
+.Os NetBSD 
+.Sh NAME
+.Nm sea
+.Nd
+Seagate/Future Domain ISA SCSI adapter card.
+.Sh SYNOPSIS
+.Cd "sea0 at isa? iomem 0xc8000 irq 5"
+.Cd "scsibus* at sea?"
+.Sh DESCRIPTION
+The
+.Nm sea
+driver provides support for the following boards:
+.Pp
+.Bl -tag -width -offset indent -compact
+.It ST01/02 
+.It Future Domain TMC-885
+.It Future Domain TMC-950
+.El
+.Sh SEE ALSO
+.Xr intro 4 ,
+.Xr sd 4 ,
+.Xr st 4 ,
+.Xr cd 4 ,
+.Xr ch 4  
diff --git a/share/man/man4/man4.i386/speaker.4 b/share/man/man4/man4.i386/speaker.4
new file mode 100644
index 00000000000..dce825750ed
--- /dev/null
+++ b/share/man/man4/man4.i386/speaker.4
@@ -0,0 +1,152 @@
+.\"
+.\" Copyright (c) 1993 Christopher G. Demetriou
+.\" All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"      This product includes software developed by Christopher G. Demetriou.
+.\" 3. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.\"	$Id: speaker.4,v 1.1 1995/10/18 08:44:30 deraadt Exp $
+.\"
+.Dd August 6, 1993
+.Dt SPEAKER 4 i386
+.Os NetBSD 0.8a
+.Sh NAME
+speaker \- console speaker device driver
+.Sh SYNOPSIS
+.Cd "pseudo-device speaker"
+.Sh DESCRIPTION
+The speaker device driver allows applications to control the PC console
+speaker on an IBM-PC-compatible machine running UNIX.
+.Pp
+Only one process may have this device open at any given time; open() and
+close() are used to lock and relinquish it. An attempt to open() when
+another process has the device locked will return -1 with an EBUSY error
+indication. Writes to the device are interpreted as 'play strings' in a
+simple ASCII melody notation. An ioctl() for tone generation at arbitrary
+frequencies is also supported.
+.Pp
+Sound-generation does \fInot\fR monopolize the processor; in fact, the driver
+spends most of its time sleeping while the PC hardware is emitting
+tones. Other processes may emit beeps while the driver is running.
+.Pp
+Applications may call ioctl() on a speaker file descriptor to control the
+speaker driver directly; definitions for the ioctl() interface are in
+machine/spkr.h. The tone_t structure used in these calls has two fields,
+specifying a frequency (in hz) and a duration (in 1/100ths of a second).
+A frequency of zero is interpreted as a rest.
+.Pp
+At present there are two such ioctls. SPKRTONE accepts a pointer to a
+single tone structure as third argument and plays it. SPKRTUNE accepts a
+pointer to the first of an array of tone structures and plays them in
+continuous sequence; this array must be terminated by a final member with
+a zero duration.
+.Pp
+The play-string language is modelled on the PLAY statement conventions of
+IBM BASIC 2.0. The MB, MF and X primitives of PLAY are not useful in a UNIX 
+environment and are omitted. The `octave-tracking' feature is also new.
+.Pp
+There are 84 accessible notes numbered 1-83 in 7 octaves, each running from
+C to B, numbered 0-6; the scale is equal-tempered A440 and octave 3 starts
+with middle C. By default, the play function emits half-second notes with the
+last 1/16th second being `rest time'.
+.Pp
+Play strings are interpreted left to right as a series of play command groups;
+letter case is ignored. Play command groups are as follows:
+.Pp
+CDEFGAB -- letters A through G cause the corresponding note to be played in the
+current octave. A note letter may optionally be followed by an \fIaccidental
+sign\fR, one of # + or -; the first two of these cause it to be sharped one
+half-tone, the last causes it to be flatted one half-tone. It may also be
+followed by a time value number and by sustain dots (see below). Time values
+are interpreted as for the L command below;.
+.Pp
+O <n> -- if <n> is numeric, this sets the current octave. <n> may also be one
+of 'L' or 'N' to enable or disable octave-tracking (it is disabled by default).
+When octave-tracking is on, interpretation of a pair of letter notes will
+change octaves if necessary in order to make the smallest possible jump between
+notes. Thus "olbc" will be played as "olb>c", and "olcb" as "olc<b". Octave
+locking is disabled for one letter note following by >, < and O[0123456].
+.Pp
+> -- bump the current octave up one.
+.Pp
+< -- drop the current octave down one.
+.Pp
+N <n> -- play note n, n being 1 to 84 or 0 for a rest of current time value.
+May be followedv by sustain dots.
+.Pp
+L <n> -- sets the current time value for notes. The default is L4, quarter
+notes. The lowest possible value is 1; values up to 64 are accepted. L1 sets
+whole notes, L2 sets half notes, L4 sets quarter notes, etc..
+.Pp
+P <n> -- pause (rest), with <n> interpreted as for L. May be followed by
+sustain dots. May also be written '~'.
+.Pp
+T <n> -- Sets the number of quarter notes per minute; default is 120. Musical
+names for common tempi are:
+.Bl -column Description Tempo BPM -offset indent
+.Em 	Tempo		Beats per Minute
+very slow	Larghissimo	
+        	Largo	 	40-60
+         	Larghetto	60-66
+        	Grave       	
+        	Lento       	
+        	Adagio	 	66-76
+slow    	Adagietto    	
+        	Andante	 	76-108
+medium   	Andantino	
+        	Moderato 	108-120
+fast    	Allegretto	
+        	Allegro	 	120-168
+        	Vivace    	
+        	Veloce    	
+        	Presto	 	168-208
+very fast	Prestissimo	
+.El
+.Pp
+M[LNS] -- set articulation. MN (N for normal) is the default; the last 1/8th of
+the note's value is rest time. You can set ML for legato (no rest space) or
+MS (staccato) 1/4 rest space.
+.Pp
+Notes (that is, CDEFGAB or N command character groups) may be followed by
+sustain dots. Each dot causes the note's value to be lengthened by one-half
+for each one. Thus, a note dotted once is held for 3/2 of its undotted value;
+dotted twice, it is held 9/4, and three times would give 27/8. 
+.Pp
+Whitespace in play strings is simply skipped and may be used to separate
+melody sections.
+.Sh BUGS
+Due to roundoff in the pitch tables and slop in the tone-generation and timer
+hardware (neither of which was designed for precision), neither pitch accuracy
+nor timings will be mathematically exact. There is no volume control.
+.Pp
+In play strings which are very long (longer than your system's physical I/O
+blocks) note suffixes or numbers may occasionally be parsed incorrectly due
+to crossing a block boundary.
+.Sh FILES
+.Bl -tag -width Pa -compact
+.It Pa /dev/speaker
+.El
+.Sh AUTHOR
+Eric S. Raymond (esr@snark.thyrsus.com) Feb 1990
diff --git a/share/man/man4/man4.i386/uha.4 b/share/man/man4/man4.i386/uha.4
new file mode 100644
index 00000000000..5ed06d6b759
--- /dev/null
+++ b/share/man/man4/man4.i386/uha.4
@@ -0,0 +1,50 @@
+.\"
+.\" Copyright (c) 1994 James A. Jegers
+.\" 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. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission
+.\" 
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.\"
+.Dd November 29, 1994
+.Dt UHA 4 i386
+.Os NetBSD 
+.Sh NAME
+.Nm uha
+.Nd Ultrastor SCSI adapter driver
+.Sh SYNOPSIS
+.Cd "uha0 at isa? port 0x330 irq ? drq ?"
+.Cd "uha* at eisa? slot ? irq ?"
+.Cd "scsibus* at uha?"
+.Sh DESCRIPTION
+The
+.Nm uha
+driver provides support for the following SCSI adapters:
+.Pp
+.Bl -tag -width -offset indent -compact
+.It Ultrastor 14f
+.It Ultrastor 24f
+.It Ultrastor 34f 
+.El
+.Sh SEE ALSO
+.Xr intro 4 ,
+.Xr sd 4 ,
+.Xr st 4 ,
+.Xr cd 4 ,
+.Xr ch 4  
diff --git a/share/man/man4/man4.i386/wd.4 b/share/man/man4/man4.i386/wd.4
new file mode 100644
index 00000000000..a588fe82883
--- /dev/null
+++ b/share/man/man4/man4.i386/wd.4
@@ -0,0 +1,43 @@
+.\"
+.\" Copyright (c) 1994 James A. Jegers
+.\" 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. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission
+.\" 
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.Dd November 29, 1994
+.Dt WD 4 i386
+.Os NetBSD 
+.Sh NAME
+.Nm wd 
+.Nd WD100x compatible hard disk driver
+.Sh SYNOPSIS
+.Cd "wdc0 at isa? port 0x1f0 irq 14"
+.Cd "wd* at wdc? drive ?"
+.Sh DESCRIPTION
+The
+.Nm wd 
+driver supports hard disk controllers which emulate the Western
+Digital WD100x.  This includes standard MFM, RLL, ESDI and IDE
+controllers.
+.Pp
+Support for extended EIDE controllers is
+.Ud .
+.Sh SEE ALSO
+.Xr intro 4
diff --git a/share/man/man4/man4.i386/wt.4 b/share/man/man4/man4.i386/wt.4
new file mode 100644
index 00000000000..dfecd71877b
--- /dev/null
+++ b/share/man/man4/man4.i386/wt.4
@@ -0,0 +1,44 @@
+.\"
+.\" Copyright (c) 1994 James A. Jegers
+.\" 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. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission
+.\" 
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.Dd July 10, 1995
+.Dt WT 4 i386
+.Os 
+.Sh NAME
+.Nm wt
+.Nd
+Archive/Wangtek cartrige tape driver
+.Sh SYNOPSIS
+.Cd "wt0 at isa? port 0x300 irq 5 drq 1"
+.Sh DESCRIPTION
+The
+.Nm wt 
+driver provides support for the following Archive and Wangtek boards:
+.Pp
+.Bl -tag -width -offset indet -compact
+.It QIC-02 
+.It QIC-36 
+.El
+.Pp
+.Sh SEE ALSO
+.Xr intro 4
diff --git a/share/man/man4/man4.mac68k/Makefile b/share/man/man4/man4.mac68k/Makefile
new file mode 100644
index 00000000000..0ab5d31ca5d
--- /dev/null
+++ b/share/man/man4/man4.mac68k/Makefile
@@ -0,0 +1,8 @@
+#	from: @(#)Makefile	5.1 (Berkeley) 6/29/90
+#	$Id: Makefile,v 1.1 1995/10/18 08:44:30 deraadt Exp $
+
+MAN=
+MLINKS=
+MANSUBDIR=/mac68k
+
+.include <bsd.prog.mk>
diff --git a/share/man/man4/man4.pc532/Makefile b/share/man/man4/man4.pc532/Makefile
new file mode 100644
index 00000000000..86185f79674
--- /dev/null
+++ b/share/man/man4/man4.pc532/Makefile
@@ -0,0 +1,10 @@
+#	$NetBSD: Makefile,v 1.2 1995/06/27 18:22:51 phil Exp $
+#	Makefile for man4/man4.pc532
+
+MAN=	lpt.4 plip.4
+MANSUBDIR=/pc532
+
+plip.cat4:
+	tbl ${.IMPSRC} | nroff -mandoc > ${.TARGET}
+
+.include <bsd.prog.mk>
diff --git a/share/man/man4/man4.pc532/lpt.4 b/share/man/man4/man4.pc532/lpt.4
new file mode 100644
index 00000000000..72f32304a33
--- /dev/null
+++ b/share/man/man4/man4.pc532/lpt.4
@@ -0,0 +1,69 @@
+.\"	$NetBSD: lpt.4,v 1.1 1995/06/22 04:45:43 phil Exp $
+.\"
+.\" Copyright (c) 1994 Matthias Pfaller.
+.\" 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 Matthias Pfaller.
+.\" 4. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.\"	$Id: lpt.4,v 1.1 1995/10/18 08:44:30 deraadt Exp $
+.\"
+.Dd December 1, 1994
+.Dt LPT 4 pc532
+.Os NetBSD 1.0
+.Sh NAME
+.Nm lpt
+.Nd Parallel port driver
+.Sh SYNOPSIS
+.Cd "lpt0 at membus? iomem ? irq ?"
+.Cd "lpt1 at membus? iomem ? irq ?"
+.Sh DESCRIPTION
+This driver provides access to centronics ports. Bit 6 in the minor number
+selects wether to omit pulling PRIME low on opens or not. If the minor has
+bit 5 set, AUTOLINEFEED will be asserted when transfering data to the printer.
+Iomem defaults to 0xffc80030 for lpt0 and to 0xffc80034 for lpt1. 
+Irq defaults to 7 for lpt0 and to 6 for lpt1.
+.Sh FILES
+.Bl -tag -width Pa -compact
+.It Pa /dev/lpt0
+first parallel port device
+.It Pa /dev/lpt1
+second parallel port device
+.El
+.Sh DIAGNOSTICS
+.Bl -diag
+.It "lpt?: out of paper"
+The printer asserted the
+.Em Paper Empty
+signal.
+.It "lpt?: offline"
+The printer did not assert the
+.Em Select
+signal.
+.It "lpt?: output error"
+The printer asserted the
+.Em /Error
+signal.
+.El
diff --git a/share/man/man4/man4.pc532/plip.4 b/share/man/man4/man4.pc532/plip.4
new file mode 100644
index 00000000000..ac721e1e1a0
--- /dev/null
+++ b/share/man/man4/man4.pc532/plip.4
@@ -0,0 +1,92 @@
+.\"	$NetBSD: plip.4,v 1.2 1995/06/27 18:11:07 phil Exp $
+.\"
+.\" Copyright (c) 1994 Matthias Pfaller.
+.\" 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 Matthias Pfaller.
+.\" 4. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.\"
+.Dd December 1, 1994
+.Dt PLIP 4 pc532
+.Os NetBSD 1.0
+.Sh NAME
+.Nm plip
+.Nd "Option for the lpt driver to allow IP over centronics ports"
+.Sh SYNOPSIS
+.Cd "options PLIP"
+.Cd "options COMPAT_PLIP10"
+.Sh DESCRIPTION
+The
+.Nm
+interface provides a way to transport IP over centronics ports.
+Protocols to communicate with Linux 1.0 and Linux 1.1 hosts are provided.
+By default the 1.1 protocol is used. To choose the 1.0 protocol use
+the link0 flag with
+.Xr ifconfig 8
+or in your /etc/hostname.plip? file. In order to use the 1.0 protocol
+the kernel has to be compiled with COMPAT_PLIP10.
+.Sh NOTES
+To connect two computers a "Laplink parallel cabel" is used:
+.sp
+.TS
+allbox tab(|);
+c|c|c|c
+l|n|n|l.
+Signalname|Con A|Con B|Description
+Data 0|2|15|Data out 0
+Data 1|3|13|Data out 1
+Data 2|4|12|Data out 2
+Data 3|5|10|Data out 3/Wake out
+Data 4|6|11|Data clock out
+/Ack|10|5|Data in 3/Wake in
+Busy|11|6|Data clock in
+No Paper|12|4|Data in 2
+Select|13|3|Data in 1
+/Error|15|2|Data in 0
+Gnd|18-25|18-25|Ground
+.TE
+.sp
+In both protocol versions ethernet frames are used. The 1.0 protocol assings
+an ethernet address of the form FD:FD:ww:xx:yy:zz to the interface. The 1.1
+protocol uses FC instead of FD. ww, xx, yy and zz are taken from the internet
+address ww.xx.yy.zz of the interface. Ethernet support has
+to be configured into the kernel in order to use the
+.Nm
+interface.
+.Sh SEE ALSO
+.Xr lpt 4
+.Xr ifconfig 8
+.Sh DIAGNOSTICS
+.Bl -diag
+.It "plip?: tx hard error"
+Packet transmission failed even after PLIPMXRETRY (20) retries.
+.It "plip?: rx hard error"
+PLIPMXERRS (20) packets caused receive errors in sequence.
+.It "plip?: checksum error"
+A packet with a bad checksum was received.
+.It "plip?: packet > MTU"
+A bogus packet longer then MTU was received.
+.El
diff --git a/share/man/man4/man4.sparc/Makefile b/share/man/man4/man4.sparc/Makefile
new file mode 100644
index 00000000000..f9e61d71a4e
--- /dev/null
+++ b/share/man/man4/man4.sparc/Makefile
@@ -0,0 +1,8 @@
+# 	from: @(#)Makefile	8.2 (Berkeley) 2/16/94
+#	$Id: Makefile,v 1.1 1995/10/18 08:44:31 deraadt Exp $
+
+MAN=	bwtwo.4 cgsix.4 cgthree.4 le.4 mem.4 openprom.4
+MLINKS=	mem.4 kmem.4
+MANSUBDIR=/sparc
+
+.include <bsd.prog.mk>
diff --git a/share/man/man4/man4.sparc/bwtwo.4 b/share/man/man4/man4.sparc/bwtwo.4
new file mode 100644
index 00000000000..998a01b51b2
--- /dev/null
+++ b/share/man/man4/man4.sparc/bwtwo.4
@@ -0,0 +1,55 @@
+.\" Copyright (c) 1992, 1993
+.\"	The Regents of the University of California.  All rights reserved.
+.\"
+.\" This software was developed by the Computer Systems Engineering group
+.\" at Lawrence Berkeley Laboratory under DARPA contract BG 91-66 and
+.\" contributed to Berkeley.
+.\"
+.\" 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: Header: bwtwo.4,v 1.3 94/02/03 20:42:13 leres Exp
+.\"     from: @(#)bwtwo.4	8.2 (Berkeley) 2/16/94
+.\"	$Id: bwtwo.4,v 1.1 1995/10/18 08:44:31 deraadt Exp $
+.\"
+.Dd February 16, 1994
+.Dt BWTWO 4 sparc
+.Os
+.Sh NAME
+.Nm bwtwo
+.Nd monochromatic frame buffer
+.Sh SYNOPSIS
+.Cd "bwtwo* at sbus? slot ? offset ?"
+.Sh DESCRIPTION
+The 
+.Nm
+is a memory based black and white frame buffer.
+It supports the minimal ioctl's needed to run X11.
+.Sh SEE ALSO
+.Xr cgsix 4 ,
+.Xr cgthree 4
diff --git a/share/man/man4/man4.sparc/cgsix.4 b/share/man/man4/man4.sparc/cgsix.4
new file mode 100644
index 00000000000..25ebae26925
--- /dev/null
+++ b/share/man/man4/man4.sparc/cgsix.4
@@ -0,0 +1,54 @@
+.\" Copyright 1994
+.\"	The Regents of the University of California.  All rights reserved.
+.\"
+.\" This software was developed by the Computer Systems Engineering group
+.\" at Lawrence Berkeley Laboratory under DARPA contract BG 91-66 and
+.\" contributed to Berkeley.
+.\"
+.\" 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: @(#)cgsix.4	8.1 (Berkeley) 2/16/94
+.\"	$Id: cgsix.4,v 1.1 1995/10/18 08:44:31 deraadt Exp $
+.\"
+.Dd February 16, 1994
+.Dt CGSIX 4 sparc
+.Os
+.Sh NAME
+.Nm cgsix
+.Nd accelerated 8-bit color frame buffer
+.Sh SYNOPSIS
+.Cd "cgsix* at sbus? slot ? offset ?"
+.Sh DESCRIPTION
+The 
+.Nm cgsix
+is a memory based color frame buffer.
+It supports the minimal ioctl's needed to run X11.
+.Sh SEE ALSO
+.Xr bwtwo 4 ,
+.Xr cgthree 4
diff --git a/share/man/man4/man4.sparc/cgthree.4 b/share/man/man4/man4.sparc/cgthree.4
new file mode 100644
index 00000000000..9e010123b90
--- /dev/null
+++ b/share/man/man4/man4.sparc/cgthree.4
@@ -0,0 +1,56 @@
+.\" Copyright (c) 1992, 1993
+.\"	The Regents of the University of California.  All rights reserved.
+.\"
+.\" This software was developed by the Computer Systems Engineering group
+.\" at Lawrence Berkeley Laboratory under DARPA contract BG 91-66 and
+.\" contributed to Berkeley.
+.\"
+.\" 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: Header: cgthree.4,v 1.3 94/02/03 20:49:52 leres Exp
+.\"     from: @(#)cgthree.4	8.2 (Berkeley) 2/16/94
+.\"	$Id: cgthree.4,v 1.1 1995/10/18 08:44:31 deraadt Exp $
+.\"
+.Dd February 16, 1994
+.Dt CGTHREE 4 sparc
+.Os
+.Sh NAME
+.Nm cgthree
+.Nd 8-bit color frame buffer
+.Sh SYNOPSIS
+...Cd "bwtwo*  at sbus? slot ? offset ?"
+.Cd "cgthree* at sbus? slot ? offset ?"
+.Sh DESCRIPTION
+The 
+.Nm
+is a memory based color frame buffer.
+It supports the minimal ioctl's needed to run X11.
+.Sh SEE ALSO
+.Xr bwtwo 4 ,
+.Xr cgsix 4
diff --git a/share/man/man4/man4.sparc/le.4 b/share/man/man4/man4.sparc/le.4
new file mode 100644
index 00000000000..533eb0f1dd9
--- /dev/null
+++ b/share/man/man4/man4.sparc/le.4
@@ -0,0 +1,70 @@
+.\" Copyright (c) 1992, 1993
+.\"	The Regents of the University of California.  All rights reserved.
+.\"
+.\" This software was developed by the Computer Systems Engineering group
+.\" at Lawrence Berkeley Laboratory under DARPA contract BG 91-66 and
+.\" contributed to Berkeley.
+.\"
+.\" 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: Header: le.4,v 1.2 92/10/13 05:31:33 leres Exp
+.\"	from: @(#)le.4	8.1 (Berkeley) 6/9/93
+.\"	$Id: le.4,v 1.1 1995/10/18 08:44:31 deraadt Exp $
+.\"
+.Dd June 9, 1993
+.Dt LE 4 sparc
+.Os
+.Sh NAME
+.Nm le
+.Nd SPARC AMD 7990 LANCE ethernet interface
+.Sh SYNOPSIS
+.Cd "le* at sbus? slot ? offset ?"
+.Sh DESCRIPTION
+The 
+.Nm
+interface provides access to the 10 Mb/s Ethernet network via the
+.Tn AMD
+7990
+.Tn LANCE
+Ethernet chip set.
+.Pp
+Each of the host's network addresses
+is specified at boot time with an
+.Dv SIOCSIFADDR
+.Xr ioctl .
+The
+.Nm
+interface employs the address resolution protocol described in
+.Xr arp 4
+to dynamically map between Internet and Ethernet addresses on the local
+network.
+.Sh SEE ALSO
+.Xr intro 4 ,
+.Xr inet 4 ,
+.Xr arp 4
diff --git a/share/man/man4/man4.sparc/mem.4 b/share/man/man4/man4.sparc/mem.4
new file mode 100644
index 00000000000..513b1f3e384
--- /dev/null
+++ b/share/man/man4/man4.sparc/mem.4
@@ -0,0 +1,80 @@
+.\" Copyright (c) 1992, 1993
+.\"	The Regents of the University of California.  All rights reserved.
+.\"
+.\" This software was developed by the Computer Systems Engineering group
+.\" at Lawrence Berkeley Laboratory under DARPA contract BG 91-66 and
+.\" contributed to Berkeley.
+.\"
+.\" 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	8.1 (Berkeley) 6/5/93
+.\"	$Id: mem.4,v 1.1 1995/10/18 08:44:31 deraadt Exp $
+.\"
+.Dd June 5, 1993
+.Dt MEM 4 sparc
+.Os
+.Sh NAME
+.Nm mem ,
+.Nm kmem
+.Nd main memory
+.Sh DESCRIPTION
+The 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.
+An error will be returned if an attempt is made to reference
+an offset outside of
+.Nm /dev/mem .
+.Pp
+Kernel virtual memory is accessed via the file
+.Nm /dev/kmem
+in the same manner as
+.Nm /dev/mem .
+Only kernel virtual addresses that are currently mapped to memory are allowed.
+.Sh SPARC
+On the
+.Tn SPARC ,
+physical memory may be discontiguous;
+kernel virtual memory begins at
+.Li 0xf8000000 .
+.Sh FILES
+.Bl -tag -width /dev/kmem -compact
+.It Pa /dev/mem
+.It Pa /dev/kmem
+.El
+.Sh HISTORY
+The files
+.Nm mem
+and
+.Nm kmem
+appeared in
+.At v6 .
diff --git a/share/man/man4/man4.sparc/openprom.4 b/share/man/man4/man4.sparc/openprom.4
new file mode 100644
index 00000000000..9aeb200e967
--- /dev/null
+++ b/share/man/man4/man4.sparc/openprom.4
@@ -0,0 +1,154 @@
+.\" Copyright (c) 1992, 1993
+.\"	The Regents of the University of California.  All rights reserved.
+.\"
+.\" This software was developed by the Computer Systems Engineering group
+.\" at Lawrence Berkeley Laboratory under DARPA contract BG 91-66 and
+.\" contributed to Berkeley.
+.\"
+.\" 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: @(#)openprom.4	8.1 (Berkeley) 6/5/93
+.\"	$Id: openprom.4,v 1.1 1995/10/18 08:44:31 deraadt Exp $
+.\"
+.Dd June 5, 1993
+.Dt OPENPROM 4 sparc
+.Os
+.Sh NAME
+.Nm openprom
+.Nd OPENPROM and EEPROM interface
+.Sh SYNOPSIS
+.Fd #include <machine/openpromio.h>
+.Sh DESCRIPTION
+The file
+.Nm /dev/openprom
+is an interface to the SPARC OPENPROM,
+including the EEPROM area.
+This interface is highly stylized;
+ioctls are used for all operations.
+These ioctls refer to
+.Dq nodes ,
+which are simply
+.Dq magic
+integer values describing data areas.
+Occasionally the number 0 may be used or returned instead,
+as described below.
+A special distinguished
+.Dq options
+node holds the EEPROM settings.
+.Pp
+The calls that take and/or return a node
+use a pointer to an
+.Li int
+variable for this purpose;
+others use a pointer to an
+.Li struct opiocdesc
+descriptor,
+which contains a node and two counted strings.
+The first string is comprised of the fields
+.Li op_namelen
+(an
+.Li int )
+and
+.Li op_name
+(a
+.Li "char *" ) ,
+giving the name of a field.
+The second string is comprised of the fields
+.Li op_buflen
+and
+.Li op_buf ,
+used analogously.
+These two counted strings work in a
+.Dq value-result
+fashion.
+At entry to the ioctl,
+the counts are expected to reflect the buffer size;
+on return,
+the counts are updated to reflect the buffer contents.
+.Pp
+The following ioctls are supported:
+.Bl -tag -width OPIOCGETOPTNODE
+.It Dv OPIOCGETOPTNODE
+Takes nothing, and fills in the options node number.
+.It OPIOCGETNEXT
+Takes a node number and returns the number of the following node.
+The node following the last node is number 0;
+the node following number 0 is the first node.
+.It Dv OPIOCGETCHILD
+Takes a node number and returns the number of the first
+.Dq child
+of that node.
+This child may have siblings; these can be discovered by using
+.Dv OPIOCGETNEXT .
+.It Dv OPIOCGET
+Fills in the value of the named property for the given node.
+If no such property is associated with that node,
+the value length is set to -1.
+If the named property exists but has no value,
+the value length is set to 0.
+.It Dv OPIOCSET
+Writes the given value under the given name.
+The OPENPROM may refuse this operation;
+in this case
+.Dv EINVAL
+is returned.
+.It Dv OPIOCNEXTPROP
+Finds the property whose name follows the given name
+in OPENPROM internal order.
+The resulting name is returned in the value field.
+If the named property is the last, the
+.Dq next
+name is the empty string.
+As with
+.Dv OPIOCGETNEXT ,
+the next name after the empty string is the first name.
+.El
+.Sh FILES
+.Pa /dev/openprom
+.Sh ERRORS
+The following may result in rejection of an operation:
+.Bl -tag -width Er
+.It Bq Er EINVAL
+The given node number
+is not zero
+and does not correspond to any valid node,
+or is zero where zero is not allowed.
+.It Bq Er EBADF
+The requested operation requires permissions not specified at the call to
+.Fn open .
+.It Bq Er ENAMETOOLONG
+The given name or value field
+exceeds the maximum allowed length (8191 bytes).
+.El
+.Sh SEE ALSO
+.Xr ioctl 2
+.Sh BUGS
+Due to limitations within the OPENPROM itself,
+these functions run at elevated priority
+and may adversely affect system performance.
diff --git a/share/man/man4/man4.sun3/Makefile b/share/man/man4/man4.sun3/Makefile
new file mode 100644
index 00000000000..6f07f3308f7
--- /dev/null
+++ b/share/man/man4/man4.sun3/Makefile
@@ -0,0 +1,8 @@
+# 	from: @(#)Makefile	8.2 (Berkeley) 2/16/94
+#	$NetBSD: Makefile,v 1.1.1.1 1995/08/08 20:18:53 gwr Exp $
+
+MAN=	bwtwo.4 cgtwo.4 cgfour.4 ie.4 le.4 mem.4
+MLINKS=	mem.4 kmem.4
+MANSUBDIR=/sun3
+
+.include <bsd.prog.mk>
diff --git a/share/man/man4/man4.sun3/bwtwo.4 b/share/man/man4/man4.sun3/bwtwo.4
new file mode 100644
index 00000000000..ab2c14e3302
--- /dev/null
+++ b/share/man/man4/man4.sun3/bwtwo.4
@@ -0,0 +1,55 @@
+.\" Copyright (c) 1992, 1993
+.\"	The Regents of the University of California.  All rights reserved.
+.\"
+.\" This software was developed by the Computer Systems Engineering group
+.\" at Lawrence Berkeley Laboratory under DARPA contract BG 91-66 and
+.\" contributed to Berkeley.
+.\"
+.\" 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: Header: bwtwo.4,v 1.3 94/02/03 20:42:13 leres Exp
+.\"     from: @(#)bwtwo.4	8.2 (Berkeley) 2/16/94
+.\"	$NetBSD: bwtwo.4,v 1.1.1.1 1995/08/08 20:18:53 gwr Exp $
+.\"
+.Dd February 16, 1994
+.Dt BWTWO 4 sun3
+.Os
+.Sh NAME
+.Nm bwtwo
+.Nd monochromatic frame buffer
+.Sh SYNOPSIS
+.Cd "bwtwo0 at obmem0 addr ?"
+.Sh DESCRIPTION
+The 
+.Nm
+is a memory based black and white frame buffer.
+It supports the minimal ioctl's needed to run X11.
+.Sh SEE ALSO
+.Xr cgtwo 4 ,
+.Xr cgfour 4
diff --git a/share/man/man4/man4.sun3/cgfour.4 b/share/man/man4/man4.sun3/cgfour.4
new file mode 100644
index 00000000000..4644f024194
--- /dev/null
+++ b/share/man/man4/man4.sun3/cgfour.4
@@ -0,0 +1,55 @@
+.\" Copyright (c) 1992, 1993
+.\"	The Regents of the University of California.  All rights reserved.
+.\"
+.\" This software was developed by the Computer Systems Engineering group
+.\" at Lawrence Berkeley Laboratory under DARPA contract BG 91-66 and
+.\" contributed to Berkeley.
+.\"
+.\" 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: Header: cgthree.4,v 1.3 94/02/03 20:49:52 leres Exp
+.\"     from: @(#)cgthree.4	8.2 (Berkeley) 2/16/94
+.\"	$NetBSD: cgfour.4,v 1.1.1.1 1995/08/08 20:18:53 gwr Exp $
+.\"
+.Dd February 16, 1994
+.Dt CGFOUR 4 sun3
+.Os
+.Sh NAME
+.Nm cgfour
+.Nd 8-bit color frame buffer
+.Sh SYNOPSIS
+.Cd "cgfour0 at obmem0 addr ?"
+.Sh DESCRIPTION
+The 
+.Nm
+is a memory based color frame buffer.
+It supports the minimal ioctl's needed to run X11.
+.Sh SEE ALSO
+.Xr bwtwo 4 ,
+.Xr cgtwo 4
diff --git a/share/man/man4/man4.sun3/cgtwo.4 b/share/man/man4/man4.sun3/cgtwo.4
new file mode 100644
index 00000000000..f6cdb09db45
--- /dev/null
+++ b/share/man/man4/man4.sun3/cgtwo.4
@@ -0,0 +1,55 @@
+.\" Copyright (c) 1992, 1993
+.\"	The Regents of the University of California.  All rights reserved.
+.\"
+.\" This software was developed by the Computer Systems Engineering group
+.\" at Lawrence Berkeley Laboratory under DARPA contract BG 91-66 and
+.\" contributed to Berkeley.
+.\"
+.\" 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: Header: cgthree.4,v 1.3 94/02/03 20:49:52 leres Exp
+.\"     from: @(#)cgthree.4	8.2 (Berkeley) 2/16/94
+.\"	$NetBSD: cgtwo.4,v 1.1.1.1 1995/08/08 20:18:53 gwr Exp $
+.\"
+.Dd February 16, 1994
+.Dt CGTWO 4 sun3
+.Os
+.Sh NAME
+.Nm cgtwo
+.Nd 8-bit color frame buffer
+.Sh SYNOPSIS
+.Cd "cgtwo0 at vmes0 addr 0xff400000 level 4 vect 0xA8"
+.Sh DESCRIPTION
+The 
+.Nm
+is a memory based color frame buffer.
+It supports the minimal ioctl's needed to run X11.
+.Sh SEE ALSO
+.Xr bwtwo 4 ,
+.Xr cgfour 4
diff --git a/share/man/man4/man4.sun3/ie.4 b/share/man/man4/man4.sun3/ie.4
new file mode 100644
index 00000000000..49ed0a37799
--- /dev/null
+++ b/share/man/man4/man4.sun3/ie.4
@@ -0,0 +1,70 @@
+.\" Copyright (c) 1992, 1993
+.\"	The Regents of the University of California.  All rights reserved.
+.\"
+.\" This software was developed by the Computer Systems Engineering group
+.\" at Lawrence Berkeley Laboratory under DARPA contract BG 91-66 and
+.\" contributed to Berkeley.
+.\"
+.\" 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: Header: le.4,v 1.2 92/10/13 05:31:33 leres Exp
+.\"	from: @(#)le.4	8.1 (Berkeley) 6/9/93
+.\"	$NetBSD: ie.4,v 1.1.1.1 1995/08/08 20:18:53 gwr Exp $
+.\"
+.Dd June 9, 1993
+.Dt IE 4 sun3
+.Os
+.Sh NAME
+.Nm ie
+.Nd Intel 82586 Ethernet interface
+.Sh SYNOPSIS
+.Cd "ie0 at obio0 addr ? level ?"
+.Cd "ie1 at vmes0 addr 0xffe88000 level 3 vect 0x75"
+.Sh DESCRIPTION
+The 
+.Nm
+interface provides access to the 10 Mb/s Ethernet network via the
+.Tn Intel
+82586 Ethernet chip set.
+.Pp
+Each of the host's network addresses
+is specified at boot time with an
+.Dv SIOCSIFADDR
+.Xr ioctl .
+The
+.Nm
+interface employs the address resolution protocol described in
+.Xr arp 4
+to dynamically map between Internet and Ethernet addresses on the local
+network.
+.Sh SEE ALSO
+.Xr le 4 ,
+.Xr intro 4 ,
+.Xr inet 4 ,
+.Xr arp 4
diff --git a/share/man/man4/man4.sun3/le.4 b/share/man/man4/man4.sun3/le.4
new file mode 100644
index 00000000000..c7d6c5ac227
--- /dev/null
+++ b/share/man/man4/man4.sun3/le.4
@@ -0,0 +1,71 @@
+.\" Copyright (c) 1992, 1993
+.\"	The Regents of the University of California.  All rights reserved.
+.\"
+.\" This software was developed by the Computer Systems Engineering group
+.\" at Lawrence Berkeley Laboratory under DARPA contract BG 91-66 and
+.\" contributed to Berkeley.
+.\"
+.\" 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: Header: le.4,v 1.2 92/10/13 05:31:33 leres Exp
+.\"	from: @(#)le.4	8.1 (Berkeley) 6/9/93
+.\"	$NetBSD: le.4,v 1.1.1.1 1995/08/08 20:18:53 gwr Exp $
+.\"
+.Dd June 9, 1993
+.Dt LE 4 sun3
+.Os
+.Sh NAME
+.Nm le
+.Nd AMD 7990 LANCE ethernet interface
+.Sh SYNOPSIS
+.Cd "le* at obio0 addr ? level ?"
+.Sh DESCRIPTION
+The 
+.Nm
+interface provides access to the 10 Mb/s Ethernet network via the
+.Tn AMD
+7990
+.Tn LANCE
+Ethernet chip set.
+.Pp
+Each of the host's network addresses
+is specified at boot time with an
+.Dv SIOCSIFADDR
+.Xr ioctl .
+The
+.Nm
+interface employs the address resolution protocol described in
+.Xr arp 4
+to dynamically map between Internet and Ethernet addresses on the local
+network.
+.Sh SEE ALSO
+.Xr ie 4 ,
+.Xr intro 4 ,
+.Xr inet 4 ,
+.Xr arp 4
diff --git a/share/man/man4/man4.sun3/mem.4 b/share/man/man4/man4.sun3/mem.4
new file mode 100644
index 00000000000..9cd33a8a57c
--- /dev/null
+++ b/share/man/man4/man4.sun3/mem.4
@@ -0,0 +1,79 @@
+.\" Copyright (c) 1992, 1993
+.\"	The Regents of the University of California.  All rights reserved.
+.\"
+.\" This software was developed by the Computer Systems Engineering group
+.\" at Lawrence Berkeley Laboratory under DARPA contract BG 91-66 and
+.\" contributed to Berkeley.
+.\"
+.\" 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	8.1 (Berkeley) 6/5/93
+.\"	$NetBSD: mem.4,v 1.1.1.1 1995/08/08 20:18:53 gwr Exp $
+.\"
+.Dd June 5, 1993
+.Dt MEM 4 sun3
+.Os NetBSD 1.0
+.Sh NAME
+.Nm mem ,
+.Nm kmem
+.Nd main memory
+.Sh DESCRIPTION
+The 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.
+An error will be returned if an attempt is made to reference
+an offset outside of
+.Nm /dev/mem .
+.Pp
+Kernel virtual memory is accessed via the file
+.Nm /dev/kmem
+in the same manner as
+.Nm /dev/mem .
+Only kernel virtual addresses that are currently mapped to memory are allowed.
+.Pp
+On the
+.Tn Sun3 ,
+kernel virtual memory begins at
+.Ad 0x0E000000 .
+.Sh FILES
+.Bl -tag -width /dev/kmem -compact
+.It Pa /dev/mem
+.It Pa /dev/kmem
+.El
+.Sh HISTORY
+The files
+.Nm mem
+and
+.Nm kmem
+appeared in
+.At v6 .
diff --git a/share/man/man4/man4.tahoe/Makefile b/share/man/man4/man4.tahoe/Makefile
new file mode 100644
index 00000000000..bff0957a39f
--- /dev/null
+++ b/share/man/man4/man4.tahoe/Makefile
@@ -0,0 +1,9 @@
+#	from: @(#)Makefile	5.4 (Berkeley) 5/11/90
+#	$Id: Makefile,v 1.1 1995/10/18 08:44:32 deraadt Exp $
+
+MAN=	ace.4 autoconf.4 cons.4 cy.4 dr.4 enp.4 ik.4 intro.4 lp.4 mem.4 \
+	mtio.4 vd.4 vx.4
+MLINKS=	mem.4 kmem.4
+MANSUBDIR=/tahoe
+
+.include <bsd.prog.mk>
diff --git a/share/man/man4/man4.tahoe/ace.4 b/share/man/man4/man4.tahoe/ace.4
new file mode 100644
index 00000000000..21e3a4b8b66
--- /dev/null
+++ b/share/man/man4/man4.tahoe/ace.4
@@ -0,0 +1,117 @@
+.\" 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: @(#)ace.4	6.5 (Berkeley) 3/27/91
+.\"	$Id: ace.4,v 1.1 1995/10/18 08:44:32 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt ACE 4 tahoe
+.Os BSD 4.2
+.Sh NAME
+.Nm ace
+.Nd
+.Tn ACC
+10 Mb/s Ethernet interface
+.Sh SYNOPSIS
+.Cd "device ace0 at vba? csr 0xffff0000 flags 0xfff80000 vector acecint acerint"
+.Sh DESCRIPTION
+The
+.Nm ace
+interface provides access to a 10 Mb/s Ethernet network through
+an
+.Tn ACC
+controller.
+.Pp
+The hardware has 32 kilobytes of dual-ported memory on the
+.Tn VERSAbus . 
+This memory
+is used for internal buffering by the board, and the interface code reads
+the buffer contents directly through the
+.Tn VERSAbus .
+The address of this memory is given in the
+.Ar flags
+field
+in the configuration file.
+.Pp
+Each of the host's network addresses
+is specified at boot time with an
+.Dv SIOCSIFADDR
+.Xr ioctl 2 .
+The
+.Nm ace
+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 device implements an exponential backoff algorithm
+when notified of a collision on the cable.  This algorithm utilizes
+a table of random numbers setup by the system at boot time.
+The delay is done in the controller.
+.Sh DIAGNOSTICS
+.Bl -diag
+.It "ace%d: stray xmit interrupt, xnct %d."
+An unexpected transmission complete interrupt was received;
+the interrupt is ignored.
+.It "ace%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 intro 4 ,
+.Xr inet 4 ,
+.Xr arp 4
+.Sh HISTORY
+The
+.Nm
+driver appeared in
+.Bx 4.3 tahoe .
+.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
+The device doesn't autoconfigure its interrupt vector; it is set
+at 0x90 + eight times the unit number.
diff --git a/share/man/man4/man4.tahoe/autoconf.4 b/share/man/man4/man4.tahoe/autoconf.4
new file mode 100644
index 00000000000..0df73990845
--- /dev/null
+++ b/share/man/man4/man4.tahoe/autoconf.4
@@ -0,0 +1,154 @@
+.\" 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: @(#)autoconf.4	6.3 (Berkeley) 3/27/91
+.\"	$Id: autoconf.4,v 1.1 1995/10/18 08:44:32 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt AUTOCONF 4 tahoe
+.Os BSD 4.3t
+.Sh NAME
+.Nm autoconf
+.Nd diagnostics from autoconfiguration code
+.Sh DESCRIPTION
+When
+.Tn UNIX
+bootstraps it probes the innards of the machine it is running
+on and locates controllers, drives, and other devices, printing out
+what it finds 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
+.Tn VERSAbus
+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
+A generic system may be built which picks its root device at boot time
+as the
+.Dq best
+available device.
+If such a system is booted with the
+.Dv RB_ASKNAME
+option of (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 vba%d at %x.
+A
+.Tn VERSAbus
+adapter was found and mapped into the
+address space of the operating system starting at virtual address
+.Sq Li  %x .
+.Tn UNIX
+will call it
+.Sq Li vba%d .
+.It %s%d at vba%d drive %d.
+A tape formatter or a disk was found
+on the
+.Tn VERSAbus ;
+for disks
+.Sq Li %s%d
+will look like
+.Sq Li dk0 ,
+for tape formatters
+like
+.Sq Li yc1 .
+The drive number comes from the unit plug on the drive
+or in the tape formatter
+.Pf ( Em not
+on the tape drive; see below).
+.It %s%d at %s%d slave %d.
+Which would look like
+.Sq Li yc0 at cy0 slave 0% ,
+where
+.Em yc0
+is the name for the tape device and
+.Em cy0
+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).
+.Tn UNIX
+will call the device, e.g.,
+.Li cy0.
+.It %s%d at vba%d csr %x vec %x ipl %x.
+The device
+.Sq Li %s%d ,
+e.g.
+.Sq Li vd0
+was found on
+.Sq Li vba%d
+at control-status register address
+.Sq Li %x
+and with
+device vector
+.Sq Li %x .
+The device interrupted at priority level
+.Sq Li %x .
+.It %s%d at vba%d csr %x no interrupts.
+The device was found
+on
+.Sq Li vba%d
+at control-status register address
+.Sq Li %x ;
+no
+interrupts were configured for the device.
+.It %s%d at vba%d csr %x 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.  The csr address is interpreted as described above.
+.It %s%d at %s%d slave %d.
+Which would look like
+.Sq Li dk0 at vd0 slave 0 ,
+where
+.Em dk0
+is the name of a disk drive and
+.Em vd0
+is the name
+of the controller. 
+.El
+.Sh SEE ALSO
+.Xr config 8
+.Sh HISTORY
+The
+.Nm
+special file appeared in
+.Bx 4.3 tahoe .
+.Sh BUGS
+Very few devices actually figure out their interrupt vector
+by forcing the device to interrupt.  Only the upper megabyte of the
+.Tn VERSAbus
+address space is mapped into the system's virtual address space.
diff --git a/share/man/man4/man4.tahoe/cons.4 b/share/man/man4/man4.tahoe/cons.4
new file mode 100644
index 00000000000..3b2cde2e836
--- /dev/null
+++ b/share/man/man4/man4.tahoe/cons.4
@@ -0,0 +1,101 @@
+.\" 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: @(#)cons.4	6.3 (Berkeley) 3/27/91
+.\"	$Id: cons.4,v 1.1 1995/10/18 08:44:32 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt CONS 4 tahoe
+.Os BSD 4.3t
+.Sh NAME
+.Nm cons ,
+.Nm CP ,
+.Nm remote
+.Nd Tahoe console interface
+.Sh DESCRIPTION
+The console is available to the processor through the console registers.
+It acts like a normal terminal, except that a
+.Dq Ic ~
+is used to transfer
+commands to the console processor when the front panel key switch is
+in the
+.Dq foo
+or
+.Dq bar
+position.
+When the console processor
+is in control, a
+.Ql #>
+prompt is displayed.  To continue execution
+after halting the machine with
+.Ql ~h ,
+use
+.Ql r .
+.Bl -tag -width Ds
+.It Ic \&~h
+Halt the machine.
+.It Ic \&~b
+Force a reboot.
+.It Ic \&~r
+Continue execution after a
+.Ic \&~h .
+.El
+.Pp
+Refer to the Tahoe
+console processor handbook for the complete list of facilities available
+through the console processor.
+.Pp
+The
+.Nm CP
+device provides direct access to the console processor.  The
+.Nm remote
+device is a secondary console terminal used for remote diagnosis;
+it is normally connected to a modem.
+.Sh FILES
+.Bl -tag -width /dev/consolexx -compact
+.It Pa /dev/console
+.It Pa /dev/CP
+.It Pa /dev/remote
+.El
+.Sh DIAGNOSTICS
+None.
+.Sh SEE ALSO
+.Xr kdb 4 ,
+.Xr tty 4 ,
+.Xr reboot 8
+.Rs
+.%T Console Processor Handbook
+.Re
+.Sh HISTORY
+The
+.Nm
+interface appeared in
+.Bx 4.3 tahoe .
diff --git a/share/man/man4/man4.tahoe/cy.4 b/share/man/man4/man4.tahoe/cy.4
new file mode 100644
index 00000000000..ce69dbb58b6
--- /dev/null
+++ b/share/man/man4/man4.tahoe/cy.4
@@ -0,0 +1,177 @@
+.\" 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: @(#)cy.4	6.4 (Berkeley) 3/27/91
+.\"	$Id: cy.4,v 1.1 1995/10/18 08:44:32 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt CY 4 tahoe
+.Os BSD 4.3t
+.Sh NAME
+.Nm cy
+.Nd Cipher/tapemaster magtape interface
+.Sh SYNOPSIS
+.Cd "controller cy0 at vba? csr 0xffff4000 vector cyintr"
+.Cd "device yc0 at cy0 drive 0"
+.Sh DESCRIPTION
+The Cipher
+.Tn F880 ,
+.Tn M990 Ns / Tapemaster
+combination provides a standard tape drive
+interface as described in
+.Xr mt 4 .
+The Cipher
+.Tn F880
+tape drive operates at 1600 or 3200
+.Tn BPI \-
+controlled by a switch on the drive. 
+The Cipher
+.Tn M990
+operates at 1600, 3200 or 6250
+.Tn BPI \-
+controlled by switches on the front of the drive.
+.Pp
+The Tapemaster controller board is actually a Multibus controller
+accessed through a Halversa Multibus to
+.Tn VERSAbus
+converter card.
+.Sh DIAGNOSTICS
+.Bl -diag
+.It cy%d: %dkb buffer.
+The formatter was found to have a
+.Ql %d
+kilobyte buffer during autoconfiguration.
+.It cy%d: timeout or err during init, status=%b.
+The controller
+timed out or an error occurred on a nop command during autoconfiguration;
+the controller may be hung.
+.It cy%d: configuration failure, status=%b.
+The controller
+timed out or an error occurred on a configure command during
+autoconfiguration; the controller may be hung.
+.It yc%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.
+.It yc%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.
+.It cy%d: i/o size too large.
+A read or a write request exceeded the
+maximum transfer size for the controller \- 32 kilobytes; this message
+is written on the terminal of the user who made the read or write request.
+.It yc%d: hard error bn%d status=%b.
+A tape error occurred
+at block
+.Em bn ;
+the cy error register is
+printed in hexadecimal 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.
+For known errors, the trailing
+.Ql %s
+is one of the following:
+.Pp
+.Bl -diag -offset indent -compact
+.It timeout, timeout1, timeout2, timeout3, timeout4.
+Time out errors; this may be due to trying to read a blank tape
+or the controller failing to interrupt or the drive dropping off-line.
+.It non-existent memory.
+A controller transfer to memory timed out.
+.It blank tape.
+The controller detected a blank tape when
+data was expected.
+.It micro-diagnostic, missing diagnostic jumper.
+An error occurred in the micro-diagnostics or
+the diagnostic mode jumper was not installed while attempting to execute
+a diagnostics command.
+.It eot/bot detected.
+The controller unexpectedly encountered
+end-of-tape or beginning-of-tape during an operation.
+.It retry unsuccessful.
+An error occurred which could not be recovered by repeated retries.
+.It fifo over/under-flow.
+The controller was unable to transfer data to the drive fast enough.
+This usually occurs because a transfer was performed without using the
+controller's internal buffer.
+.It drive to controller parity error.
+A parity error was detected by the controller in data transferred
+between the drive and the controller's internal buffer.
+.It prom checksum.
+The controller thinks its
+.Tn PROM
+is corrupted.
+.It time out tape strobe (record length error).
+The controller timed out while looking for an inter-record gap.
+This usually occurs because the records on the tape are larger than
+expected (or can be handled).
+.It tape not ready.
+The drive does not respond; usually the power has been turned off
+or a cable has come off.
+.It write protected.
+A write ring was present in the tape when a write was attempted.
+.It invalid link pointer.
+An invalid pointer was encountered in a tape parameter block.
+.It unexpected file mark.
+A tape file mark was encountered while trying to read or space.
+.It invalid byte count.
+An invalid byte count parameter was encountered in a tape parameter
+block.
+.It unidentified hardware error.
+.It streaming terminated.
+These should not happen.
+.El
+.Pp
+.It yc%d: lost interrupt.
+The controller failed to respond with an interrupt signifying completion
+of the current command.  The system will attempt to abort the
+outstanding command and reset the controller.
+.Pp
+.It cy%d: reset failed.
+The system was unable to reset the controller.  This is normally preceded
+by another message from the driver.
+.El
+.Sh SEE ALSO
+.Xr mt 1 ,
+.Xr tar 1 ,
+.Xr mtio 4
+.Sh HISTORY
+The
+.Nm
+driver appeared in
+.Bx 4.3 tahoe .
+.Sh BUGS
+The controller supports only 20-bit addresses.  The only way the
+system can insure the controller will be able to address data
+to be transferred
+is to copy it into an intermediate buffer allocated in the first megabyte
+of system memory.
diff --git a/share/man/man4/man4.tahoe/dr.4 b/share/man/man4/man4.tahoe/dr.4
new file mode 100644
index 00000000000..d811bbd3145
--- /dev/null
+++ b/share/man/man4/man4.tahoe/dr.4
@@ -0,0 +1,164 @@
+.\" 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: @(#)dr.4	6.3 (Berkeley) 3/27/91
+.\"	$Id: dr.4,v 1.1 1995/10/18 08:44:32 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt DR 4 tahoe
+.Os BSD 4.2
+.Sh NAME
+.Nm dr
+.Nd Ikon
+.Tn DR-11W
+interface
+.Sh SYNOPSIS
+.Cd "device dr0 at vba? csr 0xffff8000 vector drintr"
+.Sh DESCRIPTION
+The
+.Nm dr
+driver provides access
+to an Ikon
+.Tn DR-11W
+.Tn DMA
+controller.
+Each minor device is a different controller.
+.Pp
+In addition to reading and writing, the following
+.Xr ioctl 2
+requests are available:
+.Bl -tag -width DRSETNORSTALL
+.It Dv DRWAIT
+Wait for an attention interrupt from the associated device.
+.It Dv DRPIOW
+Write to the programmed
+.Tn I/O
+register.
+.It Dv DRPACL
+Write to the pulse register.
+.It Dv DRDACL
+Set the ``ac-low'' bit in the next command sent to the
+.Tn DR-11W .
+.It Dv DRPCYL
+Set the ``cycle'' bit in the next command sent to the
+.Tn DR-11W .
+.It Dv DRDFCN
+Hold the function bits until the next command is issused.
+.It Dv DRRATN
+Reset the attention flag.
+.It Dv DRRDMA
+Reset the
+.Tn DMA
+complete flag.
+.It Dv DRSFCN
+Set the function bits in the control status register and,
+as a side effect, clear the interrupt enable flag.
+.It Dv DRRPER
+Reset the parity error flag.
+.It Dv DRSETRSTALL
+Set ``no stall'' mode for all subsequent reads.
+In no stall mode the driver will abort
+read requests that fail to complete before a user
+specified timeout expires.
+.It Dv DRSETNORSTALL
+Disable no stall mode for reads.
+.It Dv DRGETRSTALL
+Return true if in no stall mode for reads.
+.It Dv DRSETRTIMEOUT
+Set the value of the timeout used in no stall mode  for
+reads.  The time is specified in tenths of seconds.
+.It Dv DRGETRTIMEOUT
+Return the time until (in tenths of seconds) before a read
+is timed out when in no stall mode.
+.It Dv DRSETWSTALL
+Set ``no stall'' mode for all subsequent writes.
+In no stall mode the driver will abort
+write requests that fail to complete before a user
+specified timeout expires.
+.It Dv DRSETNOWSTALL
+Disable no stall mode for writes.
+.It Dv DRGETWSTALL
+Return true if in no stall mode for writes.
+.It Dv DRSETWTIMEOUT
+Set the value of the timeout used in no stall mode  for
+writes.  The time is specified in tenths of seconds.
+.It Dv DRGETRTIMEOUT
+Return the time until (in tenths of seconds) before a write
+is timed out when in no stall mode.
+.It Dv DRWRITEREADY
+Return 1 if the device can accept data, 0 otherwise
+(this is really the
+.Tn DR-11W A
+status bit).
+.It Dv DRREADREADY
+Return 1 if the device has data for the host to read,
+0 otherwise (this is really the
+.Tn DR-11W B
+status bit).
+.It Dv DRBUSY
+Return 1  if the device is busy, 0 otherwise.
+.It Dv DRRESET
+Reset the DR-11W.
+.It Dv DR11STAT
+Return the driver status and the contents of the
+.Tn DR-11W
+.Tn I/O registers.  The
+eight words returned are, in order, the driver
+status flags, the contents of the control status
+register, the contents of the status register
+at the time of the last interrupt from the device,
+the contents of the programmed
+.Tn I/O data register,
+a combination of the address modifier used by the
+device in performing
+.Tn VERSAbus
+transfers and the
+interrupt vector used by the device, the contents
+of the range register, the contents of the rahi
+register, and the contents of the ralo register.
+.It Dv DR11LOOP
+Perform loopback testing (the loopback cable must
+be in place for this to work).
+.El
+.Sh FILES
+.Bl -tag -width /dev/dr[0-7]xx -compact
+.It Pa /dev/dr[0-7]
+standard devices
+.El
+.Sh DIAGNOSTICS
+Lots of them, none of them meaningful.
+.Sh HISTORY
+The
+.Nm
+driver appeared in
+.Bx 4.3 tahoe .
+.Sh BUGS
+This driver needs to be rewritten.
diff --git a/share/man/man4/man4.tahoe/enp.4 b/share/man/man4/man4.tahoe/enp.4
new file mode 100644
index 00000000000..f483cdd2c7e
--- /dev/null
+++ b/share/man/man4/man4.tahoe/enp.4
@@ -0,0 +1,122 @@
+.\" 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: @(#)enp.4	5.4 (Berkeley) 3/27/91
+.\"	$Id: enp.4,v 1.1 1995/10/18 08:44:32 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt ENP 4 tahoe
+.Os BSD 4.3t
+.Sh NAME
+.Nm enp
+.Nd
+.Tn CMC
+10 Mb/s Ethernet interface
+.Sh SYNOPSIS
+.Cd "device enp0 at vba? csr 0xfff40000 vector enpintr"
+.Sh DESCRIPTION
+The
+.Nm enp
+interface provides access to a 10 Mb/s Ethernet network through
+a
+.Tn CMC ENP-20
+controller.
+.Pp
+The hardware has 128 kilobytes of dual-ported memory on the
+.Tn VERSAbus . 
+This memory
+is used for internal buffering by the board, and the interface code reads
+the buffer contents directly through the
+.Tn VERSAbus .
+The address of this memory is derived from the address specified
+in the configuration file.
+.Pp
+Each of the host's network addresses
+is specified at boot time with an
+.Dv SIOCSIFADDR
+.Xr ioctl 2 .
+The
+.Nm enp
+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
+Associated with each interface is a character device which
+is used to dowload, start, and reset the firmware in the controller.
+Reading or writing the
+.Dq ram device
+reads or writes the writable
+control store in the controller.  Two
+.Xr ioctl 2
+calls,
+.Dv ENPIOGO
+and
+.Dv ENPIORESET ,
+are used to start and reset the
+firmware.
+.Sh DIAGNOSTICS
+.Bl -diag
+.It enp%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 intro 4 ,
+.Xr inet 4 ,
+.Xr arp 4 ,
+.Xr enpload 8
+.Sh HISTORY
+The
+.Nm
+driver appeared in
+.Bx 4.3 tahoe .
+.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
+The link level firmware does not support setting the board's
+Ethernet address.
diff --git a/share/man/man4/man4.tahoe/ik.4 b/share/man/man4/man4.tahoe/ik.4
new file mode 100644
index 00000000000..cd7560c5a4c
--- /dev/null
+++ b/share/man/man4/man4.tahoe/ik.4
@@ -0,0 +1,191 @@
+.\" 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.3 (Berkeley) 3/27/91
+.\"	$Id: ik.4,v 1.1 1995/10/18 08:44:32 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt IK 4
+.Os BSD 4.2
+.Sh NAME
+.Nm ik
+.Nd Evans and Sutherland Picture System 300 graphics device interface
+.Sh SYNOPSIS
+.Cd "device ik0 at vba? csr 0xfffb100 vector ikintr"
+.Sh DESCRIPTION
+The
+.Nm ik
+driver provides access
+to an Evans and
+Sutherland Picture System 300 through an Ikon
+.Tn DR-11W
+interface card.
+Each two minor device numbers are a different
+.Tn PS300 ;
+within a pair of device numbers the odd valued
+device is used for ``diagnostic'' purposes.   That is,
+for even numbered minor devices, opening the device results
+in a
+.Tn PS300
+``attach'' request being performed while for
+odd numbered minor devices the attach request is not performed.
+.Pp
+All operations between the host and the
+.Tn PS300
+utilize
+.Tn DMA .
+The driver currently supports only physical
+.Tn I/O operations
+when reading and writing; this makes the device useless with
+standard Evans and Sutherland software.
+.Pp
+The interface provided by the interface is as
+.Ux Ns -like
+as possible.
+When a device is opened a
+.Tn PS300
+attach request is automatically
+performed.  When a device is closed a detach is performed.  Reads
+and writes result in physical
+.Tn I/O
+requests, but hide all the details
+of the physical
+.Tn I/O
+protocol.  This is programming style is completely
+different from the
+.Tn VMS Ns -oriented
+qio-style interface supplied by Evans
+and Sutherland.
+.Pp
+Reads and writes to the device result in a physical
+.Tn I/O
+request
+to the
+.Tn PS300 .
+If a
+.Xr readv 2
+or
+.Xr writev 2
+call is used, each
+.Tn I/O
+request results in a single physical
+.Tn I/O
+request (i.e. the scatter-gather facilities are not supported).
+In normal operation, the address used in a physical
+.Tn I/O
+request
+is the current file offset as specified explicitly with
+.Xr lseek 2
+or implictly as a result of reading or writing the device.
+To specify an address to be used with each physical
+.Tn I/O
+request,
+the
+.Nm ik
+driver interprets the
+.Ar iov
+entries in a non-standard way.  If
+.Ar iov_len
+is zero, then
+.Ar iov_base
+is interpreted as an address to be used in the physical
+.Tn I/O
+request.  If the address has the
+.Dv PSIO_SYNC
+flag or-d into it,
+the physical
+.Tn I/O
+request is made as a ``write with sync''.
+All addresses and data presented to the driver should be in
+the byte order of the host; any byte swapping required to converse
+with the
+.Tn PS300
+is performed in the driver/controller.
+.Pp
+In addition to reading and writing, the following
+.Xr ioctl
+requests are available:
+.Bl -tag -width PSIOGETERROR
+.It Dv PSIOLOOKUP
+Perform a ``name lookup'' request.  The
+.Ar pslookup
+structure passed indicates the symbol name to be looked up
+and contains the address returned by the
+.Tn PS300 .
+A zero
+address return indicates the symbol was undefined.
+.It Dv PSIOGETERROR
+In the event of an error, this request may be made to
+return a more detailed and, sometimes
+.Tn PS300 Ns -specific ,
+error code.
+.Sh FILES
+.Bl -tag -width /dec/ik[0-7]xx -compact
+.It Pa /dev/ik[0-7]
+auto-attach devices
+.It Pa /dev/ik[0-7]d
+diagnostic interfaces to devices
+.El
+.Sh DIAGNOSTICS
+.Bl -diag
+.It ik%d: bad cmd %x.
+An unknown or unsupported command was received by the host.
+.It ik%d: spurious interrupt, code %x.
+An unexpected interrupt was received from the
+.Tn PS300 ;
+the
+attention code from the
+.Tn PS300
+is printed.
+.It ik%d: timeout.
+A command failed to elicit a response within a reasonable
+time; the
+.Tn PS300
+probably crashed.
+.El
+.Sh HISTORY
+The
+Tahoe Version
+.Nm
+driver appeared in
+.Bx 4.2 .
+.Sh BUGS
+An invalid access (e.g. illegal address) to the
+.Tn PS300
+can
+cause the
+.Tn PS300
+to crash.  It is not always possible to unwedge
+the
+.Tn PS300
+interface hardware hung by an
+.Tn I/O
+request.
diff --git a/share/man/man4/man4.tahoe/intro.4 b/share/man/man4/man4.tahoe/intro.4
new file mode 100644
index 00000000000..6d895dfce9a
--- /dev/null
+++ b/share/man/man4/man4.tahoe/intro.4
@@ -0,0 +1,120 @@
+.\" 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: @(#)intro.4	6.5 (Berkeley) 3/27/91
+.\"	$Id: intro.4,v 1.1 1995/10/18 08:44:32 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt INTRO 4 tahoe
+.Os
+.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 in the system error log
+.Pa /var/log/messages
+due to errors in device operation.
+.Sh CCI DEVICE SUPPORT
+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 the
+.Tn VERSAbus
+and, if found, enable the software
+support for it.  If a
+.Tn VERSAbus
+device does not respond at autoconfiguration
+time it is not accessible at any time afterwards.  To
+enable a
+.Tn VERSAbus
+device which did not autoconfigure, the system will have to
+be rebooted.
+.Pp
+The autoconfiguration system is described in
+.Xr autoconf 4 .
+.Sh SEE ALSO
+.Xr autoconf 4 ,
+.Xr netintro 4 ,
+.Xr config 8
+.Sh LIST OF DEVICES
+The devices listed below are supported in this incarnation of
+the system.  Devices are indicated by their functional interface.
+If second vendor products provide functionally identical interfaces
+they should be usable with the supplied software.
+.Bf Sy
+(Beware however that we promise the software works
+ONLY with the hardware indicated on the appropriate manual page.)
+.Ef
+.Pp
+.Bl -column cons
+ace	ACC 10 Mb/s Ethernet controller
+cons	Tahoe console interface
+cy	Cypher tape drive interface
+dr	Ikon DR-11W controller
+enp	3Com 10 Mb/s Ethernet controller
+ik	Evans and Sutherland PS300 interface through an Ikon DR-11W
+	controller
+vd	CCI vd mass storage disk controller
+vx	CCI vioc terminal multiplexor
+.El
+.Sh HISTORY
+The section 4
+.Nm
+appeared in
+.Bx 4.2 .
diff --git a/share/man/man4/man4.tahoe/lp.4 b/share/man/man4/man4.tahoe/lp.4
new file mode 100644
index 00000000000..168a535d0b7
--- /dev/null
+++ b/share/man/man4/man4.tahoe/lp.4
@@ -0,0 +1,60 @@
+.\" 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: @(#)lp.4	6.2 (Berkeley) 3/27/91
+.\"	$Id: lp.4,v 1.1 1995/10/18 08:44:32 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt LP 4 tahoe
+.Os 4.3t
+.Sh NAME
+.Nm lp
+.Nd line printer
+.Sh SYNOPSIS
+device lp on the
+.Tn VIOC-P
+.Sh DESCRIPTION
+The
+.Nm lp
+driver provides an interface to 4 serial
+printer lines.
+.Sh FILES
+.Bl -tag -width /dev/lpxx
+.It Pa /dev/lp
+.El
+.Sh SEE ALSO
+.Xr lpr 1 ,
+.Xr vioc 4
+.Sh HISTORY
+The
+.Nm
+driver appeared in
+.Bx 4.3 tahoe .
diff --git a/share/man/man4/man4.tahoe/mem.4 b/share/man/man4/man4.tahoe/mem.4
new file mode 100644
index 00000000000..b4dcae2e131
--- /dev/null
+++ b/share/man/man4/man4.tahoe/mem.4
@@ -0,0 +1,128 @@
+.\" 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: @(#)mem.4	6.3 (Berkeley) 3/27/91
+.\"	$Id: mem.4,v 1.1 1995/10/18 08:44:32 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt MEM 4 tahoe
+.Os
+.Sh NAME
+.Nm mem ,
+.Nm kmem ,
+.Nm vmem
+.Nd main memory
+.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/vmem
+allows access to the mapped portion of the
+.Tn VERSAbus
+.Tn I/O
+space.  On the Tahoe the upper megabyte
+of the physical address space is accessible through
+this file (0xfff00000 through 0xffffffff). 
+Accesses to the upper 64 kilobytes of
+the
+.Tn I/O
+space result in
+.Tn VERSAbus
+transfers with a
+16-bit address (the offset in this region) and a
+.Dq No non-privileged short Tn I/O
+.Tn VERSAbus
+address modifier.
+Accesses to the remainder of the mapped region,
+result in
+.Tn VERSAbus
+transfers with a 24-bit address
+and a ``non-privileged standard''
+.Tn VERSAbus
+address
+modifier.  This region is actually part of the region
+between 0xfeff0000 and 0xffff0000
+which generates
+.Tn VERSAbus
+transfers with a 24-bit address.
+Accesses to the remainder of the one gigabyte
+.Tn I/O
+space
+generate transfers that utilize a 32-bit address with
+a ``non-privileged extended'' address modifier.  Any
+32-bit address generated by a cpu access to this part
+of the
+.Tn I/O
+space have the upper two bits zero; thus,
+for example, an access to physical address 0xfe000000
+causes the address 0x3e000000 to be supplied in the
+resultant
+.Tn VERSAbus
+read/write cycle.
+.Pp
+On the Tahoe, the 
+base address for the
+per-process data of the current process
+is virtual address 0xbffff000.
+.Sh FILES
+.Bl -tag -width Pa -compact
+.It Pa /dev/mem
+.It Pa /dev/kmem
+.It Pa /dev/vmm
+.El
+.Sh HISTORY
+The
+.Nm mem ,
+.Nm kmem
+files appeared in
+.At v6 .
+The file
+.Nm vmem
+appeared in
+.Bx 4.3 tahoe .
+.Sh BUGS
+Memory files are accessed one byte
+at a time, an inappropiate method for some
+device registers.
diff --git a/share/man/man4/man4.tahoe/mtio.4 b/share/man/man4/man4.tahoe/mtio.4
new file mode 100644
index 00000000000..b1c1bb311e8
--- /dev/null
+++ b/share/man/man4/man4.tahoe/mtio.4
@@ -0,0 +1,218 @@
+.\" 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: @(#)mtio.4	6.4 (Berkeley) 5/6/91
+.\"	$Id: mtio.4,v 1.1 1995/10/18 08:44:33 deraadt Exp $
+.\"
+.Dd May 6, 1991
+.Dt MTIO 4
+.Os
+.Sh NAME
+.Nm mtio
+.Nd
+.Tn UNIX
+magtape interface
+.Sh DESCRIPTION
+The special files named
+.Pa /dev/cy0s ,
+...,
+.Pa /dev/cy15s
+are interfaces to the
+.Tn UNIX
+magtape drivers.
+For the
+Tahoe, these interfaces
+may be on the
+.Tn VERSABUS
+via a
+.Tn CIPHER
+tapemaster formatter
+.Xr cy 4 .
+The files
+.Pa cy0s ,
+...,
+.Pa cy15s
+are read/written in 25
+.Tn IPS , 
+The density (1600
+.Tn BPI
+or 3200
+.Tn BPI )
+is selected by a switch on the drive.
+The following table of device names
+applies to any of the transport/controller pairs.
+.Bl -column "rewindxxx" "No-rewindxxx" "rewindxxxx" "No-rewindxxxx" -offset indent
+.Em Rewind	No-rewind	Rewind	No-rewind
+cy0s/rcy0s	ncy0s/nrcy0s	cy8s/rcy8s	ncy8s/nrcy8s
+cy1s/rcy1s	ncy1s/nrcy1s	cy9s/rcy9s	ncy9s/nrcy9s
+cy2s/rcy2s	ncy2s/nrcy2s	cy10s/rcy10s	ncy10s/nrcy10s
+cy3s/rcy3s	ncy3s/nrcy3s	cy11s/rcy11s	ncy11s/nrcy11s
+cy4s/rcy4s	ncy4s/nrcy4s	cy12s/rcy12s	ncy12s/nrcy12s
+cy5s/rcy5s	ncy5s/nrcy5s	cy13s/rcy13s	ncy13s/nrcy13s
+cy6s/rcy6s	ncy6s/nrcy6s	cy14s/rcy14s	ncy14s/nrcy14s
+cy7s/rcy7s	ncy7s/nrcy7s	cy15s/rcy15s	ncy15s/nrcy15s
+.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
+For compatibility with customary
+.Tn UNIX
+tape device
+names
+.Dq Em mt* ,
+the
+.Bo Pa n Bc Pa cy*s
+files are linked to appropriate
+.Bo Pa n Bc Em mt*
+files.
+.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 other
+.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
+.Sh FILES
+.Bl -tag -width /dev/nrcy? -compact
+.It Pa /dev/cy? ,
+.It Pa /dev/rcy?
+Rewind devices.
+.It Pa /dev/ncy? ,
+.It Pa /dev/nrcy?
+No-rewind devices.
+.It Pa /dev/[n]mt? ,
+.It Pa /dev/[n]rmt?
+Linked device names.
+.El
+.Sh SEE ALSO
+.Xr mt 1 ,
+.Xr tar 1 ,
+.Xr cy 4
diff --git a/share/man/man4/man4.tahoe/vd.4 b/share/man/man4/man4.tahoe/vd.4
new file mode 100644
index 00000000000..9927c182ca4
--- /dev/null
+++ b/share/man/man4/man4.tahoe/vd.4
@@ -0,0 +1,244 @@
+.\" 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: @(#)vd.4	6.4 (Berkeley) 3/27/91
+.\"	$Id: vd.4,v 1.1 1995/10/18 08:44:33 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt VD 4 tahoe
+.Os
+.Sh NAME
+.Nm vd
+.Nd
+.Tn VERSAbus
+storage module controller/drives
+.Sh SYNOPSIS
+.Cd "controller vd0 at vba? csr 0xffff2000 vector vdintr"
+.Cd "disk dk0 at vd0 drive 0"
+.Sh DESCRIPTION
+This is a generic
+.Tn VERSAbus
+storage module disk driver for the
+Computer Consoles
+.Tn SMD
+.Pq Tn VDDC
+and
+.Tn SMD-E
+disk controllers.
+.Pp
+The
+.Nm vd
+driver is a fairly typical block
+.Tn I/O
+device, except
+raw block
+.Tn I/O
+counts must be a multiple of 1024 bytes,
+whether the actual sector size is 512 or 1024 bytes.
+Likewise,
+.Xr seek
+calls should specify a multiple of 1024 bytes.
+See
+.Xr physio 4 .
+.Pp
+The first sector of each disk contains 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.
+.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 checks for a disk label on sector 0 of each drive
+during autoconfiguration.
+If no label is found,
+the driver tries to access the last track on each drive
+to determine the type of drive attached.
+The driver has default partition tables for
+seven different drives:
+.Tn CDC FSD
+(160
+.Tn MB ) ,
+.Tn CDC
+9766 (300
+.Tn MB ) ,
+.Tn CDC XFSD
+(340
+.Tn MB ) ,
+.Tn CDC
+515
+.Tn MB ,
+Fujitsu 360
+.Tn MB ,
+Fujitsu Eagle (440
+.Tn MB ) ,
+and Maxtor 340
+.Tn MB .
+If the drive is not recognized, a single small partition is created
+to allow a label to be written.
+.Pp
+The partition tables in the disk label and the
+.Pa disktab
+file specify partition offsets and sizes in sectors, which are 512 bytes
+on
+.Tn SMD
+drives and 1024 bytes on 5 1/4"
+.Tn ESDI
+drives.
+By convention,
+the ?a partition is normally used for the root file system or other small
+file system,
+and the ?b partition is used as a paging area.
+The ?c partition maps the rest of the pack,
+except the last 5 cylinders which are reserved for bad sector forwarding,
+and diagnostic use.
+.Sh FILES
+.Bl -tag -width /dev/dk[0-7][a-f]xx -compact
+.It Pa /dev/dk[0-7][a-f]
+dk block files
+.It Pa /dev/rdk[0-7][a-f]
+dk raw files
+.El
+.Sh DIAGNOSTICS
+.Bl -diag
+.It vd%d: %s controller.
+This message is printed during autoconfiguration to identify
+the type of controller, either
+.Tn VDDC
+or
+.Tn SMDE .
+.Pp
+.It vd%d: init error.
+During autoconfiguration the controller failed to respond to
+an initialize command.
+.Pp
+.It vd%d: diagnostic error.
+During autoconfiguration the controller failed  to respond to
+a diagnostic command.
+.Pp
+.It dk%d: unknown drive type.
+The system was unable to identify the specified drive as
+one of the drives described above; the drive will not be
+configured.
+.Pp
+.It vd%d: drive %d: config error.
+The system encountered a hard error when it tried to configure
+a drive during autoconfiguration.
+.Pp
+.It vd%d: starting drives, wait ... .
+This message indicates the system is about to tell the
+controller to ``start'' the drives attached to  it.
+.Pp
+.It dk%d: %s <ntrak %d, ncyl %d, nsec %d>.
+For each drive recognized during autoconfiguration the system
+prints a message of this form.  The drive type is displayed
+as well as the geometry: tracks/cylinder, cylinders, and sectors/track.
+.Pp
+.It vd%d: lost interrupt.
+The system failed to receive an interrupt from the controller after
+submitting a request.
+The system attempts to abort the current request and simulate an
+interrupt to unwedge the controller.
+During processing of the simulated interrupt, a controller error
+will be reported as described below.
+.Pp
+.It vd%d: stray interrupt.
+The system received an unexpected interrupt; it is ignored.
+.Pp
+.It dk%d%c: write locked.
+An attempt was made to write to a drive that is physically write-protected.
+.Pp
+.It "dk%d%c: controller err %sing fsbn %d [of %d-%d] (dk%d bn %d cn %d tn %d sn %d) status %b ecode %x; resetting controller... retrying."
+.br
+.It "dk%d%c: drive err %sing fsbn %d [of %d-%d] (dk%d bn %d cn %d tn %d sn %d) status %b ecode %x; resetting drive... retrying."
+An attempted transfer resulted in a controller or drive error.
+The controller or drive is reset, and the transfer is attempted
+a second time.
+.Pp
+.It "dk%d%c: hard error %sing fsbn %d [of %d-%d] (dk%d bn %d cn %d tn %d sn %d) status %b ecode %x."
+An unrecoverable error was encountered.  The filesystem block number reported
+is a logical sector number on the indicated partition;
+it is expressed using 1024-byte sectors.
+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
+(in 512- or 1024-byte blocks, as appropriate),
+as well as the cylinder, track and sector number of the block.
+The error status field of the device control
+block is printed in hexadecimal followed by a symbolic description.
+If this is an
+.Tn SMDE
+controller, the error code is also displayed.
+.Pp
+.It "dk%d%c: soft error %sing fsbn %d [of %d-%d] (dk%d bn %d cn %d tn %d sn %d) status %b ecode %x."
+A recoverable error was detected by the controller.
+The fields are interpreted in the same way as those for hard errors.
+.Pp
+.It "dk%d%c: soft ecc %sing fsbn %d [of %d-%d] (dk%d bn %d cn %d tn %d sn %d)."
+A recoverable
+.Tn ECC
+error was detected and corrected by the controller
+during the indicated transfer.
+.Pp
+.It vd%d: drive %d: couldn't reset.
+The system was unable to reconfigure a drive during a controller reset.
+.Pp
+.It vd%d: controller timeout.
+The controller failed to complete an operation within a reasonable
+time.  This message is usually followed by another message indicating
+what operation timed out; e.g. ``during config'' for a configuration
+command.
+.El
+.Sh SEE ALSO
+.Xr disklabel 5 ,
+.Xr disklabel 8
+.Sh HISTORY
+The
+.Nm
+driver appeared in
+.Bx 4.3 tahoe .
+.Sh BUGS
+Writes
+scribble on the tail of incomplete blocks.
+.Pp
+The system should use real disk sector numbers internally,
+instead of assuming 1024-byte sectors;
+errors should report filesystem block numbers using the actual sector size.
+Raw
+.Tn I/O
+should be permitted on any sector boundary.
diff --git a/share/man/man4/man4.tahoe/vx.4 b/share/man/man4/man4.tahoe/vx.4
new file mode 100644
index 00000000000..cab06611249
--- /dev/null
+++ b/share/man/man4/man4.tahoe/vx.4
@@ -0,0 +1,125 @@
+.\" 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: @(#)vx.4	6.3 (Berkeley) 3/27/91
+.\"	$Id: vx.4,v 1.1 1995/10/18 08:44:33 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt VX 4 tahoe
+.Os
+.Sh NAME
+.Nm vx
+.Nd
+.TN VIOC-X
+communications multiplexor
+.Sh SYNOPSIS
+.Cd "device vx0 at vba? csr 0xfffe0000 vector vackint vcmdrsp vunsol"
+.Sh DESCRIPTION
+A
+.Tn VIOC-X
+provides 16 communication lines with partial modem control,
+adequate for
+.Tn UNIX
+dialup use.
+and may be set to run at any of 16 speeds; see
+.Xr tty 4 .
+.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 vx%d: vc proc err, ustat %x.
+.Pp
+.It vx%d: vc uqual err, uqual %x.
+.Pp
+.It vx%d: %d exceeds silo size.
+.Pp
+.It vx%d: receiver overrun.
+.Pp
+.It VIOC-BOP no. %d at %x.
+The system identified a vioc supporting the bit oriented protocol.
+The number
+.Em %d
+is the board number assigned by the system
+while the address
+.Em %x
+is the address of the command control
+block for the vioc.
+.It vx%d: unknown type %x.
+The system encountered a vioc of unknown type during autoconfiguration.
+.It vx%d: didn't respond to LIDENT.
+The device did not respond to the configuration command that
+sets the interrupt vectors and port configuration.
+.It vx%d: %s%s, ports %d-%d.
+This is informatory message printed during autoconfiguration
+indicating the type of hardware present the port configuration.
+.It vx%d: no buffers.
+All the command buffers were in use; this indicates the device
+is constipated for some reason.
+.It vx%d: setq overflow.
+An attempt to append a command to an existing command buffer
+failed because the buffer was full or the hardware doesn't
+support this facility.
+.It vx%d: cmd q overflow.
+An attempt to place a new command on the command queue failed
+because it was full.  The device is either overloaded or hung
+up for some reason.  If this happens, the system tries to
+reset the device to unwedge it.
+.It vx%d INTR ERR type %x v_dcd %x.
+An error was returned by the device in response to some command.
+The command identifier and data carrier detect mask are printed
+followed by the contents of the command buffer in error.
+.It vx%d: vcmdrsp interrupt.
+A command response interrupt was received from a bop (bit oriented
+protocol) vioc.  This should not happen.
+.It vx%d: cmdresp debug.
+.Pp
+.It vx%d: vunsol from
+.Tn BOP .
+An unsolicited interrupt was received from a bop vioc.  This should
+not happen.
+.It vx%d: interrupt q overflow.
+The queue of pending interrupts to be delivered to the vioc is
+full.  This is probably due to the vioc being wedged.  The system
+resets the vioc if this occurs.
+.It vx%d: reset....
+The system attempted to reset the vioc.
+.El
+.Sh SEE ALSO
+.Xr tty 4
+.Sh HISTORY
+The
+.Nm
+special file appeared in
+.Bx 4.3 tahoe .
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.
diff --git a/share/man/man4/netintro.4 b/share/man/man4/netintro.4
new file mode 100644
index 00000000000..062104385e4
--- /dev/null
+++ b/share/man/man4/netintro.4
@@ -0,0 +1,330 @@
+.\"	$NetBSD: netintro.4,v 1.3 1994/11/30 16:22:24 jtc Exp $
+.\"
+.\" Copyright (c) 1983, 1990, 1991, 1993
+.\"	The Regents of the University of California.  All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     @(#)netintro.4	8.2 (Berkeley) 11/30/93
+.\"
+.Dd November 30, 1993
+.Dt NETINTRO 4
+.Os BSD 4.2
+.Sh NAME
+.Nm networking
+.Nd introduction to networking facilities
+.Sh SYNOPSIS
+.Fd #include <sys/socket.h>
+.Fd #include <net/route.h>
+.Fd #include <net/if.h>
+.Sh DESCRIPTION
+This section is a general introduction to the networking facilities
+available in the system.
+Documentation in this part of section
+4 is broken up into three areas:
+.Em protocol families
+(domains),
+.Em protocols ,
+and
+.Em network interfaces .
+.Pp
+All network protocols are associated with a specific
+.Em protocol family .
+A protocol family provides basic services to the protocol
+implementation to allow it to function within a specific
+network environment.  These services may include 
+packet fragmentation and reassembly, routing, addressing, and 
+basic transport.  A protocol family may support multiple
+methods of addressing, though the current protocol implementations
+do not.  A protocol family is normally comprised of a number
+of protocols, one per
+.Xr socket 2
+type.  It is not required that a protocol family support
+all socket types.  A protocol family may contain multiple
+protocols supporting the same socket abstraction. 
+.Pp
+A protocol supports one of the socket abstractions detailed in
+.Xr socket 2 .
+A specific protocol may be accessed either by creating a
+socket of the appropriate type and protocol family, or
+by requesting the protocol explicitly when creating a socket.
+Protocols normally accept only one type of address format,
+usually determined by the addressing structure inherent in
+the design of the protocol family/network architecture.
+Certain semantics of the basic socket abstractions are
+protocol specific.  All protocols are expected to support
+the basic model for their particular socket type, but may,
+in addition, provide non-standard facilities or extensions
+to a mechanism.  For example, a protocol supporting the
+.Dv SOCK_STREAM
+abstraction may allow more than one byte of out-of-band
+data to be transmitted per out-of-band message.
+.Pp
+A network interface is similar to a device interface.
+Network interfaces comprise the lowest layer of the
+networking subsystem, interacting with the actual transport
+hardware.  An interface may support one or more protocol
+families and/or address formats.
+The SYNOPSIS section of each network interface
+entry gives a sample specification
+of the related drivers for use in providing
+a system description to the
+.Xr config 8
+program.
+The DIAGNOSTICS section lists messages which may appear on the console
+and/or in the system error log,
+.Pa /var/log/messages
+(see
+.Xr syslogd 8 ) ,
+due to errors in device operation.
+.Sh PROTOCOLS
+The system currently supports the
+Internet
+protocols, the Xerox Network Systems(tm) protocols,
+and some of the
+.Tn ISO OSI
+protocols.
+Raw socket interfaces are provided to the
+.Tn IP
+protocol
+layer of the
+Internet, and to the
+.Tn IDP
+protocol of Xerox
+.Tn NS .
+Consult the appropriate manual pages in this section for more
+information regarding the support for each protocol family.
+.Sh ADDRESSING
+Associated with each protocol family is an address
+format.  All network address adhere to a general structure,
+called a sockaddr, described below. However, each protocol
+imposes finer and more specific structure, generally renaming
+the variant, which is discussed in the protocol family manual
+page alluded to above.
+.Bd -literal -offset indent
+    struct sockaddr {
+	u_char	sa_len;
+    	u_char	sa_family;
+    	char	sa_data[14];
+};
+.Ed
+.Pp
+The field
+.Ar sa_len
+contains the total length of the of the structure,
+which may exceed 16 bytes.
+The following address values for
+.Ar sa_family
+are known to the system
+(and additional formats are defined for possible future implementation):
+.Bd -literal
+#define    AF_UNIX      1    /* local to host (pipes, portals) */
+#define    AF_INET      2    /* internetwork: UDP, TCP, etc. */
+#define    AF_NS        6    /* Xerox NS protocols */
+#define    AF_CCITT     10   /* CCITT protocols, X.25 etc */
+#define    AF_HYLINK    15   /* NSC Hyperchannel */
+#define    AF_ISO       18   /* ISO protocols */
+.Ed
+.Sh ROUTING
+.Tn UNIX
+provides some packet routing facilities.
+The kernel maintains a routing information database, which
+is used in selecting the appropriate network interface when
+transmitting packets.
+.Pp
+A user process (or possibly multiple co-operating processes)
+maintains this database by sending messages over a special kind
+of socket.
+This supplants fixed size
+.Xr ioctl 2
+used in earlier releases.
+.Pp
+This facility is described in
+.Xr route 4 .
+.Sh INTERFACES
+Each network interface in a system corresponds to a
+path through which messages may be sent and received.  A network
+interface usually has a hardware device associated with it, though
+certain interfaces such as the loopback interface,
+.Xr lo 4 ,
+do not.
+.Pp
+The following 
+.Xr ioctl
+calls may be used to manipulate network interfaces.
+The
+.Xr ioctl
+is made on a socket (typically of type
+.Dv SOCK_DGRAM )
+in the desired domain.
+Most of the requests supported in earlier releases 
+take an
+.Ar ifreq
+structure as its parameter.  This structure has the form
+.Bd -literal
+struct	ifreq {
+#define    IFNAMSIZ    16
+    char    ifr_name[IFNAMSIZE];        /* if name, e.g. "en0" */
+    union {
+        struct    sockaddr ifru_addr;
+        struct    sockaddr ifru_dstaddr;
+        struct    sockaddr ifru_broadaddr;
+        short     ifru_flags;
+        int       ifru_metric;
+        caddr_t   ifru_data;
+    } ifr_ifru;
+#define ifr_addr      ifr_ifru.ifru_addr    /* address */
+#define ifr_dstaddr   ifr_ifru.ifru_dstaddr /* other end of p-to-p link */
+#define ifr_broadaddr ifr_ifru.ifru_broadaddr /* broadcast address */
+#define ifr_flags     ifr_ifru.ifru_flags   /* flags */
+#define ifr_metric    ifr_ifru.ifru_metric  /* metric */
+#define ifr_data      ifr_ifru.ifru_data    /* for use by interface */
+};
+.Ed
+.Pp
+Calls which are now deprecated are:
+.Bl -tag -width SIOCGIFBRDADDR
+.It Dv SIOCSIFADDR
+Set interface address for protocol family.  Following the address
+assignment, the ``initialization'' routine for
+the interface is called.
+.It Dv SIOCSIFDSTADDR
+Set point to point address for protocol family and interface.
+.It Dv SIOCSIFBRDADDR
+Set broadcast address for protocol family and interface.
+.El
+.Pp
+.Xr Ioctl
+requests to obtain addresses and requests both to set and
+retrieve other data are still fully supported
+and use the
+.Ar ifreq
+structure:
+.Bl -tag -width SIOCGIFBRDADDR
+.It Dv SIOCGIFADDR
+Get interface address for protocol family.
+.It Dv SIOCGIFDSTADDR
+Get point to point address for protocol family and interface.
+.It Dv SIOCGIFBRDADDR
+Get broadcast address for protocol family and interface.
+.It Dv SIOCSIFFLAGS
+Set interface flags field.  If the interface is marked down,
+any processes currently routing packets through the interface
+are notified;
+some interfaces may be reset so that incoming packets are no longer received.
+When marked up again, the interface is reinitialized.
+.It Dv SIOCGIFFLAGS
+Get interface flags.
+.It Dv SIOCSIFMETRIC
+Set interface routing metric.
+The metric is used only by user-level routers.
+.It Dv SIOCGIFMETRIC
+Get interface metric.
+.El
+.Pp
+There are two requests that make use of a new structure:
+.Bl -tag -width SIOCGIFBRDADDR
+.It Dv SIOCAIFADDR
+An interface may have more than one address associated with it
+in some protocols.  This request provides a means to
+add additional addresses (or modify characteristics of the
+primary address if the default address for the address family
+is specified).  Rather than making separate calls to
+set destination or broadcast addresses, or network masks
+(now an integral feature of multiple protocols)
+a separate structure is used to specify all three facets simultaneously
+(see below).
+One would use a slightly tailored version of this struct specific
+to each family (replacing each sockaddr by one
+of the family-specific type).
+Where the sockaddr itself is larger than the
+default size, one needs to modify the
+.Xr ioctl
+identifier itself to include the total size, as described in
+.Xr ioctl .
+.It Dv SIOCDIFADDR
+This requests deletes the specified address from the list
+associated with an interface.  It also uses the
+.Ar if_aliasreq
+structure to allow for the possibility of protocols allowing
+multiple masks or destination addresses, and also adopts the
+convention that specification of the default address means
+to delete the first address for the interface belonging to
+the address family in which the original socket was opened.
+.It Dv SIOCGIFCONF
+Get interface configuration list.  This request takes an
+.Ar ifconf
+structure (see below) as a value-result parameter.  The 
+.Ar ifc_len
+field should be initially set to the size of the buffer
+pointed to by 
+.Ar ifc_buf .
+On return it will contain the length, in bytes, of the
+configuration list.
+.El
+.Bd -literal
+/*
+* Structure used in SIOCAIFCONF request.
+*/
+struct ifaliasreq {
+        char    ifra_name[IFNAMSIZ];   /* if name, e.g. "en0" */
+        struct  sockaddr        ifra_addr;
+        struct  sockaddr        ifra_broadaddr;
+        struct  sockaddr        ifra_mask;
+};
+.Ed
+.Pp
+.Bd -literal
+/*
+* Structure used in SIOCGIFCONF request.
+* Used to retrieve interface configuration
+* for machine (useful for programs which
+* must know all networks accessible).
+*/
+struct ifconf {
+    int   ifc_len;		/* size of associated buffer */
+    union {
+        caddr_t    ifcu_buf;
+        struct     ifreq *ifcu_req;
+    } ifc_ifcu;
+#define ifc_buf ifc_ifcu.ifcu_buf /* buffer address */
+#define ifc_req ifc_ifcu.ifcu_req /* array of structures returned */
+};
+.Ed
+.Sh SEE ALSO
+.Xr socket 2 ,
+.Xr ioctl 2 ,
+.Xr intro 4 ,
+.Xr config 8 ,
+.Xr routed 8
+.Sh HISTORY
+The
+.Nm netintro
+manual appeared in
+.Bx 4.3 tahoe .
diff --git a/share/man/man4/ns.4 b/share/man/man4/ns.4
new file mode 100644
index 00000000000..fd7c6bb4f9e
--- /dev/null
+++ b/share/man/man4/ns.4
@@ -0,0 +1,181 @@
+.\"	$NetBSD: ns.4,v 1.3 1994/11/30 16:22:26 jtc Exp $
+.\"
+.\" Copyright (c) 1985, 1991, 1993
+.\"	The Regents of the University of California.  All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     @(#)ns.4	8.2 (Berkeley) 11/30/93
+.\"
+.Dd November 30, 1993
+.Dt NS 4
+.Os BSD 4.3
+.Sh NAME
+.Nm ns
+.Nd Xerox Network Systems(tm) protocol family
+.Sh SYNOPSIS
+.Nm options NS
+.Nm options NSIP
+.Nm pseudo-device ns
+.Sh DESCRIPTION
+The
+.Tn NS
+protocol family is a collection of protocols
+layered atop the
+.Em Internet  Datagram  Protocol
+.Pq Tn IDP
+transport layer, and using the Xerox 
+.Tn NS
+address formats.
+The
+.Tn NS
+family provides protocol support for the
+.Dv SOCK_STREAM , SOCK_DGRAM , SOCK_SEQPACKET ,
+and
+.Dv SOCK_RAW
+socket types; the
+.Dv SOCK_RAW
+interface is a debugging tool, allowing you to trace all packets
+entering, (or with toggling kernel variable, additionally leaving) the local
+host.
+.Sh ADDRESSING
+.Tn NS
+addresses are 12 byte quantities, consisting of a 
+4 byte Network number, a 6 byte Host number and a 2 byte port number,
+all stored in network standard format.
+(on the
+.Tn VAX
+these are word and byte reversed; on the
+.Tn SUN 
+they are not
+reversed).  The include file
+.Aq Pa netns/ns.h
+defines the
+.Tn NS
+address as a structure containing unions (for quicker
+comparisons).
+.Pp
+Sockets in the Internet protocol family use the following
+addressing structure:
+.Bd -literal -offset indent
+struct sockaddr_ns {
+	short		sns_family;
+	struct ns_addr	sns_addr;
+	char		sns_zero[2];
+};
+.Ed
+.Pp
+where an
+.Ar ns_addr
+is composed as follows:
+.Bd -literal -offset indent
+union ns_host {
+	u_char		c_host[6];
+	u_short		s_host[3];
+};
+
+union ns_net {
+	u_char		c_net[4];
+	u_short		s_net[2];
+};
+
+struct ns_addr {
+	union ns_net	x_net;
+	union ns_host	x_host;
+	u_short	x_port;
+};
+.Ed
+.Pp
+Sockets may be created with an address of all zeroes to effect
+.Dq wildcard
+matching on incoming messages.
+The local port address specified in a
+.Xr bind 2
+call is restricted to be greater than
+.Dv NSPORT_RESERVED
+(=3000, in
+.Aq Pa netns/ns.h )
+unless the creating process is running
+as the super-user, providing a space of protected port numbers.
+.Sh PROTOCOLS
+The
+.Tn NS
+protocol family supported by the operating system
+is comprised of
+the Internet Datagram Protocol
+.Pq Tn IDP
+.Xr idp 4 ,
+Error Protocol (available through
+.Tn IDP ) ,
+and
+Sequenced Packet Protocol
+.Pq Tn SPP
+.Xr spp 4 .
+.Pp
+.Tn SPP
+is used to support the
+.Dv SOCK_STREAM
+and
+.Dv SOCK_SEQPACKET
+abstraction,
+while
+.Tn IDP
+is used to support the
+.Dv SOCK_DGRAM
+abstraction.
+The Error protocol is responded to by the kernel
+to handle and report errors in protocol processing;
+it is, however,
+only accessible to user programs through heroic actions.
+.Sh SEE ALSO
+.Xr intro 3 ,
+.Xr byteorder 3 ,
+.Xr gethostbyname 3 ,
+.Xr getnetent 3 ,
+.Xr getprotoent 3 ,
+.Xr getservent 3 ,
+.Xr ns 3 ,
+.Xr intro 4 ,
+.Xr spp 4 ,
+.Xr idp 4 ,
+.Xr nsip 4
+.Rs
+.%T "Internet Transport Protocols"
+.%R Xerox Corporation document XSIS
+.%N 028112
+.Re
+.Rs
+.%T "An Advanced 4.3 BSD Interprocess Communication Tutorial"
+.Re
+.Sh HISTORY
+The
+.Nm
+protocol family
+appeared in
+.Bx 4.3 .
diff --git a/share/man/man4/nsip.4 b/share/man/man4/nsip.4
new file mode 100644
index 00000000000..a9b2ce9ab71
--- /dev/null
+++ b/share/man/man4/nsip.4
@@ -0,0 +1,130 @@
+.\"	$NetBSD: nsip.4,v 1.3 1994/11/30 16:22:27 jtc Exp $
+.\"
+.\" Copyright (c) 1985, 1991, 1993
+.\"	The Regents of the University of California.  All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     @(#)nsip.4	8.2 (Berkeley) 11/30/93
+.\"
+.Dd November 30, 1993
+.Dt NSIP 4
+.Os BSD 4.3
+.Sh NAME
+.Nm nsip
+.Nd software network interface encapsulating NS packets in IP packets
+.Sh SYNOPSIS
+.Cd options NSIP
+.Fd #include <netns/ns_if.h>
+.Sh DESCRIPTION
+The
+.Nm nsip
+interface is a software mechanism which may be
+used to transmit Xerox
+.Tn NS Ns (tm)
+packets through otherwise uncooperative
+networks.
+It functions by prepending an
+.Tn IP
+header, and resubmitting the packet
+through the
+.Tn UNIX
+.Tn IP
+machinery.
+.Pp
+The super-user can advise the operating system of a willing partner
+by naming an
+.Tn IP
+address to be associated with an
+.Tn NS
+address.
+Presently, only specific hosts pairs are allowed, and for each host
+pair, an artificial point-to-point interface is constructed.
+At some future date,
+.Tn IP
+broadcast addresses or hosts may be paired
+with
+.Tn NS
+networks or hosts.
+.Pp
+Specifically, a socket option of
+.Dv SO_NSIP_ROUTE
+is set on a socket
+of family
+.Dv AF_NS ,
+type
+.Dv SOCK_DGRAM ,
+passing the following structure:
+.Bd -literal
+struct nsip_req {
+	struct sockaddr rq_ns;	/* must be ns format destination */
+	struct sockaddr rq_ip;	/* must be ip format gateway */
+	short rq_flags;
+};
+.Ed
+.Sh DIAGNOSTICS
+.Bl -diag
+.It nsip%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 intro 4 ,
+.Xr ns 4
+.Sh HISTORY
+The
+.Nm
+interface appeared in
+.Bx 4.3 .
+.Sh BUGS
+It is absurd to have a separate pseudo-device for each pt-to-pt
+link.
+There is no way to change the
+.Tn IP
+address for an
+.Tn NS
+host once the
+encapsulation interface is set up.
+The request should honor flags of
+.Dv RTF_GATEWAY
+to indicate
+remote networks, and the absence of
+.Dv RTF_UP
+should be a clue
+to remove that partner.
+This was intended to postpone the necessity of rewriting reverse
+.Tn ARP
+for the 
+.Xr en 4
+device, and to allow passing
+.Tn XNS
+packets through an
+Arpanet-Milnet gateway, to facilitate testing between some co-operating
+universities.
diff --git a/share/man/man4/null.4 b/share/man/man4/null.4
new file mode 100644
index 00000000000..e45c98bf4d0
--- /dev/null
+++ b/share/man/man4/null.4
@@ -0,0 +1,58 @@
+.\"	$NetBSD: null.4,v 1.3 1994/11/30 16:22:29 jtc Exp $
+.\"
+.\" Copyright (c) 1991, 1993
+.\"	The Regents of the University of California.  All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"	@(#)null.4	8.1 (Berkeley) 6/5/93
+.\"
+.Dd June 5, 1993
+.Dt NULL 4
+.Os
+.Sh NAME
+.Nm null
+.Nd the null device
+.Sh DESCRIPTION
+The
+.Nm
+device accepts and reads data as any ordinary (and willing)
+file \-
+but throws it away. The length of the
+.Nm null
+device is always zero.
+.Sh FILES
+.Bl -tag -width /dev/null
+.It Pa /dev/null
+.El
+.Sh HISTORY
+A
+.Nm
+device appeared in
+.At v7 .
diff --git a/share/man/man4/pty.4 b/share/man/man4/pty.4
new file mode 100644
index 00000000000..125995a5ab0
--- /dev/null
+++ b/share/man/man4/pty.4
@@ -0,0 +1,214 @@
+.\"	$NetBSD: pty.4,v 1.3 1994/11/30 16:22:30 jtc Exp $
+.\"
+.\" Copyright (c) 1983, 1991, 1993
+.\"	The Regents of the University of California.  All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     @(#)pty.4	8.2 (Berkeley) 11/30/93
+.\"
+.Dd November 30, 1993
+.Dt PTY 4
+.Os BSD 4.2
+.Sh NAME
+.Nm pty
+.Nd pseudo terminal driver
+.Sh SYNOPSIS
+.Nm pseudo-device pty
+.Op Ar count
+.Sh DESCRIPTION
+The
+.Xr pty
+driver provides support for a device-pair termed a
+.Em pseudo terminal .
+A pseudo terminal is a pair of character devices, a
+.Em master
+device and a
+.Em slave
+device.  The slave device provides to a process
+an interface identical
+to that described in
+.Xr tty 4 .
+However, whereas all other devices which provide the 
+interface described in
+.Xr tty 4
+have a hardware device of some sort behind them, the slave
+device has, instead, another process manipulating
+it through the master half of the pseudo terminal.
+That is, anything written on the master device is
+given to the slave device as input and anything written
+on the slave device is presented as input on the master
+device.
+.Pp
+In configuring, if an optional
+.Ar count
+is given in
+the specification, that number of pseudo terminal pairs are configured;
+the default count is 32.
+.Pp
+The following 
+.Xr ioctl 2
+calls apply only to pseudo terminals:
+.Bl -tag -width TIOCREMOTE
+.It Dv TIOCSTOP
+Stops output to a terminal (e.g. like typing
+.Ql ^S ) .
+Takes
+no parameter.
+.It Dv TIOCSTART
+Restarts output (stopped by
+.Dv TIOCSTOP
+or by typing
+.Ql ^S ) .
+Takes no parameter.
+.It Dv TIOCPKT
+Enable/disable 
+.Em packet
+mode.  Packet mode is enabled by specifying (by reference)
+a nonzero parameter and disabled by specifying (by reference)
+a zero parameter.  When applied to the master side of a pseudo
+terminal, each subsequent 
+.Xr read
+from the terminal will return data written on the slave part of
+the pseudo terminal preceded by a zero byte (symbolically
+defined as
+.Dv TIOCPKT_DATA ) ,
+or a single byte reflecting control
+status information.  In the latter case, the byte is an inclusive-or
+of zero or more of the bits:
+.Bl -tag -width TIOCPKT_FLUSHWRITE
+.It Dv TIOCPKT_FLUSHREAD
+whenever the read queue for the terminal is flushed.
+.It Dv TIOCPKT_FLUSHWRITE
+whenever the write queue for the terminal is flushed.
+.It Dv TIOCPKT_STOP
+whenever output to the terminal is stopped a la
+.Ql ^S .
+.It Dv TIOCPKT_START
+whenever output to the terminal is restarted.
+.It Dv TIOCPKT_DOSTOP
+whenever 
+.Em t_stopc
+is
+.Ql ^S
+and 
+.Em t_startc
+is
+.Ql ^Q .
+.It Dv TIOCPKT_NOSTOP
+whenever the start and stop characters are not
+.Ql ^S/^Q .
+.Pp
+While this mode is in use, the presence of control status information
+to be read from the master side may be detected by a
+.Xr select 2
+for exceptional conditions.
+.Pp
+This mode is used by
+.Xr rlogin 1
+and
+.Xr rlogind 8
+to implement a remote-echoed, locally
+.Ql ^S/^Q
+flow-controlled
+remote login with proper back-flushing of output; it can be
+used by other similar programs.
+.El
+.It Dv TIOCUCNTL
+Enable/disable a mode that allows a small number of simple user
+.Xr ioctl
+commands to be passed through the pseudo-terminal,
+using a protocol similar to that of
+.Dv TIOCPKT .
+The
+.Dv TIOCUCNTL
+and
+.Dv TIOCPKT
+modes are mutually exclusive.
+This mode is enabled from the master side of a pseudo terminal
+by specifying (by reference)
+a nonzero parameter and disabled by specifying (by reference)
+a zero parameter.
+Each subsequent 
+.Xr read
+from the master side will return data written on the slave part of
+the pseudo terminal preceded by a zero byte,
+or a single byte reflecting a user control operation on the slave side.
+A user control command consists of a special
+.Xr ioctl
+operation with no data; the command is given as
+.Dv UIOCCMD Ns (n) ,
+where
+.Ar n
+is a number in the range 1-255.
+The operation value
+.Ar n
+will be received as a single byte on the next
+.Xr read
+from the master side.
+The
+.Xr ioctl
+.Dv UIOCCMD Ns (0)
+is a no-op that may be used to probe for
+the existence of this facility.
+As with
+.Dv TIOCPKT
+mode, command operations may be detected with a
+.Xr select
+for exceptional conditions.
+.It Dv TIOCREMOTE
+A mode for the master half of a pseudo terminal, independent
+of
+.Dv TIOCPKT .
+This mode causes input to the pseudo terminal
+to be flow controlled and not input edited (regardless of the
+terminal mode).  Each write to the control terminal produces
+a record boundary for the process reading the terminal.  In
+normal usage, a write of data is like the data typed as a line
+on the terminal; a write of 0 bytes is like typing an end-of-file
+character.
+.Dv TIOCREMOTE
+can be used when doing remote line
+editing in a window manager, or whenever flow controlled input
+is required.
+.El
+.Sh FILES
+.Bl -tag -width /dev/tty[p-r][0-9a-f]x -compact
+.It Pa /dev/pty[p-r][0-9a-f]
+master pseudo terminals
+.It Pa /dev/tty[p-r][0-9a-f]
+slave pseudo terminals
+.El
+.Sh DIAGNOSTICS
+None.
+.Sh HISTORY
+The
+.Nm
+driver appeared in
+.Bx 4.2 .
diff --git a/share/man/man4/route.4 b/share/man/man4/route.4
new file mode 100644
index 00000000000..382dc323615
--- /dev/null
+++ b/share/man/man4/route.4
@@ -0,0 +1,272 @@
+.\"	$NetBSD: route.4,v 1.3 1994/11/30 16:22:31 jtc Exp $
+.\"
+.\" Copyright (c) 1990, 1991, 1993
+.\"	The Regents of the University of California.  All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     @(#)route.4	8.6 (Berkeley) 4/19/94
+.\"
+.Dd April 19, 1994
+.Dt ROUTE 4
+.Os
+.Sh NAME
+.Nm route 
+.Nd kernel packet forwarding database
+.Sh SYNOPSIS
+.Fd #include <sys/socket.h>
+.Fd #include <net/if.h>
+.Fd #include <net/route.h>
+.Ft int
+.Fn socket PF_ROUTE SOCK_RAW "int family"
+.Sh DESCRIPTION
+.Tn UNIX
+provides some packet routing facilities.
+The kernel maintains a routing information database, which
+is used in selecting the appropriate network interface when
+transmitting packets.
+.Pp
+A user process (or possibly multiple co-operating processes)
+maintains this database by sending messages over a special kind
+of socket.
+This supplants fixed size
+.Xr ioctl 2 Ns 's
+used in earlier releases.
+Routing table changes may only be carried out by the super user.
+.Pp
+The operating system may spontaneously emit routing messages in response
+to external events, such as receipt of a re-direct, or failure to
+locate a suitable route for a request.
+The message types are described in greater detail below.
+.Pp
+Routing database entries come in two flavors: for a specific
+host, or for all hosts on a generic subnetwork (as specified
+by a bit mask and value under the mask.
+The effect of wildcard or default route may be achieved by using
+a mask of all zeros, and there may be hierarchical routes.
+.Pp
+When the system is booted and addresses are assigned
+to the network interfaces, each protocol family
+installs a routing table entry for each interface when it is ready for traffic.
+Normally the protocol specifies the route
+through each interface as a
+.Dq direct
+connection to the destination host
+or network.  If the route is direct, the transport layer of
+a protocol family usually requests the packet be sent to the
+same host specified in the packet.  Otherwise, the interface
+is requested to address the packet to the gateway listed in the routing entry
+(i.e. the packet is forwarded).
+.Pp
+When routing a packet,
+the kernel will attempt to find 
+the most specific route matching the destination.
+(If there are two different mask and value-under-the-mask pairs
+that match, the more specific is the one with more bits in the mask.
+A route to a host is regarded as being supplied with a mask of
+as many ones as there are bits in the destination).
+If no entry is found, the destination is declared to be unreachable,
+and a routing\-miss message is generated if there are any
+listers on the routing control socket described below.
+.Pp
+A wildcard routing entry is specified with a zero
+destination address value, and a mask of all zeroes.
+Wildcard routes will be used
+when the system fails to find other routes matching the
+destination.  The combination of wildcard
+routes and routing redirects can provide an economical
+mechanism for routing traffic.
+.Pp
+One opens the channel for passing routing control messages
+by using the socket call shown in the synopsis above:
+.Pp
+The
+.Fa family
+parameter may be
+.Dv AF_UNSPEC
+which will provide
+routing information for all address families, or can be restricted
+to a specific address family by specifying which one is desired.
+There can be more than one routing socket open per system.
+.Pp
+Messages are formed by a header followed by a small
+number of sockadders (now variable length particularly
+in the
+.Tn ISO
+case), interpreted by position, and delimited
+by the new length entry in the sockaddr.
+An example of a message with four addresses might be an
+.Tn ISO
+redirect:
+Destination, Netmask, Gateway, and Author of the redirect.
+The interpretation of which address are present is given by a
+bit mask within the header, and the sequence is least significant
+to most significant bit within the vector.
+.Pp
+Any messages sent to the kernel are returned, and copies are sent
+to all interested listeners.  The kernel will provide the process
+id. for the sender, and the sender may use an additional sequence
+field to distinguish between outstanding messages.  However,
+message replies may be lost when kernel buffers are exhausted.
+.Pp
+The kernel may reject certain messages, and will indicate this
+by filling in the
+.Ar rtm_errno
+field.
+The routing code returns
+.Dv EEXIST
+if
+requested to duplicate an existing entry,
+.Dv ESRCH
+if
+requested to delete a non-existent entry,
+or
+.Dv ENOBUFS
+if insufficient resources were available
+to install a new route.
+In the current implementation, all routing process run locally,
+and the values for
+.Ar rtm_errno
+are available through the normal
+.Em errno
+mechanism, even if the routing reply message is lost.
+.Pp
+A process may avoid the expense of reading replies to
+its own messages by issuing a
+.Xr setsockopt 2
+call indicating that the
+.Dv SO_USELOOPBACK
+option
+at the
+.Dv SOL_SOCKET
+level is to be turned off.
+A process may ignore all messages from the routing socket
+by doing a 
+.Xr shutdown 2
+system call for further input.
+.Pp
+If a route is in use when it is deleted,
+the routing entry will be marked down and removed from the routing table,
+but the resources associated with it will not
+be reclaimed until all references to it are released. 
+User processes can obtain information about the routing
+entry to a specific destination by using a
+.Dv RTM_GET
+message,
+or by reading the
+.Pa /dev/kmem
+device, or by issuing a
+.Xr getkerninfo 2
+system call.
+.Pp
+Messages include:
+.Bd -literal
+#define	RTM_ADD		0x1    /* Add Route */
+#define	RTM_DELETE	0x2    /* Delete Route */
+#define	RTM_CHANGE	0x3    /* Change Metrics, Flags, or Gateway */
+#define	RTM_GET		0x4    /* Report Information */
+#define	RTM_LOOSING	0x5    /* Kernel Suspects Partitioning */
+#define	RTM_REDIRECT	0x6    /* Told to use different route */
+#define	RTM_MISS	0x7    /* Lookup failed on this address */
+#define	RTM_RESOLVE	0xb    /* request to resolve dst to LL addr */
+.Ed
+.Pp
+A message header consists of:
+.Bd -literal
+struct rt_msghdr {
+    u_short rmt_msglen;  /* to skip over non-understood messages */
+    u_char  rtm_version; /* future binary compatibility */
+    u_char  rtm_type;    /* message type */
+    u_short rmt_index;   /* index for associated ifp */
+    pid_t   rmt_pid;     /* identify sender */
+    int     rtm_addrs;   /* bitmask identifying sockaddrs in msg */
+    int     rtm_seq;     /* for sender to identify action */
+    int     rtm_errno;   /* why failed */
+    int     rtm_flags;   /* flags, incl kern & message, e.g. DONE */
+    int     rtm_use;     /* from rtentry */
+    u_long  rtm_inits;   /* which values we are initializing */
+    struct  rt_metrics rtm_rmx;	/* metrics themselves */
+};
+.Ed
+.Pp
+where
+.Bd -literal
+struct rt_metrics {
+    u_long rmx_locks;     /* Kernel must leave these values alone */
+    u_long rmx_mtu;       /* MTU for this path */
+    u_long rmx_hopcount;  /* max hops expected */
+    u_long rmx_expire;    /* lifetime for route, e.g. redirect */
+    u_long rmx_recvpipe;  /* inbound delay-bandwith product */
+    u_long rmx_sendpipe;  /* outbound delay-bandwith product */
+    u_long rmx_ssthresh;  /* outbound gateway buffer limit */
+    u_long rmx_rtt;       /* estimated round trip time */
+    u_long rmx_rttvar;    /* estimated rtt variance */
+};
+.Ed
+.Pp
+Flags include the values:
+.Bd -literal
+#define	RTF_UP        0x1       /* route usable */
+#define	RTF_GATEWAY   0x2       /* destination is a gateway */
+#define	RTF_HOST      0x4       /* host entry (net otherwise) */
+#define	RTF_REJECT    0x8       /* host or net unreachable */
+#define	RTF_DYNAMIC   0x10      /* created dynamically (by redirect) */
+#define	RTF_MODIFIED  0x20      /* modified dynamically (by redirect) */
+#define	RTF_DONE      0x40      /* message confirmed */
+#define	RTF_MASK      0x80      /* subnet mask present */
+#define	RTF_CLONING   0x100     /* generate new routes on use */
+#define	RTF_XRESOLVE  0x200     /* external daemon resolves name */
+#define	RTF_LLINFO    0x400     /* generated by ARP or ESIS */
+#define	RTF_STATIC    0x800     /* manually added */
+#define	RTF_BLACKHOLE 0x1000    /* just discard pkts (during updates) */
+#define	RTF_PROTO2    0x4000    /* protocol specific routing flag #1 */
+#define	RTF_PROTO1    0x8000    /* protocol specific routing flag #2 */
+.Ed
+.Pp
+Specifiers for metric values in rmx_locks and rtm_inits are:
+.Bd -literal
+#define	RTV_SSTHRESH  0x1    /* init or lock _ssthresh */
+#define	RTV_RPIPE     0x2    /* init or lock _recvpipe */
+#define	RTV_SPIPE     0x4    /* init or lock _sendpipe */
+#define	RTV_HOPCOUNT  0x8    /* init or lock _hopcount */
+#define	RTV_RTT       0x10   /* init or lock _rtt */
+#define	RTV_RTTVAR    0x20   /* init or lock _rttvar */
+#define	RTV_MTU       0x40   /* init or lock _mtu */
+.Ed
+.Pp
+Specifiers for which addresses are present in the messages are:
+.Bd -literal
+#define RTA_DST       0x1    /* destination sockaddr present */
+#define RTA_GATEWAY   0x2    /* gateway sockaddr present */
+#define RTA_NETMASK   0x4    /* netmask sockaddr present */
+#define RTA_GENMASK   0x8    /* cloning mask sockaddr present */
+#define RTA_IFP       0x10   /* interface name sockaddr present */
+#define RTA_IFA       0x20   /* interface addr sockaddr present */
+#define RTA_AUTHOR    0x40   /* sockaddr for author of redirect */
+.Ed
diff --git a/share/man/man4/spp.4 b/share/man/man4/spp.4
new file mode 100644
index 00000000000..71a820339b4
--- /dev/null
+++ b/share/man/man4/spp.4
@@ -0,0 +1,193 @@
+.\"	$NetBSD: spp.4,v 1.3 1994/11/30 16:22:33 jtc Exp $
+.\"
+.\" Copyright (c) 1985, 1991, 1993
+.\"	The Regents of the University of California.  All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     @(#)spp.4	8.2 (Berkeley) 4/19/94
+.\"
+.Dd April 19, 1994
+.Dt SPP 4
+.Os BSD 4.3
+.Sh NAME
+.Nm spp
+.Nd Xerox Sequenced Packet Protocol
+.Sh SYNOPSIS
+.Fd #include <sys/socket.h>
+.Fd #include <netns/ns.h>
+.Fd #include <netns/sp.h>
+.Ft int
+.Fn socket AF_NS SOCK_STREAM 0
+.Ft int
+.Fn socket AF_NS SOCK_SEQPACKET 0
+.Sh DESCRIPTION
+The
+.Tn SPP
+protocol provides reliable, flow-controlled, two-way
+transmission of data.  It is a byte-stream protocol used to
+support the
+.Dv SOCK_STREAM
+abstraction.
+.Tn SPP
+uses the standard
+.Tn NS Ns (tm)
+address formats.
+.Pp
+Sockets utilizing the
+.Tn SPP
+protocol are either
+.Dq active
+or
+.Dq passive .
+Active sockets initiate connections to passive
+sockets.  By default
+.Tn SPP
+sockets are created active; to create a
+passive socket the
+.Xr listen 2
+system call must be used
+after binding the socket with the
+.Xr bind 2
+system call.  Only
+passive sockets may use the 
+.Xr accept 2
+call to accept incoming connections.  Only active sockets may
+use the
+.Xr connect 2
+call to initiate connections.
+.Pp
+Passive sockets may
+.Dq underspecify
+their location to match
+incoming connection requests from multiple networks.  This
+technique, termed
+.Dq wildcard addressing ,
+allows a single
+server to provide service to clients on multiple networks.
+To create a socket which listens on all networks, the
+.Tn NS
+address of all zeroes must be bound.
+The
+.Tn SPP
+port may still be specified
+at this time; if the port is not specified the system will assign one.
+Once a connection has been established the socket's address is
+fixed by the peer entity's location.   The address assigned the
+socket is the address associated with the network interface
+through which packets are being transmitted and received.  Normally
+this address corresponds to the peer entity's network.
+.Pp
+If the
+.Dv SOCK_SEQPACKET
+socket type is specified,
+each packet received has the actual 12 byte sequenced packet header
+left for the user to inspect:
+.Bd -literal -offset indent
+struct sphdr {
+	u_char		sp_cc;	/* connection control */
+#define	SP_EM	0x10		/* end of message */
+	u_char		sp_dt;	/* datastream type */
+	u_short		sp_sid;
+	u_short		sp_did;
+	u_short		sp_seq;
+	u_short		sp_ack;
+	u_short		sp_alo;
+};
+.Ed
+.Pp
+This facilitates the implementation of higher level Xerox protocols
+which make use of the data stream type field and the end of message bit.
+Conversely, the user is required to supply a 12 byte header,
+the only part of which inspected is the data stream type and end of message
+fields.
+.Pp
+For either socket type,
+packets received with the Attention bit sent are interpreted as
+out of band data.  Data sent with
+.Dq send(..., ..., ..., Dv MSG_OOB )
+cause the attention bit to be set.
+.Sh DIAGNOSTICS
+A socket operation may fail with one of the following errors returned:
+.Bl -tag -width [EADDRNOTAVAIL]
+.It Bq Er EISCONN
+when trying to establish a connection on a socket which
+already has one;
+.It Bq Er ENOBUFS
+when the system runs out of memory for
+an internal data structure;
+.It Bq Er ETIMEDOUT
+when a connection was dropped
+due to excessive retransmissions;
+.It Bq Er ECONNRESET
+when the remote peer
+forces the connection to be closed;
+.It Bq Er ECONNREFUSED
+when the remote
+peer actively refuses connection establishment (usually because
+no process is listening to the port);
+.It Bq Er EADDRINUSE
+when an attempt
+is made to create a socket with a port which has already been
+allocated;
+.It Bq Er EADDRNOTAVAIL
+when an attempt is made to create a 
+socket with a network address for which no network interface
+exists.
+.El
+.Sh SOCKET OPTIONS
+.Bl -tag -width SO_DEFAULT_HEADERS
+.It Dv SO_DEFAULT_HEADERS
+when set, this determines the data stream type and whether
+the end of message bit is to be set on every ensuing packet.
+.It Dv SO_MTU
+This specifies the maximum amount of user data in a single packet.
+The default is 576 bytes - sizeof(struct spidp).  This quantity
+affects windowing \- increasing it without increasing the amount
+of buffering in the socket will lower the number of unread packets
+accepted.  Anything larger than the default will not be forwarded
+by a bona fide
+.Tn XEROX
+product internetwork router.
+The data argument for the setsockopt call must be
+an unsigned short.
+.El
+.Sh SEE ALSO
+.Xr intro 4 ,
+.Xr ns 4
+.Sh HISTORY
+The
+.Nm
+protocol appeared in
+.Bx 4.3 .
+.Sh BUGS
+There should be some way to reflect record boundaries in
+a stream.
+For stream mode, there should be an option to get the data stream type of
+the record the user process is about to receive.
diff --git a/share/man/man4/tb.4 b/share/man/man4/tb.4
new file mode 100644
index 00000000000..cb5aefe0c49
--- /dev/null
+++ b/share/man/man4/tb.4
@@ -0,0 +1,110 @@
+.\"	$NetBSD: tb.4,v 1.3 1994/12/10 08:04:57 glass Exp $
+.\"
+.\" Copyright (c) 1986, 1991 Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. 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.
+.\"
+.\"     @(#)tb.4	6.4 (Berkeley) 3/27/91
+.\"
+.Dd March 27, 1991
+.Dt TB 4
+.Os BSD 4.3
+.Sh NAME
+.Nm tb
+.Nd line discipline for digitizing devices
+.Sh SYNOPSIS
+.Cd pseudo-device tb
+.Sh DESCRIPTION
+This line discipline provides a polled interface to many common
+digitizing devices which are connected to a host through a serial line.
+When these devices stream data at high speed, the use of the
+line discipline is critical in minimizing the number of samples
+that would otherwise be lost due to buffer exhaustion in the
+.Xr tty 4
+handler.
+.Pp
+The line discipline is enabled by a sequence:
+.Bd -literal -offset indent
+#include <sys/tablet.h>
+int ldisc = TBLDISC, fildes; ...
+ioctl(fildes, TIOCSETD, &ldisc);
+.Ed
+.Pp
+A typical application program then polls the digitizing device by
+reading a binary data structure which contains: the current X and
+Y positions (in the device coordinate space),
+up-down status of the buttons or pen stylus,
+proximity information (when available), and a count
+of the number of samples received from the input device
+since it was opened.  In addition, devices such as the
+.Tn GTCO
+append tilt and pressure information to the end of
+the aforementioned structure.  For the Polhemus 3-D digitizer
+the structure read is completely different. Refer to the
+include file for a complete description.
+.Pp
+While in tablet mode, normal teletype input and output functions take place.
+Thus, if an 8 bit output data path is desired, it is necessary
+to prepare the output line by putting it into
+.Tn RAW
+mode using
+.Xr ioctl 2 .
+This must be done
+.Em before
+changing the discipline with
+.Dv TIOCSETD ,
+as most
+.Xr ioctl 2
+calls are disabled while in tablet line-discipline mode.
+.Pp
+The line discipline supports
+.Xr ioctl 2
+requests to get/set the operating mode, and to get/set the tablet type
+and operating mode by
+.Em or Ns -ing
+the two values together.
+.Pp
+The line discipline supports digitizing devices which are
+compatible with Hitachi,
+.Tn GTCO ,
+or Polhemus protocol formats.
+For Hitachi there are several formats with that used in the
+newer model
+.Tn HDG-1111B
+the most common.
+.Sh DIAGNOSTICS
+None.
+.Sh SEE ALSO
+.Xr tty 4
+.Sh HISTORY
+The
+.Nm
+interface appeared in
+.Bx 4.3 .
diff --git a/share/man/man4/tcp.4 b/share/man/man4/tcp.4
new file mode 100644
index 00000000000..62bb958d562
--- /dev/null
+++ b/share/man/man4/tcp.4
@@ -0,0 +1,180 @@
+.\"	$NetBSD: tcp.4,v 1.3 1994/11/30 16:22:35 jtc Exp $
+.\"
+.\" Copyright (c) 1983, 1991, 1993
+.\"	The Regents of the University of California.  All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     @(#)tcp.4	8.1 (Berkeley) 6/5/93
+.\"
+.Dd June 5, 1993
+.Dt TCP 4
+.Os BSD 4.2
+.Sh NAME
+.Nm tcp
+.Nd Internet Transmission Control Protocol
+.Sh SYNOPSIS
+.Fd #include <sys/socket.h>
+.Fd #include <netinet/in.h>
+.Ft int
+.Fn socket AF_INET SOCK_STREAM 0
+.Sh DESCRIPTION
+The
+.Tn TCP
+protocol provides reliable, flow-controlled, two-way
+transmission of data.  It is a byte-stream protocol used to
+support the
+.Dv SOCK_STREAM
+abstraction.  TCP uses the standard
+Internet address format and, in addition, provides a per-host
+collection of
+.Dq port addresses .
+Thus, each address is composed
+of an Internet address specifying the host and network, with
+a specific
+.Tn TCP
+port on the host identifying the peer entity.
+.Pp
+Sockets utilizing the tcp protocol are either
+.Dq active
+or
+.Dq passive .
+Active sockets initiate connections to passive
+sockets.  By default
+.Tn TCP
+sockets are created active; to create a
+passive socket the
+.Xr listen 2
+system call must be used
+after binding the socket with the
+.Xr bind 2
+system call.  Only
+passive sockets may use the 
+.Xr accept 2
+call to accept incoming connections.  Only active sockets may
+use the
+.Xr connect 2
+call to initiate connections.
+.Pp
+Passive sockets may
+.Dq underspecify
+their location to match
+incoming connection requests from multiple networks.  This
+technique, termed
+.Dq wildcard addressing ,
+allows a single
+server to provide service to clients on multiple networks.
+To create a socket which listens on all networks, the Internet
+address
+.Dv INADDR_ANY
+must be bound.  The
+.Tn TCP
+port may still be specified
+at this time; if the port is not specified the system will assign one.
+Once a connection has been established the socket's address is
+fixed by the peer entity's location.   The address assigned the
+socket is the address associated with the network interface
+through which packets are being transmitted and received.  Normally
+this address corresponds to the peer entity's network.
+.Pp
+.Tn TCP
+supports one socket option which is set with
+.Xr setsockopt 2
+and tested with
+.Xr getsockopt 2 .
+Under most circumstances,
+.Tn TCP
+sends data when it is presented;
+when outstanding data has not yet been acknowledged, it gathers
+small amounts of output to be sent in a single packet once
+an acknowledgement is received.
+For a small number of clients, such as window systems
+that send a stream of mouse events which receive no replies,
+this packetization may cause significant delays.
+Therefore,
+.Tn TCP
+provides a boolean option,
+.Dv TCP_NODELAY
+(from
+.Aq Pa netinet/tcp.h ,
+to defeat this algorithm.
+The option level for the
+.Xr setsockopt
+call is the protocol number for
+.Tn TCP ,
+available from
+.Xr getprotobyname 3 .
+.Pp
+Options at the
+.Tn IP
+transport level may be used with
+.Tn TCP ;
+see
+.Xr ip 4 .
+Incoming connection requests that are source-routed are noted,
+and the reverse source route is used in responding.
+.Sh DIAGNOSTICS
+A socket operation may fail with one of the following errors returned:
+.Bl -tag -width [EADDRNOTAVAIL]
+.It Bq Er EISCONN
+when trying to establish a connection on a socket which
+already has one;
+.It Bq Er ENOBUFS
+when the system runs out of memory for
+an internal data structure;
+.It Bq Er ETIMEDOUT
+when a connection was dropped
+due to excessive retransmissions;
+.It Bq Er ECONNRESET
+when the remote peer
+forces the connection to be closed;
+.It Bq Er ECONNREFUSED
+when the remote
+peer actively refuses connection establishment (usually because
+no process is listening to the port);
+.It Bq Er EADDRINUSE
+when an attempt
+is made to create a socket with a port which has already been
+allocated;
+.It Bq Er EADDRNOTAVAIL
+when an attempt is made to create a 
+socket with a network address for which no network interface
+exists.
+.El
+.Sh SEE ALSO
+.Xr getsockopt 2 ,
+.Xr socket 2 ,
+.Xr intro 4 ,
+.Xr inet 4 ,
+.Xr ip 4
+.Sh HISTORY
+The
+.Nm
+protocol stack appeared in
+.Bx 4.2 .
diff --git a/share/man/man4/termios.4 b/share/man/man4/termios.4
new file mode 100644
index 00000000000..c3581acf1c5
--- /dev/null
+++ b/share/man/man4/termios.4
@@ -0,0 +1,1413 @@
+.\"	$NetBSD: termios.4,v 1.5 1994/11/30 16:22:36 jtc Exp $
+.\"
+.\" Copyright (c) 1991, 1992, 1993
+.\"	The Regents of the University of California.  All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"	@(#)termios.4	8.4 (Berkeley) 4/19/94
+.\"
+.Dd April 19, 1994
+.Dt TERMIOS 4
+.Os BSD 4
+.Sh NAME
+.Nm termios
+.Nd general terminal line discipline
+.Sh SYNOPSIS
+.Fd #include <termios.h>
+.Sh DESCRIPTION
+This describes a general terminal line discipline that is
+supported on tty asynchronous communication ports.
+.Ss Opening a Terminal Device File
+When a terminal file is opened, it normally causes the process to wait
+until a connection is established.  For most hardware, the presence
+of a connection is indicated by the assertion of the hardware
+.Dv CARRIER line.
+If the termios structure associated with the terminal file has the
+.Dv CLOCAL
+flag set in the cflag, or if the
+.Dv O_NONBLOCK
+flag is set
+in the
+.Xr open 2
+call, then the open will succeed even without
+a connection being present.
+In practice, applications
+seldom open these files; they are opened by special programs, such
+as
+.Xr getty 2
+or
+.Xr rlogind 2 ,
+and become
+an application's standard input, output, and error files.
+.Ss Job Control in a Nutshell
+Every process is associated with a particular process group and session.
+The grouping is hierarchical: every member of a particular process group is a
+member of the same session.  This structuring is used in managing groups
+of related processes for purposes of
+.\" .Gw "job control" ;
+.Em "job control" ;
+that is, the
+ability from the keyboard (or from program control) to simultaneously
+stop or restart
+a complex command (a command composed of one or more related
+processes).  The grouping into process groups allows delivering
+of signals that stop or start the group as a whole, along with
+arbitrating which process group has access to the single controlling
+terminal.  The grouping at a higher layer into sessions is to restrict
+the job control related signals and system calls to within processes
+resulting from a particular instance of a "login".  Typically, a session
+is created when a user logs in, and the login terminal is setup
+to be the controlling terminal; all processes spawned from that
+login shell are in the same session, and inherit the controlling
+terminal.
+A job control shell
+operating interactively (that is, reading commands from a terminal)
+normally groups related processes together by placing them into the
+same process group.  A set of processes in the same process group
+is collectively referred to as a "job". When the foreground process
+group of the terminal is the same as the process group of a particular
+job, that job is said to be in the "foreground".  When the process
+group of the terminal is different than the process group of
+a job (but is still the controlling terminal), that job is said
+to be in the "background".  Normally the
+shell reads a command and starts the job that implements that
+command.  If the command is to be started in the foreground (typical), it
+sets the process group of the terminal to the process group
+of the started job, waits for the job to complete, and then
+sets the process group of the terminal back to its own process
+group (it puts itself into the foreground).  If the job is to
+be started in the background (as denoted by the shell operator "&"),
+it never changes the process group of the terminal and doesn't
+wait for the job to complete (that is, it immediately attempts to read the next
+command).  If the job is started in the foreground, the user may
+type a key (usually
+.Ql \&^Z )
+which generates the terminal stop signal
+.Pq Dv SIGTSTP
+and has the affect of stopping the entire job.
+The shell will notice that the job stopped, and will resume running after
+placing itself in the foreground.
+The shell also has commands for placing stopped jobs in the background,
+and for placing stopped or background jobs into the foreground.
+.Ss Orphaned Process Groups
+An orphaned process group is a process group that has no process
+whose parent is in a different process group, yet is in the same
+session.  Conceptually it means a process group that doesn't have
+a parent that could do anything if it were to be stopped.  For example,
+the initial login shell is typically in an orphaned process group.
+Orphaned process groups are immune to keyboard generated stop
+signals and job control signals resulting from reads or writes to the
+controlling terminal.
+.Ss The Controlling Terminal
+A terminal may belong to a process as its controlling terminal.  Each
+process of a session that has a controlling terminal has the same
+controlling terminal.  A terminal may be the controlling terminal for at
+most one session.  The controlling terminal for a session is allocated by
+the session leader by issuing the
+.Dv TIOCSCTTY
+ioctl.  A controlling terminal
+is never acquired by merely opening a terminal device file.
+When a controlling terminal becomes
+associated with a session, its foreground process group is set to
+the process group of the session leader.
+.Pp
+The controlling terminal is inherited by a child process during a
+.Xr fork 2
+function call.  A process relinquishes its controlling terminal when it
+creates a new session with the
+.Xr setsid 2
+function; other processes
+remaining in the old session that had this terminal as their controlling
+terminal continue to have it.
+A process does not relinquish its
+controlling terminal simply by closing all of its file descriptors
+associated with the controlling terminal if other processes continue to
+have it open.
+.Pp
+When a controlling process terminates, the controlling terminal is
+disassociated from the current session, allowing it to be acquired by a
+new session leader.  Subsequent access to the terminal by other processes
+in the earlier session will be denied, with attempts to access the
+terminal treated as if modem disconnect had been sensed.
+.Ss Terminal Access Control
+If a process is in the foreground process group of its controlling
+terminal, read operations are allowed.
+Any attempts by a process
+in a background process group to read from its controlling terminal
+causes a
+.Dv SIGTTIN
+signal to be sent to
+the process's group
+unless one of the
+following special cases apply:  If the reading process is ignoring or
+blocking the
+.Dv SIGTTIN signal, or if the process group of the reading
+process is orphaned, the
+.Xr read 2
+returns -1 with
+.Va errno set to
+.Er Dv EIO
+and no
+signal is sent.  The default action of the
+.Dv SIGTTIN
+signal is to stop the
+process to which it is sent.
+.Pp
+If a process is in the foreground process group of its controlling
+terminal, write operations are allowed.
+Attempts by a process in a background process group to write to its
+controlling terminal will cause the process group to be sent a
+.Dv SIGTTOU
+signal unless one of the following special cases apply:  If
+.Dv TOSTOP
+is not
+set, or if
+.Dv TOSTOP
+is set and the process is ignoring or blocking the
+.Dv SIGTTOU
+signal, the process is allowed to write to the terminal and the
+.Dv SIGTTOU
+signal is not sent.  If
+.Dv TOSTOP
+is set, and the process group of
+the writing process is orphaned, and the writing process is not ignoring
+or blocking
+.Dv SIGTTOU ,
+the
+.Xr write
+returns -1 with
+errno set to
+.Er Dv EIO
+and no signal is sent.
+.Pp
+Certain calls that set terminal parameters are treated in the same
+fashion as write, except that
+.Dv TOSTOP
+is ignored; that is, the effect is
+identical to that of terminal writes when
+.Dv TOSTOP
+is set.
+.Ss Input Processing and Reading Data
+A terminal device associated with a terminal device file may operate in
+full-duplex mode, so that data may arrive even while output is occurring.
+Each terminal device file has associated with it an input queue, into
+which incoming data is stored by the system before being read by a
+process.  The system imposes a limit,
+.Pf \&{ Dv MAX_INPUT Ns \&} ,
+on the number of
+bytes that may be stored in the input queue.  The behavior of the system
+when this limit is exceeded depends on the setting of the
+.Dv IMAXBEL
+flag in the termios
+.Fa c_iflag .
+If this flag is set, the terminal
+is sent an
+.Tn ASCII
+.Dv BEL
+character each time a character is received
+while the input queue is full.  Otherwise, the input queue is flushed
+upon receiving the character.
+.Pp
+Two general kinds of input processing are available, determined by
+whether the terminal device file is in canonical mode or noncanonical
+mode. Additionally,
+input characters are processed according to the
+.Fa c_iflag
+and
+.Fa c_lflag
+fields.  Such processing can include echoing, which
+in general means transmitting input characters immediately back to the
+terminal when they are received from the terminal.  This is useful for
+terminals that can operate in full-duplex mode.
+.Pp
+The manner in which data is provided to a process reading from a terminal
+device file is dependent on whether the terminal device file is in
+canonical or noncanonical mode.
+.Pp
+Another dependency is whether the
+.Dv O_NONBLOCK
+flag is set by
+.Xr open()
+or
+.Xr fcntl() .
+If the
+.Dv O_NONBLOCK
+flag is clear, then the read request is
+blocked until data is available or a signal has been received.  If the
+.Dv O_NONBLOCK
+flag is set, then the read request is completed, without
+blocking, in one of three ways:
+.Bl -enum -offset indent
+.It
+If there is enough data available to satisfy the entire request,
+and the read completes successfully the number of
+bytes read is returned.
+.It
+If there is not enough data available to satisfy the entire
+request, and the read completes successfully, having read as
+much data as possible, the number of bytes read is returned.
+.It
+If there is no data available, the read returns -1, with
+errno set to
+.Er EAGAIN .
+.El
+.Pp
+When data is available depends on whether the input processing mode is
+canonical or noncanonical.
+.Ss Canonical Mode Input Processing
+In canonical mode input processing, terminal input is processed in units
+of lines.  A line is delimited by a newline
+.Ql \&\en
+character, an end-of-file
+.Pq Dv EOF
+character, or an end-of-line
+.Pq Dv EOL
+character.  See the
+.Sx "Special Characters"
+section for
+more information on
+.Dv EOF
+and
+.Dv EOL .
+This means that a read request will
+not return until an entire line has been typed, or a signal has been
+received.  Also, no matter how many bytes are requested in the read call,
+at most one line is returned.  It is not, however, necessary to
+read a whole line at once; any number of bytes, even one, may be
+requested in a read without losing information.
+.Pp
+.Pf \&{ Dv MAX_CANON Ns \&}
+is a limit on the
+number of bytes in a line.
+The behavior of the system when this limit is
+exceeded is the same as when the input queue limit
+.Pf \&{ Dv MAX_INPUT Ns \&} ,
+is exceeded.
+.Pp
+Erase and kill processing occur when either of two special characters,
+the
+.Dv ERASE
+and
+.Dv KILL
+characters (see the
+.Sx "Special Characters section" ) ,
+is received.
+This processing affects data in the input queue that has not yet been
+delimited by a newline
+.Dv NL,
+.Dv EOF ,
+or
+.Dv EOL
+character.  This un-delimited
+data makes up the current line.  The
+.Dv ERASE
+character deletes the last
+character in the current line, if there is any.  The
+.Dv KILL
+character
+deletes all data in the current line, if there is any.  The
+.Dv ERASE
+and
+.Dv KILL
+characters have no effect if there is no data in the current line.
+The
+.Dv ERASE
+and
+.Dv KILL
+characters themselves are not placed in the input
+queue.
+.Ss Noncanonical Mode Input Processing
+In noncanonical mode input processing, input bytes are not assembled into
+lines, and erase and kill processing does not occur.  The values of the
+.Dv MIN
+and
+.Dv TIME
+members of the
+.Fa c_cc
+array are used to determine how to
+process the bytes received.
+.Pp
+.Dv MIN
+represents the minimum number of bytes that should be received when
+the
+.Xr read
+function successfully returns.
+.Dv TIME
+is a timer of 0.1 second
+granularity that is used to time out bursty and short term data
+transmissions.  If
+.Dv MIN
+is greater than
+.Dv \&{ Dv MAX_INPUT Ns \&} ,
+the response to the
+request is undefined.  The four possible values for
+.Dv MIN
+and
+.Dv TIME
+and
+their interactions are described below.
+.Ss "Case A: MIN > 0, TIME > 0"
+In this case
+.Dv TIME
+serves as an inter-byte timer and is activated after
+the first byte is received.  Since it is an inter-byte timer, it is reset
+after a byte is received.  The interaction between
+.Dv MIN
+and
+.Dv TIME
+is as
+follows:  as soon as one byte is received, the inter-byte timer is
+started.  If
+.Dv MIN
+bytes are received before the inter-byte timer expires
+(remember that the timer is reset upon receipt of each byte), the read is
+satisfied.  If the timer expires before
+.Dv MIN
+bytes are received, the
+characters received to that point are returned to the user.  Note that if
+.Dv TIME
+expires at least one byte is returned because the timer would
+not have been enabled unless a byte was received.  In this case
+.Pf \&( Dv MIN
+> 0,
+.Dv TIME
+> 0) the read blocks until the
+.Dv MIN
+and
+.Dv TIME
+mechanisms are
+activated by the receipt of the first byte, or a signal is received.  If
+data is in the buffer at the time of the read(), the result is as
+if data had been received immediately after the read().
+.Ss "Case B: MIN > 0, TIME = 0"
+In this case, since the value of
+.Dv TIME
+is zero, the timer plays no role
+and only
+.Dv MIN
+is significant.  A pending read is not satisfied until
+.Dv MIN
+bytes are received (i.e., the pending read blocks until
+.Dv MIN
+bytes
+are received), or a signal is received.  A program that uses this case to
+read record-based terminal
+.Dv I/O
+may block indefinitely in the read
+operation.
+.Ss "Case C: MIN = 0, TIME > 0"
+In this case, since
+.Dv MIN
+= 0,
+.Dv TIME
+no longer represents an inter-byte
+timer.  It now serves as a read timer that is activated as soon as the
+read function is processed.  A read is satisfied as soon as a single
+byte is received or the read timer expires.  Note that in this case if
+the timer expires, no bytes are returned.  If the timer does not
+expire, the only way the read can be satisfied is if a byte is received.
+In this case the read will not block indefinitely waiting for a byte; if
+no byte is received within
+.Dv TIME Ns *0.1
+seconds after the read is initiated,
+the read returns a value of zero, having read no data.  If data is
+in the buffer at the time of the read, the timer is started as if
+data had been received immediately after the read.
+.Ss Case D: MIN = 0, TIME = 0
+The minimum of either the number of bytes requested or the number of
+bytes currently available is returned without waiting for more
+bytes to be input.  If no characters are available, read returns a
+value of zero, having read no data.
+.Ss Writing Data and Output Processing
+When a process writes one or more bytes to a terminal device file, they
+are processed according to the
+.Fa c_oflag
+field (see the
+.Sx "Output Modes
+section).  The
+implementation may provide a buffering mechanism; as such, when a call to
+write() completes, all of the bytes written have been scheduled for
+transmission to the device, but the transmission will not necessarily
+have been completed.
+.\" See also .Sx "6.4.2" for the effects of
+.\" .Dv O_NONBLOCK
+.\" on write.
+.Ss Special Characters
+Certain characters have special functions on input or output or both.
+These functions are summarized as follows:
+.Bl -tag -width indent
+.It Dv INTR
+Special character on input and is recognized if the
+.Dv ISIG
+flag (see the
+.Sx "Local Modes"
+section) is enabled.  Generates a
+.Dv SIGINT
+signal which is sent to all processes in the foreground
+process group for which the terminal is the controlling
+terminal.  If
+.Dv ISIG
+is set, the
+.Dv INTR
+character is
+discarded when processed.
+.It Dv QUIT
+Special character on input and is recognized if the
+.Dv ISIG
+flag is enabled.  Generates a
+.Dv SIGQUIT
+signal which is
+sent to all processes in the foreground process group
+for which the terminal is the controlling terminal.  If
+.Dv ISIG
+is set, the
+.Dv QUIT
+character is discarded when
+processed.
+.It Dv ERASE
+Special character on input and is recognized if the
+.Dv ICANON
+flag is set.  Erases the last character in the
+current line; see
+.Sx "Canonical Mode Input Processing" .
+It does not erase beyond
+the start of a line, as delimited by an
+.Dv NL ,
+.Dv EOF ,
+or
+.Dv EOL
+character.  If
+.Dv ICANON
+is set, the
+.Dv ERASE
+character is
+discarded when processed.
+.It Dv KILL
+Special character on input and is recognized if the
+.Dv ICANON
+flag is set.  Deletes the entire line, as
+delimited by a
+.Dv NL ,
+.Dv EOF ,
+or
+.Dv EOL
+character.  If
+.Dv ICANON
+is set, the
+.Dv KILL
+character is discarded when processed.
+.It Dv EOF
+Special character on input and is recognized if the
+.Dv ICANON
+flag is set.  When received, all the bytes
+waiting to be read are immediately passed to the
+process, without waiting for a newline, and the
+.Dv EOF
+is discarded.  Thus, if there are no bytes waiting (that
+is, the
+.Dv EOF
+occurred at the beginning of a line), a byte
+count of zero is returned from the read(),
+representing an end-of-file indication.  If
+.Dv ICANON
+is
+set, the
+.Dv EOF
+character is discarded when processed.
+.Dv NL
+Special character on input and is recognized if the
+.Dv ICANON
+flag is set.  It is the line delimiter
+.Ql \&\en .
+.It Dv EOL
+Special character on input and is recognized if the
+.Dv ICANON
+flag is set.  Is an additional line delimiter,
+like
+.Dv NL .
+.It Dv SUSP
+If the
+.Dv ISIG
+flag is enabled, receipt of the
+.Dv SUSP
+character causes a
+.Dv SIGTSTP
+signal to be sent to all processes in the
+foreground process group for which the terminal is the
+controlling terminal, and the
+.Dv SUSP
+character is
+discarded when processed.
+.It Dv STOP
+Special character on both input and output and is
+recognized if the
+.Dv IXON
+(output control) or
+.Dv IXOFF
+(input
+control) flag is set.  Can be used to temporarily
+suspend output.  It is useful with fast terminals to
+prevent output from disappearing before it can be read.
+If
+.Dv IXON
+is set, the
+.Dv STOP
+character is discarded when
+processed.
+.It Dv START
+Special character on both input and output and is
+recognized if the
+.Dv IXON
+(output control) or
+.Dv IXOFF
+(input
+control) flag is set.  Can be used to resume output that
+has been suspended by a
+.Dv STOP
+character.  If
+.Dv IXON
+is set, the
+.Dv START
+character is discarded when processed.
+.Dv CR
+Special character on input and is recognized if the
+.Dv ICANON
+flag is set; it is the
+.Ql \&\er ,
+as denoted in the
+.Tn \&C
+Standard {2}.  When
+.Dv ICANON
+and
+.Dv ICRNL
+are set and
+.Dv IGNCR
+is not set, this character is translated into a
+.Dv NL ,
+and
+has the same effect as a
+.Dv NL
+character.
+.El
+.Pp
+The following special characters are extensions defined by this
+system and are not a part of 1003.1 termios.
+.Bl -tag -width indent
+.It Dv EOL2
+Secondary
+.Dv EOL
+character.  Same function as
+.Dv EOL.
+.It Dv WERASE
+Special character on input and is recognized if the
+.Dv ICANON
+flag is set.  Erases the last word in the current
+line according to one of two algorithms.  If the
+.Dv ALTWERASE
+flag is not set, first any preceding whitespace is
+erased, and then the maximal sequence of non-whitespace
+characters.  If
+.Dv ALTWERASE
+is set, first any preceding
+whitespace is erased, and then the maximal sequence
+of alphabetic/underscores or non alphabetic/underscores.
+As a special case in this second algorithm, the first previous
+non-whitespace character is skipped in determining
+whether the preceding word is a sequence of
+alphabetic/undercores.  This sounds confusing but turns
+out to be quite practical.
+.It Dv REPRINT
+Special character on input and is recognized if the
+.Dv ICANON
+flag is set.  Causes the current input edit line
+to be retyped.
+.It Dv DSUSP
+Has similar actions to the
+.Dv SUSP
+character, except that
+the
+.Dv SIGTSTP
+signal is delivered when one of the processes
+in the foreground process group issues a read() to the
+controlling terminal.
+.It Dv LNEXT
+Special character on input and is recognized if the
+.Dv IEXTEN
+flag is set.  Receipt of this character causes the next
+character to be taken literally.
+.It Dv DISCARD
+Special character on input and is recognized if the
+.Dv IEXTEN
+flag is set.  Receipt of this character toggles the flushing
+of terminal output.
+.It Dv STATUS
+Special character on input and is recognized if the
+.Dv ICANON
+flag is set.  Receipt of this character causes a
+.Dv SIGINFO
+signal to be sent to the foreground process group of the
+terminal.  Also, if the
+.Dv NOKERNINFO
+flag is not set, it
+causes the kernel to write a status message to the terminal
+that displays the current load average, the name of the
+command in the foreground, its process ID, the symbolic
+wait channel, the number of user and system seconds used,
+the percentage of cpu the process is getting, and the resident
+set size of the process.
+.El
+.Pp
+The
+.Dv NL
+and
+.Dv CR
+characters cannot be changed.
+The values for all the remaining characters can be set and are
+described later in the document under
+Special Control Characters.
+.Pp
+Special
+character functions associated with changeable special control characters
+can be disabled individually by setting their value to
+.Dv {_POSIX_VDISABLE};
+see
+.Sx "Special Control Characters" .
+.Pp
+If two or more special characters have the same value, the function
+performed when that character is received is undefined.
+.Ss Modem Disconnect
+If a modem disconnect is detected by the terminal interface for a
+controlling terminal, and if
+.Dv CLOCAL
+is not set in the
+.Fa c_cflag
+field for
+the terminal, the
+.Dv SIGHUP
+signal is sent to the controlling
+process associated with the terminal.  Unless other arrangements have
+been made, this causes the controlling process to terminate.
+Any subsequent call to the read() function returns the value zero,
+indicating end of file.  Thus, processes that read a terminal
+file and test for end-of-file can terminate appropriately after a
+disconnect.
+.\" If the
+.\" .Er EIO
+.\" condition specified in 6.1.1.4 that applies
+.\" when the implementation supports job control also exists, it is
+.\" unspecified whether the
+.\" .Dv EOF
+.\" condition or the
+.\" .Pf [ Dv EIO
+.\" ] is returned.
+Any
+subsequent write() to the terminal device returns -1, with
+.Va errno
+set to
+.Er EIO ,
+until the device is closed.
+.Sh General Terminal Interface
+.Pp
+.Ss Closing a Terminal Device File
+The last process to close a terminal device file causes any output
+to be sent to the device and any input to be discarded.  Then, if
+.Dv HUPCL
+is set in the control modes, and the communications port supports a
+disconnect function, the terminal device performs a disconnect.
+.Ss Parameters That Can Be Set
+Routines that need to control certain terminal
+.Tn I/O
+characteristics
+do so by using the termios structure as defined in the header
+.Aq Pa termios.h .
+This structure contains minimally four scalar elements of bit flags
+and one array of special characters.  The scalar flag elements are
+named:
+.Fa c_iflag ,
+.Fa c_oflag ,
+.Fa c_cflag ,
+and
+.Fa c_lflag .
+The character array is named
+.Fa c_cc ,
+and its maximum index is
+.Dv NCCS .
+.Ss Input Modes
+Values of the
+.Fa c_iflag
+field describe the basic
+terminal input control, and are composed of
+following masks:
+.Pp
+.Bl -tag -width IMAXBEL -offset indent -compact
+.It Dv IGNBRK
+/* ignore BREAK condition */
+.It Dv BRKINT
+/* map BREAK to SIGINTR */
+.It Dv IGNPAR
+/* ignore (discard) parity errors */
+.It Dv PARMRK
+/* mark parity and framing errors */
+.It Dv INPCK
+/* enable checking of parity errors */
+.It Dv ISTRIP
+/* strip 8th bit off chars */
+.It Dv INLCR
+/* map NL into CR */
+.It Dv IGNCR
+/* ignore CR */
+.It Dv ICRNL
+/* map CR to NL (ala CRMOD) */
+.It Dv IXON
+/* enable output flow control */
+.It Dv IXOFF
+/* enable input flow control */
+.It Dv IXANY
+/* any char will restart after stop */
+.It Dv IMAXBEL
+/* ring bell on input queue full */
+.El
+.Pp
+In the context of asynchronous serial data transmission, a break
+condition is defined as a sequence of zero-valued bits that continues for
+more than the time to send one byte.  The entire sequence of zero-valued
+bits is interpreted as a single break condition, even if it continues for
+a time equivalent to more than one byte.  In contexts other than
+asynchronous serial data transmission the definition of a break condition
+is implementation defined.
+.Pp
+If
+.Dv IGNBRK
+is set, a break condition detected on input is ignored, that
+is, not put on the input queue and therefore not read by any process.  If
+.Dv IGNBRK
+is not set and
+.Dv BRKINT
+is set, the break condition flushes the
+input and output queues and if the terminal is the controlling terminal
+of a foreground process group, the break condition generates a
+single
+.Dv SIGINT
+signal to that foreground process group.  If neither
+.Dv IGNBRK
+nor
+.Dv BRKINT
+is set, a break condition is read as a single
+.Ql \&\e0 ,
+or if
+.Dv PARMRK
+is set, as
+.Ql \&\e377 ,
+.Ql \&\e0 ,
+.Ql \&\e0 .
+.Pp
+If
+.Dv IGNPAR
+is set, a byte with a framing or parity error (other than
+break) is ignored.
+.Pp
+If
+.Dv PARMRK
+is set, and
+.Dv IGNPAR
+is not set, a byte with a framing or parity
+error (other than break) is given to the application as the
+three-character sequence
+.Ql \&\e377 ,
+.Ql \&\e0 ,
+X, where
+.Ql \&\e377 ,
+.Ql \&\e0
+is a two-character
+flag preceding each sequence and X is the data of the character received
+in error.  To avoid ambiguity in this case, if
+.Dv ISTRIP
+is not set, a valid
+character of
+.Ql \&\e377
+is given to the application as
+.Ql \&\e377 ,
+.Ql \&\e377 .
+If
+neither
+.Dv PARMRK
+nor
+.Dv IGNPAR
+is set, a framing or parity error (other than
+break) is given to the application as a single character
+.Ql \&\e0 .
+.Pp
+If
+.Dv INPCK
+is set, input parity checking is enabled.  If
+.Dv INPCK
+is not set,
+input parity checking is disabled, allowing output parity generation
+without input parity errors.  Note that whether input parity checking is
+enabled or disabled is independent of whether parity detection is enabled
+or disabled (see
+.Sx "Control Modes" ) .
+If parity detection is enabled but input
+parity checking is disabled, the hardware to which the terminal is
+connected recognizes the parity bit, but the terminal special file
+does not check whether this bit is set correctly or not.
+.Pp
+If
+.Dv ISTRIP
+is set, valid input bytes are first stripped to seven bits,
+otherwise all eight bits are processed.
+.Pp
+If
+.Dv INLCR
+is set, a received
+.Dv NL
+character is translated into a
+.Dv CR
+character.  If
+.Dv IGNCR
+is set, a received
+.Dv CR
+character is ignored (not
+read).  If
+.Dv IGNCR
+is not set and
+.Dv ICRNL
+is set, a received
+.Dv CR
+character is
+translated into a
+.Dv NL
+character.
+.Pp
+If
+.Dv IXON
+is set, start/stop output control is enabled.  A received
+.Dv STOP
+character suspends output and a received
+.Dv START
+character
+restarts output. If
+.Dv IXANY
+is also set, then any character may
+restart output. When
+.Dv IXON
+is set,
+.Dv START
+and
+.Dv STOP
+characters are not
+read, but merely perform flow control functions.  When
+.Dv IXON
+is not set,
+the
+.Dv START
+and
+.Dv STOP
+characters are read.
+.Pp
+If
+.Dv IXOFF
+is set, start/stop input control is enabled.  The system shall
+transmit one or more
+.Dv STOP
+characters, which are intended to cause the
+terminal device to stop transmitting data, as needed to prevent the input
+queue from overflowing and causing the undefined behavior described in
+.Sx "Input Processing and Reading Data" ,
+and shall transmit one or more
+.Dv START
+characters, which are
+intended to cause the terminal device to resume transmitting data, as
+soon as the device can continue transmitting data without risk of
+overflowing the input queue.  The precise conditions under which
+.Dv STOP
+and
+START
+characters are transmitted are implementation defined.
+.Pp
+If
+.Dv IMAXBEL
+is set and the input queue is full, subsequent input shall cause an
+.Tn ASCII
+.Dv BEL
+character to be transmitted to the
+the output queue.
+.Pp
+The initial input control value after open() is implementation defined.
+.Ss Output Modes
+Values of the
+.Fa c_oflag
+field describe the basic terminal output control,
+and are composed of the following masks:
+.Pp
+.Bl -tag -width OXTABS -offset indent -compact
+.It Dv OPOST
+/* enable following output processing */
+.It Dv ONLCR
+/* map NL to CR-NL (ala
+.Dv CRMOD)
+*/
+.It Dv OXTABS
+/* expand tabs to spaces */
+.It Dv ONOEOT
+/* discard
+.Dv EOT Ns 's
+.Ql \&^D
+on output) */
+.El
+.Pp
+If
+.Dv OPOST
+is set, the remaining flag masks are interpreted as follows;
+otherwise characters are transmitted without change.
+.Pp
+If
+.Dv ONLCR
+is set, newlines are translated to carriage return, linefeeds.
+.Pp
+If
+.Dv OXTABS
+is set, tabs are expanded to the appropriate number of
+spaces (assuming 8 column tab stops).
+.Pp
+If
+.Dv ONOEOT
+is set,
+.Tn ASCII
+.Dv EOT NS 's
+are discarded on output.
+.Ss Control Modes
+Values of the
+.Fa c_cflag
+field describe the basic
+terminal hardware control, and are composed of the
+following masks.
+Not all values
+specified are supported by all hardware.
+.Pp
+.Bl -tag -width CRTSXIFLOW -offset indent -compact
+.It Dv CSIZE
+/* character size mask */
+.It Dv CS5
+/* 5 bits (pseudo) */
+.It Dv CS6
+/* 6 bits */
+.It Dv CS7
+/* 7 bits */
+.It Dv CS8
+/* 8 bits */
+.It Dv CSTOPB
+/* send 2 stop bits */
+.It Dv CREAD
+/* enable receiver */
+.It Dv PARENB
+/* parity enable */
+.It Dv PARODD
+/* odd parity, else even */
+.It Dv HUPCL
+/* hang up on last close */
+.It Dv CLOCAL
+/* ignore modem status lines */
+.It Dv CCTS_OFLOW
+/*
+.Dv CTS
+flow control of output */
+.It Dv CRTSCTS
+/* same as
+.Dv CCTS_OFLOW
+*/
+.It Dv CRTS_IFLOW
+/* RTS flow control of input */
+.It Dv MDMBUF
+/* flow control output via Carrier */
+.El
+.Pp
+The
+.Dv CSIZE
+bits specify the byte size in bits for both transmission and
+reception.  The
+.Fa c_cflag
+is masked with
+.Dv CSIZE
+and compared with the
+values
+.Dv CS5 ,
+.Dv CS6 ,
+.Dv CS7 ,
+or
+.Dv CS8 .
+This size does not include the parity bit, if any.  If
+.Dv CSTOPB
+is set, two stop bits are used, otherwise one stop bit.  For example, at
+110 baud, two stop bits are normally used.
+.Pp
+If
+.Dv CREAD
+is set, the receiver is enabled.  Otherwise, no character is
+received. 
+Not all hardware supports this bit.  In fact, this flag
+is pretty silly and if it were not part of the
+.Nm termios
+specification
+it would be omitted.
+.Pp
+If
+.Dv PARENB
+is set, parity generation and detection are enabled and a parity
+bit is added to each character.  If parity is enabled,
+.Dv PARODD
+specifies
+odd parity if set, otherwise even parity is used.
+.Pp
+If
+.Dv HUPCL
+is set, the modem control lines for the port are lowered
+when the last process with the port open closes the port or the process
+terminates.  The modem connection is broken.
+.Pp
+If
+.Dv CLOCAL
+is set, a connection does not depend on the state of the modem
+status lines.  If
+.Dv CLOCAL
+is clear, the modem status lines are
+monitored.
+.Pp
+Under normal circumstances, a call to the open() function waits for
+the modem connection to complete.  However, if the
+.Dv O_NONBLOCK
+flag is set
+or if
+.Dv CLOCAL
+has been set, the open() function returns
+immediately without waiting for the connection.
+.Pp
+The
+.Dv CCTS_OFLOW
+.Pf ( Dv CRTSCTS )
+flag is currently unused.
+.Pp
+If
+.Dv MDMBUF
+is set then output flow control is controlled by the state
+of Carrier Detect.
+.Pp
+If the object for which the control modes are set is not an asynchronous
+serial connection, some of the modes may be ignored; for example, if an
+attempt is made to set the baud rate on a network connection to a
+terminal on another host, the baud rate may or may not be set on the
+connection between that terminal and the machine it is directly connected
+to.
+.Ss Local Modes
+Values of the
+.Fa c_lflag
+field describe the control of
+various functions, and are composed of the following
+masks.
+.Pp
+.Bl -tag -width NOKERNINFO -offset indent -compact
+.It Dv ECHOKE
+/* visual erase for line kill */
+.It Dv ECHOE
+/* visually erase chars */
+.It Dv ECHO
+/* enable echoing */
+.It Dv ECHONL
+/* echo
+.Dv NL
+even if
+.Dv ECHO
+is off */
+.It Dv ECHOPRT
+/* visual erase mode for hardcopy */
+.It Dv ECHOCTL
+/* echo control chars as ^(Char) */
+.It Dv ISIG
+/* enable signals
+.Dv INTR ,
+.Dv QUIT ,
+.Dv [D]SUSP
+*/
+.It Dv ICANON
+/* canonicalize input lines */
+.It Dv ALTWERASE
+/* use alternate
+.Dv WERASE
+algorithm */
+.It Dv IEXTEN
+/* enable
+.Dv DISCARD
+and
+.Dv LNEXT
+*/
+.It Dv EXTPROC
+/* external processing */
+.It Dv TOSTOP
+/* stop background jobs from output */
+.It Dv FLUSHO
+/* output being flushed (state) */
+.It Dv NOKERNINFO
+/* no kernel output from
+.Dv VSTATUS
+*/
+.It Dv PENDIN
+/* XXX retype pending input (state) */
+.It Dv NOFLSH
+/* don't flush after interrupt */
+.El
+.Pp
+If
+.Dv ECHO
+is set, input characters are echoed back to the terminal.  If
+.Dv ECHO
+is not set, input characters are not echoed.
+.Pp
+If
+.Dv ECHOE
+and
+.Dv ICANON
+are set, the
+.Dv ERASE
+character causes the terminal
+to erase the last character in the current line from the display, if
+possible.  If there is no character to erase, an implementation may echo
+an indication that this was the case or do nothing.
+.Pp
+If
+.Dv ECHOK
+and
+.Dv ICANON
+are set, the
+.Dv KILL
+character causes
+the current line to be discarded and the system echoes the
+.Ql \&\en
+character after the
+.Dv KILL
+character.
+.Pp
+If
+.Dv ECHOKE
+and
+.Dv ICANON
+are set, the
+.Dv KILL
+character causes
+the current line to be discarded and the system causes
+the terminal
+to erase the line from the display.
+.Pp
+If
+.Dv ECHOPRT
+and
+.Dv ICANON
+are set, the system assumes
+that the display is a printing device and prints a
+backslash and the erased characters when processing
+.Dv ERASE
+characters, followed by a forward slash.
+.Pp
+If
+.Dv ECHOCTL
+is set, the system echoes control characters
+in a visible fashion using a caret followed by the control character.
+.Pp
+If
+.Dv ALTWERASE
+is set, the system uses an alternative algorithm
+for determining what constitutes a word when processing
+.Dv WERASE
+characters (see
+.Dv WERASE ) .
+.Pp
+If
+.Dv ECHONL
+and
+.Dv ICANON
+are set, the
+.Ql \&\en
+character echoes even if
+.Dv ECHO
+is not set.
+.Pp
+If
+.Dv ICANON
+is set, canonical processing is enabled.  This enables the
+erase and kill edit functions, and the assembly of input characters into
+lines delimited by
+.Dv NL,
+.Dv EOF ,
+and
+.Dv EOL,
+as described in
+.Sx "Canonical Mode Input Processing" .
+.Pp
+If
+.Dv ICANON
+is not set, read requests are satisfied directly from the input
+queue.  A read is not satisfied until at least
+.Dv MIN
+bytes have been
+received or the timeout value
+.Dv TIME
+expired between bytes.  The time value
+represents tenths of seconds.  See
+.Sx "Noncanonical Mode Input Processing"
+for more details.
+.Pp
+If
+.Dv ISIG
+is set, each input character is checked against the special
+control characters
+.Dv INTR ,
+.Dv QUIT ,
+and
+.Dv SUSP
+(job control only).  If an input
+character matches one of these control characters, the function
+associated with that character is performed.  If
+.Dv ISIG
+is not set, no
+checking is done.  Thus these special input functions are possible only
+if
+.Dv ISIG
+is set.
+.Pp
+If
+.Dv IEXTEN
+is set, implementation-defined functions are recognized
+from the input data.  How
+.Dv IEXTEN
+being set
+interacts with
+.Dv ICANON ,
+.Dv ISIG ,
+.Dv IXON ,
+or
+.Dv IXOFF
+is implementation defined.
+If
+.Dv IEXTEN
+is not set, then
+implementation-defined functions are not recognized, and the
+corresponding input characters are not processed as described for
+.Dv ICANON ,
+.Dv ISIG ,
+.Dv IXON ,
+and
+.Dv IXOFF .
+.Pp
+If
+.Dv NOFLSH
+is set, the normal flush of the input and output queues
+associated with the
+.Dv INTR ,
+.Dv QUIT ,
+and
+.Dv SUSP
+characters
+are not be done.
+.Pp
+If
+.Dv TOSTOP
+is set, the signal
+.Dv SIGTTOU
+is sent to the process group of a process that tries to write to
+its controlling terminal if it is not in the foreground process group for
+that terminal.  This signal, by default, stops the members of the process
+group.  Otherwise, the output generated by that process is output to the
+current output stream.  Processes that are blocking or ignoring
+.Dv SIGTTOU
+signals are excepted and allowed to produce output and the
+.Dv SIGTTOU
+signal
+is not sent.
+.Pp
+If
+.Dv NOKERNINFO
+is set, the kernel does not produce a status message
+when processing
+.Dv STATUS
+characters (see
+.Dv STATUS ) .
+.Ss Special Control Characters
+The special control characters values are defined by the array
+.Fa c_cc .
+This table lists the array index, the corresponding special character,
+and the system default value.  For an accurate list of
+the system defaults, consult the header file
+.Aq Pa ttydefaults.h .
+.Pp
+.Bl -column "Index Name" "Special Character" -offset indent -compact
+.It Em "Index Name	Special Character	Default Value"
+.It Dv VEOF Ta EOF Ta \&^D
+.It Dv VEOL Ta EOL Ta _POSIX_VDISABLE
+.It Dv VEOL2 Ta EOL2 Ta _POSIX_VDISABLE
+.It Dv VERASE Ta ERASE Ta \&^? Ql \&\e177
+.It Dv VWERASE  Ta WERASE Ta \&^W
+.It Dv VKILL Ta KILL Ta \&^U
+.It Dv VREPRINT Ta REPRINT Ta \&^R
+.It Dv VINTR Ta INTR Ta \&^C
+.It Dv VQUIT Ta QUIT Ta \&^\e\e Ql \&\e34
+.It Dv VSUSP Ta SUSP Ta \&^Z
+.It Dv VDSUSP Ta DSUSP Ta \&^Y
+.It Dv VSTART Ta START Ta \&^Q
+.It Dv VSTOP Ta STOP Ta \&^S
+.It Dv VLNEXT Ta LNEXT Ta \&^V
+.It Dv VDISCARD Ta DISCARD Ta \&^O
+.It Dv VMIN Ta --- Ta \&1
+.It Dv VTIME Ta --- Ta \&0
+.It Dv VSTATUS Ta STATUS Ta \&^T
+.El
+.Pp
+If the
+value of one of the changeable special control characters (see
+.Sx "Special Characters" )
+is
+.Dv {_POSIX_VDISABLE} ,
+that function is disabled; that is, no input
+data is recognized as the disabled special character.
+If
+.Dv ICANON
+is
+not set, the value of
+.Dv {_POSIX_VDISABLE}
+has no special meaning for the
+.Dv VMIN
+and
+.Dv VTIME
+entries of the
+.Fa c_cc
+array.
+.Pp
+The initial values of the flags and control characters
+after open() is set according to
+the values in the header
+.Aq Pa sys/ttydefaults.h .
diff --git a/share/man/man4/tp.4 b/share/man/man4/tp.4
new file mode 100644
index 00000000000..e761caaa72c
--- /dev/null
+++ b/share/man/man4/tp.4
@@ -0,0 +1,724 @@
+.\"	$NetBSD: tp.4,v 1.4 1994/11/30 16:22:38 jtc Exp $
+.\"
+.\" Copyright (c) 1990, 1991, 1993
+.\"	The Regents of the University of California.  All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     @(#)tp.4	8.4 (Berkeley) 4/19/94
+.\"
+.Dd April 19, 1994
+.Dt TP 4
+.Os
+.Sh NAME
+.Nm TP
+.Nd
+.Tn ISO
+Transport Protocol
+.Sh SYNOPSIS
+.Fd #include <sys/socket.h>
+.Fd #include <netiso/iso_errno.h>
+.Fd #include <netiso/tp_param.h>
+.Fd #include <netiso/tp_user.h>
+.Ft int
+.Fn socket "[AF_INET, AF_ISO]" SOCK_SEQPACKET 0
+.Sh DESCRIPTION
+.Pp
+The
+.Tn TP
+protocol provides reliable, flow-controlled, two-way
+transmission of data and record boundaries. 
+It is a byte-stream protocol and is accessed according to
+the
+.Dv SOCK_SEQPACKET
+abstraction.
+The
+.Tn TP
+protocol makes use of a standard
+.Tn ISO
+address format,
+including a Network Service Access Point, and a Transport Service Entity
+Selector.
+Subclass 4 may make use of the internet
+Internet address format.
+.Pp
+Sockets utilizing the tp protocol are either
+.Dq active
+or
+.Dq passive .
+Active sockets initiate connections to passive
+sockets.  By default
+.Tn TCP
+sockets are created active; to create a
+passive socket the
+.Xr listen 2
+system call must be used
+after binding the socket with the
+.Xr bind 2
+system call.  Only
+passive sockets may use the 
+.Xr accept 2
+call to accept incoming connections.  Only active sockets may
+use the
+.Xr connect 2
+call to initiate connections.
+.Pp
+Passive sockets may
+.Dq underspecify
+their location to match
+incoming connection requests from multiple networks.  This
+technique, termed
+.Dq wildcard addressing ,
+allows a single
+server to provide service to clients on multiple networks.
+To create a socket which listens on all networks, the
+.Tn NSAP
+portion
+of the bound address must be void (of length zero).
+The Transport Selector may still be specified
+at this time; if the port is not specified the system will assign one.
+Once a connection has been established the socket's address is
+fixed by the peer entity's location.   The address assigned the
+socket is the address associated with the network interface
+through which packets are being transmitted and received.
+.Pp
+The
+.Tn ISO
+Transport Protocol implemented for
+.Tn AOS R2
+at the University of Wisconsin - Madison,
+and modified for inclusion in the Berkeley Software Distribution,
+includes classes 0 and 4 
+of the
+.Tn ISO
+transport protocols
+as specified in
+the June 1986 version of
+.Tn IS
+8073.
+Class 4 of the protocol provides reliable, sequenced,
+flow-controlled, two-way
+transmission of data packets with an alternate stop-and-wait data path called
+the "expedited data" service.
+Class 0 is essentially a null transport protocol, which is used
+when the underlying network service provides reliable, sequenced,
+flow-controlled, two-way data transmission.
+Class 0 does not provide the expedited data service.
+The protocols are implemented as a single transport layer entity 
+that coexists with the Internet protocol suite.
+Class 0 may be used only in the
+.Tn ISO
+domain.
+Class 4 may be used in the Internet domain as well as in the
+.Tn ISO
+domain.
+.Pp
+Two system calls were modified from the previous
+release of the Berkeley Software Distribution
+to permit the support of the end-of-transport-service-data-unit
+.Pq Dv EOTSDU
+indication, and for the receipt and transmission of user
+connect, confirm, and disconnect data.
+See
+.Xr sendmsg 2
+and
+.Xr recvmsg 2 ,
+and further discussion
+below for the formats of the data in the ancillary data buffer.
+If the
+.Dv EOTSDU
+is not needed, the normal
+.Xr read 2 ,
+and
+.Xr write 2
+system calls may be used.
+.Pp
+Through the 
+.Xr getsockopt
+and
+.Xr setsockopt
+system calls,
+.Tn TP
+supports several options 
+to control such things as negotiable options
+in the protocol and protocol strategies.
+The options are defined in
+.Aq Pa netiso/tp_user.h ,
+and are described below.
+.Pp
+In the tables below,
+the options marked with a pound sign
+.Ql \&#
+may be used 
+with
+.Xr setsockopt
+after a connection is established.
+Others must be used before the connection
+is established, in other words,
+before calling
+.Xr connect
+or 
+.Xr accept .
+All options may be used 
+with
+.Xr getsockopt
+before or
+after a connection is established.
+.Bl -tag -width TPOPT_PSTATISTICS
+.It Dv TPOPT_CONN_DATA
+(char *) [none]
+.br
+Data to send on
+.Xr connect .
+The passive user may issue a
+.Xr getsockopt
+call to retrieve a connection request's user data,
+after having done the
+.Xr accept
+system call without implying confirmation of the connection.
+.Pp
+The data may also be retrieved by issuing a
+.Xr recvmsg
+request for ancillary data only,
+without implying confirmation of the connection.
+The returned
+.Va cmsghdr
+will contain
+.Dv SOL_TRANSPORT
+for the
+.Va csmg_level
+and
+.Dv TPOPT_CONN_DATA
+for
+.Va cmsg_type.
+.It Dv TPOPT_DISC_DATA \&#
+(char *) [none]
+.br
+Data to send on
+.Xr close .
+Disconnect data may be sent by the side initiating the close
+but not by the passive side ("passive" with respect to the closing
+of the connection), so there is no need to read disconnect data
+after calling
+.Xr close .
+This may be sent by a
+.Xr setsockopt
+system call, or by issuing a
+.Xr sendmsg
+request specifying ancillary data only.
+The user-provided
+.Va cmsghdr
+must contain
+.Dv SOL_TRANSPORT
+for
+.Va csmg_level
+and
+.Dv TPOPT_DISC_DATA
+for
+.Va cmsg_type .
+Sending of disconnect data will in of itself tear down (or reject)
+the connection.
+.It Dv TPOPT_CFRM_DATA \&#
+(char *) [none]
+.br
+Data to send when confirming a connection.
+This may also be sent by a 
+.Xr setsockopt
+system call, or by issuing a
+.Xr sendmsg
+request, as above.
+Sending of connect confirm data will cause the connection
+to be confirmed rather than rejected.
+.It Dv TPOPT_PERF_MEAS \&#
+Boolean.
+.br
+When
+.Xr true ,
+performance measurements will be kept
+for this connection.  
+When set before a connection is established, the
+active side will use a locally defined parameter on the
+connect request packet; if the peer is another
+.Tn ARGO
+implementation, this will cause performance measurement to be
+turned on 
+on the passive side as well.
+See
+.Xr tpperf 8 .
+.It Dv TPOPT_PSTATISTICS
+No associated value on input.
+On output,
+.Ar struct tp_pmeas .
+.Pp
+This command is used to read the performance statistics accumulated
+during a connection's lifetime.
+It can only be used with
+.Xr getsockopt .
+The structure it returns is described in
+.Aq Pa netiso/tp_stat.h .
+See
+.Xr tpperf 8 .
+.It Dv TPOPT_FLAGS
+unsigned integer. [0x0]
+.br
+This command can only be used with
+.Xr getsockopt .
+See the description of the flags below.
+.It Dv TPOPT_PARAMS
+.Ar struct tp_conn_param
+.br
+Used to get or set a group parameters for a connection.
+The
+.Ar struct tp_conn_param
+is the argument used with the
+.Xr getsockopt
+or
+.Xr setsockopt
+system call. 
+It is described in 
+.Aq Pa netiso/tp_user.h .
+.Pp
+The fields of the
+.Ar tp_conn_param
+structure are
+described below.
+.El
+.Pp
+.Em Values for TPOPT_PARAMS:
+.Bl -tag -width p_sendack_ticks
+.It Ar p_Nretrans
+nonzero short integer [1]
+.br
+Number of times a TPDU
+will be retransmitted before the
+local TP entity closes a connection.
+.It Ar p_dr_ticks
+nonzero short integer [various]
+.br
+Number of clock ticks between retransmissions of disconnect request
+TPDUs.
+.It Ar p_dt_ticks
+nonzero short integer [various]
+.br
+Number of clock ticks between retransmissions of data
+TPDUs.
+This parameter applies only to class 4.
+.It Ar p_cr_ticks
+nonzero short integer [various]
+.br
+Number of clock ticks between retransmissions of connection request
+TPDUs.
+.It Ar p_cc_ticks
+nonzero short integer [various]
+.br
+Number of clock ticks between retransmissions of connection confirm
+TPDUs.
+This parameter applies only to class 4.
+.It Ar p_x_ticks
+nonzero short integer [various]
+.br
+Number of clock ticks between retransmissions of expedited data
+TPDUs.
+This parameter applies only to class 4.
+.It Ar p_sendack_ticks
+nonzero short integer [various]
+.br
+Number of clock ticks that the local TP entity
+will wait before sending an acknowledgment for normal data
+(not applicable if the acknowledgement strategy is
+.Dv TPACK_EACH ) .
+This parameter applies only to class 4.
+.It Ar p_ref_ticks
+nonzero short integer [various]
+.br
+Number of clock ticks for which a reference will
+be considered frozen after the connection to which
+it applied is closed.
+This parameter applies to classes 4 and 0 in the 
+.Tn ARGO
+implementation, despite the fact that
+the frozen reference function is required only for
+class 4.
+.It Ar p_inact_ticks
+nonzero short integer [various]
+.br
+Number of clock ticks without an incoming packet from the peer after which 
+.Tn TP
+close the connection.
+This parameter applies only to class 4.
+.It Ar p_keepalive_ticks
+nonzero short integer [various]
+.br
+Number of clock ticks between acknowledgments that are sent
+to keep an inactive connection open (to prevent the peer's
+inactivity control function from closing the connection).
+This parameter applies only to class 4.
+.It Ar p_winsize
+short integer between 128 and 16384. [4096 bytes]
+.br
+The buffer space limits in bytes for incoming and outgoing data.
+There is no way to specify different limits for incoming and outgoing
+paths.
+The actual window size at any time
+during the lifetime of a connection
+is a function of the buffer size limit, the negotiated
+maximum TPDU
+size, and the 
+rate at which the user program receives data.
+This parameter applies only to class 4.
+.It Ar p_tpdusize
+unsigned char between 0x7 and 0xd. 
+[0xc for class 4] [0xb for class 0]
+.br
+Log 2 of the maximum TPDU size to be negotiated.
+The
+.Tn TP
+standard
+.Pf ( Tn ISO
+8473) gives an upper bound of 
+0xd for class 4 and 0xb for class 0.
+The
+.Tn ARGO
+implementation places upper bounds of
+0xc on class 4 and 0xb on class 0.
+.It Ar p_ack_strat
+.Dv TPACK_EACH
+or
+.Dv TPACK_WINDOW.
+.Bq Dv TPACK_WINDOW
+.br
+This parameter applies only to class 4.
+Two acknowledgment strategies are supported:
+.Pp
+.Dv TPACK_EACH means that each data TPDU
+is acknowledged
+with an AK TPDU.
+.Pp
+.Dv TPACK_WINDOW
+means that upon receipt of the packet that represents
+the high edge of the last window advertised, an AK TPDU is generated.
+.It Ar p_rx_strat
+4 bit mask
+.Bq Dv TPRX_USE_CW No \&|\  Dv TPRX_FASTSTART
+over
+connectionless network protocols]
+.Pf [ Dv TPRX_USE_CW
+over
+connection-oriented network protocols]
+.br
+This parameter applies only to class 4.
+The bit mask may include the following values:
+.Pp
+.Dv TPRX_EACH :
+When a retransmission timer expires, retransmit
+each packet in the send window rather than
+just the first unacknowledged packet.
+.Pp
+.Dv TPRX_USE_CW :
+Use a "congestion window" strategy borrowed
+from Van Jacobson's congestion window strategy for TCP.
+The congestion window size is set to one whenever
+a retransmission occurs.
+.Pp
+.Dv TPRX_FASTSTART :
+Begin sending the maximum amount of data permitted
+by the peer (subject to availability).
+The alternative is to start sending slowly by 
+pretending the peer's window is smaller than it is, and letting
+it slowly grow up to the peer window's real size.
+This is to smooth the effect of new connections on a congested network
+by preventing a transport connection from suddenly 
+overloading the network with a burst of packets.
+This strategy is also due to Van Jacobson.
+.It Ar p_class
+5 bit mask
+.Bq Dv TP_CLASS_4 No \&|\  Dv TP_CLASS_0
+.br
+Bit mask including one or both of the values
+.Dv TP_CLASS_4
+and
+.Dv TP_CLASS_0 .
+The higher class indicated is the preferred class.
+If only one class is indicated, negotiation will not occur
+during connection establishment.
+.It Ar p_xtd_format
+Boolean.
+[false]
+.br
+Boolean indicating that extended format is negotiated.
+This parameter applies only to class 4.
+.It Ar p_xpd_service
+Boolean.
+[true]
+.br
+Boolean indicating that 
+the expedited data transport service will be negotiated.
+This parameter applies only to class 4.
+.It Ar p_use_checksum
+Boolean.
+[true]
+.br
+Boolean indicating the the use of checksums will be negotiated.
+This parameter applies only to class 4.
+.It Ar p_use_nxpd
+Reserved for future use.
+.It Ar p_use_rcc
+Reserved for future use.
+.It Ar p_use_efc
+Reserved for future use.
+.It Ar p_no_disc_indications
+Boolean.
+[false]
+.Pp
+Boolean indicating that the local
+.Tn TP
+entity will not issue
+indications (signals) when a
+.Tn TP
+connection is disconnected.
+.It Ar p_dont_change_params
+Boolean.  [false]
+.br
+If
+.Em true
+the
+.Tn TP
+entity will not override
+any of the other values given in this structure.
+If the values cannot be used, the
+.Tn TP
+entity will drop, disconnect,
+or refuse to establish the connection to which this structure pertains.
+.It Ar p_netservice
+One of {
+.Dv ISO_CLNS ,
+.Dv ISO_CONS ,
+.Dv ISO_COSNS ,
+.Dv IN_CLNS } .
+.Pf [ Dv ISO_CLNS ]
+.br
+Indicates which network service is to be used.
+.Pp
+.Dv ISO_CLNS
+indicates the connectionless network service provided
+by CLNP 
+.Pf ( Tn ISO
+8473).
+.Pp
+.Dv ISO_CONS
+indicates the connection-oriented network service provided
+by X.25
+.Pf ( Tn ISO
+8208) and
+.Tn ISO
+8878.
+.Pp
+.Dv ISO_COSNS
+indicates the 
+connectionless network service running over a
+connection-oriented subnetwork service: CLNP 
+.Pf ( Tn ISO
+8473) over X.25
+.Pf ( Tn ISO
+8208).
+.Pp
+.Dv IN_CLNS
+indicates the 
+DARPA Internet connectionless network service provided by IP (RFC 791).
+.It Ar p_dummy
+Reserved for future use.
+.El
+.Pp
+The
+.Dv TPOPT_FLAGS
+option is used for obtaining
+various boolean-valued options.
+Its meaning is as follows.
+The bit numbering used is that of the RT PC, which means that bit
+0 is the most significant bit, while bit 8 is the least significant bit.
+.sp 1
+.Em Values for TPOPT_FLAGS:
+.Bl -tag -width Bitsx
+.It Sy Bits
+.Sy Description [Default]
+.It \&0
+.Dv TPFLAG_NLQOS_PDN :
+set when the quality of the 
+network service is
+similar to that of a public data network.
+.It \&1
+.Dv TPFLAG_PEER_ON_SAMENET :
+set when the peer
+.Tn TP
+entity
+is considered to be on the same network as the local
+.Tn TP
+entity.
+.It \&2
+Not used.
+.It \&3
+.Dv TPFLAG_XPD_PRES :
+set when expedited data are present
+[0]
+.It 4\&..7
+Reserved.
+.El
+.Sh ERROR VALUES
+.Pp
+The
+.Tn TP
+entity returns
+.Va errno
+error values as defined in
+.Aq Pa sys/errno.h
+and
+.Aq Pa netiso/iso_errno.h .
+User programs may print messages associated with these value by
+using an expanded version of
+.Xr perror
+found in the
+.Tn ISO
+library,
+.Pa libisodir.a .
+.Pp
+If the
+.Tn TP
+entity encounters asynchronous events
+that will cause a transport connection to be closed,
+such as
+timing out while retransmitting a connect request TPDU,
+or receiving a DR TPDU,
+the
+.Tn TP
+entity issues a
+.Dv SIGURG
+signal, indicating that
+disconnection has occurred.
+If the signal is issued during a 
+a system call, the system call may be interrupted,
+in which case the
+.Va errno
+value upon return from the system call is
+.Er EINTR.
+If the signal
+.Dv SIGURG
+is being handled by reading
+from the socket, and it was an
+.Xr accept 2
+that
+timed out, the read may result in
+.Er ENOTSOCK ,
+because the
+.Xr accept
+call had not yet returned a
+legitimate socket descriptor when the signal was handled.
+.Dv ETIMEDOUT
+(or a some other errno value appropriate to the
+type of error) is returned if
+.Dv SIGURG
+is blocked
+for the duration of the system call.
+A user program should take one of the following approaches:
+.Bl -tag -width Ds
+.It Block Dv SIGURG
+If the program is servicing
+only one connection, it can block or ignore
+.Dv SIGURG
+during connection 
+establishment.
+The advantage of this is that the
+.Va errno
+value
+returned is somewhat meaningful.
+The disadvantage of this is that
+if ignored, disconnection and expedited data indications could be
+missed.
+For some programs this is not a problem.
+.It Handle Dv SIGURG
+If the program is servicing more than one connection at a time
+or expedited data may arrive or both, the program may elect to
+service
+.Dv SIGURG .
+It can use the
+.Fn getsockopt ...TPOPT_FLAGS...
+system 
+call to see if the signal
+was due to the arrival of expedited data or due to a disconnection.
+In the latter case, 
+.Xr getsockopt
+will return
+.Er ENOTCONN .
+.El
+.Sh SEE ALSO
+.Xr tcp 4 ,
+.Xr netstat 1 ,
+.Xr iso 4 ,
+.Xr clnp 4 ,
+.Xr cltp 4 ,
+.Xr ifconfig 8 .
+.Sh BUGS
+The protocol definition of expedited data is slightly problematic,
+in a way that renders expedited data almost useless,
+if two or more packets of expedited data are send within
+time epsilon, where epsilon
+depends on the application.
+The problem is not of major significance since most applications
+do not use transport expedited data.
+The problem is this:
+the expedited data acknowledgment TPDU
+has no field for conveying
+credit, thus it is not possible for a
+.Tn TP
+entity to inform its peer
+that "I received your expedited data but have no room to receive more."
+The
+.Tn TP
+entity has the choice of acknowledging receipt of the
+XPD TPDU:
+.Bl -tag -width Ds
+.It "when the user receives the" XPD TSDU
+which may be a fairly long time,
+which may cause the sending
+.Tn TP
+entity to retransmit the packet,
+and possibly to close the connection after retransmission, or
+.It "when the" Tn TP No "entity receives it"
+so the sending entity does not retransmit or close the connection.
+If the sending user then tries to send more expedited data
+.Dq soon ,
+the expedited data will not be acknowledged (until the
+receiving user receives the first XPD TSDU).
+.El
+.Pp
+The
+.Tn ARGO
+implementation acknowledges XPD TPDUs
+immediately,
+in the hope that most users will not use expedited data frequently
+enough for this to be a problem.
diff --git a/share/man/man4/tty.4 b/share/man/man4/tty.4
new file mode 100644
index 00000000000..fa2fab6cbe2
--- /dev/null
+++ b/share/man/man4/tty.4
@@ -0,0 +1,396 @@
+.\"	$NetBSD: tty.4,v 1.2 1994/11/30 16:22:40 jtc Exp $
+.\"
+.\" Copyright (c) 1991, 1992, 1993
+.\"	The Regents of the University of California.  All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     @(#)tty.4	8.3 (Berkeley) 4/19/94
+.\"
+.Dd August 14, 1992
+.Dt TTY 4
+.Os BSD 4
+.Sh NAME
+.Nm tty
+.Nd general terminal interface
+.Sh SYNOPSIS
+.Fd #include <sys/ioctl.h>
+.Sh DESCRIPTION
+This section describes the interface to the terminal drivers
+in the system.
+.Ss Terminal Special Files
+Each hardware terminal port on the system usually has a terminal special device
+file associated with it in the directory ``/dev/'' (for
+example, ``/dev/tty03'').
+When a user logs into
+the system on one of these hardware terminal ports, the system has already
+opened the associated device and prepared the line for normal interactive
+use (see
+.Xr getty 8 .)
+There is also a special case of a terminal file that connects not to
+a hardware terminal port, but to another program on the other side.
+These special terminal devices are called
+.Em ptys
+and provide the mechanism necessary to give users the same interface to the
+system when logging in over a network (using
+.Xr rlogin 1 ,
+or
+.Xr telnet 1
+for example.)  Even in these cases the details of how the terminal
+file was opened and set up is already handled by special software
+in the system.
+Thus, users do not normally need to worry about the details of
+how these lines are opened or used.  Also, these lines are often used
+for dialing out of a system (through an out-calling modem), but again
+the system provides programs that hide the details of accessing
+these terminal special files (see
+.Xr tip 2 .)
+.Pp
+When an interactive user logs in, the system prepares the line to
+behave in a certain way (called a
+.Em "line discipline" ) ,
+the particular details of which is described in
+.Xr stty 1
+at the command level, and in
+.Xr termios 4
+at the programming level.  A user may be concerned with changing
+settings associated with his particular login terminal and should refer
+to the preceding man pages for the common cases.  The remainder of
+this man page is concerned
+with describing details of using and controlling terminal devices
+at a low level, such as that possibly required by a program wishing
+to provide features similar to those provided by the system.
+.Ss Line disciplines
+A terminal file is used like any other file in the system in that
+it can be opened, read, and written to using standard system
+calls.  For each existing terminal file, there is a software processing module
+called a
+.Em "line discipline"
+is associated with it.  The
+.Em "line discipline"
+essentially glues the low level device driver code with the high
+level generic interface routines (such as
+.Xr read 2
+and
+.Xr write 2 ),
+and is responsible for implementing the semantics associated
+with the device.  When a terminal file is first opened by a program,
+the default
+.Em "line discipline"
+called the
+.Dv termios
+line discipline is associated with the file.  This is the primary
+line discipline that is used in most cases and provides the semantics
+that users normally associate with a terminal.  When the
+.Dv termios
+line discipline is in effect, the terminal file behaves and is
+operated according to the rules described in
+.Xr termios 4 .
+Please refer to that man page for a full description of the terminal
+semantics.
+The operations described here
+generally represent features common
+across all
+.Em "line disciplines" ,
+however some of these calls may not
+make sense in conjunction with a line discipline other than
+.Dv termios ,
+and some may not be supported by the underlying
+hardware (or lack thereof, as in the case of ptys).
+.Ss Terminal File Operations
+All of the following operations are invoked using the
+.Xr ioctl 2
+system call.  Refer to that man page for a description of
+the
+.Em request
+and
+.Em argp
+parameters.
+In addition to the ioctl
+.Em requests
+defined here, the specific line discipline
+in effect will define other
+.Em requests
+specific to it (actually
+.Xr termios 4
+defines them as function calls, not ioctl
+.Em requests . )
+The following section lists the available ioctl requests.  The
+name of the request, a description of its purpose, and the typed
+.Em argp
+parameter (if any)
+are listed.  For example, the first entry says
+.Pp
+.D1 Em "TIOCSETD int *ldisc"
+.Pp
+and would be called on the terminal associated with
+file descriptor zero by the following code fragment:
+.Bd -literal
+	int ldisc;
+
+	ldisc = TTYDISC;
+	ioctl(0, TIOCSETD, &ldisc);
+.Ed
+.Ss Terminal File Request Descriptions
+.Bl -tag -width TIOCGWINSZ
+.It Dv TIOCSETD Fa int *ldisc
+Change to the new line discipline pointed to by
+.Fa ldisc .
+The available line disciplines are listed in
+.Pa Aq sys/termios.h
+and currently are:
+.Pp
+.Bl -tag -width TIOCGWINSZ -compact
+.It TTYDISC
+Termios interactive line discipline.
+.It TABLDISC
+Tablet line discipline.
+.It SLIPDISC
+Serial IP line discipline.
+.El
+.Pp
+.It Dv TIOCGETD Fa int *ldisc
+Return the current line discipline in the integer pointed to by
+.Fa ldisc .
+.It Dv TIOCSBRK Fa void
+Set the terminal hardware into BREAK condition.
+.It Dv TIOCCBRK Fa void
+Clear the terminal hardware BREAK condition.
+.It Dv TIOCSDTR Fa void
+Assert data terminal ready (DTR).
+.It Dv TIOCCDTR Fa void
+Clear data terminal ready (DTR).
+.It Dv TIOCGPGRP Fa int *tpgrp
+Return the current process group the terminal is associated
+with in the integer pointed to by
+.Fa tpgrp .
+This is the underlying call that implements the
+.Xr termios 4
+.Fn tcgetattr
+call.
+.It Dv TIOCSPGRP Fa int *tpgrp
+Associate the terminal with the process group (as an integer) pointed to by
+.Fa tpgrp .
+This is the underlying call that implements the
+.Xr termios 4
+.Fn tcsetattr
+call.
+.It Dv TIOCGETA Fa struct termios *term
+Place the current value of the termios state associated with the
+device in the termios structure pointed to by
+.Fa term .
+This is the underlying call that implements the
+.Xr termios 4
+.Fn tcgetattr
+call.
+.It Dv TIOCSETA Fa struct termios *term
+Set the termios state associated with the device immediately.
+This is the underlying call that implements the
+.Xr termios 4
+.Fn tcsetattr
+call with the
+.Dv TCSANOW
+option.
+.It Dv TIOCSETAW Fa struct termios *term
+First wait for any output to complete, then set the termios state
+associated with the device.
+This is the underlying call that implements the
+.Xr termios 4
+.Fn tcsetattr
+call with the
+.Dv TCSADRAIN
+option.
+.It Dv TIOCSETAF Fa struct termios *term
+First wait for any output to complete, clear any pending input,
+then set the termios state associated with the device.
+This is the underlying call that implements the
+.Xr termios 4
+.Fn tcsetattr
+call with the
+.Dv TCSAFLUSH
+option.
+.It Dv TIOCOUTQ Fa int *num
+Place the current number of characters in the output queue in the
+integer pointed to by
+.Fa num .
+.It Dv TIOCSTI Fa char *cp
+Simulate typed input.  Pretend as if the terminal received the
+character pointed to by
+.Fa cp .
+.It Dv TIOCNOTTY Fa void
+This call is obsolete but left for compatibility.  In the past, when
+a process that didn't have a controlling terminal (see
+.Em The Controlling Terminal
+in
+.Xr termios 4 )
+first opened a terminal device, it acquired that terminal as its
+controlling terminal.  For some programs this was a hazard as they
+didn't want a controlling terminal in the first place, and this
+provided a mechanism to disassociate the controlling terminal from
+the calling process.  It
+.Em must
+be called by opening the file
+.Pa /dev/tty
+and calling
+.Dv TIOCNOTTY
+on that file descriptor.
+.Pp
+The current system does not allocate a controlling terminal to
+a process on an
+.Fn open
+call: there is a specific ioctl called
+.Dv TIOSCTTY
+to make a terminal the controlling
+terminal.
+In addition, a program can
+.Fn fork
+and call the
+.Fn setsid
+system call which will place the process into its own session - which
+has the effect of disassociating it from the controlling terminal.  This
+is the new and preferred method for programs to lose their controlling
+terminal.
+.It Dv TIOCSTOP Fa void
+Stop output on the terminal (like typing ^S at the keyboard).
+.It Dv TIOCSTART Fa void
+Start output on the terminal (like typing ^Q at the keyboard).
+.It Dv TIOCSCTTY Fa void
+Make the terminal the controlling terminal for the process (the process
+must not currently have a controlling terminal).
+.It Dv TIOCDRAIN Fa void
+Wait until all output is drained.
+.It Dv TIOCEXCL Fa void
+Set exclusive use on the terminal.  No further opens are permitted
+except by root.  Of course, this means that programs that are run by
+root (or setuid) will not obey the exclusive setting - which limits
+the usefulness of this feature.
+.It Dv TIOCNXCL Fa void
+Clear exclusive use of the terminal.  Further opens are permitted.
+.It Dv TIOCFLUSH Fa int *what
+If the value of the int pointed to by
+.Fa what
+contains the
+.Dv FREAD
+bit as defined in
+.Pa Aq sys/file.h ,
+then all characters in the input queue are cleared.  If it contains
+the
+.Dv FWRITE
+bit, then all characters in the output queue are cleared.  If the
+value of the integer is zero, then it behaves as if both the
+.Dv FREAD
+and
+.Dv FWRITE
+bits were set (i.e. clears both queues).
+.It Dv TIOCGWINSZ Fa struct winsize *ws
+Put the window size information associated with the terminal in the
+.Va winsize
+structure pointed to by
+.Fa ws .
+The window size structure contains the number of rows and columns (and pixels
+if appropriate) of the devices attached to the terminal.  It is set by user software
+and is the means by which most full\&-screen oriented programs determine the
+screen size.  The
+.Va winsize
+structure is defined in
+.Pa Aq sys/ioctl.h .
+.It Dv TIOCSWINSZ Fa struct winsize *ws
+Set the window size associated with the terminal to be the value in
+the
+.Va winsize
+structure pointed to by
+.Fa ws
+(see above).
+.It Dv TIOCCONS Fa int *on
+If
+.Fa on
+points to a non-zero integer, redirect kernel console output (kernel printf's)
+to this terminal.
+If
+.Fa on
+points to a zero integer, redirect kernel console output back to the normal
+console.  This is usually used on workstations to redirect kernel messages
+to a particular window.
+.It Dv TIOCMSET Fa int *state
+The integer pointed to by
+.Fa state
+contains bits that correspond to modem state.  Following is a list
+of defined variables and the modem state they represent:
+.Pp
+.Bl -tag -width TIOCMXCTS -compact
+.It TIOCM_LE
+Line Enable.
+.It TIOCM_DTR
+Data Terminal Ready.
+.It TIOCM_RTS
+Request To Send.
+.It TIOCM_ST
+Secondary Transmit.
+.It TIOCM_SR
+Secondary Receive.
+.It TIOCM_CTS
+Clear To Send.
+.It TIOCM_CAR
+Carrier Detect.
+.It TIOCM_CD
+Carier Detect (synonym).
+.It TIOCM_RNG
+Ring Indication.
+.It TIOCM_RI
+Ring Indication (synonym).
+.It TIOCM_DSR
+Data Set Ready.
+.El
+.Pp
+This call sets the terminal modem state to that represented by
+.Fa state .
+Not all terminals may support this.
+.It Dv TIOCMGET Fa int *state
+Return the current state of the terminal modem lines as represented
+above in the integer pointed to by
+.Fa state .
+.It Dv TIOCMBIS Fa int *state
+The bits in the integer pointed to by
+.Fa state
+represent modem state as described above, however the state is OR-ed
+in with the current state.
+.It Dv TIOCMBIC Fa int *state
+The bits in the integer pointed to by
+.Fa state
+represent modem state as described above, however each bit which is on
+in
+.Fa state
+is cleared in the terminal.
+.El
+.Sh SEE ALSO
+.Xr getty 8 ,
+.Xr ioctl 2 ,
+.Xr pty 4 ,
+.Xr stty 1 ,
+.Xr termios 4
diff --git a/share/man/man4/udp.4 b/share/man/man4/udp.4
new file mode 100644
index 00000000000..5e8f7eae3d0
--- /dev/null
+++ b/share/man/man4/udp.4
@@ -0,0 +1,139 @@
+.\"	$NetBSD: udp.4,v 1.3 1994/11/30 16:22:41 jtc Exp $
+.\"
+.\" Copyright (c) 1983, 1991, 1993
+.\"	The Regents of the University of California.  All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     @(#)udp.4	8.1 (Berkeley) 6/5/93
+.\"
+.Dd June 5, 1993
+.Dt UDP 4
+.Os BSD 4.2
+.Sh NAME
+.Nm udp
+.Nd Internet User Datagram Protocol
+.Sh SYNOPSIS
+.Fd #include <sys/socket.h>
+.Fd #include <netinet/in.h>
+.Ft int
+.Fn socket AF_INET SOCK_DGRAM 0
+.Sh DESCRIPTION
+.Tn UDP
+is a simple, unreliable datagram protocol which is used
+to support the
+.Dv SOCK_DGRAM
+abstraction for the Internet
+protocol family.
+.Tn UDP
+sockets are connectionless, and are
+normally used with the
+.Xr sendto
+and
+.Xr recvfrom
+calls, though the
+.Xr connect 2
+call may also be used to fix the destination for future
+packets (in which case the 
+.Xr recv 2
+or
+.Xr read 2
+and 
+.Xr send 2
+or
+.Xr write 2
+system calls may be used).
+.Pp
+.Tn UDP
+address formats are identical to those used by
+.Tn TCP .
+In particular
+.Tn UDP
+provides a port identifier in addition
+to the normal Internet address format.  Note that the
+.Tn UDP
+port
+space is separate from the
+.Tn TCP
+port space (i.e. a
+.Tn UDP
+port
+may not be
+.Dq connected
+to a
+.Tn TCP
+port).  In addition broadcast
+packets may be sent (assuming the underlying network supports
+this) by using a reserved
+.Dq broadcast address ;
+this address
+is network interface dependent.
+.Pp
+Options at the
+.Tn IP
+transport level may be used with
+.Tn UDP ;
+see
+.Xr ip 4 .
+.Sh DIAGNOSTICS
+A socket operation may fail with one of the following errors returned:
+.Bl -tag -width [EADDRNOTAVAIL]
+.It Bq Er EISCONN
+when trying to establish a connection on a socket which
+already has one, or when trying to send a datagram with the destination
+address specified and the socket is already connected;
+.It Bq Er ENOTCONN
+when trying to send a datagram, but
+no destination address is specified, and the socket hasn't been
+connected;
+.It Bq Er ENOBUFS
+when the system runs out of memory for
+an internal data structure;
+.It Bq Er EADDRINUSE
+when an attempt
+is made to create a socket with a port which has already been
+allocated;
+.It Bq Er EADDRNOTAVAIL
+when an attempt is made to create a 
+socket with a network address for which no network interface
+exists.
+.El
+.Sh SEE ALSO
+.Xr getsockopt 2 ,
+.Xr recv 2 ,
+.Xr send 2 ,
+.Xr socket 2 ,
+.Xr intro 4 ,
+.Xr inet 4 ,
+.Xr ip 4
+.Sh HISTORY
+The
+.Nm
+protocol appeared in
+.Bx 4.2 .
diff --git a/share/man/man4/unix.4 b/share/man/man4/unix.4
new file mode 100644
index 00000000000..dae0ae6dea2
--- /dev/null
+++ b/share/man/man4/unix.4
@@ -0,0 +1,163 @@
+.\"	$NetBSD: unix.4,v 1.3 1994/11/30 16:22:43 jtc Exp $
+.\"
+.\" Copyright (c) 1991, 1993
+.\"	The Regents of the University of California.  All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     @(#)unix.4	8.1 (Berkeley) 6/9/93
+.\"
+.Dd June 9, 1993
+.Dt UNIX 4
+.Os
+.Sh NAME
+.Nm unix
+.Nd UNIX-domain protocol family
+.Sh SYNOPSIS
+.Fd #include <sys/types.h>
+.Fd #include <sys/un.h>
+.Sh DESCRIPTION
+The
+.Tn UNIX Ns -domain
+protocol family is a collection of protocols
+that provides local (on-machine) interprocess
+communication through the normal
+.Xr socket 2
+mechanisms.
+The 
+.Tn UNIX Ns -domain
+family supports the
+.Dv SOCK_STREAM
+and
+.Dv SOCK_DGRAM
+socket types and uses
+filesystem pathnames for addressing.
+.Sh ADDRESSING
+.Tn UNIX Ns -domain
+addresses are variable-length filesystem pathnames of
+at most 104 characters.
+The include file
+.Aq Pa sys/un.h
+defines this address:
+.Bd -literal -offset indent
+struct sockaddr_un {
+u_char	sun_len;
+u_char	sun_family;
+char	sun_path[104];
+};
+.Ed
+.Pp
+Binding a name to a
+.Tn UNIX Ns -domain
+socket with
+.Xr bind 2
+causes a socket file to be created in the filesystem.
+This file is
+.Em not
+removed when the socket is closed\(em\c
+.Xr unlink 2
+must be used to remove the file.
+.Pp
+The
+.Tn UNIX Ns -domain
+protocol family does not support broadcast addressing or any form
+of
+.Dq wildcard
+matching on incoming messages. 
+All addresses are absolute- or relative-pathnames
+of other
+.Tn UNIX Ns -domain
+sockets.
+Normal filesystem access-control mechanisms are also
+applied when referencing pathnames; e.g., the destination
+of a
+.Xr connect 2
+or
+.Xr sendto 2
+must be writable.
+.Sh PROTOCOLS
+The 
+.Tn UNIX Ns -domain
+protocol family is comprised of simple
+transport protocols that support the
+.Dv SOCK_STREAM
+and
+.Dv SOCK_DGRAM
+abstractions.
+.Dv SOCK_STREAM
+sockets also support the communication of 
+.Ux
+file descriptors through the use of the
+.Ar msg_control
+field in the
+.Ar msg
+argument to
+.Xr sendmsg 2
+and
+.Xr recvmsg 2 .
+.Pp
+Any valid descriptor may be sent in a message.
+The file descriptor(s) to be passed are described using a 
+.Ar struct cmsghdr
+that is defined in the include file
+.Aq Pa sys/socket.h .
+The type of the message is
+.Dv SCM_RIGHTS ,
+and the data portion of the messages is an array of integers
+representing the file descriptors to be passed.
+The number of descriptors being passed is defined
+by the length field of the message;
+the length field is the sum of the size of the header
+plus the size of the array of file descriptors.
+.Pp
+The received descriptor is a 
+.Em duplicate
+of the sender's descriptor, as if it were created with a call to
+.Xr dup 2 .
+Per-process descriptor flags, set with
+.Xr fcntl 2 ,
+are 
+.Em not
+passed to a receiver.
+Descriptors that are awaiting delivery, or that are
+purposely not received, are automatically closed by the system
+when the destination socket is closed.
+.Sh SEE ALSO
+.Xr socket 2 ,
+.Xr intro 4
+.Rs
+.%T "An Introductory 4.3 BSD Interprocess Communication Tutorial"
+.%B PS1
+.%N 7
+.Re
+.Rs
+.%T "An Advanced 4.3 BSD Interprocess Communication Tutorial"
+.%B PS1
+.%N 8
+.Re