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 use that file if it exists. You don't have to > use th enetlink layer.
I guess the point here is, that the Debian kernels no longer provide /proc/acpi/events, so acpid will use netlink by default, so there shouldn't be any clashes anymore with hal, as netlink doesn't have that restriction. But with hal not started by initscript anymore what's > the right way to restart it? Interestingly enough the whole code does nothing > right now and apparently no problem has come up. As said, I guess this is due to Debian kernels not using/providing /proc/acpi/events anymore. To be safe I take it acpid has > to be started before dbus, right? Such a dependency seems to be artificial. Let's accept that this CONFIG_ACPI_PROC_EVENT has been deprecated since quite some time and just drop all those ugly workarounds. I don't see a point why we should try to support lenny kernels in wheezy. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
