On Mon, 14 Jan 2002 06:36, Tim Wunder wrote: > Previously, Tim Wunder chose to write: > <snip>
[slash] [snippety] [hack] 1) network issues are irrelevant, look elsewhere. 2) paride is required for any parallel connected zip, ls120 or backpack device. It, and all it's associated drivers (pf, epat etc) are TOTALLY irrelevant to your ide based zip drive. Compile or no compile, they make no difference. 3) ide-floppy >>>>IS<<<<< the driver for ide zips and ls120's. Period. it is NOT for floppies per se. 4) ide-scsi (surprise surprise) will serve as a REPLACEMENT to ide-floppy. Why? Because ide-floppy is a cut down lean and mean ide-scsi. (so too, ide-tape) ide-floppy MUST be hard wired. Meaning it must either be part of the inittab process for the distro. Eg: /etc/rc.d/rc.local for RH, /etc/modules/default for Caldera. OR, it must be compiled monolothic. OR you can invoke ide-scsi Either way, you *also* require sd_mod.o and scsi-mod.o to load. (These normally autoload on an /sbin/mount) The resulting device name from either method is /dev/sdX (a hard drive) The problem you are having (with either method) is discovering where the hell your *&%%&*(* /dev/sdXn device got to!!! The reason is that the scsi base module (scsi_mod.o) will assign device names on a first come, first served basis. If you have no other scsi devices in your system, it's /dev/sda. Otherwise it depends solely on what gets loaded first. see bulk storage-> zip->internal->ide on the site below for a topology of the modules required. -- 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
