On Sun, 2009-05-31 at 21:01 +0200, Marcel Holtmann wrote: > > 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? > > we can be smart and send an additional CHANGE_ALL when opening the > control device if it is set. We can also just send these anyway. Doesn't > really matter? Does it? Well, I don't think we want/need this. See, Henrique says that the use case is Thinkpads which store the previous state in the BIOS. But that matters to you only if you use a mixture of operation systems, which we don't have to support. On the other hand, people on machines that don't store the rfkill state in the BIOS might care about having their machine boot up with the same rfkill state(s) as they shut down with, so the sane thing to do would be to have rfkilld store the state persistently, and then recover it at boot. At which point the BIOS state becomes irrelevant and a detail we actually end up not even _wanting_ to support because it means we need to be aware of machine differences in userspace. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
