06-04-2008
They are both the same type of objects. I don't know what os you're using so I talk talk specificly to that. But imagine a version of unix with device files like /dev/mt0 to talk to a tape drive. Any device file has a major and a minor number. The major number identifies which driver is being used. The minor number is passed to the driver for its use. It the case of a typical mt driver, it ids the particular tape drive. So you can open /dev/mt0 and read or write to the tape drive via it. You can also invoke the ioctl system call for special purposes like rewinding the tape. This is the typical type a tape driver that existed for years and it is what you call a "named device".
Now someone invents a new type of tape drive that can hold 5 tapes. How to control that? The mt ioctl doesn't handle stuff like that. Well one answer is to redefine the rewind or the unload command to now mean "go to the next tape". A lot of juke box style drives do just that and call it stacker mode. But we want something more... we want to just jump to tape number 4 (as an example) regardless of where we were. The tape drive can do that but the mt driver doesn't have a way to send the right command. All we need is some quick a dirty way to send a particular scsi command to the tape drive. This is where the pass-though driver comes in. It does not know it is controlling a tape drive. But you can give it a scsi command and it can send it to the device. And it can even return a status code. But that is it. It just passes simple commands to a device. Now a real smart program figures out what scsi command is needed to jump to tape number 4, it uses the pass though driver to send it, and it gets a status code back. So now we are using a secondary driver to access extra device features that the primary driver can't control.
But the pass through device is a special file too with a major and minor number. You don't use it to tranfer large blocks of data though. Just special commands.
In this case both special files referred to the same device. But often there will be a collection of tape drives in a juke box with a single pass-though device for the box itself.
We would use the mt driver where we can. And we use the pass-though driver only when we must. Drivers like mt have a man page that describes which ioctl command it can do. Pass though drivers usually have sparse man pages because you can't document all possible scsi commands.
10 More Discussions You Might Find Interesting
1. HP-UX
Is it possible to create the CDROM device file for a drive attached to the parallel port? I have a removable CDROM drive (gift - I'm trying not to return it, but may have to anyways) that attaches via parallel port. The only device that I can attach to that hardware address is /dev/c1t0d0_lp, a... (9 Replies)
Discussion started by: LivinFree
9 Replies
2. UNIX for Dummies Questions & Answers
Hi
I am trying to determine the access to unix devices. I found the follow access description which I have been told is a symbolic link and is not the actual file. I was also told that all symbolic links will have rwxrwxrwx access.
kmem: lrwxrwxrwx 1 root 27 May 28 16:06 /dev/kmem ->... (2 Replies)
Discussion started by: GW01
2 Replies
3. UNIX for Dummies Questions & Answers
I am new in unix, and I need to fix a printer, but I don't even know the difference between /dev/ttys printers and lp printers. Can someone explain this to me and tell me how I cancel jobs in both of them?
I will appreciate it, thank you. (15 Replies)
Discussion started by: HN19
15 Replies
4. Red Hat
I am trying to get a flash card reader to work with my machine. My question is, are all of my USB ports screwed up? Do I need to buy a seperate USB controller? I does not appear that the onboard USB ports work.
In trying to get it to work, I typed cat /proc/scsi/scsi and got this:
# cat... (2 Replies)
Discussion started by: davidkretsch
2 Replies
5. Solaris
I have added a sun storage array from a faiulty server onto a new server and copied the md.conf files etc. I can now access the /dev/md/dsk file systems, but I want to delete some metadevices that do not exist (it still thinks the 0 and 1 (root /var /export) disk are mirrored. How do I do this? (8 Replies)
Discussion started by: ozzmosiz
8 Replies
6. Solaris
Hi all,
what does this mean?
if
then
<something>
fi
here is what i know..
it checks if the specified argument no($devid) in some function call is made into a block device and then proceeds with the execution of the loop.
However am not understand what lofi@0:means?
also is there... (3 Replies)
Discussion started by: wrapster
3 Replies
7. UNIX for Dummies Questions & Answers
Hi folks,
I am trying to learn Unix based in Linux...
In Linux, in /Dev are files related to cards, mouse, etc..
how about Unix?
What is the difference between /Dev and /Devices?
Thanks,
Fernanda (0 Replies)
Discussion started by: ffpradella
0 Replies
8. HP-UX
Hi,
I need to rediracte all the names of the devices (only disks) to a file.
Thanks:confused: (3 Replies)
Discussion started by: yoavbe
3 Replies
9. Programming
Hi guys.
what is the benefits of using raw devices in programming?
which applications mostly use raw devices?
how can i use raw devices in C programs? is there any system calls or library functions? (1 Reply)
Discussion started by: majid.merkava
1 Replies
10. Red Hat
Can you please modify my script. This script is not working
for i in /dev/sdf
do
/bin/raw /dev/raw/`/bin/basename ${i}` ${i}
/bin/sleep 2
/bin/chown orasm:ordba /dev/raw/`/bin/basename ${i}`
/bin/chmod 660... (9 Replies)
Discussion started by: karthik9358
9 Replies
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)