parq, The fix for this bug is that, when your locally-modified menu.lst disagrees with how update-grub would calculate the boot entries, a warning is shown letting you know about this inconsistency. There is no way that we can reliably "fix" the fact that the autogenerated entries don't match your local modifications, because the generated entries are generated based on the kopt and groot values that you didn't modify. The best we can hope to achieve, short of migrating to a completely different config syntax (grub2), is to warn the user about inconsistencies, which is indeed what has been done here.
To ultimately resolve this inconsistency on your system, you should update the groot variable within menu.lst and re-run update-grub. -- Default update-grub behaviour is not intuitive with respect to user modifications https://bugs.launchpad.net/bugs/21412 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
