/etc/init.d/acpid requires /proc/acpi/event to exist. However alternatively acpid depends on input layer and netlink: "If the events file does not exist, acpid will attempt to connect to the Linux kernel via the input layer and netlink." - man acpid Therefore we might adapt checkconfig() to reflect this change. Unfortunately I don't know what kernel version and parameters to check exactly, so I apreciate very much any helping hints.
Same deal for 2.0.3. It seems to want /dev/input/event* for Power Button e.g. $ cat /proc/bus/input/devices I: Bus=0019 Vendor=0000 Product=0001 Version=0000 N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0 U: Uniq= H: Handlers=kbd event0 B: EV=3 B: KEY=10000000000000 0 and second similar one. does kernel's rfkill have something to do with this?
Debian was doing something like this as well. I don't think there is an easy way to determine whether you will get ACPI-related messages via netlink and the input layer. (I guess you could query the input layer files to see if there's anything ACPI-related there, but then there's still netlink to check. I think the only reliable thing that might work would be to check for the proper CONFIG_* entries in the kernel .config. That doesn't sound easy or reliable to me.) It's probably best to always load acpid and let it see if it can find what it needs. Since it will always be able to hook up to netlink, it will probably always run. You'll have to leave it up to the user to remove it or turn it off if they don't want it.
thanks for explanation +*acpid-2.0.3-r1 (04 Apr 2010) + + 04 Apr 2010; Samuli Suominen <ssuominen@gentoo.org> + +acpid-2.0.3-r1.ebuild, +files/acpid-2.0.3-init.d: + Don't check for /proc/acpi anymore wrt #295854.
