On Tuesday 23 October 2001 04:42, Susan Machia wrote: [snip]
There ARE differences between Kernel 2.2.x (RH7.0) and 2.4.x (RH7.1). They are not Redhat related (except for kudzu). The bottom line is this. There is no such thing as an 'ide cd burner' program (you never said that). All linux burning software ultimately relies on the console only app: cdrecord. And cdrecord knows only about scsi. To get round this, you need to use a wedge module called ide-scsi. It converts scsi commands to ide. Secondly, the ide-cdrom module (intentionally) does not recognise cd-rw devices, you must use ide-scsi to access them. Regardles of kernel, ide-scsi scans the ide channels for UNregistered devices. Anything UNregistered becomes a scsi device. This therefore does not apply to the ide hard drives because they are compiled monolithic, ergo registered, does not apply to any other monolothic driver (sometimes ide-cd) and does not apply to any device 'registered' via a module prior to invoking ide-scsi. The bottom line here is that ide-scsi will make your cd-rom device a scsi device node, if you let it. You don't let it by pre-loading the given device driver BEFORE ide-scsi.o Preloading modules is done via (Caldera=/etc/modules/default) and (Redhat=/etc/rc.d/rc.local). You place the order of module load thusly. modprobe ide-cd modprobe ide-floppy # for ls120/zip modprobe ide-scsi In fact, the need to do so is not there since the equivalent scsi access to these devices is just as good. It's more a question of not getting confused with what used to be a /dev/hd? node becoming a /dev/<scsi> node and the modifications to fstab you would need to do. There is one good reason however for forcing above, and that is because scsi device addressing is a piece of crap waiting to happen. You can never be certain which /dev/srX you're looking at. ---- HOWEVER, In a 2.2..x kernel, the append statement is required at boot time due to some 'bug' specifically related to the cd burning device node access. Delving into why isn't interesting because 2.2x is dead. The effect is that all devices (other than monolithic drivers noted above) become /dev/<scsi> device nodes. And by /dev/<scsi> i simply mean the names sr0. scd0 etc dependent on the module accessed. Finally, once you move up to kernel 2.4.x, but specifically, RH7.1 kudzu, there are further flies in the ointment. Kudzu is intelligent and 'understands; these driver anomolies. If say you are running KDE on RH7.1, kde itself autoprobes for cd-style devices, and attempts to automont them. Kudzu then gets in the act, recognises a conflict between ide-scsi.o and ide-cd and ensures ide-cd is loaded first. This is the basic scenario, the very common one, of having both a burner and a reader in the same system. You can add variations to the theme with ls120 and and ide zip drives. Essentially, for a zip, the ide-floppy.o module is crippled because ide-scsi does a better job of it, versus ls120 where the ide-floppy is invoked prior to ide-scsi. Hope this is all clearer than mud. -- http://linux.nf -- [EMAIL PROTECTED] _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com _______________________________________________ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
