On Sat, 2006-04-22 at 00:14 +0200, Mostafa Afgani wrote: > Hi, > > On FC3/4 I used to use a custom *.fdi for hal to automount all of my > windows partitions at boot. Starting with FC5 I've run into some > problems. It seems that no matter what mount options I set in the > *.fdi, the disks are always mounted under GNOME as > (rw,noexec,nosuid,nodev). As a result, a regular user has no access > to the partitions. 'lshal' shows that the options specified in the > *.fdi are indeed in effect as far as hal is concerned. > > Question is, why is gnome-mount not respecting the > "volume.policy.mount_option.*" options set via hal?? > > Best, > -M > > PS: The storage-fixed.fdi: > > http://pandora.iu-bremen.de/~mafgani/stuff/storage-fixed.fdi Drive policy keys are no longer used. See https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=183735 . About the best I've been able to do is define a HAL rule to override the {volume.name} parameter such that it's at least constant and under my control. The following will cause a CD/DVD in my drive to always mount at /media/cdrecorder instead of /media/{volume.name} [jcliburn@osprey ~]$ cat /usr/share/hal/fdi/policy/95userpolicy/optical.fdi <?xml version="1.0" encoding="ISO-8859-1"?> <!-- -*- SGML -*- --> <deviceinfo version="0.2"> <device> <match key="block.device" string="/dev/hdc"> <match key="@block.storage_device:storage.model" string="_NEC DVD_RW ND-3520A"> <merge key="volume.label" type="string">cdrecorder</merge> </match> </match> </device> </deviceinfo>
