Bug#591320: /etc/modprobe.d/initramfs.conf is lost
-----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-----
Reply to: