[Pkg-acpi-devel] acpid module loading
meskes at debian.org
Thu Oct 30 10:01:22 UTC 2008
On Thu, Oct 30, 2008 at 10:24:16AM +0100, Loïc Minier wrote:
> Julien reported set -x during boot to end with the "modprobe --all"
> failing; I'm not sure the method of looking at the set -x output during
> boot was reliable enough and don't understand why the call would fail
> except for an empty list of modules with some whitespaces, but we
> confirmed his list was empty.
Derrick's list is not empty:
My previous tests confirmed that $MODULES is not empty and contains
well defined space-delimited modules as defined in /etc/default/acpid.
> This is inherently fragile because the same acpid could be used with
> multiple kernels. :-/
> I'm pretty sure it would either fix 502704, or would make it clear that
> acpid has a more serious bug if it's started and exits because
> kernel/module are not yet setup.
> I agree the slope for the lenny updates has been slippery with the init
How about keeping the logic in the init script and just changing the default
setting? Well, maybe this is your plan anyway. I think we can do that. However,
we still have to figure out what causes 502704.
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
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes at jabber.org
Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL!
More information about the Pkg-acpi-devel