On Tue, 30 Mar 2010 09:46:40 -0400 (EDT) Stephen Powell <[email protected]> wrote:
> On Mon, 29 Mar 2010 22:54:55 -0400 (EDT), Brian wrote: > > why does linux image try to use grub ? > > I don't have grub installed, but I _do_ have lilo installed. > > Should this be a bug report ? > > > > you should know that I haven't done a full upgrade in a while, that > > may be part of the problem. used to be Debian unstable wasn't. It > > is now :-( > > > > Setting up linux-image-2.6.32-3-amd64 (2.6.32-9) ... > > Running depmod. > > Running update-initramfs. > > update-initramfs: Generating /boot/initrd.img-2.6.32-3-amd64 > > initrd.img(/boot/initrd.img-2.6.32-3-amd64 > > ) points to /boot/initrd.img-2.6.32-3-amd64 > > (/boot/initrd.img-2.6.32-3-amd64) -- doing nothing > > at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 400. > > vmlinuz(/boot/vmlinuz-2.6.32-3-amd64 ) points > > to /boot/vmlinuz-2.6.32-3-amd64 (/boot/vmlinuz-2.6.32-3-amd64) -- > > doing nothing > > at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 400. > > Running update-grub. User postinst hook script [update-grub] failed > > to execute: No such file or directory > > >From the error messages it appears that your /etc/kernel-img.conf > >file > is not set up properly. I'm guessing that it contains lines like: > > postinst_hook = update-grub > postrm_hook = update-grub > > De-installing grub does not get rid of these lines in this file! > They have to be manually removed. ok. > Here is what I recommend that this file look like for a lilo user > under Squeeze/Sid: > > do_symlinks = yes > do_bootloader = yes > do_initrd = yes > link_in_boot = yes ok. > > This assumes that you want to maintain your symlinks in the /boot > directory, which it appears you are doing from the above messages. > Of course, /etc/lilo.conf must be set up to use those symbolic links > as well. Something like this: at first I didn't understand this, but now I see what's going on. debian has got symlinks which point to the most recently installed kernel. initrd.img-> initrd.img-2.6.32-3-amd64 vmlinuz -> vmlinuz-2.6.32-3-amd64 > Note that the "image" and "initrd" lines start out with "/boot", > which indicates that the boot loader expects the symlinks to be > in the /boot directory as well. I'm going from memory here, as > I don't have access to a lilo-configured machine at the moment. you are correct, they should be in the boot directory. > > HTH > yes indeed. thanks very much. Brian -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
