>From: Manuel Clos <[EMAIL PROTECTED]>
>After running Linux for two years, from zero to being a losely programer
>I have never
>understood why ide-scsi. I know it is to make able to send SCSI command
>over IDE, but then
>my /dev/hdd is gone, and now I have a /dev/scd0 that _moves_ to scd1
>whenever I connect some
>other CD. What I wish is my ATAPI CD behaving like it should.
>Can someone please explain me the technical/hystorical reason for such a
>thing?
>I'm very excited about understanding this.
What you see is a result of a design flaw in the Linux kernel:
A "natural" implementation would look like this:
- one or more SCSI parallel Host adapter drivers
- one oe more SCSI serial Host adapter drivers (e.g. ieee 1034 ??? Fire
wire)
- one or more IDE packet SCSI hostadapter drivers
All working with a single SCSI glue library to:
- CD-ROM driver
- Tape driver
...
Well as it seems that there is no co-ordination between different driver groups
for the Linux kernel, you now have two SCSI CD-ROM drivers :-(
- One sending SCSI commands directly to the SCSI glue layer
- One wrapping SCSI commands into ATAPI IDE packets
If the driver structure would follow the natural way of device definitions,
there would only be one SCSI-CD-ROM driver and you would have no problem
to use cdrecord on a standard kernel.
A possible solution would be to talk to the driver developers and please them
to make the natural way the default Linux configuration.
J�rg
EMail:[EMAIL PROTECTED] (home) J�rg Schilling D-13353 Berlin
[EMAIL PROTECTED] (uni) If you don't have iso-8859-1
[EMAIL PROTECTED] (work) chars I am J"org Schilling
URL: http://www.fokus.gmd.de/usr/schilling ftp://ftp.fokus.gmd.de/pub/unix
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
