John Summerfied wrote: > Ian Malone wrote:
>> It took quite a while to work out how to change the HAL options for >> mounting the player. Neither the fstab-sync manpage or the HAL >> documentation mention the need to restart the haldaemon to re-read >> /usr/share/hal/fdi/, which took a while to find out. Once I had that >> I couldn't find a rule that would match usb disks, although it should >> have been easy:
> If you found a config file in /usr it's a bug and FC isn't > LSB-compliant as I understand it.
> If there's a file in /usr that you need to diddle with and it's not a > config file, it sounds like it ought to be.
> I suggest that someone who's affected write up a bug report describing > the original problem, the workaround and these opinions.
> destroying computer equipment is a fairly serious matter, but so is > standards-compliance.
As I was doing it I thought "So we're keeping configuration files in /usr now?"
From man fstab-stync:
"By default, the /usr/share/hal/fdi/90defaultpolicy/storage-policy.fdi file specifies the policy - this file should never be edited by the system administrator as it might get updated by the OS vendor for security updates. Instead, system- or site-specific rules can be put
in the /usr/share/hal/fdi/95userpolicy directory."
It looks like the default policy can be justified being under /usr since it's supposed to be part of the package, not a configuration file. However, I think a 'system-specific' rule probably should be under /etc.
Since the rules are XML I wonder if it's possible to create an include in /usr/share/hal/fdi/95userpolicy pointing to something under /etc (or maybe just symlink, but I'm not sure how elegant people think that is).
(sorry about any corruption, but I'm using a Windows machine to cut and paste from a redirected manpage: not ideal) -- imalone
