Hi Maximilan ! >From your suggestions I manage to find a solution to my issue, sorry about the unnecessary noise :o(
For the record here is my kernel-img.conf : $ cat /etc/kernel-img.conf do_symlinks = yes relative_links = yes do_bootloader = yes do_bootfloppy = no do_initrd = yes link_in_boot = no But I indeed had a lilo.conf remaining of a previous configuration, removing it did the trick... sorry to have bother you with something as simple :o( Anyway thanks a million for your answer Cheers Anthony Le lundi 28 août 2006 à 12:07 +0200, maximilian attems a écrit : > tags 384967 moreinfo > thanks > > On Mon, Aug 28, 2006 at 10:29:58AM +0100, Anthony Callegaro wrote: > > > > Hi all, > > > > I've seen lots of discussion already on the initramfs/lilo dependency when > > people are using grub, but I didn't see any report of my issue. > > > > I'm using grub only (lilo is not installed) on my machine and during the > > last > > 2 upgrades of initramfs-tools I received the following error message : > > > > update-initramfs: Generating /boot/initrd.img-2.6.17-2-k7 > > /usr/sbin/update-initramfs: line 88: lilo: command not found > > > > I resolved the issue with a simple > > touch /usr/sbin/lilo > > chmod +x /usr/sbin/lilo > > > > But I wondered what would have happened if lilo WAS installed. As I'm using > > grub > > it would certainly have broken my boot... > > please send the output of > cat /etc/kernel-img.conf > > > If I remember correctly the issue started with 0.75 (at least I remember > > only > > having to use the above workaround only twice). > > > > Let me know if you need more info, I'll be glad to help. > > Cheers > > Anthony > > if aboves doesn't look like i suppose, i may need more info. > thanks for your report. > > -- > maks >
