On 5/6/19 2:53 PM, Chris Murphy wrote:
> On Mon, May 6, 2019 at 7:39 AM Steven A. Falco <stevenfa...@gmail.com> wrote:
>>
>> Thanks for the explanation. Here are the contents of /etc/default/grub. As
>> you suspected, there is a GRUB_DEFAULT=saved line in there.
>>
>> GRUB_TIMEOUT=5
>> GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
>> GRUB_DEFAULT=saved
>> GRUB_DISABLE_SUBMENU=true
>> GRUB_TERMINAL_OUTPUT="console"
>> GRUB_CMDLINE_LINUX="resume=/dev/mapper/fedora-swap rd.lvm.lv=fedora/root
>> rd.md.uuid=77ae1678:58a79067:c0ad29e6:bd1862f8
>> rd.md.uuid=bac1fa34:2d7a26e5:969d63ac:33ff4572 rd.lvm.lv=fedora/swap"
>> GRUB_DISABLE_RECOVERY="true"
>> GRUB_ENABLE_BLSCFG=true
>
> This is a stock /etc/default/grub - there's nothing custom about it.
>
>> I looked for grubenv, and the only one I found is at /boot/grub2/grubenv.
>> There is nothing in /boot/efi/EFI/fedora. This machine was set up on
>> 2018-11-24, so it started life as a Fedora 29 machine.
>
> Ahh not sure. Might be new in Fedora 30 and doesn't get changed on upgrades?
>
>> Is there a command I should run to move grubenv to /boot/efi/EFI/fedora? I
>> think I would also have to create a symlink from
>> /boot/efi/EFI/fedora/grubenv to /etc/default/grub. I could of course do it
>> manually, but if there is a better procedure, like re-installing some
>> package(s), that would be preferable.
>
> The purpose of the symlink is so that grubenv commands and usage just
> work without respect to firmware type. You don't have to fix this. But
> I'm still curious about the contents of that grubenv, so what do you
> get fro
>
> # grub2-editenv list
Here is the command output:
saved_entry=2aa6409d5c354eea9cc2e4630c4efda0-5.0.11-300.fc30.x86_64
boot_success=1
boot_indeterminate=1
kernelopts=root=/dev/mapper/fedora-root ro resume=/dev/mapper/fedora-swap
rd.lvm.lv=fedora/root rd.md.uuid=77ae1678:58a79067:c0ad29e6:bd1862f8
rd.md.uuid=bac1fa34:2d7a26e5:969d63ac:33ff4572 rd.lvm.lv=fedora/swap
I'm reading through the various scripts trying to understand the impact of
GRUB_DEFAULT. It seems like having GRUB_DEFAULT=saved is not currently hurting
me. The last upgrade, to 5.0.11-300, properly made that kernel the new default.
If GRUB_DEFAULT is commented out, then I think grub will always choose the
first item in its menu, which would be fine, because the newest kernel always
appears first in the grub menu. Is that why you recommended commenting it out?
Steve
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
