Bug#591320: /etc/modprobe.d/initramfs.conf is lost
On Mon, Aug 02, 2010 at 11:14:43PM +0200, Harald Dunkel wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> > This is the intended behaviour.
>
> Is this documented somewhere?
Not specifically, but the kernel parameters interpreted by the
initramfs scripts generally do not apply to what the rest of the
system does. Also, it seems wrong for the initramfs to dynamically
modify the persistent system configuration.
> This restriction would make the blacklist feature pretty useless,
> doesn't it?
No, see below.
> As soon as udev is started in single user mode (using
> /etc/modprobe.d found on root filesystem) all the blacklisted
> modules are no longer suppressed.
>
> In my case I get a "bad" acpi module crashing the system before
> single user mode is completely setup. What would you suggest?
>
> Of course I understand that this would be difficult to implement,
> since the root filesystem becomes writable very late in the boot
> procedure.
You can use break=init to get a shell at the point where the real init is
about to be started. Then you can add a blacklist file. (And you can
remount the root rw if necessary.)
You could perhaps report a wishlist bug on module-init-tools, requesting
that modprobe should obey the 'blacklist' parameter on the kernel command
line, perhaps using an init script to do something similar to what
initramfs-tools does.
Ben.
--
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
- Albert Camus
Reply to: