On Tue, 2010-07-20 at 22:46 -0700, Manoj Srivastava wrote: > On Tue, May 25 2010, Benoît Zhang wrote: > > >>> * if the kernel does not need an initrd and the system is set up for > >>> initrd-generation the initrd is generated and update-grub adds an > >>> initrd-line into menu.conf. > >> > >> This is not the case. If the kernel was not set up with an > >> initrd in mind, no inird is created. My desktop never gets an initrd > >> line. > > > > There is another problem/bug (kernel-package or initramfs-tools or > > grub2 bug ?). > > - If initramfs-tools is installed, a intrd is always generated in > > /boot even the kernel is built without initrd. > > - If grub2 finds a initrd in /boot, it uses root=UUID=... in > > /boot/grub/grub.cfg, but the kernel can't boot UUID if it is built > > without initrd. > > A workaround is to remove the /etc/kernel/*.d/initramfs* scripts > and instead use the scripts shipped with kernel-package, which don't > build an initrd unless one is asked for.
initramfs-tools checks for kernel-package's INITRD=No setting, therefore I think this is no longer a problem in practice. However this is not written into policy at http://kernel-handbook.alioth.debian.org/ch-update-hooks.html#s-kernel-hooks-initramfs so this is not entirely solved. Ben. -- Ben Hutchings One of the nice things about standards is that there are so many of them.
signature.asc
Description: This is a digitally signed message part
