BSD 4_1_snap development

Work on file usr/man/man4/autoconf.4
Work on file usr/man/man4/mt.4
Work on file usr/man/man4/dn.4
Work on file usr/man/man4/mtop.4
Work on file usr/man/man4/ra.4
Work on file usr/man/man4/ts.4
Work on file usr/man/man4/tm.4
Work on file usr/man/man4/tu.4

Synthesized-from: CSRG/cd1/4.1.snap

diff --git a/usr/man/man4/autoconf.4 b/usr/man/man4/autoconf.4
new file mode 100644 (file)
index 0000000..ea713ce
--- /dev/null
+++ b/usr/man/man4/autoconf.4
@@ -0,0 +1,101 @@
+.TH AUTOCONF 4 10/8/81
+.UC 4
+.SH NAME
+autoconf \- diagnostics from autoconfiguration code
+.SH DESCRIPTION
+When 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
+.IR config (8)
+and compiled into each kernel.
+.PP
+Devices in NEXUS slots are normally noted, thus memory controllers,
+UNIBUS and MASSBUS adaptors.  Devices which are not supported which
+are found in NEXUS slots are noted also.
+.PP
+MASSBUS devices are located by a very deterministic procedure since
+MASSBUS space is completely probable very easily.  If devices exist which
+are not configured they will be silently ignored; if devices exist of
+unsupported type they will be noted.
+.PP
+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.  (A command
+.IR attach (8)
+is planned to cause the device to be attached irregardless of its
+failure to interrupt, after the system is bootstrapped, for irksome
+devices.  This is not in as of this writing, however.)
+.PP
+A generic system may be built which picks its root device at boot time
+as the ``best'' available device (MASSBUS disks are better than
+SMD UNIBUS disks are better than RK07's; the device must be drive 0
+to be considered.)
+If such a system is booted with the RB_ASKNAME option of (see
+.IR reboot (2V)),
+then the name of the root device is read from the console terminal at boot
+time, and any available device may be used.
+.SH SEE ALSO
+config(8)
+.SH DIAGNOSTICS
+\fBcpu type %d not configured\fR.  You tried to boot UNIX on a cpu
+type which it doesn't (or at least this compiled version of UNIX doesn't)
+understand.
+.PP
+\fBmba%d at tr%d\fR.  A MASSBUS adapter was found in tr%d (the NEXUS
+slot number).  UNIX will call it mba%d.
+.PP
+\fB%d mba's not configured\fR.  More MASSBUS adapters were found on
+the machine than were declared in the machine configuration; the excess
+MASSBUS adapters will not be accessible.
+.PP
+\fBuba%d at tr%d\fR.  A UNIBUS adapter was found in tr%d (the NEXUS
+slot number).  UNIX will call it uba%d.
+.PP
+\fBdr32 unsupported (at tr %d)\fR.  A DR32 interface was found in
+a NEXUS, for which UNIX does not have a driver.
+.PP
+\fBmcr%d at tr%d\fR.  A memory controller was found in tr%d (the NEXUS
+slot number).  UNIX will call it mcr%d.
+.PP
+\fB5 mcr's unsupported\fR.  UNIX supports only 4 memory controllers
+per cpu.
+.PP
+\fBmpm unsupported (at tr%d)\fR.  Multi-port memory is unsupported
+in the sense that UNIX does not know how to poll it for ECC errors.
+.PP
+\fB%s%d at mba%d drive %d\fR.  A tape formatter or a disk was found
+on the MASSBUS; for disks %s%d will look like ``hp0'', for tape formatters
+like ``ht1'' or ``mt1''.  The drive number comes from the unit plug on the drive
+or in the TM formatter (\fBnot\fR on the tape drive; see below).
+.PP
+\fB%s%d at %s%d slave %d\fR.  (For MASSBUS devices).
+Which would look like ``tu0 at ht0 slave 0'' or ``mu0 at mt0 slave 0'',
+where \fBtu0\fR or \fBmu0\fR is the name for the tape device
+and \fBht0\fR or \fBmt0\fR 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).
+UNIX will call the device, e.g., \fBtu0\fR or \fBmu0\fR.
+.PP
+\fB%s%d at uba%d csr %o vec %o ipl %x\fR.  The device %s%d, e.g. dz0
+was found on uba%d at control-status register address %o and with
+device vector %o.  The device interrupted at priority level %x.
+.PP
+\fB%s%d at uba%d csr %o zero vector\fR.  The device did not present
+a valid interrupt vector, rather presented 0 (a passive release condition)
+to the adapter.
+.PP
+\fB%s%d at uba%d csr %o didn't interrupt\fR.  The device did not interrupt,
+likely because it is broken, hung, or not the kind of device it is advertised
+to be.
+.PP
+\fB%s%d at %s%d slave %d\fR.  (For UNIBUS devices).
+Which would look like ``up0 at sc0 slave 0'',
+where \fBup0\fR is the name of a disk drive and \fBsc0\fR is the name
+of the controller.  Analogous to MASSBUS case.
+.SH BUGS
+Should write
+.IR attach (8)
+and system call it needs to work.

