Brain, Try adding following to your /etc/fstab: /dev/hdd /media/zip subfs fs=floppyfss,procuid,nodev,nosuid,sync 0 0 /media/zip is a directory you create yourself. HTH, Eric On Monday 14 June 2004 01:22, Brian Jonas wrote:

floppy drive in the /media folder. For what it's worth, I do see it in the start up log: "<4>hdd: IOMEGA ZIP 100 ATAPI, ATAPI FLOPPY drive".

Brian, Topposting - since this seems the way this thread is handled... You can use any editor you like and cut and paste it (watch out for returns!). VI is a classic and works everywhere and this is the point to learn to handle it. But personally i prefer the lazy approach and use a more modern editor. What i often do from KDE onwards is: Launch System -> file manager -> File manager super user mode. Rightclick on the file and oen the file with kwrite, kate or your preferred editor. Working in init 1 or init 3 (no graphics/ KDE) i often use mc (midnight commander) to browse the filesystem and to edit files for tasks like this. Works like th Norton Commander i was used to... Note that Suse had the bad taste not to enable it by standard in 9.0 i think. To each its own (editor) Peter Vollebregt Brian Jonas wrote:

Eric,

<snip>

Unfortunately, I can't seem to find directions for editing a system file like this in

On Monday 14 June 2004 10:36 am, Eric Seynaeve wrote:

...

Brain,

Try adding following to your /etc/fstab: /dev/hdd /media/zip subfs fs=floppyfss,procuid,nodev,nosuid,sync 0 0

/media/zip is a directory you create yourself.

HTH,

Eric

On Monday 14 June 2004 01:22, Brian Jonas wrote:

...

floppy drive in the /media folder. For what it's worth, I do see it in the start up log: "<4>hdd: IOMEGA ZIP 100 ATAPI, ATAPI FLOPPY drive".

Brian Jonas wrote:

Peter and Eric,

Peter, thanks for the tip! I had not used the File Manager - Super User Mode before -- it was a lot easier. Eric's "/dev/hdd /media/zip subfs fs=floppyfss,procuid,nodev,nosuid,sync 0 0" (w/o quotes) line almost worked, but I must have missed a step. The Zip Drive Icon is now on the desktop. But when I go to open it I get a warning box that reads:

"[mntent]: warning: no final newline at the end of /etc/fstab mount: only root can mount /dev/hdd on /media/zip Please check that the disk is entered correct"

When I had opened fstab in KWrite, and paseted in Eric's line, I heeded Peter's warning to "watch out for returns!" comment and didn't do anything else but save and close the file.

When I now go back to fstab, I can't reopen it using any of the right-click menu editor options. Also looking into /etc/ I now have a second icon named ~fstab.

Any suggestions?

Thanks to both of you for your help! Brian

Brian, Strange that the file will not open the second time around? What are the permissions set for the fstab file? You can see this in konqueror when you set the view mode on detailed list view or when you ask for the file in a terminal with 'ls -l fstab'. My permissions are: rw-r--r-- root root (on 9.0). The ~fstab file is the backup copy created by the editor you used (kwrite does this) so you can revert to it. By the way you should always keep a copy of a working original if you mess with important files like this.... The thing about the returns was just becasue lines are often wrapped in emails. But given the fact that you entered this as the last line i normally would give a return to end it properly. Don't know about the subfs stuff. But in 9.0 i aslo had to add a line in fstab and a mount directory. When using my method of opening files sometimes you get an error like 'KDEinit could not launch kwrite'. Logging off and on again helps. The other solution is to delete or rename the .Xauthority file in the /root directory. HTH Peter Vollebregt

Brian Jonas wrote:

...

<snip> Don't know about the subfs stuff. But in 9.0 i aslo had to add a line in fstab and a mount directory.

When using my method of opening files sometimes you get an error like 'KDEinit could not launch kwrite'. Logging off and on again helps. The other solution is to delete or rename the .Xauthority file in the /root directory.

HTH Peter Vollebregt

Hi Peter,

I was also getting the 'KDEinit could not launch kwrite' warning, I'm sorry I didn't mention that. I logged off and on again and that fixed it. I added a hard return after the line from Eric that I added to fstab and that fixed the "[mntent]: warning: no final newline at the end of /etc/fstab mount" issue.

I still need to figure out why I continue to get the "mount: only root can mount /dev/hdd on /media/zip. Please check that the disk is entered correctly" prompt when trying to open the zip drive.

I appreciate your help -- I'm glad to be making some progress with this issue.

Brian

Brian, Glad to help you out. The problem you have is subfs related. Maybe someone knows how to solve it. In former days you added the 'user' parameter to allow other users to mount. You can try to do it the 'old' normal way and do not use subfs. My line in fstab is: /dev/sda4 /media/zip auto noauto,user 0 0 You already created a directory /media/zip. Otherwise do. In KDE you can put an icon on your desktop to mount the zip drive (you can ofcourse do it manually). In 9.0 this is done like (do not have my 9.1 for me): right-click -> create new device -> zip device and choose the correct device (/de/sda4). Mount and umount via this icon. HTH, Peter

