Unix/Linux Go Back    

BSD 2.11 - man page for tm (bsd section 4)

Linux & Unix Commands - Search Man Pages
Man Page or Keyword Search:   man
Select Man Page Set:       apropos Keyword Search (sections above)

TM(4)											    TM(4)

       tm - TM-11/TE-10 magtape interface

	    # Setting AVIVTM configures the TM driver for the AVIV 800/1600/6250
	    # controller.  For more details, see /sys/pdpuba/tm.c.
	    NTM    tm_drives # TM11
	    AVIVTM YES	     # AVIV 800/1600/6250 controller

	    #Name Unit# Addr   Vector Br Handler(s)	 # Comments
	    tm	  ?	172520 224    5  tmintr 	 # tm11 driver

       major device number(s):
	    raw: 7
	    block: 1
       minor device encoding:
	    bits 0003 specify TS drive
	    bit  0004 specifies no-rewind operation
	    bits 0030 specify recording density:
		 0000:	 800BPI
		 0010:	1600BPI (AVIVTM and some other controllers)
		 0020:	6250BPI (AVIVTM only)

       The  tm-11/te-10  combination  provides	a  standard  tape drive interface as described in
       mtio(4).  The standard DEC tm-11 operates only at 800 bpi.  Other controllers of this type
       may also allow operation at 1600 bpi, under software control or by switching manually.

       /dev/MAKEDEV	   script to create special files
       /dev/MAKEDEV.local  script to localize special files

       mt(1), tar(1), tp(1), mtio(4), ht(4), ts(4), mt(4), dtab(5), autoconfig(8)

       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

       te%d:  not online.  An attempt was made to access the tape while it was offline; this mes-
       sage is written on the terminal of the user who tried to access the tape.

       te%d: can't change density in mid-tape.	An attempt was made to write on a tape at a  dif-
       ferent  density than is already recorded on the tape.  This message is written on the ter-
       minal of the user who tried to switch the density.

       te%d: hard error bn%d er=%b.   A tape error occurred at block 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.

       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.

       If any non-data error is encountered on non-raw tape, it refuses to do anything more until

3rd Berkeley Distribution		 January 28, 1988				    TM(4)
Unix & Linux Commands & Man Pages : ©2000 - 2018 Unix and Linux Forums

All times are GMT -4. The time now is 07:44 AM.