Re: ACL_MANAGE meaning in udev is inconsistent

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Mar 3, 2010 at 23:26, Martin Pitt <martin.pitt@xxxxxxxxxx> wrote:
> 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?id=514798
>
> It really shouldn't be used outside of 70-acl.rules.
>
> Kay, perhaps we should turn this into a non-public symbol, like
> "_ACL_MANAGE"?

We need to find it in the db at coldplug time. :)

If we are not getting a better idea, I'm planing to add a TAG=
feature, which maintains an index database which supports a
reverse-lookup. Also for other use-cases, we need a more efficient way
to select a set of devices tagged by rules. At this time ACL_MANAGE
will go away.

Thanks,
Kay
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel]     [Linux DVB]     [Asterisk Internet PBX]     [DCCP]     [Netdev]     [X.org]     [Util Linux NG]     [Fedora Women]     [ALSA Devel]     [Linux USB]

  Powered by Linux