TS(4) Kernel Interfaces Manual TS(4)NAME
ts - TS-11 magtape interface
NTS ts_drives # TS11
#Name Unit# Addr Vector Br Handler(s) # Comments
ts ? 172520 224 5 tsintr # ts11 driver
major device number(s):
minor device encoding:
bits 0003 specify TS drive
bit 0004 specifies no-rewind operation
bit 0010 ignored
The ts-11 combination provides a standard tape drive interface as described in mtio(4). The ts-11 operates only at 1600 bpi, and only one
transport is possible per controller.
/dev/MAKEDEV script to create special files
/dev/MAKEDEV.local script to localize special files
SEE ALSO mt(1), tar(1), tp(1), mtio(4), ht(4), tm(4), dtab(5), autoconfig(8)DIAGNOSTICS
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 termi-
nal of the user who tried to access the tape.
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.
ts%d: hard error bn%d xs0=%b xs1=%b xs2=%b xs3=%b. A hard error occurred on the tape at block bn; status registers 0-3 are printed in
octal and symbolically decoded as bits.
ts%d: addr mod 4 != 0. The address of a TS-11 command packet was not on an even longword boundary.
If any non-data error is encountered on non-raw tape, it refuses to do anything more until closed.
The device lives at the same address as a tm-11 tm(4).
3rd Berkeley Distribution January 28, 1988 TS(4)
Check Out this Related Man Page
HT(4) Kernel Interfaces Manual HT(4)NAME
ht - RH-11/TU-16 magtape interface
The files mt0, mt1, ... refer to the DEC RH/TM/TU16 magtape. When opened for reading or writing, the tape is not rewound. When closed,
it is rewound (unless the 0200 bit is on, see below). If the tape was open for writing, a double end-of-file is written. If the tape is
not to be rewound the tape is backspaced to just between the two tapemarks.
A standard tape consists of a series of 512 byte records terminated by a double 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.
The last octal digit of the minor device number selects the drive. The middle digit selects a controller. The initial digit is even to
select 800 BPI, odd to select 1600 BPI. If the 0200 bit is on (initial digit 2 or 3), the tape is not rewound on close. Note that the
minor device number has no necessary connection with the file name, and in fact tp(1) turns the short name x into `/dev/mtx'.
The 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
may be named rmt0, ..., rmt7, but the same minor-device considerations as for the regular files still apply.
Each read or 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, the buffer must begin on a word boundary and the count must be even. Seeks are ignored. A
zero count is returned when a tape mark is read; another read will fetch the first record of the next tape file.
SEE ALSO tp(1)BUGS
The magtape system is supposed to be able to take 64 drives. Such addressing has never been tried.
Taking a drive off line, or running off the end of tape, while writing have been known to hang the system.
If any non-data error is encountered, it refuses to do anything more until closed. In raw I/O, there should be a way to perform forward
and backward record and file spacing and to write an EOF mark explicitly.