** Description changed: Binary package hint: gnome-mount Hi, I have a FAT and a ntfs partition on my system. I would like to hide (or no automounting) the ntfs partition, so I edited fstab, but the partition is still mounted on startup. And I like to set the uid, gid, noauto and exec for the fat partition, but this isn't working. I found a guide that said to set those options "right click on a device". Uh windows feeling and: - the mountpoint isn't moveable. It only uses /media - the options must be separated by spaces and not by commas like in fstab (not very intuitive) - if I set common options like "user(s)" und "defaults" it says invalid option, but it don't say which options are valid. - you can set the security relevant option exec and uid but can`t set gid... - The owner of my partitions is root, group plugdev and not me. + The owner of my partitions is 'unknown' and not my user. From man gnome-mount "Note that HAL has a notion of what mount options are valid for a given volume. They are listed in the HAL property volume.mount.valid_options on the device object representing the volume to mount.." Ok there are the possible options, but no word about why other options are not allowed and HOW TO CHANGE THEM. I thought I am the root or am I not? So I used "hal-set-property" but there is no documentation for it and it says succinct: "This program attempts to set property for a device. Note that, due to security considerations, it may not be possible to set a property" No additional words nessacery. One more outline from man gnome-mount "In addition to using HAL as the mechanism for mounting file systems, the /etc/fstab file is also consulted as HAL will refuse to mount any file system listed in this file as it would violate system policy. If this is the case, gnome-mount will invoke mount(1) as the calling user rather than invoking the Mount method on the org.freedesktop.Hal.Device.Volume interface on the device object representing the volume / drive. This means that settings (mount point, mount options, file system type) read by gnome-mount are not passed along as these are already specified in the /etc/fstab file and there are no mechanism to override them. When parsing the /etc/fstab file, gnome-mount (and also HAL for that matter) resolves symbolic links and also respects the LABEL= and UUID= notations. For example, if this line is in /etc/fstab LABEL=MyVolume /mnt/myvolume auto user,defaults 0 0 then gnome-mount mounts the file system with the label MyVolume via mount(1) and /etc/fstab rather than using the HAL mechanisms." This sounds like a solution but it is not working. Some options aren't interpreted or ignored, "normal" mounted drives can't be unmounted or are missing in places or computer. Another solution could be to change the policies in /etc/hal/fdi/policy by editing or creating a file (Not that beginner friendly). I have a lot of respect of such hacks. I would prefer if hal could also use the fstab as mentioned in the man. Thanks for reading. Feel free to post solutions or hints Greetings Dan
-- Can't set (for me) important partition options https://bugs.launchpad.net/bugs/114815 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
