busybox: add the `rfkill` command

3 files changed, 36 insertions, 3 deletions

diff --git a/aports/busybox/APKBUILD b/aports/busybox/APKBUILD
index 112c885..35ead0b 100644
--- a/aports/busybox/APKBUILD
+++ b/aports/busybox/APKBUILD
@@ -1,7 +1,7 @@
 # Maintainer: Gabor Pali <pali.gabor@gmail.com>
 pkgname=busybox
 pkgver=1.35.0
-pkgrel=3 # base: 29
+pkgrel=4 # base: 29
 pkgdesc="Size optimized toolbox of many common UNIX utilities"
 url="https://busybox.net/"
 arch="all"
@@ -219,7 +219,7 @@ ead4ad65d270d8659e1898fa16f76b6cbcf567d8aba238eacccda3764edb4362240d9359d6389873
 22e2fa8f7a6105fd9990f93b71c235980fd4eab62269939a0e3a920fe517ee4f913c6bd0148a554b67fe01d1660bf0fd76a80e9dcac290b4b8b2c304ef6080a9  CVE-2022-30065.patch
 d1a2fcbf9de623531953e7ad869e41e896aa79a0917983e6f0d20ddf7393e11220dda8be93c796b7abbf34006d8f03e871a6ab293988267df5aadb74cbd8aeb1  0001-sed-check-errors-writing-file-with-sed-i.patch
 aa93095e20de88730f526c6f463cef711b290b9582cdbd8c1ba2bd290019150cbeaa7007c2e15f0362d5b9315dd63f60511878f0ea05e893f4fdfb4a54af3fb1  acpid.logrotate
-0b92eafab0722a6c9cc4880e3be4976de9713e1e1c715c6c727a948cbd68268fce01ce308291834f70d0cf3328f7c8a44cbdb5b7c70d90f91b15efcb5b90acb3  config
+3265cb4489feae24b253ddeee2f74814b96017027d80dfeb5ba324a3a938faef445ce148e9efc7ec1f5898346254abcfc9627924ee348514be3c9697dc473baf  config
 e063599f412df919b75584fee9501925418ef21689232792e9d61178f4e34a65c3cff8a3b1b4cf3e5be61efea2065cc303db35c53ec07b361d3a65e888247544  default.script
 dd548670114a92404b8e35fb915fdbe5994498b05b0a418583271c3dd72fb7800950e42c095c902a014eb198c046b8a346d43dccd8e7a158048ae33767c572ed  acpid.initd
 34c6f3197064bb91619b899b28a201bd4d920b18bded3845440b2cb36dc6f16cabf447c96878349b16e46c30184cbe48bac00a01c5f7cf1be038c0b7136064c5  crond.confd
diff --git a/aports/busybox/config b/aports/busybox/config
index 5114bd3..953b502 100644
--- a/aports/busybox/config
+++ b/aports/busybox/config
@@ -825,7 +825,7 @@ CONFIG_FEATURE_LESS_ENV=y
 # CONFIG_PARTPROBE is not set
 # CONFIG_RAIDAUTORUN is not set
 # CONFIG_READAHEAD is not set
-# CONFIG_RFKILL is not set
+CONFIG_RFKILL=y
 CONFIG_RUNLEVEL=y
 # CONFIG_RX is not set
 # CONFIG_SETFATTR is not set
diff --git a/man/wifibox-alpine.5 b/man/wifibox-alpine.5
index 3216431..3160124 100644
--- a/man/wifibox-alpine.5
+++ b/man/wifibox-alpine.5
@@ -487,6 +487,39 @@ command.
 .Bd -literal -offset indent
 # iw dev wlan0 station dump
 .Ed
+.Sh BLOCKED WIRELESS DEVICES
+Sometimes it happens that even if the driver has successfully detected
+the wireless device, it is not yet ready to be used.  That is because
+the use of the device might be blocked either by software or hardware
+means, i.e. by a physical switch. The image contains the
+.Sy rfkill
+tool as part of BusyBox to unblock the wireless device.  Use the
+.Sy list
+command to see if
+.Sy rfkill
+is usable and list the available interfaces.
+.Bd -literal -offset indent
+# rfkill list
+.Ed
+.Pp
+If the interface is shown to be blocked, use the
+.Sy unblock
+command to unblock it.  This can be done either by function or index.
+.Bd -literal -offset indent
+# rfkill unblock wlan
+.Ed
+.Pp
+Or:
+.Bd -literal -offset indent
+# rfkill unblock 0
+.Ed
+.Pp
+Note that \(lqhard\(rq block status cannot be changed this way, as it
+is typically performed by the hardware switch or it is implemented by
+the firmware itself.  For example, the computer might be configured to
+turn off the wireless device when the wired networking interface card
+is activate and the LAN cable is inserted.
+
 .Sh SUPPORTED HARDWARE
 There are a number of Linux drivers available as kernel modules.  Note
 that not all of them could be used immediately because there might be