Bug#465144: menu.lst: wrong default entry 0saved

[Robert Millan]

On Mon, Feb 11, 2008 at 01:08:48AM +0100, Michael Biebl wrote:
> Robert Millan wrote:
> > On Sun, Feb 10, 2008 at 11:25:45PM +0100, Michael Biebl wrote:
> >> Package: grub-pc
> >> Version: 1.96+20080209-1
> >> Severity: normal
> >>
> >> After installing grub-pc, I got the option to chainload grub2 from
> >> /boot/grub/menu.lst, which I chose.
> >>
> >> I use
> >> default saved
> >> in /boot/grub/menu.lst
> >> After the installation this entry was changed to
> >> default 0saved
> >> which is obviously wrong.
> > 
> > How does GRUB Legacy react to this oddity?
> > 
> 
> The saved default boot entry will not be selected. It falls back to boot
> the first boot entry.

That is the intended behaviour.  When you uninstall grub-pc, is menu.lst
restored to a sane state?  (either "default 0" or "default saved")

-- 
Robert Millan

<GPLv2> I know my rights; I want my phone call!
<DRM> What use is a phone call… if you are unable to speak?
(as seen on /.)