Eduard Bloch wrote:
> pumount -d hda
> checking whether hda is a mounted directory
> checking whether /media/hda is a mounted directory
> resolved mount point /media/hda to device /dev/hda
> resolved /dev/hda to device /dev/hda
> device /dev/cdrom handled by fstab, calling umount
> umount: /dev/hda is not in the fstab (and you are not root)
>
>
> grep cdrom /etc/fstab
> /dev/cdrom /media/cdrom0 iso9660 ro,user,noauto 0 0
> /dev/cdrom1 /media/cdrom1 iso9660 ro,user,noauto 0 0
> ls -la /dev/cdrom*
> lrwxrwxrwx 1 root root 3 2007-06-17 19:02 /dev/cdrom -> hda
> lrwxrwxrwx 1 root root 3 2007-06-17 19:02 /dev/cdrom7 -> hdb
OK... I found that pmount is actually doing a realpath on fstab
entries. As your case demonstrate, it is generally a bad idea, as mount
does not try to resolve symlinks in fstab entries (which is probably the
most reasonable way to go).
I'll upload in a few minutes a newer version of pmount where the
lookup is disabled. I think that it is the best way to do. Another
option would be to actually call mount (without root privileges) but
with the device name referenced in /etc/fstab. I don't see much benefits
from this, and it is much more code intrusive to do so.
Thanks for the information !
Vincent
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
