BSD 4_1c_2 development

Work on file usr/man/man4/imp.4v
Work on file usr/man/man4/il.4v
Work on file usr/man/man4/intro.4v
Work on file usr/man/man4/mt.4v

Synthesized-from: CSRG/cd1/4.1c.2

diff --git a/usr/man/man4/il.4v b/usr/man/man4/il.4v
new file mode 100644 (file)
index 0000000..fadd6a6
--- /dev/null
+++ b/usr/man/man4/il.4v
@@ -0,0 +1,38 @@
+.TH IL 4V "25 February 1983"
+.UC 4
+.SH NAME
+il \- Interlan 10 Mb/s Ethernet interface
+.SH SYNOPSIS
+.B "device il0 at uba0 csr 161000 flags 0x4e000298 vector ilrint ilcint"
+.SH DESCRIPTION
+The
+.I il
+interface provides access to a 10 Mb/s Ethernet network through
+an Interlan controller.
+In configuring, the flags value is used to define the 
+network to which the interface is attached.
+The host's address
+is discovered at boot time by reading it from the device's command
+register.
+.PP
+The interface handles the Internet protocol family,
+with the interface address maintained in Internet format.
+The three low-order bytes of the board's built-in Ethernet address
+are used as the 24-bit Internet address, and the network number is
+taken from the flags as described above.  The software assumes that
+all Ethernet addresses on the network will have the same three high-order
+bytes.
+.SH DIAGNOSTICS
+\fBil%d: input error\fP.  The hardware indicated an error
+in reading a packet off the cable or an illegally sized packet.
+.PP
+\fBil%d: can't handle af%d\fP.  The interface was handed
+a message with addresses formatted in an unsuitable address
+family; the packet was dropped.
+.SH SEE ALSO
+intro(4N), inet(4F)
+.SH BUGS
+The PUP protocol family should be added.
+.PP
+A better mapping from Ethernet to Internet addresses is needed if one is
+to mix controllers from different vendors on a network.

