It would only be a problem, if the deprecated /proc/acpi/event is around and
acpid is started after hal. Then hal would use /proc/acpi/event.
But acpid would still use netlink.
I don't feel like porting hal to use netlink (with hal being dead and all),
but
what I could do is, to remove the
As said, I guess this is due to Debian kernels not using/providing
/proc/acpi/events anymore.
Valid point, I just made the mistake to check that on a system not running a
Debian kernel.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at
2.) The postinst tries to restart hal if it find the init script.
I guess with acpid using netlink now this can be dropped completely?
You mean the logic needed to access/allow hal to access /proc/acpi/events? No,
not really. Acpid still does/can use that file if it exists. You don't have to
Am 23.03.2011 20:22, schrieb Michael Meskes:
2.) The postinst tries to restart hal if it find the init script.
I guess with acpid using netlink now this can be dropped completely?
You mean the logic needed to access/allow hal to access /proc/acpi/events? No,
not really. Acpid still does/can
Am 23.03.2011 20:22, schrieb Michael Meskes:
2.) The postinst tries to restart hal if it find the init script.
I guess with acpid using netlink now this can be dropped completely?
You mean the logic needed to access/allow hal to access /proc/acpi/events? No,
not really. Acpid still does/can
Package: acpid
Version: 1:2.0.8-3
Severity: normal
Hi,
in hal 0.5.14-4 (wheezy) I changed it to use D-Bus activation so it is started
on
demand. That means there is no longer a hal sysv init script.
As a result:
1.) The Should-Start: hal in the acpid LSB header is no longer useful,
As it is
6 matches
Mail list logo
