| 2012-09-25 10:57:40 |
YannUbuntu |
description |
On Ubuntu 12.04 (grub 1.99), grub-efi creates a /efi/ubuntu/grubx64.efi file, which is recognized as an entry in the UEFI firmware.
When you install two Ubuntu (let's say UbuntuA, then UbuntuB) in dualboot, UbuntuB will overwrite the /efi/ubuntu/grubx64.efi file (linked to UbuntuA) by a new /efi/ubuntu/grubx64.efi file (linked to UbuntuB).
THE PROBLEM IS:
if UbuntuB's /boot/grub/grub.cfg is damaged or erased, the user can't access neither UbuntuA nor UbuntuB.
EXPECTED BEHAVIOR:
UbuntuA creates its own entry (eg /efi/ubuntu/grubx64_UUID-A.efi ), and UbuntuB creates another entry (eg /efi/ubuntu/grubx64_UUID-B.efi ), so that if UbuntuB's /boot/grub/grub.cfg is damaged, the user can still access UbuntuA via the UEFI firmware. |
On Ubuntu 12.04 (grub 1.99), grub-efi creates a /efi/ubuntu/grubx64.efi file, which is recognized as an entry in the UEFI firmware.
When you install two Ubuntu (let's say UbuntuA, then UbuntuB) in dualboot, UbuntuB will overwrite the /efi/ubuntu/grubx64.efi file (linked to UbuntuA) by a new /efi/ubuntu/grubx64.efi file (linked to UbuntuB).
THE PROBLEM IS:
if UbuntuB's /boot/grub/grub.cfg is damaged or erased, the user can't access neither UbuntuA nor UbuntuB.
EXPECTED BEHAVIOR:
UbuntuA creates its own entry (eg /efi/ubuntu/grubx64_uuidA.efi ), and UbuntuB creates another entry (eg /efi/ubuntu/grubx64_uuidB.efi ), so that if UbuntuB's /boot/grub/grub.cfg is damaged, the user can still access UbuntuA via the UEFI firmware. |
|
