Robert Millan wrote: > 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") >
I had re-run dpkg-reconfigure grub-pc and disabled the chain-loading. Now rerunning dpkg-reconfigure grub-pc and enabling chain-loading again doesn't update /boot/grub/menu.lst. So I can't tell if menu.lst is restored to a sane state after removing grub-pc. What I can tell though is that uninstalling grub-pc leaves *a lot* of cruft in /boot/grub/. I'm not sure, if the chain-loading idea is so great. I'd rather have /boot/grub cleaned up from any grub legacy cruft, everything imported into grub2 and simply make grub2 bullet proof, so the chain-loading workaround is no longer necessary. Would seem to be a cleaner solution to me. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature