2009/10/29 Steve Langasek <steve.langa...@canonical.com>: > On Thu, Oct 29, 2009 at 08:44:57AM -0000, Przemysław Kulczycki wrote: >> Same thing after upgrading from Jaunty to Karmic. Update-grub fails to >> update menu.lst after I chose to keep my version of menu.lst during the >> upgrade. > > If you chose to keep your version of menu.lst, this is not a "failure". > It's doing what you told it to.
Then the wording of the notice in update-manager should be changed. My expectation was the same as with update-manager offering to replace ie. /etc/modprobe.d/blacklist.conf I thought that update-manager will delete my menu.lst completely, and then I would have to add my Windows entries manually. > The bug here is that currently, it's very hard to go back and change your > mind after telling update-grub to do this; but you only see this prompt in > the first place because you're working against update-grub by not using its > kernel stanza autogeneration support. If you set your variables where > update-grub looks for them, there's no reason for you to get a conflict at > all. Will it retain the additional OS entries outside of the automagically generated list? (Windows) Or will it erase them? I wanted to keep them, that's why I chose to retain my old menu.lst - I expected update-grub to update the kernel list without touching the additional OSes. -- ## Przemysław Kulczycki >><< Azrael Nightwalker ## # jabber: azrael[na]jabster.pl | tlen: azrael29a # ### www: http://reksio.ftj.agh.edu.pl/~azrael/ ### -- update-grub not updating menu.lst https://bugs.launchpad.net/bugs/202009 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
