On 28/12/19 2:48 am, Mauricio Tavares wrote:
With that said, if that is the case, why would the alias
/etc/grub2.cfg still be created if it points to a non-existing file?
Wouldn't it make sense for it to just either not to be there at all or
point to the efi one? I can make arguments for both sides, but not for
a homeless alias.
[root@linux etc]# rpm -qf /etc/grub2.cfg
grub2-pc-2.02-0.80.el7.centos.x86_64
[root@linux etc]# rpm -qf /etc/grub2-efi.cfg
grub2-efi-x64-2.02-0.80.el7.centos.x86_64
...in other words, the grub2.cfg link is installed with the grub2-pc
package and the grub2-efi.cfg link is created with the grub2-efi
package. You can probably get away without the grub2-efi package on a
legacy bios system, but not the other way around, so an efi system will
have both links.
At the end of the day it's harmless, don't loose any sleep over it.
Peter
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
