Pixel wrote:
>
> J�rgen Zimmermann <[EMAIL PROTECTED]> writes:
>
> > Hello,
> > I have a current cooker installation with the grub bootloader
> > and noticed, that a kernel install/upgrade does not modify
> > grub's menu, but instead does ALWAYS update /etc/lilo.conf,
> > even if it does not exist, and "lilo" is uninstalled
> > (using "--nodeps"...)
> >
> > This is a behaviour which can render a running system by a simple
> > kernel install in a "not startable" system...
> >
> > When will this be fixed???
>
> can you run "detectloader" and tell what it outputs? (when grub is installed)
Yes, did it yesterday evening (computer is a home). Says "LILO".
I dumped the MBR (dd if=/dev/sda of=testfile ...) and analysed it.
And there: "LILO" appears somewhere near the start.
I must admit that I switched from "lilo" to "grub" three or more months
ago, and lilo was configured to install in the MBR. Where grub does
install, I have no idea, though.
BUT: grub is the bootloader which runs the system, I get the menu and
the ability to modify the command line.
I have no clue, where grub installs and why it is used, as the MBR
shows all signs of LILO...
Any idea?
So long,
Juergen
