https://bugzilla.novell.com/show_bug.cgi?id=382784
User dkukawka@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=382784#c14
--- Comment #14 from Danny Kukawka
(In reply to comment #12 from Danny Kukawka)
If there are rfkill-buttons which don't have a specific hardware device, how should HAL be able to get (and provide information) about the actual state of the button? Should HAL guess it? AFAIK the keyboard buttons have no state, you can't get information about the state.
HAL tracks the button presses of the item and toggles the power state accordingly. What the default state is when HAL starts, or whether that state gets save across reboots, I'm not sure.
If HAL can't find out the correct state on startup, the state will we ALLWAYS wrong, if the initial state isn't correct. Guessing the current state is a no-go. And that's why the whole discussion make no sense because HAL shouldn't provide any unreliable information. And if you use SIOCSIWTXPOW to control the state of WLAN HAL also can't know the correct state. Btw. You are obviously wrong: The current rfkill interface/method don't tell the state of the button or switch, it tells you the state of the radio (from HAL SPEC: "This interface provides a mechanism for both querying whether a radio is on as well as turning it on and off.") IMO we have NM (and removed network stuff from HAL) because NM is the network abstraction layer. Because of this NM should also listen the input layer (and HAL) and handle all the network related stuff like the network related buttons. Only NM can know the correct state of the radio, HAL can't. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.