diff --git a/usr/man/man4/dn.4 b/usr/man/man4/dn.4
new file mode 100644 (file)
index 0000000..bfa9a2a
--- /dev/null
+++ b/usr/man/man4/dn.4
@@ -0,0 +1,56 @@
+.TH DN 4 12/2/81
+.UC 4
+.SH NAME
+dn \- dn-11 automatic calling unit interface
+.SH SYNOPSIS
+device dn0 at uba0 csr 0175200 vector dnintr
+.SH DESCRIPTION
+A dn-11 is a controller for an automatic calling unit (ACU).
+With a dn-11, a call unit, and a modem
+a computer may dial a telephone number and establish a data link.
+Hardware supporting this interface includes the DEC DN11 and Able
+Quadracall controllers working with either Bell 801 or Racal/Vadic
+801 or 811 call units.
+.PP
+A dn-11 interface can control as many as four call units.
+In normal operation
+a data link is established by opening the file associated with
+a call unit, sending the desired phone number in a single
+.IR write (2)
+operation, then opening the terminal line attached to the appropriate
+outgoing modem.  If the phone call was successful and the remote host
+presented a carrier signal, the open on the terminal line should be
+successful.  At this point the call unit should be closed and a link
+has been established.  This sequence is normally performed for the user
+by one of 
+.IR cu (1),
+.IR uucp (1),
+or
+.IR dnd (8).
+.PP
+Each controller/call unit pair has different programming 
+characteristics which
+impact the programmer; the dn-11 interface presents a
+.I "raw interface"
+rather than imbed local dependencies in the device driver.  For
+example, the Racal/Vadic 811 call unit is multiplexed,
+providing the user with the ability to place phones calls on as many as
+64 separate phone lines from a single interface.  This multiplexing
+is carried out based on the first two digits of the phone number presented
+by the user (the first digit selects the modem's rack and modem type, while
+the second digit selects the specific modem in the rack).
+.PP
+The legal dn-11 dial codes are: \fB0-9\fP, \fB*\fP (\fB:\fP is a synonym),
+\fB#\fP (\fB;\fP is a synonym), \fB=\fP (\fBw\fP is a synonym), and \fB\-\fP.
+A phone number may optionally be terminated with a \fB<\fP or \fBe\fP.
+Phone numbers may be no more than 40 characters long.
+.PP
+By convention /dev/cu[al]0 are connected to a 300 baud interface, while
+/dev/cu[al]1 provides a 1200 baud interface.
+.SH FILES
+.DT
+/dev/cua[0-9]  ACU interfaces
+.br
+/dev/cul[0-9]  associated outgoing terminal line
+.SH "SEE ALSO"
+rv(4)

diff --git a/usr/man/man4/mt.4 b/usr/man/man4/mt.4
new file mode 100644 (file)
index 0000000..95b4879
--- /dev/null
+++ b/usr/man/man4/mt.4
@@ -0,0 +1,43 @@
+.TH MT 4 10/8/81
+.UC 4
+.SH NAME
+mt \- TM-78/TU-78 MASSBUS magtape interface
+.SH SYNOPSIS
+formatter mt0 at mba? drive ?
+.br
+tape mu0 at mt0 slave 0
+.SH DESCRIPTION
+The tm-78/transport combination provides a standard tape drive
+interface as described in
+.IR mtop (4).
+The TU78 provides both 1600 and 6250 bpi,
+runs at 125 ips, and autoloads tapes.
+.SH "SEE ALSO"
+mt(1), tar(1), tp(1), mtop(4), ht(4), tm(4), ts(4)
+.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=%o 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 drive status 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\fR.  An attempt was made to read or space a blank tape.
+.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.

