Message-ID: <email address hidden>
Date: Sat, 3 Jul 2004 07:54:58 +0200
From: <email address hidden> (Thomas Hood)
To: Per Olofsson <email address hidden>
Cc: <email address hidden>, <email address hidden>
Subject: Working around busybox modprobe problem
> I do think fixing
> busybox is the best solution, but since this does prevent a lot of
> pcmcia hardware from being usable in the installer, and for all I know
> we have code that depends on the current modprobe behavior, I'd
> appreciate a quick fix if possible.
If a workaround has to be hacked into the initscript then I suggest the
following technique:
Message-ID: <email address hidden>
Date: Sat, 3 Jul 2004 07:54:58 +0200
From: <email address hidden> (Thomas Hood)
To: Per Olofsson <email address hidden>
Cc: <email address hidden>, <email address hidden>
Subject: Working around busybox modprobe problem
> I do think fixing
> busybox is the best solution, but since this does prevent a lot of
> pcmcia hardware from being usable in the installer, and for all I know
> we have code that depends on the current modprobe behavior, I'd
> appreciate a quick fix if possible.
If a workaround has to be hacked into the initscript then I suggest the
following technique:
fail_ on_modprobe( ) { echo "Drat, $1 failed to load" >&2 ; exit 1 ; } already_ loaded( ) { grep -q "^$1" /proc/modules ; }
is_
modprobe foo || is_already_loaded foo || fail_on_modprobe foo
--
Thomas