On Wed, 03 Jun 2009, Marcel Holtmann wrote: > any user program with proper rights (remember that /dev/rfkill can now > be controlled by Unix permissions and SELinux) can bring up a specific > device. That is policy and it belongs in userspace. If I hardkill (EPO) the devices, I want them to stay hardkilled, and only a system daemon (if that) should be able to mess with that. I very much doubt I am the only one who see things that way :-) I'd like to keep working towards that goal (no, we're not there yet), and not away from it. > This of course only works on soft blocked devices. The hard blocked > devices stay off. And in case of ThinkPads where the button does the > hard block, you can't bring it back from software. Yes. But the rfkill core is also meant to bring some band-aid help to the devices that the hardware can't kill by itself. That's good usability. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- 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
