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 system, i.e. the blacklist
is lost.


Regards

Harri



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4c5665cc.2000...@aixigo.de



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 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.


Regards

Harri
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkxXNUMACgkQUTlbRTxpHjcq9QCaA+17o5ndz3L7E0SYN/CqQZDt
cHwAn26NK54gb4Ek7Km5my8VGE8Pf+Kb
=7pLJ
-END PGP SIGNATURE-



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4c573543.1040...@afaics.de



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 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.

I'd suggest to have m-i-t parse the blacklist bootparam.
the thing is this one is initramfs-tools specific dracut prefix rd to it
marking it as a non linux-2.6 param. We didn't have that discussion yet.



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100802212826.gs19...@baikonur.stro.at



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 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



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100802215355.gr3...@decadent.org.uk



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 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.
 

One could argue that moving from initrd mode to single user mode
should be transparent. Next week the rest of the system might
include other components.

There is no second kernel started at boot time (AFAICS), so it
might be reasonable to expect that the kernel command line arguments
are not ignored later. Of course I understand that the blacklist
is not a real kernel command line argument, but an argument to
the init script on the initrd.

  
 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.)
 

Actually I don't want to change the persistent system configuration,
either. The system is an universal USB boot stick with a local root
file system. If I change /etc, then it might not boot on the next PC.
I understand that there is a problem to get rid of the kernel command
line blacklist later.


Regards

Harri
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkxXm8wACgkQUTlbRTxpHjcdSwCeMzq1pChzz33tHWgv1BCxx/bn
pEAAn0dntSDV1A0gnLtnUu3D/SBbAHkB
=JW/g
-END PGP SIGNATURE-



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4c579bd1.1040...@afaics.de