GRUB problem after upgrading to 10.04
Goh Lip
g.lip at gmx.com
Sun May 2 04:21:36 UTC 2010
On 05/02/2010 12:01 PM, Tom H wrote:
> On Sat, May 1, 2010 at 11:37 PM, Goh Lip<g.lip at gmx.com> wrote:
>> On 05/02/2010 10:40 AM, user1 wrote:
>>>
>>> I mean that such an important part of an OS as the bootloader should work
>>> out of the box and recognize all the other installed OS without any bugs.
>>> If not a lot of people might get a heavy problem. *smile*
>>
>> Okay, I normally don't use 'sudo update-grub' myself. It's the most
>> popular grub command. I'll use baby command 'grub-mkconfig -o
>> /boot/grub/grub.cfg' or the grandmother of all grub commands
>> 'grub-install /dev/sda' if all fails.
>
> update-grub just runs grub-mkconfig!
>
> # less /usr/sbin/update-grub
> #!/bin/sh -e
> exec grub-mkconfig -o /boot/grub/grub.cfg "$@"
>
> # less /usr/sbin/update-grub2
> #!/bin/sh -e
> exec update-grub "$@"
Yes, I know. You pointed that out to me last time. :)
>
> I have not followed this thread (except that I remember that the last
> four Ubuntu's were cohabitating on the disk, each with its own grub;
> my first thought was that I would uninstall three of them but I did
> not want to suggest it and have to deal with any possible subsequent
> problems...).
>
> Regarding the last para of user1's last post: The Ubuntu developers
> feel the same way. After the release of 10.04, there was a migration
> assistant problem (IIRC) whereby grub2's menu was only listing 10.04's
> entries and an update-grub would have been needed to populate the menu
> fully. They respun some/many/all the isos in order to correct the bug
> in spite of the fact that it might have delayed 10.04's release enough
> to warrant calling it 10.05.
>
Could be related to this bug..
https://bugs.edge.launchpad.net/ubuntu/+source/ubiquity/+bug/570765
Regards - Goh Lip
More information about the ubuntu-users
mailing list