Mike Andrew wrote: > 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. >
Agreed. > 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. > Agreed. > 3) ide-floppy >>>>IS<<<<< the driver for ide zips and ls120's. Period. > > it is NOT for floppies per se. > Agreed. > 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. > > This is contrary to my experience yesterday. I have one other SCSI device, my scsi CD-RW, scd0 (sr0). I'm fairly certain I tried mounting sda AND sda4, no go (mighta even tried sda1, 2 and 3...). I know tried various sdX4 devices, none of which would mount. What works, as I mentioned in my previous post, is loading the ide-floppy module before ide-scsi. When i do this, I can mount the device hdc4 as my Zip drive. Now if what you're telling me is true, and ide-floppy is a subset of ide-scsi, there should be no reason why I need to load ide-floppy to get access to the Zip drive. And this may well be true. I know that I tried insmod'ing ide-floppy after ide-scsi was already loaded and I couldn't find the drive anywhere. This is worth more experimentation and when I get home, I'll play around with it a little more. Regards, Tim -- Caldera eWorkstation 3.1, Kernel 2.4.9, KDE 2.2.1, XFree86 4.1.0 _______________________________________________ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
