On Tue, May 7, 2019 at 8:29 AM Steven A. Falco wrote:
>
> On 5/6/19 5:51 PM, Chris Murphy wrote:
>
> > But it's worth keeping an eye on anomalies. There is the potential for
> > goofy things happening. Unrelated to this particular feature, rather
> > it was grub.cfg being updated, in cases where
On 5/6/19 5:51 PM, Chris Murphy wrote:
> But it's worth keeping an eye on anomalies. There is the potential for
> goofy things happening. Unrelated to this particular feature, rather
> it was grub.cfg being updated, in cases where that update happened
> very quickly followed by an immediate
On Mon, May 6, 2019 at 2:47 PM Chris Murphy wrote:
>
> I suggest keeping things as is, with saved_entry set in the grubenv.
> And that's because GRUB and the grub-boot-success.service are able to
> do an automatic fallback to the previous working kernel if boot fails
> following a kernel upgrade.
On Mon, May 6, 2019 at 3:51 PM Chris Murphy wrote:
>
> GRUB pre-boot environment can read grubenv from anything GRUB supports
> reading, which is practically anything including mdadm RAID. Your
> grubenv can be read, it just can be changed by GRUB in the pre-boot
^can't
!!
--
Chris Murphy
On Mon, May 6, 2019 at 3:15 PM Steven A. Falco wrote:
>
> As I was reading through the documentation, I came across a statement that
> grubenv is unavailable on RAID - please see the second to last sentence here:
>
> https://www.gnu.org/software/grub/manual/grub/html_node/Environment-block.html
On 5/6/19 4:47 PM, Chris Murphy wrote:
> On Mon, May 6, 2019 at 1:04 PM Steven A. Falco wrote:
>>
>>> # grub2-editenv list
>>
>> Here is the command output:
>>
>> saved_entry=2aa6409d5c354eea9cc2e4630c4efda0-5.0.11-300.fc30.x86_64
>> boot_success=1
>> boot_indeterminate=1
>>
On Mon, May 6, 2019 at 1:04 PM Steven A. Falco wrote:
>
> > # 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
On 5/6/19 2:53 PM, Chris Murphy wrote:
> On Mon, May 6, 2019 at 7:39 AM Steven A. Falco 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,
On Mon, May 6, 2019 at 7:39 AM Steven A. Falco 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)"
>
On 5/5/19 6:29 PM, Chris Murphy wrote:
> On Sun, May 5, 2019 at 8:22 AM Steven A. Falco wrote:
>>
>> I just upgraded my machine from F29 to F30. Now, whenever I install a new
>> kernel, the new kernel does not automatically become the default. In other
>> words, when I reboot, the previous
On Sun, May 5, 2019 at 8:22 AM Steven A. Falco wrote:
>
> I just upgraded my machine from F29 to F30. Now, whenever I install a new
> kernel, the new kernel does not automatically become the default. In other
> words, when I reboot, the previous kernel is still chosen by grub2.
>
> I can
On 5/5/19 2:04 PM, Nico Kadel-Garcia wrote:
> On Sun, May 5, 2019 at 10:22 AM Steven A. Falco wrote:
>>
>> I just upgraded my machine from F29 to F30. Now, whenever I install a new
>> kernel, the new kernel does not automatically become the default. In other
>> words, when I reboot, the
On Sun, May 5, 2019 at 10:22 AM Steven A. Falco wrote:
>
> I just upgraded my machine from F29 to F30. Now, whenever I install a new
> kernel, the new kernel does not automatically become the default. In other
> words, when I reboot, the previous kernel is still chosen by grub2.
>
> I can
13 matches
Mail list logo
