update to grub 2:2.06.r415.g1a241e050-1 is live.
Like on every update of the grub package it is recommended to reinstall grub files into the system (grub-install) and regenerate the grub.cfg as you will get noticed in the update terminal.
Make sure to do this before rebooting after the update!!
:: To use the new features provided in this GRUB update, it is recommended
to install it to the MBR or UEFI. Due to potential configuration
incompatibilities, it is advised to run both, installation and generation
$ grub-install ...
$ grub-mkconfig -o /boot/grub/grub.cfg
It is more about making sure the used package and installed files work nicely together, in cases it could be something changed on package what is not compatible with what is installed by older package into the system.
This will not be the case for every grub update but redoing these two steps is the recommendedsafe way to handle it.
Don’t update the package grub at all: It will probably break eventually when something becomes incompatible. You also won’t get security updates.
Don’t run grub-install but do run grub-mkconfig: Any updates that grub makes to the EFI stub(including security issues) will not be present on your system. Additionally, if there is an incompatibility between the EFI stub and the generated grub config it could result in an unbootable system
Don’t run grub-install or grub-mkconfig: Any updates that grub makes to the EFI stub(including security issues) will not be present on your system. Also, if you ever add/remove a kernel and run grub-mkconfig you will could cause the same situation as #2
well… I thought I was getting security updates through UpdateInTerminal…
I would do it if it didn’t include so many things that I have no idea about and feel anxious about even trying to touch these settings…
but asking someone to do a 5-year-old step-by-step guide for me feels like too much to ask
I guess I’m just gonna hope that if anything happens, someone kind and smart here will help me out
by the way… will installing rEFInd free me from these issues?..
not real trouble as long as you can boot just fine there is no issue it is only the recommended way to handle grub updates on arch now… to reinstall grub files and regenerate the grub.cfg…
and using --no-nvram option is smart to not rewrite the bootentry in the nvram.