On 3/19/24 17:28, Sam Varshavchik wrote:
Samuel Sieb writes:
Then there's nothing you need to do. grub has been updated.
But what do you mean by the "bootloader" though?
Well, what actually loads grub and runs it. On my other, BIOS system,
the one that I replaced a failed disk, recently – after I reassembled
and resynced all RAID partitions, I ran grub2-install and I'm fairly
certain there was a definitive change in grub's behavior, afterwards.
Originally three periods were initially shown, for a few seconds, before
the grub menu opened. I have a recollection that the number of periods
is a diagnostic indications what went wrong if grub fails to start for
some reason. This changed to a "Welcome to grub" banner.
So, it looks to me like years of regular grub updates, and countless
Fedora releases, did not really end up updating …everything, on a BIOS
system.
That's the difference between a BIOS (legacy) system and a UEFI system.
On the legacy system, the bootloader is embedded in the boot sector and
elsewhere and needs to be specially updated. On UEFI, the "BIOS" loads
the grub executable from the EFI partition and runs it directly. So if
you update that file, the new code is run on the next boot. And that
file is managed by the package.
rpm -ql grub2-efi-x64
--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
