Sponsored Content
Full Discussion: mt -f
Top Forums UNIX for Dummies Questions & Answers mt -f Post 10001 by Perderabo on Tuesday 6th of November 2001 10:27:40 AM
Old 11-06-2001
On Suns a "ls -lL /dev/rmt/*" will give you a better idea of whats happening. You don't have too many special files, it's supposed to work that way. Each file specifies various different behaviors to be applied during open, read, write, and close calls on that device.

Your example is just rewinding the tape. This is one case where it doesn't matter. It doesn't matter what tape density you pick since rewind is rewind. It doesn't matter is there is an automatic rewind when you close the device since you did a rewind anyway. It doesn't matter what woulda happened had you tried to read past EOF since you didn't. So yes, in the example of just rewinding the tape, it doesn't matter. But someday maybe you will do something with your tape drive besides rewinding a tape. Smilie Then it will matter.

The various options are documented on Suns on the mtio man page. Read that and see if you still have any questions.
 
TS(4)							     Kernel Interfaces Manual							     TS(4)

NAME
ts - TS-11 magtape interface SYNOPSIS
/sys/conf/SYSTEM: NTS ts_drives # TS11 /etc/dtab: #Name Unit# Addr Vector Br Handler(s) # Comments ts ? 172520 224 5 tsintr # ts11 driver major device number(s): raw: 8 block: 2 minor device encoding: bits 0003 specify TS drive bit 0004 specifies no-rewind operation bit 0010 ignored DESCRIPTION
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. FILES
/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. BUGS
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)
All times are GMT -4. The time now is 01:04 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy