Originally Posted by nx5000
No clue for gnome.. sorry
I particularly don't like autofs because it is kernel based. It happened to me several time (when I was using Mandrake) that the kernel would lock up because I removed the disk manually or the network share was unavailable.
your right about /by-label/ stuff, I should also do it
(btw, I am using pmount for removable medias, it can integrate with hal to automount)
Hi, I'm back again with some more information.
The mount was indeed happening through gnome-volume-manager which listens to events from HAL.
I could even find the documentation to provide mount options to "high-in-stack" software (i.e. gnome-mount-manager) but it seems it is not honoring these flags.
I added my own policy in HAL which looks like below...
<match key="block.is_volume" bool="true">
<match key="volume.fsusage" string="filesystem">
<match key="volume.fstype" string="ntfs">
<merge key="volume.policy.desired_mount_point" type="string">kamal_usbdisk</merge>
<merge key="volume.policy.mount_option.ro" type="bool">true</merge>
<merge key="storage.policy.mount_option.ro" type="bool">true</merge>
<merge key="storage.policy.default.mount_option.ro" type="bool">true</merge>
To confirm my policy is loaded and working, I also changed the desired_mount_point which worked. But the drive is still mounted as read-write.
Any ideas... as you use pmount.. which actually is embedded inside gnome-volume-manager, you might give me some clue...
- Kamal N