On Wed, May 1, 2019 at 7:19 PM Charles R. Dennett <cdenn...@gmail.com> wrote: > On 5/1/19 11:07 AM, Tom H wrote: >> On Wed, May 1, 2019 at 12:48 PM Charles R. Dennett <cdenn...@gmail.com> >> wrote: >>> >>> Is there any way to tell just by looking for the presence or absence >>> of any particular file or directory that you would run into this >>> bug? >> >> Unless you're multi-booting and grub's managed by another >> distribution, you may as well run "grub2-install /dev/...". The bug >> report says that it's supposed to be fragile, but it last failed for >> me seven years ago (more or less) with "/boot" on mdraid1. Maybe I've >> just been lucky... > > I went ahead and run grub2-install /dev/sda and rebooted. All seems > well. No changes in the boot process that I could see. I still get the > kernel menu and then it boots and I get all the messages about what's > starting. (I removed the rhgb and quiet option years ago. As an old > retired Linux/Solaris admin I prefer to see things happening. It just > makes me feel better.)
Good :) There shouldn't be a difference. BLS means that the grub menu's built from "/boot/loader/entries/*" instead of from a monolithic "/boor/grub2/grub.cfg". I had to use "grub2-switch-to-blscfg" for the switch to be made, for a new install using dnf instead of anaconda. The latter might set up BLS by default (does anyone know?). _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
