> >cdrecord has a problem with SCSI-(RAID)-Controllers that don't allocate a
> >ne scsibus for each Channels.
>
>
> This is a problem with the Linux SCSI driver structure.
>
>
> >Yesterday i got a 5 Channel FAST-SCSI RAID-Controller (ICP-Vortex)
>
> >I have 4 CD-Rs and every one has a dedicated channel on the new
> >Controller. First i had configured every CD-R to ID-0. But then cdrecord
> >could only see the first one. Now i configured every drive with diffrent
> >IDs (cdrecord -scanbus attached). But that's not "the(tm)" solution.
>
> >AFAIK other OSses use "Adapter,Channel,ID,Lun" Adresses too. Why does
> >cdrecord "only" use "scsibus,ID,Lun" (Hmmm. Do ANY cases exist where the
> >LUNs are needed? (i only know 1 case, SCSI2SCSI-Bridges which map the ID
> >from the "slave"-Channels to LUNs of the ID on the Main-Channel. But i
> >think those bridges are "unusual")
>
>
> Cdrecord uses what the standard addressing scheme with SCSI is.
>
> A SCSI Bus is an entity where the SCSI ANSI T10 adressing scheme is valid.
>
> T10 defines Target & Lun, the bus is the only layer above.
>
> If you read the Linux SCSI sources it is easy to find that Linux is wrong.
> Linux calls a SCSI adapterCARD a Bus which has nothing to do with a SCSI bus.
OK. "Fixed" with the newer driver-Version (cdrecord -scanbus looks "cool"
with scsibus0 up to scsibus8)
Bis denn
--
Real Programmers consider "what you see is what you get" to be just as
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated,
cryptic, powerful, unforgiving, dangerous.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
