On May 31, 2015 1:53 PM, "Adrian Sevcenco" <Adrian.Sevcenco(a)cern.ch>
wrote:
On 05/31/2015 10:27 PM, Pete Travis wrote:
> On 05/31/2015 01:27 AM, Adrian Sevcenco wrote:
>>
>> One more clarification i would like:
>> what is the difference between the loaders?:
>> gcdx64.efi
>> grubx64.efi
>> MokManager.efi
>> shim.efi
>> shim-fedora.efi
>>
>> the shim part i know that is for secure boot (which is disabled in my
case).
>> what are the others? is there a wiki page explaining this
files?
>>
>> Thank you!
>> Adrian
>>
>>
>>
>
> There might be wiki pages that explain all this, but wiki pages can be
> hard to find and often get lost and unmaintained, so I wrote a guide
> instead. It doesn't explain the individual files at the moment
> (although there is some copy in the sources for it) because it's
> information that you don't really need to get the system going, and I
> didn't want to overwhelm new users. I'll look at adding the info in an
> appropriate section.
>
> Until then, grubx64.efi is the actual grub second stage binary,
> MokManager.efi is for signature management, shim is the part that is
> signed and allows SecureBoot to work.
Thanks a lot for help and info!
One more thing i would like to clarify (as i am new to EFI stuff):
is it possible to have a boot media with live isos (like an usb stick)
for both
EFI and non-EFI systems? (i was wondering if just adding the
/boot/efi
part from
a system with a corresponding grub.conf would be enough to being
bootable
by both
legacy and UEFI only systems)
Thank you!
Adrian
Yes, the Fedora install media is designed to work with both UEFI and not
(as you discovered :)
Installing the grub2-efi and shim packages will populate /boot/efi/ for
Fedora. I think the part we might have brushed over was setting up the
existing EFI System Partition in fstab and the chroot...
--Pete