Okay, so I have a theory... I have no idea where the ID_PDA comes from so
based on that and what I can observe, it exists in two places,
69-pilot-link.rules <== owned by gnome-pilot-link for pda syncing - just
sets the environment variable when matching a hardware id
70-acl.rules <== owned by udev -- Sets an action (TAG+="udev-acl")
If my hunch is correct, we would request some id from the udev folk (or
piggy back on the ID_PDA) and remove the ACL_MANAGE and change it to
ENV{ID_PDA}="1", setting it to that means that the tag is invoked and the
ACL is managed by udev-acl... If that is all correct, the only question left
is do we use ID_PDA, or request our own?
------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand
malware threats, the impact they can have on your business, and how you
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel
