Re: ACL_MANAGE meaning in udev is inconsistent

[Frederic Crozat <fcrozat@mandriva.com>]

Le 04/03/2010 10:26, Martin Pitt a écrit :
> Frederic Crozat [2010-03-04  9:40 +0100]:
>> Hmm, this is problematic : a lot of rules outside udev are using
>> ACL_MANAGE to specify ACL should be set for some devices. I would
>> suggest to not "deprecate" ACL_MANAGE outside 70-acl.rules but
>> internally to 70-acl.rules, use another variable.
>
> Oh, do you know which? The only one I'm aware of is gnome-bluetooth
> for /dev/rfkill, which is evil, bad, and wrong:
>
>    https://bugzilla.redhat.com/show_bug.cgi?idQ4798
>
> It really shouldn't be used outside of 70-acl.rules.

For a quick check on my test system :

/etc/udev/rules.d/60-libpisock.rules
needed for Palm devices

/etc/udev/rules.d/69-floppy-acl.rules
needed for mtools

/etc/udev/rules.d/69-gammu-acl.rules
needed for gammu

/lib/udev/rules.d/60-libmtp.rules
needed for MTP devices

/lib/udev/rules.d/69-printeracl.rules
for parallel printers (not sure it is still needed these days)

/etc/udev/rules.d/55-Argyll.rules:
needed for colorimeters (this file is supposed to be used across various 
udev releases and distribution, even if COLOR_MEASUREMENT_DEVICE is now 
merged in udev upstream : I've removed this specific ACL_MANAGE in our 
Mandriva package)

/lib/udev/rules.d/95-gcm-colorimeters.rules
for gnome-color-manager : it kind of duplicate some of the work done in 
argyllcms rules, because you might not have argyllcms installed 
initially (Richard is going to rename the rule which is currently 
executed after 70-acl which is a bug).

I might have missed other rules, I didn't do a full search across our 
package database.

-- 
Frederic Crozat
Mandriva