Bug#618905: references obsolete hal init script
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 fallback in hal to open /proc/acpi/event and always use acpid.socket. Sounds reasonable. I wil remove the hal stuff in acpid. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org Jabber: michael.meskes at googlemail dot com VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#618905: references obsolete hal init script
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 BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org Jabber: michael.meskes at googlemail dot com VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#618905: references obsolete hal init script
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. 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. To be safe I take it acpid has to be started before dbus, right? Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org Jabber: michael.meskes at googlemail dot com VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#618905: references obsolete hal init script
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
Bug#618905: references obsolete hal init script
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 Does that mean, acpid will prefer /proc/acpi/event over netlink? That would we very strange imho. Is there a solid reason not to use netlink *always*? use th enetlink layer. 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. To be safe I take it acpid has to be started before dbus, right? I don't see a need to start before dbus or restart hal. hal will periodically check if /var/run/acpid.socket is available. So even if during boot hal would be started before acpid (which is highly unlikely) it would pick it up as soon as acpid is up. 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. 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 fallback in hal to open /proc/acpi/event and always use acpid.socket. 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
Bug#618905: references obsolete hal init script
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 not a fatal error though, you can safely keep it and it's just a little cruft you are carrying around. I'd definitely drop it for wheezy+1 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? Michael -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.38-1-686 (SMP w/1 CPU core) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages acpid depends on: ii libc6 2.11.2-11 Embedded GNU C Library: Shared lib ii lsb-base 3.2-27 Linux Standard Base 3.2 init scrip ii module-init-tools 3.12-1 tools for managing Linux kernel mo Versions of packages acpid recommends: ii acpi-support-base 0.138-8scripts for handling base ACPI eve acpid suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
