On Tue, Sep 27, 2011 at 12:08 PM, Johannes Berg
[off-list ref] wrote:

On Tue, 2011-09-27 at 12:03 +0400, Andrew V. Stepanov wrote:

quoted

On Tue, Sep 27, 2011 at 11:46 AM, Johannes Berg
[off-list ref] wrote:

quoted

On Tue, 2011-09-27 at 14:33 +0400, Andrew V. Stepanov wrote:

quoted

From: Andriy Stepanov <redacted>

Use as:
modprobe rfkill unblocked=1
or
/etc/modprobe.d/options
options rfkill unblocked=1

Apart from the obvious style problems in this patch (tons of extra
braces) I'm not convinced this is a good idea.

What problem does it solve? Why can that problem not be solved
differently with existing mechanisms (e.g. urfkilld configured to do
nothing)?

quoted

2. urfkilld  can't be used to ignore Hard blocked buttons.

Oh that's a good point -- so NACK on the patch.

You *can't* ignore hard block buttons. All you can ignore is events from
them, which is definitely not useful.

johannes

I wan't to completely ignore events (state) of software\hardware rfkill buttons.

One solution for this, is to compile Linux kernel with "CONFIG_RFKILLL
is no net".
Than hardware/software rfkill buttons dosn't have any action to wlan-interfaces.

Other method is use this patch.

Do you know third method ?