Hi Fabien! On Wed, 25 Jun 2008, Fabien Crespel wrote: > Henrique de Moraes Holschuh wrote: >> Sounds interesting. But is this functionality worth the hassle of >> implementing it? > > For the end user, I think it's better to have the device state restored > at boot time if it's possible. Even though it can be tricky to > implement, as you outlined. It is tricky alright. Talking to an user that likes "everything on" at boot (something I wouldn't be caught dead doing, but hey, to each his own and all that...), I found another one... * In order to not lose the possibility of giving rfkill a default of UNBLOCK, we could accept the kernel parameter as an override of sorts. if it is there, we block the "first state" API calls and use the value of the parameter. It wouldn't be that much of an extra mile to go, IMHO, if one is already doing the rest of the work. -- "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