diff --git a/usr/man/man4/imp.4v b/usr/man/man4/imp.4v
new file mode 100644 (file)
index 0000000..c133998
--- /dev/null
+++ b/usr/man/man4/imp.4v
@@ -0,0 +1,82 @@
+.TH IMP 4V "25 March 1982"
+.UC 4
+.SH NAME
+imp \- 1822 network interface
+.SH SYNOPSIS
+.B pseudo-device imp
+.SH DESCRIPTION
+The 
+.I imp
+interface, as described in BBN Report 1822, provides access to an
+intelligent message processor normally used when participating
+in the Department of Defense ARPA network.  The network interface
+communicates through a device controller, usually an ACC LH/DH or
+DEC IMP-11A, with the IMP.  The interface is \*(lqreliable\*(rq and
+\*(lqflow-controlled\*(rq by the host-IMP protocol.
+.PP
+In configuring an
+.I imp
+the flags word is used to define the 
+network to which the interface is attached.  The host's address
+is discovered during auto-configuration through the receipt of NOOP
+messages from the IMP.
+.PP
+The network interface is always in one of four states: up, down,
+initializing, or going down.  When the system is
+booted, the interface is marked down.  If the hardware controller
+is successfully probed, the interface enters the initializing
+state and transmits three NOOP messages to the IMP.  It then waits
+for the IMP to respond with two or more NOOP messages in reply.
+When it receives these messages it enters the up state.  The going
+down state is entered only when notified by the IMP of an impending
+shutdown.  Packets may be sent through the interface only while it
+is in the up state.  Packets received in any other state are dropped
+with the error ENETDOWN returned to the caller.
+.SH DIAGNOSTICS
+\fBimp%d: leader error\fP.  The IMP reported an error in a leader
+(1822 message header).  This causes the interface to be reset and
+any packets queued up for transmission to be purged.
+.PP
+\fBimp%d: going down in 30 seconds\fP.
+.br
+\fBimp%d: going down for hardware PM\fP.
+.br
+\fBimp%d: going down for reload software\fP.
+.br
+\fBimp%d: going down for emergency reset\fP.
+The Network Control Center (NCC) is manipulating the IMP.  By convention
+these messages are reported to all hosts on an IMP.
+.PP
+\fBimp%d: reset (host %d/imp %d)\fP.  The host has received a
+NOOP message which caused it to reset its notion of its
+current address.  This normally occurs at boot time, though
+it may also occur while the system is running (for example, if
+the IMP-controller cable is disconnected, then reconnected).
+.PP
+\fBimp%d: host dead\fP.  The IMP has noted a host, to which a
+prior packet was sent, is not up.
+.PP
+\fBimp%d: host unreachable\fP.  The IMP has discovered a host,
+to which a prior packet was sent, is not accessible.
+.PP
+\fBimp%d: data error\fP.  The IMP noted an error in data
+transmitted.  The host-IMP interface is reset and the host
+enters the init state (awaiting NOOP messages).
+.PP
+\fBimp%d: interface reset\fP.  The reset process has been
+completed.
+.PP
+\fBimp%d: marked down\fP.  After receiving a \*(lqgoing down in
+30 seconds\*(rq message, and waiting 30 seconds, the host has
+marked the IMP unavailable.  Before packets may be sent to the
+IMP again, the IMP must notify the host, through a series of
+NOOP messages, that it is back up.
+.PP
+\fBimp%d: can't handle af%d\fP.  The interface was handed
+a message with addresses formatting in an unsuitable address
+family; the packet was dropped.
+.SH SEE ALSO
+intro(4N),
+inet(4F),
+acc(4V),
+css(4V)

diff --git a/usr/man/man4/intro.4v b/usr/man/man4/intro.4v
new file mode 100644 (file)
index 0000000..6264c42
--- /dev/null
+++ b/usr/man/man4/intro.4v
@@ -0,0 +1,80 @@
+.TH INTRO 4V "25 February 1983"
+.UC 4
+.SH NAME
+intro \- introduction to VAX devices
+.SH DESCRIPTION
+This section describes the hardware supported on the DEC VAX-11.
+Software support for these devices comes in two forms.  A hardware
+device may be supported with a character or block
+.IR "device driver" ,
+or it may be used within the networking subsystem and have a
+.IR "network interface driver" .
+Block and character devices are accessed through files in the file
+system of a special type; c.f.
+.IR mknod (8).
+Network interfaces are indirectly accessed through the interprocess
+communication facilities provided by the system; c.f.
+.IR 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 then booted, the
+autoconfiguration facilities in the system probe for the device
+on either the UNIBUS or MASSBUS and, if found, enable the software
+support for it.  If a UNIBUS device does not respond at autoconfiguration
+time it is not accessable at any time afterwards.  To
+enable a UNIBUS device which did not autoconfigure, the system will have to
+be rebooted.  If a
+MASSBUS device ``comes on-line'' after the autoconfiguration sequence,
+it will be dynamically autoconfigured into the running system.
+.PP
+The autoconfiguration system is described in
+.IR autoconf (4V).
+VAX specific device support is described in ``4V'' entries.
+A list of the supported devices is given below.
+.SH SEE ALSO
+intro(4),
+intro(4N),
+autoconf(4V)
+.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 useable with the supplied software.
+(\fBBeware however that we promise the software works
+ONLY with the hardware indicated on the appropriate manual page.\fP)
+.sp
+.ta 1.0i
+.nf
+acc    ACC LH/DH IMP communications interface
+ad     Data translation A/D interface
+css    DEC IMP-11A communications interface
+ct     C/A/T phototypesetter
+dh     DH-11 emulators, terminal multiplexor
+dmc    DEC DMC-11/DMR-11 point-to-point communications device
+dmf    DEC DMF-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)
+fl     VAX-11/780 console floppy 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 10Mb/s Ethernet controller
+lp     LP-11 parallel line printer interface
+mt     TM78 MASSBUS tape drive interface
+ps     Evans and Sutherland Picture System 2 graphics interface
+rx     DEC RX02 floppy interface
+tm     TM-11/TE-10 tape drive interface
+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 UNIBUS disk controller
+ut     UNIBUS TU-45 tape drive interface
+va     Benson-Varian printer/plotter interface
+vp     Versatec printer/plotter interface
+vv     Proteon proNET 10Mb/s ring network interface

diff --git a/usr/man/man4/mt.4v b/usr/man/man4/mt.4v
new file mode 100644 (file)
index 0000000..2367836
--- /dev/null
+++ b/usr/man/man4/mt.4v
@@ -0,0 +1,55 @@
+.TH MT 4V "1 April 1981"
+.UC 4
+.SH NAME
+mt \- TM78/TU-78 MASSBUS magtape interface
+.SH SYNOPSIS
+.B master mt0 at mba? drive ?
+.br
+.B tape mu0 at mt0 slave 0
+.SH DESCRIPTION
+The tm78/tu-78 combination provides a standard tape drive
+interface as described in
+.IR mt (4).
+Only 1600 and 6250 bpi are supported; the
+TU-78 runs at 125 ips and autoloads tapes.
+.SH "SEE ALSO"
+mt(1),
+tar(1),
+tp(1),
+mt(4),
+tm(4V),
+ts(4V),
+ut(4V)
+.SH DIAGNOSTICS
+\fBmu%d: no write ring\fR.  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
+\fBmu%d: not online\fR.  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
+\fBmu%d: can't switch density in mid-tape\fR.  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
+\fBmu%d: hard error bn%d mbsr=%b er=%x ds=%b\fR.   A tape error occurred
+at block \fIbn\fR; 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
+\fBmu%d: blank tape\fP.
+An attempt was made to read a blank tape (a tape without even
+end-of-file marks).
+.PP
+\fBmu%d: offline\fP.
+During an i/o operation the device was set offline.  If a
+non-raw tape was used in the access it is closed.
+.SH BUGS
+If any non-data error is encountered on non-raw tape,
+it refuses to do anything more until closed.
+.PP
+The system should remember which controlling terminal has the tape drive
+open and write error messages to that terminal rather than on the console.