Bug#591320: /etc/modprobe.d/initramfs.conf is lost

2010-08-02 Thread Harald Dunkel
Package: initramfs-tools Version: 0.97.2 Blacklisting modules on the kernel command line doesn't work. If I set blacklist=bluetooth (just as an example), then the bluetooth module is still loaded. AFAICS the generated /etc/modprobe.d/initramfs.conf is not written to the root file

Bug#591320: /etc/modprobe.d/initramfs.conf is lost

2010-08-02 Thread Harald Dunkel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This is the intended behaviour. Is this documented somewhere? This restriction would make the blacklist feature pretty useless, doesn't it? As soon as udev is started in single user mode (using /etc/modprobe.d found on root filesystem) all the

Bug#591320: /etc/modprobe.d/initramfs.conf is lost

2010-08-02 Thread maximilian attems
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? This restriction would make the blacklist feature pretty useless, doesn't it? As soon as udev is started in single

Bug#591320: /etc/modprobe.d/initramfs.conf is lost

2010-08-02 Thread Ben Hutchings
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

Bug#591320: /etc/modprobe.d/initramfs.conf is lost

2010-08-02 Thread Harald Dunkel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/02/10 23:53, Ben Hutchings wrote: 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