diff --git a/usr/man/man4/mtop.4 b/usr/man/man4/mtop.4
new file mode 100644 (file)
index 0000000..8be0820
--- /dev/null
+++ b/usr/man/man4/mtop.4
@@ -0,0 +1,135 @@
+.TH MTOP 4 10/8/81
+.UC 4
+.SH NAME
+mt \- UNIX magtape interface
+.SH DESCRIPTION
+The files
+.I "mt0, ..., mt15"
+refer to the UNIX magtape drives,
+which may be on the MASSBUS using the TM03 or TM78 formatters
+.IR ht (4)
+or
+.IR mt (4),
+or on the UNIBUS using either the TM11, TS11, or TU45 formatters
+.IR tm (4),
+.IR ts (4)
+or
+.IR ut (4).
+The following description applies to any of the transport/controller pairs.
+The files
+.I "mt0, ..., mt7"
+are low density, and
+.I "mt8, ..., mt15"
+are high density.
+On the TM03 and TM11 low density is 800bpi and high density is 1600bpi.
+On the TM78 low density is 1600bpi and high density is 6250bpi.
+On the TS11 both low and high density are 1600bpi.
+The files
+.I "mt0, ..., mt3"
+and
+.I "mt8, ..., mt11"
+are rewound when closed; the others are not.
+When a file open for writing is closed, two end-of-files are written.
+If the tape is not to be rewound
+it is positioned with the head between the two
+tapemarks.
+.PP
+A standard tape consists of a
+series of 1024 byte records terminated by an
+end-of-file.
+To the extent possible, the system makes
+it possible, if inefficient, to treat
+the tape like any other file.
+Seeks have their usual meaning and it is possible
+to read or write a byte at a time.
+Writing in very small units is inadvisable,
+however, because it tends to create monstrous record
+gaps.
+.PP
+The
+.I mt
+files discussed above are useful
+when it is desired to access the tape in a way
+compatible with ordinary files.
+When foreign tapes are to be dealt with, and especially
+when long records are to be read or written, the
+`raw' interface is appropriate.
+The associated files are named
+.I "rmt0, ..., rmt15,"
+but the same minor-device considerations as for the regular files still apply.
+A number of other ioctl operations are available
+on raw magnetic tape.
+The following definitions are from <sys/mtio.h>:
+.PP
+.nf
+/*
+ * Structures and definitions for mag tape io control commands
+ */
+
+/* mag tape io control commands */
+#define MTIOCTOP       (('m'<<8)|1)    /* do a mag tape op */
+#define MTIOCGET       (('m'<<8)|2)    /* get mag tape status */
+
+/* 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 */
+
+/* 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
+ */
+#define MT_ISTS                01
+#define MT_ISHT                02
+#define MT_ISTM                03
+#define MT_ISMT                04
+#define MT_ISUT                05
+.fi
+.ft R
+.PP
+Each
+.I read
+or
+.I write
+call reads or writes the next record on the tape.
+In the write case the record has the same length as the
+buffer given.
+During a read, the record size is passed
+back as the number of bytes read, provided it is no greater
+than the buffer size;
+if the record is long, an error is indicated.
+In raw tape I/O seeks are ignored.
+A zero byte count is returned when a tape mark is read,
+but another read will fetch the first record of the
+new tape file.
+.SH FILES
+/dev/mt?,
+/dev/rmt?
+.SH "SEE ALSO"
+mt(1), tar(1), tp(1), ht(4), mt(4), tm(4), ts(4)
+.SH BUGS

diff --git a/usr/man/man4/ra.4 b/usr/man/man4/ra.4
new file mode 100644 (file)
index 0000000..efb078f
--- /dev/null
+++ b/usr/man/man4/ra.4
@@ -0,0 +1,134 @@
+.TH RA 4 10/8/81
+.UC 4
+.SH NAME
+ra \- UDA50/RA80 Unibus disk controller and drives
+.SH SYNOPSIS
+controller uda0 at uba? csr 0177550 vector udintr
+.br
+disk ra0 at uda0 drive 0
+.SH DESCRIPTION
+The UDA50 is an intelligent disk controller for the UNIBUS.
+It supports the RA80 124MB disk drive.
+.PP
+Files with minor device numbers 0 through 7 refer to various portions
+of drive 0;
+minor devices 8 through 15 refer to drive 1, etc.
+The standard device names begin with ``ra'' followed by
+the drive number and then a letter a-h for partitions 0-7 respectively.
+The character ? stands here for a drive number in the range 0-7.
+.PP
+The origin and size of the pseudo-disks on each drive are
+as follows:
+.PP
+.nf
+.ta .5i +\w'000000    'u +\w'000000    'u
+RA80 124M drive partitions:
+       disk    start   length
+       ra?a    0       15884
+       ra?b    15884   33440
+       ra?c    0       237298
+       ra?d    0       0
+       ra?e    0       0
+       ra?f    0       0
+       ra?g    49324   82080
+       ra?h    131404  105994
+.DT
+.fi
+.PP
+It is unwise for all of these files to be present in one installation,
+since there is overlap in addresses and protection becomes
+a sticky matter.
+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).
+Both ra?g and ra?h are used to map the
+remaining cylinders.
+.PP
+The block files access the disk via the system's normal
+buffering mechanism and may be read and written without regard to
+physical disk records.  There is also a `raw' interface
+which provides for direct transmission between the disk
+and the user's read or write buffer.
+A single read or write call results in exactly one I/O operation
+and therefore raw I/O is considerably more efficient when
+many words are transmitted.  The names of the raw files
+conventionally begin with an extra `r.'
+.PP
+In raw I/O counts should be a multiple of 512 bytes (a disk sector).
+Likewise
+.I seek
+calls should specify a multiple of 512 bytes.
+.SH FILES
+/dev/ra[0-7][a-h]      block files
+.br
+/dev/rra[0-7][a-h]     raw files
+.SH SEE ALSO
+hk(4), hp(4), up(4)
+.SH DIAGNOSTICS
+\fBra%d%c: hard error sn%d udasa %o, state %d\fR.
+.br
+\fBra%d%c: hard error sn%d status %o\fR.
+An unrecoverable
+error occured during transfer of the specified sector of the specified
+disk partition.  The contents of the udasa register are printed
+in octal and symbolically with bits decoded.  The internal state is also
+printed.  In the second form, the MSCP status is printed.
+The error was either unrecoverable, or a large number of retry attempts
+(including offset positioning and drive recalibration) could not
+recover the error.
+.PP
+\fBra%d%c: hard error sn%d OFFLINE\fR.  The drive was spun down or off
+line when it was accessed.  The i/o operation is not recoverable.
+.PP
+\fBuda%d: random interrupt ignored\fR.  The UDA received an interrupt
+before it was initialized.
+.PP
+\fBuda%d: fatal error (%o)\fR.  A fatal error was noticed in the UDA
+interrupt routine.  The contents of udasa are printed.  The controller
+will be reinitialized.
+.PP
+\fBuda%d: [soft|hard] error, controller error, event 0%o\fR.
+.br
+\fBuda%d: [soft|hard] error, host memory access error, event 0%o, addr 0%o\fR.
+.br
+\fBuda%d: [soft|hard] error, disk transfer error, unit %d, grp %d, cyl %d,
+sec %d, trk %d, lbn %d, retry %d, level %d\fR.
+.br
+\fBuda%d: [soft|hard] error, SDI error, unit %d, event 0%o, cyl %d\fR.
+.br
+\fBuda%d: [soft|hard] error, small disk error, unit %d, event 0%o, cyl %d\fR.
+.br
+\fBuda%d: [soft|hard] error, unknown error, unit %d, format 0%o, event 0%o\fR.
+.br
+See the driver and the UDA and MSCP manuals.
+.SH BUGS
+In raw I/O
+.I read
+and
+.IR write (2)
+truncate file offsets to 512-byte block boundaries,
+and
+.I write
+scribbles on the tail of incomplete blocks.
+Thus,
+in programs that are likely to access raw devices,
+.I read, write
+and
+.IR lseek (2)
+should always deal in 512-byte multiples.
+.PP
+A program to analyze the logged error information (even in its
+present reduced form) is needed.  Error messages should be more
+consistent.
+.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
+Dumps to the swap area on system crashes are not implemented.
+.PP
+Booting via block zero is not (and will not be) supported.  The ``boot''
+program must be loaded from the console storage device.
+.PP
+Although the device supports unit numbers up to 255, the driver only
+supports unit numbers up to 7.

diff --git a/usr/man/man4/tm.4 b/usr/man/man4/tm.4
new file mode 100644 (file)
index 0000000..540788c
--- /dev/null
+++ b/usr/man/man4/tm.4
@@ -0,0 +1,49 @@
+.TH TM 4 5/10/81
+.UC 4
+.SH NAME
+tm \- TM-11/TE-10 magtape interface
+.SH SYNOPSIS
+controller tm0 at uba? csr 0172520 vector tmintr
+.br
+tape te0 at tm0 drive 0
+.SH DESCRIPTION
+The tm-11/te-10 combination provides a standard tape drive
+interface as described in
+.IR mt (4).
+Hardware implementing this on the VAX is typified by the Emulex TC-11
+controller operating with a Kennedy model 9300 tape transport,
+providing 800 and 1600 bpi operation at 125 ips.
+.SH "SEE ALSO"
+mt(1), tar(1), tp(1), ht(4), mt(4), ts(4)
+.SH DIAGNOSTICS
+\fBte%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
+\fBte%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
+\fBte%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
+\fBte%d: hard error bn%d er=%b\fR.   A tape error occurred
+at block \fIbn\fR; 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
+\fBte%d: lost interrupt\fR.  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.
+.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.

diff --git a/usr/man/man4/ts.4 b/usr/man/man4/ts.4
new file mode 100644 (file)
index 0000000..50671a3
--- /dev/null
+++ b/usr/man/man4/ts.4
@@ -0,0 +1,41 @@
+.TH TS 4 5/10/81
+.UC 4
+.SH NAME
+ts \- TS-11 magtape interface
+.SH SYNOPSIS
+controller zs0 at uba? csr 0172520 vector tsintr
+.br
+tape ts0 at zs0 drive 0
+.SH DESCRIPTION
+The ts-11 combination provides a standard tape drive
+interface as described in
+.IR mt (4).
+The ts-11 operates only at 1600 bpi, and only one transport
+is possible per controller.
+.SH "SEE ALSO"
+mt(1), tar(1), tp(1), ht(4), mt(4), tm(4), ut(4)
+.SH DIAGNOSTICS
+\fBts%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
+\fBts%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
+\fBts%d: hard error bn%d xs0=%b\fR.  A hard error occurred on the tape
+at block \fIbn\fR; status register 0 is printed in octal and symbolically
+decoded as bits.
+.SH BUGS
+If any non-data error is encountered on non-raw tape, it refuses to do anything
+more until closed.
+.PP
+The device lives at the same address as a tm-11
+.IR tm (4);
+as it is very difficult to get this device to interrupt, a generic
+system assumes that a ts is present whenever no tm-11 exists but
+the csr responds and a ts-11 is configured.
+This does no harm as long as a non-existant ts-11 is not accessed.
+.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.

diff --git a/usr/man/man4/tu.4 b/usr/man/man4/tu.4
new file mode 100644 (file)
index 0000000..63e4e30
--- /dev/null
+++ b/usr/man/man4/tu.4
@@ -0,0 +1,27 @@
+.TH TU 4 10/8/81
+.UC 4
+.SH NAME
+tu \- console TU58 interface
+.SH DESCRIPTION
+.PP
+This is a simple interface to the TU58
+cassette tape unit, which is part of the console
+subsytem for VAX-11/750's.
+Access is given to the entire
+tape consisting of 1024 blocks of 512 bytes.
+.PP
+The TU58 behaves like a disk but has only a block interface (no raw).
+The cassette is commonly accessed via the
+.IR arff (8)
+command, using the `m' flag.
+.SH FILES
+/dev/floppy
+.SH SEE ALSO
+arff(8)
+.SH DIAGNOSTICS
+Lots, mostly cryptic.  Read the driver.
+.SH BUGS
+The driver is very unreliable due to the nature of the TU58 interface.
+The TU58 should be used only when the system is in single-user mode,
+since it is often necessary to reboot the system to unhang the process
+accessing the TU58.