On Mon, Jun 15, 2020 Philip Rhoades <phil@xxxxxxxxxxxxx> wrote: > On 2020-06-15 19:05, Ed Greshko wrote: >> On 2020-06-11 05:41, R. G. Newbury wrote: >>> On 2020-06-09 Stephen Morris<samorris@xxxxxxxxxxxxxxx> wrote: >>>> >>>> if in /etc/default/grub you have the entry GRUB_ENABLE_BLSCFG=true >>>> that inserts a line into the grub processes to use the new BLS >>>> standard, in which case grub2-mkconfig and possibly grubby do >>>> nothing until that entry is set to false. I have always use >>>> grub2-mkconfig because I have never liked what grubby generated, >>>> and what BLS generates appears to be the same as what grubby does, >>>> and I found that I had to set that entry to false for >>>> grub2-mkconfig to continue to work. >>> >>> THANKS FOR THAT, Steve! >>> >>> I could not get grub2-mkconfig to actually change the grub.cfg >>> file. Now I know why ( but not why such a dangerously >>> misdescriptive switch would be hidden away in a default file). In >>> the past I would just edit the damn file, > > Hear, hear! Why did things have to get so obscure and complicated? 1) You can still edit one file. Simply "chmod -x" everything except "40_custom", then write your own "grub.cfg" within it, and run "grub2-mkconfig". 2) I suspect that grub2's mkconfig was inspired by Debian's grub1 update-grub. With grub1/grub-legacy on Debian, there was a section in "menu.lst" called "AUTOMAGIC" in which you set some options, for example groot=(hdX,Y) kopt=root=UUID=<uuid> ro altoptions=(single) single altoptions=(emergency) emergency and you'd end up with the following at the end of the "AUTOMAGIC" section after running "update-grub" title Debian 5.7.2 root (hdX,Y) kernel /boot/vmlinuz-5.7.2 root=UUID=<uuid> ro initrd /boot/initrd.img-5.7.2 title Debian 5.7.2 (single) root (hdX,Y) kernel /boot/vmlinuz-5.7.2 root=UUID=<uuid> ro single initrd /boot/initrd.img-5.7.2 title Debian 5.7.2 (emergency) root (hdX,Y) kernel /boot/vmlinuz-5.7.2 root=UUID=<uuid> ro emergency initrd /boot/initrd.img-5.7.2 There were probably a few other options that you could set, but I've forgotten... But grub2's more complex thangrub1, and the grub2 developers must've wanted to massage the config file a bit more than above, so we've ended up with lines and lines of scripts. _______________________________________________ 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
