On Thu, Jun 13, 2019 at 10:27 AM Sérgio Basto <sergio@xxxxxxxxxx> wrote: > > Thanks for the answer > Correct , but anaconda generate /etc/default/grub and GRUB comand-line > in particularity and I'd like have a way to generate /etc/default/grub > again without run anaconda installer again ... . > > All the magic that anaconda does , should be interesting reproduce inbash shell . I don't think it works that way in anaconda. Most of them I expect are variables that the installer knows about because they were set at the time of installation. I don't think it discovers them from parsing fstab. In fact one of the things we've lost with the bootloaderspec change is a script that can create menuentries. Now instead of grub2-mkconfig, to recreate entries, you need to reinstall a kernel in order for the scripts to be run that create the /boot/loader/entries/*conf files. Realistically, they shouldn't go bad or vanish. But then neither should grub.cfg - and yet we do from time to time see recreating grub.cfg fix problems, perhaps mostly because grub2-mkconfig is a litany of many scripts that parse things including /etc/fstab. -- Chris Murphy _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/test@xxxxxxxxxxxxxxxxxxxxxxx
