[5903] in linux-scsi channel archive
Re: WG: AW: cdrecord problems on recent Linux versions
daemon@ATHENA.MIT.EDU (Joerg Schilling)
Fri Feb 12 09:27:16 1999
Date: Fri, 12 Feb 1999 14:57:42 +0100 (MET)
From: Joerg Schilling <schilling@fokus.gmd.de>
To: Dominik.Stadler@btk.de, axboe@image.dk, bsc@fleggaard.dk,
cdwrite@lists.debian.org, dgilbert@interlog.com,
heiko_eissfeldt@z.detesystem.de, linux-scsi@vger.rutgers.edu,
michaels@stochastik.rwth-aachen.de, rgooch@atnf.csiro.au,
schilling@fokus.gmd.de, xiphmont@mit.edu
>From cdwrite-request@other.debian.org Fri Feb 12 02:44:49 1999
>From: Monty <xiphmont@mit.edu>
>Michael wrote:
>>I must admit I came rather late into this thread, so I don't
>>understand what you mean by "requiring attachment".
>Under CAM, a generic scsi device does not refer to any particular
>piece of hardware. The device is oppened, then attached to a specific
>bus:target:lun combination.
This is no idea that is foreign to UNIX.
Note that SCSI is a protocol.
Well TCP/IP is a protocol too.
Let's assume you want to talk to your second 'hme' Interface.
HME stands for Happy Meal Ethernet.
The Happy Meal Hardware is the successor to the BIG MAC
Hardware (MAC is Medium Access Layer ;-)
To do this, you open /dev/hme and at this point there is no
hardware associated to /dev/hme.
If you like to talk to hme2, you need to send a
DL_ATTACH_PPA request message to the driver. This message then
will attach your cloned driver to a physical point of attachment.
So why don't you like to use the same semantics in SCSI?
Jörg
EMail:joerg@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
js@cs.tu-berlin.de (uni) If you don't have iso-8859-1
schilling@fokus.gmd.de (work) chars I am J"org Schilling
URL: http://www.fokus.gmd.de/usr/schilling ftp://ftp.fokus.gmd.de/pub/unix
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
