Bug#704815: Would it be possible to reenable CONFIG_ACPID
On Sat, Apr 6, 2013 at 11:05 AM, Michael Tokarev <mjt@tls.msk.ru> wrote:
Hi Michael,
Thanks a lot for the fast reply
> 06.04.2013 12:56, Guido Trotter wrote:
>> Package: busybox-static
>> Version: 1:1.20.0-7
>> Severity: wishlist
>>
>>
>> I know that acpid was disabled on purpose, but would it be possible to
>> reenable it? It is useful on VMs running with busybox only, for example.
>
> For many years, i've the following "replacement" for acpid:
>
> ---- cut ----
> #! /bin/sh
>
> [ -d /sys/module/button ] || { modprobe button; sleep 5; }
> [ -f /proc/acpi/event ] || exit 1
>
> while read x < /proc/acpi/event; do
> case "$x" in
> *button/power*)
> echo "
> Power down
> " > /dev/console
> shutdown -h -P now
> ;;
> esac
> done
> ---- cut ----
>
CONFIG_ACPI_PROC_EVENT is deprecated and unset in most modern kernels
(I know, I can always build my own kernel, but then again, I could
also build busybox, so that defeats the purpose). acpid in busybox can
read /dev/input/event* and at least under Xen does the right thing
(shuts down the system, with the proper config).
> Is it not sufficient for you?
>
> If you talk about VMs, I found it is much easier to use Ctrl+Alt+Del
> from inittab to signal shutdown, and don't bother with acpi at all.
> For this to work, just change cad action in /etc/inittab to do
> power down instead of reboot.
>
Under kvm I can always go for the "ctrl+alt+del" option you suggest,
but that still requires special knowledge that the machine does the
right thing, while acpi is supposed to be more standard. Anyway I am
not sure I could easily do that under Xen too.
> As for enabling this applet for wheezy, it definitely is not possible
> at this time because of the freeze.
>
Understood, I only mentioned it because it was enabled in squeeze
before, but then again probably busybox is too important to allow
exceptions. Well, maybe it can still be discussed and updated in
wheezy+1 and backports, perhaps?
Thanks,
Guido
Reply to: