By now we've seen a few postings that you can't customise grub the way that it's meant to be done (by modifying /etc/default/grub) as the processes used by "dnf update ..." ignore it.
Why doesn't this work the way that it's meant to?
On 08/14/2017 09:09 PM, Tim wrote:
By now we've seen a few postings that you can't customise grub the way that it's meant to be done (by modifying /etc/default/grub) as the processes used by "dnf update ..." ignore it.
Why doesn't this work the way that it's meant to?
The question is what is it meant to do. I think it's only used by grub2-mkconfig. When you dnf update the kernel, the script uses grubby to modify the grub.cfg file. Grubby takes the previous kernel's command line and uses that to make the command line for the new kernel. For most situations, that does what is needed.
Allegedly, on or about 15 August 2017, Samuel Sieb sent:
The question is what is it meant to do. I think it's only used by grub2-mkconfig. When you dnf update the kernel, the script uses grubby to modify the grub.cfg file. Grubby takes the previous kernel's command line and uses that to make the command line for the new kernel. For most situations, that does what is needed.
But you're specifically told not to hand-edit the grub config file, and put your options in the defaults file.
-
Samuel Sieb -
Tim