Weird. Wrote a nice comment here, formatted nice (not beautiful, but still nice), saved and... it vanished. Ah well. I will try again, but now short & direct.
Looking at the update-grub output I can see the chainload entry being correctly created. Here is my guess: the grub2 installation does not change a "chainload grub2" existing entry. I had previously installed grub2, tested it, and --purge remove-ed it. But it seems grub2 does not really purge: I did it again this morning, and still /boot/grub was littered with ".(mod|img)" files. And, still, a "chainload grub2" in the menu.lst. This is, to me, wrong. Now, we are not targeting upgrades on this cycle. I guess it is your call on what to do here. -- chainload grub2 fails on /boot on different partition https://bugs.launchpad.net/bugs/385055 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
