I have an external hard disk which has an nfts partition on it. I wrote an fdi file which worked under FC4, but which no longer works under FC5. The problem is that the uid and gid mount options from the file are ignored when the actual mount takes place. I believe it's gnome-mount which is responsible for this, but please re-assign to the correct component if I'm wrong. Version-Release number of selected component (if applicable): gnome-mount-0.4-5 Here is the policy file I added to the third party directory: <?xml version="1.0" encoding="UTF-8"?> <deviceinfo version="0.2"> <device> <match key="volume.fstype" string="ntfs"> <append key="volume.mount.valid_options" type="strlist">uid=</append> <append key="volume.mount.valid_options" type="strlist">gid=</append> <merge key="volume.policy.mount_option.uid=1278" type="bool">true</merge> <merge key="volume.policy.mount_option.gid=900" type="bool">true</merge> </match> </device> </deviceinfo> The hal-device-manager shows theys keys correctly, but when the disk is connected, these options are used: /dev/sda2 /media/FW_Disk ext3 rw,noexec,nosuid,nodev 0 0
This is very irritating mostly for people outside the ASCII world who have to mount filesystems with some other charset options that used to work with fstab-sync. It is two (2) months now that this matter was raised in the fedora-devel list but nothing happend. As I see it, gnome-mount is a hack, an ugly hack to introduce into a stable release with no development going on. Do you at least have predicted fix date?
Bump! Almost 2 more months have passed!
*** This bug has been marked as a duplicate of 188224 ***
Such an OLD and HUGE bug without any solution!! Like many others... So: Is Fedora Core DYING??? Luis