There's an argument for totally ignoring NVRAM. rEFInd, an EFI boot manager, produces its boot entries dynamically from fstab, a static configuration file, and the contents of /boot. It ignores NVRAM, there's no constantly modified grub.cfg on the EFI system partition when kernels are updated.
That sound worth investigating. How can it ignore NVRAM? Isn't NVRAM used by the firmware to decide which EFI executable to run? Or does rEFIind simply takes the place of the default EFI/BOOT/BOOTX64.EFI and hence there won't be any reason to have entries in NVRAM? Maybe I should RTFM instead of asking!
Thank you again for your help - it's most appreciated. Gareth -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
