Johannes Berg wrote:
On Sun, 2009-05-31 at 10:13 +0100, Alan Jenkins wrote:
If I read correctly, userspace can write to the global states, but
can't read them? I think it's awkward to implement rfkill-input in
userspace without being able to read the global states. The daemon
would have to save the states in a file, in case it is restarted.
You have a point there, but I'm not sure it even cares? When restarted
it will probably want to impose its current policy anyway? It would be
easy to add that we send the global default value for newly added ones
too but I'm not sure it's necessary -- Marcel?
johannes
This applies equally to the type-specific values; I think you'd get
multiple "global default values".
I don't think restarting the daemon should necessarily impose a policy
default state, because "whatever the kernel initialized it to" is
actually a good default, when platform devices have persistent rfkill state.
Actually, I suppose it would meet my expectations if the daemon simply
uses the state of an arbitrary rfkill device of each type, because the
kernel initializes them all to the same value. If you don't mind the
slightly arbitrary looking code, it should be fine.
alan
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
