rfkill-input madness

Johannes Berg
2009-03-27T13:07:12Z

[-- Attachment #1: Type: text/plain, Size: 766 bytes --]

The doc says:

******IMPORTANT******
When rfkill-input is ACTIVE, userspace is NOT TO CHANGE THE STATE OF AN RFKILL
SWITCH IN RESPONSE TO AN INPUT EVENT also handled by rfkill-input, unless it
has set to true the user_claim attribute for that particular switch. This rule
is *absolute*; do NOT violate it.
******IMPORTANT******

...

When rfkill-input is not active, userspace must initiate a rfkill status
change by writing to the "state" attribute in order for anything to happen.

How the hell is userspace supposed to know whether rfkill-input is
active or not? Does anybody fucking care to implement any of this mess
in userspace?