bts retitle initramfs-tools needs to honor do_bootloader in /etc/kernel-img.conf stop
On Mon, 14 Aug 2006, Jonas Smedegaard wrote: > On Wed, 09 Aug 2006 00:22:11 +0200 Jean-Michel wrote: > > > Jonas Smedegaard a écrit : > > > Jean-Michel: > > > Could you please provide the content of /etc/kernel-img.conf - > > do_symlinks = yes > > relative_links = yes > > do_bootloader = no > > do_bootfloppy = no > > do_initrd = yes > > link_in_boot = no > > postinst_hook = /sbin/update-grub > > postrm_hook = /sbin/update-grub > > No "ramdisk = " line there. Ok - then you use the default ramdisk > generator as decided by the kernel packages - currently initramfs-tools. aboves "do_bootloader = no" indicates that grub should be used for booting. if you want that the linux image runs lilo at the install time of any linux-image you need to specifiy do_bootloader = yes. > > > and also tell us if you've run some custom ramdisk-building scripts > > > yourself, in addition to the stuff done automatically by the kernel > > > image postinst routines? > > > > > I do not know what is a«custom ramdisk-building scripts». > > I just know I had had an issue when I switched from 2.6.12 to 2.6.15 > > some months ago, and I believe to remember that some line related to > > *ram* was to be added or modified in some configuration file. > > If unaware of it, then probably - and hopefully - you don't :-) the posted errors were clearly from an initrd-tools generation. this is since long not debian-kernel business. > > > Also, do you have lilo installed? Do you use it, or do you use GRUB > > > or another bootloader? > > > > > Yes, I use lilo. Grub is also installed. > > This may be the cause for the trouble, then: > > the default ramdisk generator for Debian, initramfs-tools, until > recently (and perhaps still?) did not handle lilo correctly. we handle the double installed case wrongly in the sense that we don't check for the setting, but just omit a *big* warning. here with this /etc/kernel-img.conf it would have been really fine to do nothing. anyway i'll fix for the next upgrade to double check that variable if both grub and lilo are installed. > > When I installed kernel 2.6.16 (today), grub configuration file was > > automatically updated, but I had to update (by hand) /etc/lilo.conf, > > and then run lilo (as root). > > I use lilo, because I know how to add a kernel and modify option in > > lilo. I do not use grub, because I do not know grub configuration, > > and lilo works fine till now. > > It should be no crime to run lilo. But it is arguable more fragile than > GRUB, and for most standard setups, GRUB is handled almost > automatically these days. yes grub is much easier to handle. -- maks
