Not sure where to start... I plugged it in and Fedora found it as a cdrom (/dev/cdrom2) and it is read-only.

here is the line that Fedora added to /etc/fdisk:

/dev/cdrom1 /mnt/cdrom1 udf,iso9660 noauto,owner,kudzu,ro 0 0

Any help would be appreciated.

Interesting.
Look at the output of dmesg. What are the messages relating to the drive?

I did a find / -name dsmesg
as root and nothing was found.

Since my first posting, I found this on sourceforge:
http://sourceforge.net/docman/displa...roup_id=101444

I set it up as suggested. I can find the drive and access it, but I cannot write to it (it is mounted as read-only.)

thanks

df -h reveals:
Filesystem Size Used Avail Use% Mounted on
/dev/scd0 23M 23M 0 100% /mnt/rev

/sbin/fdisk -l
shows nothing related to the rev

Here is my fstab:
/dev/rev /mnt/rev udf,iso9660 noauto,user,kudzu,rw 0 0


Here is my /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: Iomega Model: RRD Rev: 74.B
Type: CD-ROM ANSI SCSI revision: 02

ls -l /dev/rev
lrwxrwxrwx 1 root root 9 Dec 9 21:36 /dev/rev -> /dev/scd0


ls -l /dev/scd*
brw------- 1 jordan disk 11, 0 Feb 23 2004 /dev/scd0
brw-rw---- 1 root disk 11, 1 Feb 23 2004 /dev/scd1
brw-rw---- 1 root disk 11, 2 Feb 23 2004 /dev/scd2
brw-rw---- 1 root disk 11, 3 Feb 23 2004 /dev/scd3
brw-rw---- 1 root disk 11, 4 Feb 23 2004 /dev/scd4
brw-rw---- 1 root disk 11, 5 Feb 23 2004 /dev/scd5
brw-rw---- 1 root disk 11, 6 Feb 23 2004 /dev/scd6
brw-rw---- 1 root disk 11, 7 Feb 23 2004 /dev/scd7


(note /dev/scd0 was brw-rw---- and owned by root at one time...)
I changed it back and linux changed it again..

The problem is I can't write to this device and it is the wrong size!

thanks

Here is what I get when I fsck my zip (250) drive:
[root@dot mnt]# /sbin/fsck /dev/sda4
fsck 1.35 (28-Feb-2004)
dosfsck 2.8, 28 Feb 2001, FAT32, LFN
/dev/sda4: 2240 files, 7592/49039 clusters


Here is what I get when I fsck my iomega (rev) drive:
[root@dot mnt]# /sbin/fsck /dev/rev
fsck 1.35 (28-Feb-2004)
fsck: fsck.udf: not found
/sbin/fsck: Error 2 while executing fsck.udf for /dev/rev

Does this help?

Got it working!! - but I have a question :-)

First - how I got it working:

Here is my /dev/rev link:
lrwxrwxrwx 1 root root 9 Dec 9 21:36 /dev/rev -> /dev/scd0

Here is my /dev/scd0 link:
brw-rw---- 1 root disk 11, 0 Feb 23 2004 /dev/scd0

Here is my /mnt/rev directory before mounting:
drwxrwxrwx 2 root root 4096 Dec 9 20:53 rev

Here is my /mnt/rev directory after mounting:
drwxr-xr-x 3 root root 4096 Dec 10 10:07 rev

Here is my fstab entry:
/dev/rev /mnt/rev auto noauto,owner,kudzu 0 0

then I ran:
/sbin/mkfs /dev/rev

and now, df -h says:
/dev/scd0 33G 20K 31G 1% /mnt/rev


Now my question:
How do I make it rw for everyone when I mount it as either myself or root? I looked at the man pages for fstab and mount, but am still confused.

And another question (I know I said I only had one...)
Is there a way to specify a directory or file as compressed so that when files are put there the magically become compressed (like that other operating system that we don't talk much about in this type of newsgroup?)

thanks

Assuming you wish to allow any user to mount the drive, in your fstab, change "owner" to "users". That should do it. Congrats on getting it working. -- J.W.

OK, this is wierd:

my fstab is now this:
/dev/rev /mnt/rev auto noauto,users,kudzu 0 0
/dev/sda4 /mnt/zip auto noauto,users,kudzu 0 0

and my file permissions before mounting are this:
drwxrwxrwx 2 root root 4096 Dec 9 20:53 rev
drwxrwxrwx 2 root root 4096 Dec 9 20:53 zip

but my file permisions after mounting both as myself are this:
drwxr-xr-x 8 root root 4096 Dec 10 10:35 rev
drwxr-xr-x 4 jordan thompsons 16384 Dec 31 1969 zip

and if I mount them as root I get this:
drwxr-xr-x 8 root root 4096 Dec 10 10:35 rev
drwxr-xr-x 4 root root 16384 Dec 31 1969 zip


Any suggestions?

thanks again

Mount them first, then chmod 777 on them. Example
-- J.W.

what is your experience (as in performance/storage/usability) with the iomega rev...
is there anything else better than this "tape" drive

Now that it is installed and configured, I really love my drive. The only complaint I have is that it gets hot when there is a disk in it.