Description of problem: I want to configure HAL to mount my devices at some fixed point. I have made a script : /usr/share/hal/fdi/policy/20thirdparty/99-usbdisk-policy.fdi which defined the desired mount points for my devices. The desired mount points are recognaized by hal since they appear in hal-device-manager: volume.policy.desired_mount_point strlist stick The problem is that this info is not used by /usr/share/hal/scripts/hal-system-storage-mount and the device is always mounted at /media/disk I think that the argument is not passed from haldaemon to the script, since after the line: read GIVEN_MOUNTPOINT The variable GIVEN_MOUNTPOINT is empty Version-Release number of selected component (if applicable): FC5, hal-0.5.7-3 How reproducible: Always Steps to Reproduce: 1.Create a file /usr/share/hal/fdi/policy/20thirdparty/99-usbdisk-policy.fdi <?xml version="1.0" encoding="UTF-8"?> <!-- -*- SGML -*- --> <deviceinfo version="0.2"> <device> <match key="block.is_volume" bool="true"> <match key="volume.fsusage" string="filesystem"> <match key="volume.uuid" string="428C-349F"> <merge key="volume.policy.desired_mount_point" type="string">extra_fat</merge> </match> </match> </match> <match key="block.is_volume" bool="true"> <match key="volume.fsusage" string="filesystem"> <match key="volume.uuid" string="aa266bc4-86e9-4832-815e-df4ca1d71720"> <merge key="volume.policy.desired_mount_point" type="string">extra</merge> </match> </match> <match key="block.is_volume" bool="true"> <match key="volume.fsusage" string="filesystem"> <match key="volume.uuid" string="4034-0469"> <merge key="volume.policy.desired_mount_point" type="string">stick</merge> </match> </match> </match> </device> </deviceinfo> 2. restart hal service haldaemon restart 3. Plug the device Actual results: device mounted on /media/disk Expected results: device mounted on /media/stick Additional info:
Created attachment 127448 [details] Part of the log file generated when I plug the usb memory (--verbose=yes ---use-syslog)
Policy has been removed athough upstream should have deprecated it first (for their part they said they would be more careful in the future). Upstream is working on a more robust and secure way of setting policy using gnome-mount.
OK I wiil look at gnome-mount. Unfortunatly I can't find any documentatiuon... I guess that I have something to do with the file /etc/gconf/schemas/gnome-mount.schemas But I have absolutely no idea of the syntax of the file since the default file is empty. Cheers
*** Bug 186358 has been marked as a duplicate of this bug. ***
*** Bug 191057 has been marked as a duplicate of this bug. ***
Dear All, First of all I don't understand why Bug 186358 is a duplicate of this one and not the other way around since Bug 186358 is: 1. Older than this one 2. Refers to the correct component for the problem which is gnome-mount and not hal. But more important is that all 3 bug reports which are relevant were closed! Well I don't see a solution, why are they closed? Marc, don't expect to see anything in gnome-mount documantation since there is not documentation. As for gnome-mounts' development... where there is not development at all at the moment! John, besides closing bugs can you please ask for someone from 'upstream' come down here and give a solution or at least talk about this problem? Regards
Because I got all these bug reports and closed one first and the rest are all duplicates. gnome-mount is what does the mounting and policy now so it is the correct component. HAL got rid of its policy code. This is not solvable in FC-5 as is. Development is going on upstream with HAL, gnome-mount and PolicyKit to create a complete solution. When it is ready I will evaluate backporting it to FC-5. Sorry it is the best answere I can give, cutting edge technology and all. I expect PolicyKit will become the way for setting HAL policy (not just mounting) for a long time to come.
There is a very big problem here which you (and by that I include all the fc people who decided to use gnome-mount in its current state) don't seem to understand. As I describe in Bug 186358 there is a big issue mounting volumes with non-latin names or even mounting ntfs removable volumes with the correct permissions. 5 years ago it was acceptable to have automounting problems in linux but today it is not. Evaluating if the solution will be backported to FC5 it is not good enough, we are talking about major bug correction, not adding an extra feature. If this bug remains for long I (and imagine much more people) will have to change FC5 for another distro that has a working automounting system, one that respects hal policy like pmount. An answer that I would like from you is the expected bug resolving time, 1 month, 2 months, FC6 ? Can you please give me that so that I see what I will do? Regards
I belive we mount utf8 - as for ntfs you could change the hal script but that gets updated every time there is an upgrade. I will ask david about an interim solution.
Such an OLD and HUGE bug without any solution!! Like many others... So: Is Fedora Core DYING??? Luis