Re: No more GRUB legacy at install time since wheezy?
On Fri 24 Jun 2011 at 15:11:13 -0700, Freeman wrote:
> Grub2 didn't like my setup during upgrade.
>
> My menu.lst of Grub 0.97 included numerous different rc levels to select
> from. Just a way of selecting between different interfaces while booting.
>
> So the following blocks in the automagic section of menu.lst resulted in a 4
> item menu for each kernel, one item booting into GDM, the next starting xinit
> with Openbox--booting from rc5.d, rc4.d rc3.d and rc2.d respectively.
[Snip menu.lst fragment]
> When grub2 setup hit that, it gave me some garbled menu item that failed,
> followed by its basic boot items for console and maintenance.
The Release Notes for Squeeze offer advice on keeping GRUB Legacy and
chainloading GRUB 2. There is also a mention of possibly having to
adjust complex configurations to fit GRUB 2. You were in that category
so were forewarned some extra work was in prospect. It would have been
nice to have had a seamless conversion of menu.lst to grub.cfg but
sometimes it cannot be done.
> So now I have an /etc/grub.d/09_custom that renders a menu above Grub2's
> default menu. I manually edit it for kernel upgrades with "find and
> replace" of kernel numbers. I don't like having a fractured, two part menu
> that doesn't completely upgrade automagically. But it works:
You do not have to have it.
You are using 09_custom for its intended purpose; previously you edited
menu.lst. To boot with the latest kernel:
> linux /boot/vmlinuz-2.6.37-1-amd64
linux /vmlinuz
> initrd /boot/initrd.img-2.6.37-1-amd64
initrd /initrd.img
To tidy up the menu a non-executable 10_linux may be something to
consider.
Reply to: