Meelis Roos wrote:
> So in order to use a scsi cd-writer, you just plug it in. In order to use IDE
> (ATAPI) cd-writer, a glue layer is needed to represent ATAPI (which is really
> SCSI-packets-over-IDE-bus) as SCSI to the programs. Ide-scsi driver is the glue
> layer to make cd-writers accessible.
Ok, but why isn't this glue on my /dev/hdd, or just loaded "magically"
when a program
needs to access my /dev/hdd via the SCSI API?
It's just annoying to configure this in the kernel (and recompile) each
time. Because
if you have ide-cd support then it cames first. Is there any way (even
for a program),
to lock the ide-cd thing, and use the SCSI API on this device?? say
/dev/hdd??
My experience is that most distributions ship with ide-cd by default. If
I want my
ide-cdwriter to work, then recompile, and turn off (module) the ide-cd
thing or
use append "hdd=ide-scsi" on my lilo.conf that is worst. Oh! and then,
lets go
see my gtcd cd player not being able to modify volume (when it works
using ide-cd!).
Can't someone come up with an _easy_ solution?
You know, question about these configuration issues / problems came from
beginners
all the time...
--
Manuel Clos,
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
