Hello Richard,
On Sat, Oct 26, 2019 at 1:23 PM Richard Shaw <hobbes1069(a)gmail.com> wrote:
The grub2-pc package doesn't seem to do anything except provide a broken link in /etc
to grub2.cfg...
You are correct, the package is only needed for legacy BIOS installs.
There was a bug in Anaconda that caused grub2-pc to wrongly be
included for EFI installs. This was fixed by:
https://github.com/rhinstaller/anaconda/commit/8a8cc7a1a9bee434d07836e43e...
ll /etc/grub2.cfg
lrwxrwxrwx. 1 root root 22 May 20 12:19 /etc/grub2.cfg -> ../boot/grub2/grub.cfg
The /boot/grub2/grub.cfg must be a %ghost entry in the rpm as the file doesn't
actually exist:
Yes is a %ghost file and created by Anaconda on installation using the
grub2-mkconfig tool. Just like the /etc/grub2-efi.cfg file on EFI
installs, that's also a %ghost file from the grub2-efi package.
# rpm -ql grub2-pc
/boot/grub2/grub.cfg
/boot/loader/entries
/etc/grub2.cfg
The description from the info about the package is also useless:
The GRand Unified Bootloader (GRUB) is a highly configurable and
customizable bootloader with modular architecture. It supports a rich
variety of kernel formats, file systems, computer architectures and
hardware devices.
This subpackage provides support for %{1} systems.
---
It only has the standard description and a line with a variable that's no longer
getting expanded.
This has also been fixed:
https://src.fedoraproject.org/rpms/grub2/c/af06f22ee4f945189d5cd02ba4b437...
I removed it from my system and I'm about to reboot :)
Yes, it's OK to remove the grub2-pc package on an EFI system.
Thanks,
Richard
Best regards,
Javier