Peter and Eric, Thanks to both of you for the advice. In fstab I added the line: /dev/hdd /media/zip auto noauto,user 0 0. It seems to have worked, though I'm still no quite there. I didn't add an icon to the desktop using Peter's method, because after the fstab edit was saved an unmounted zip disk icon appeared on the desktop. When I click that icon, Konqueror opens, and mounthelper trys to mount the device. An Error - kio_devices_mounthelper box appears with the following error message: mount: I could not determine the filesystem type, and none was specified Please check that the disk is entered correctly. It's a disk formatted for windows, but that didn't matter in v9.0. Do I need to manually mount this manually through Kinsole? I tried it using: # mount -t vfat /dev/hdd /media/zip but then it came back with: mount: wrong fs type, bad option, bad superblock on /dev/hdd, or too many mounted file systems. Obviously I'm making a mistake somewhere. Sorry to be slow in responding, needed a weekend to give this another try. Thanks for your patience. At Peter's request I've pasted in the fstab contents below, though the width of this message makes it a mess. Brian /dev/hdb9 / reiserfs acl,user_xattr 1 1 /dev/hda1 /windows/C vfat users,gid=users,umask=0002,iocharset=utf8 0 0 /dev/hdb1 /windows/D vfat users,gid=users,umask=0002,iocharset=utf8 0 0 /dev/hdb5 /windows/E vfat users,gid=users,umask=0002,iocharset=utf8 0 0 /dev/hdb6 /windows/F vfat users,gid=users,umask=0002,iocharset=utf8 0 0 /dev/hdb7 /windows/G vfat users,gid=users,umask=0002,iocharset=utf8 0 0 /dev/hdb8 swap swap pri=42 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 proc /proc proc defaults 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 sysfs /sys sysfs noauto 0 0 /dev/cdrom /media/cdrom subfs fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 /dev/fd0 /media/floppy subfs fs=floppyfss,procuid,nodev,nosuid,sync 0 0 /dev/hdd /media/zip auto noauto,user 0 0

Hi Jorge, I have only tried /dev/hdd, so I gave /dev/hdd1 a try. After making the edit, saving and closing fstab, I then left-clicked on another new icon that has been added to the desktop(Zip Disk (hdd1)). kio_devices_mounthelper presented me with a new error message: mount: /dev/hdd1 is not a valid block device Please check that the disk is entered correctly. The disk is in the drive. Also, earlier today, I rebooted to the windows side to confirm that this was a healthy zip disk. I long-formatted it and saved a text file to it without problems. I just rebooted, keeping the zip in the drive. The other icons are gone, but I'm still getting the same error message. BTW, when right-clicking the zip disk icon, the contextual menu does not offer a "mount" choice. If my memory serves me correctly (which it seems to do less and less often) mounting was a menu option in v9.0. Thanks for your suggestion, let me know if you have any other ideas. Brian On Saturday 19 June 2004 8:10 pm, Jorge Manuel B. S. Vicetto wrote: <snip>

have you tried specifying /dev/hdd1, instead of /dev/hdd ? I think it might do the trick.

All right Jorge!, That was the right question! Here it is: linux:/home/brian # fdisk -l /dev/hdd Disk /dev/hdd: 100 MB, 100663296 bytes 64 heads, 32 sectors/track, 96 cylinders Units = cylinders of 2048 * 512 = 1048576 bytes Device Boot Start End Blocks Id System /dev/hdd4 * 1 96 98288 6 FAT16 I changed the last line in fstab to: /dev/hdd4 /media/zip auto noauto,user 0 0 I then clicked on my newest icon and up popped the test file I had saved while in Windows -- it works! Yes! I am so pleased! Thank you Jorge, Peter, and Eric for helping me through this issue. I continue to be overwhelmed with how wonderful it is that people from all parts of the world are willing to come to these newsgroups to help other people. Sincerely, Brian On Saturday 19 June 2004 9:58 pm, Jorge Manuel B. S. Vicetto wrote:

Quoting Brian Jonas :

...

Hi Jorge,

I have only tried /dev/hdd, so I gave /dev/hdd1 a try. After making the edit, saving and closing fstab, I then left-clicked on another new icon that has been added to the desktop(Zip Disk (hdd1)). kio_devices_mounthelper presented me with a new error message:

mount: /dev/hdd1 is not a valid block device Please check that the disk is entered correctly.

<snip>

Brian,

can you post here the result of running as root fdisk -l /dev/hdd ? I'm curious to see what partitions Linux "sees" on your ZIP.

------------------------------------------

Jorge Manuel B. S. Vicetto Network Manager and Systems Administrator Angra do Heroísmo Nursing School (ESEnfAH)

------------------------------------------

---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

Scott, I didn't see your message until I sent my message thanking everyone for their help. You too offered the key to fixing this problem -- thanks! Brian Saturday 19 June 2004 10:56 pm, Scott Leighton wrote:

Try /dev/hdd4 that's where my Iomega shows up.

On Sunday 13 June 2004 5:52 pm, jim barnes wrote: Jim, Thanks for the suggestion. I tried checking "show desktop icons" and then checking everything -- mounted or unmounted. I then tried with a disk in the zip drive and without , but never had the zip drive icon appear. Wish it would have worked. Brian

...

What can i do ?

configure desktop > (tab) device icons > show device icons -- Jim Barnes