sfgd> What you see is a result of a design flaw in the Linux kernel:
sfgd> A "natural" implementation would look like this:
sfgd> - one or more SCSI parallel Host adapter drivers
sfgd> - one oe more SCSI serial Host adapter drivers (e.g. ieee 1034 ??? Fire
wire)
sfgd> - one or more IDE packet SCSI hostadapter drivers
sfgd> All working with a single SCSI glue library to:
sfgd> - CD-ROM driver
sfgd> - Tape driver
sfgd> ...
AFAIK this is how Linux works. There are host adapters - real adapters,
ide-scsi virtual adapter, usb/i2o/parallel adapters (don't know whether IEEE
1394 scsi exists already). And then there are general high-level drivers liks
scsi disks, scsi cdroms, scsi tapes etc. The same scsi cdrom driver is used
for "real" scsi cdroms and ide cdrom (in case the ide interface uses ide-scsi
virtual host adapter). I see no problem with Linux. I think you are seeing
hallucinations (sp?) here.
The original problem was with choosing between ide-scsi (the virtual scsi
adapter that takes over an ide interface) and native ide cdrom driver (ide-cd)
for this interface. I find it natural that the generic scsi interface needs a
scsi host adapter (virtual or not) below it to function. So ide-scsi must be
used with this ide interface, not ide-cd. The cdrom becomes scsi cdrom to the
rest of the system - so what?
--
Meelis Roos ([EMAIL PROTECTED])
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
