>: What dist/version are you running?
>It is, I believe, the newer of the 100 MB parallel port zip drives. I'm
>not at home now but the cable has "autodetect" or something like that written
>on it. The OS is Red Hat 6.0 with the pre-compiled SMP kernel.
That is the cable they made for the ZipPlus, so you should use the imm driver.
>I can't remember if someone told me, or if I just assumed, that if /dev/sda4
>wasn't a valid partition on my hard drive the ZIP drive would take it.
>(I would have bought a SCSI ZIP drive but I received it as a gift.)
I think that the drive is assigned the first available *letter*.
Your first scsi hard drive is /dev/sda; the second is /dev/sdb; ....
When you run out of real drives, the next letter should be used for
the Zip. On that device, the fourth partition is the one that Iomega
If the driver has been loaded, various logs will have been written.
Others have written about how you can find them. There is also a file
in /proc (I think it is called /proc/partitions) that will show all
partitions (and the disks containing them). Generally, /proc is the
place to look for an efficient statement of the current state of the
system. I think I once noticed that loading the driver while there
was no disk in the Zip drive will give an entry for the whole disk,
but no partitons identified until you force the system to read the
partition table. You can probably just ask to mount the partition
where you know it will be found, but fdisk definitely does read the
partition table, so it will teach the system all it needs to know
about the layout of a disk.
R. T. Bumby ** Rutgers Math || Amer. Math. Monthly Problems Editor 1992--1996
Telephone: [USA] 732-445-0277 (full-time message line) FAX 732-445-5530