fstab symlink problems [was: VolumeUnmountForced symlink problem]
Rohan McGovern
rohan.pm at gmail.com
Thu Apr 28 22:15:52 PDT 2005
I did some more testing with HAL 0.5.1, and it seems the problem is larger
than I thought.
Failure to unmount isn't the only problem that occurs when fstab entries use
symlinks rather than the real device nodes; HAL doesn't seem to be aware when
the device is mounted at all. e.g. if I insert a CD/DVD into my drive, then
mount it via an fstab entry with /dev/cdrom as the block device (which is, in
fact, a symlink to /dev/hdc), 'lshal' reports 'volume.is_mounted = false' etc
for the device, which is obviously incorrect.
Can others duplicate this behaviour, or might it depend on which kernel / udev
versions are being used?
A lot of people like to use symlinks for their CD/DVD drives, so I think this
definitely deserves fixing :-)
_______________________________________________
hal mailing list
hal at lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/hal
More information about the Hal
mailing list