On Thu, Feb 14, 2019 at 9:12 PM Chris Murphy wrote:
>
> On Thu, Feb 14, 2019 at 3:33 AM Javier Martinez Canillas
> wrote:
>
> > > - new Fedora 30 installations, and upgrades of Fedora 28 and 29 to Fedora
> > > 30
> >
> > Correct. Although I would just say upgrades from F29 to F30. Or can
> >
On Thu, Feb 14, 2019 at 3:33 AM Javier Martinez Canillas
wrote:
> > - new Fedora 30 installations, and upgrades of Fedora 28 and 29 to Fedora 30
>
> Correct. Although I would just say upgrades from F29 to F30. Or can
> you skip a release when doing a system upgrade?
Fedora 28 folks will see an
On Thu, Feb 14, 2019, at 6:05 AM, Javier Martinez Canillas wrote:
> So our plan is to have a library + command
> line tool for configuring everything related to the bootloader.
FWIW, "rpm-ostree kargs" is already a CLI and DBus API to change the kernel
arguments that we expect people to use on
Hello Wolfgang,
On Thu, Feb 14, 2019 at 1:51 PM Wolfgang Ulbrich wrote:
>
> How can i disable this new feature complete?
You can disable it by removing the GRUB_ENABLE_BLSCFG=true from
/etc/default/grub and re-generating your grub2.cfg with grub2-mkconfig
(i.e: grub2-mkconfig -o
How can i disable this new feature complete?
I am using a multiboot system with 3 different root partitions for testing my
packages.
Sadly reading the kernel vars with root=UUID=from
[root@mother rave]# cat /boot/grub2/grubenv
# GRUB Environment Block
boot_success=1
boot_indeterminate=0
On Thu, Feb 14, 2019 at 5:06 AM Chris Murphy wrote:
>
> On Tue, Feb 12, 2019 at 5:08 AM Javier Martinez Canillas
> wrote:
> > You are correct, we will work on more documentation and also better
> > tooling to manage the BLS snippets, grubenv file, etc. For example
> > grub2-editenv is very
On Thu, Feb 14, 2019 at 10:34 AM Javier Martinez Canillas
wrote:
>
> Hello Chris,
>
> On Wed, Feb 13, 2019 at 7:49 PM Chris Murphy wrote:
> >
> > I glossed over the fact upgrades to Fedora 30 will be converted to the
> > "bls way" of things. So I want to be sure I understand feature scope:
> >
>
Hello Chris,
On Wed, Feb 13, 2019 at 7:49 PM Chris Murphy wrote:
>
> I glossed over the fact upgrades to Fedora 30 will be converted to the
> "bls way" of things. So I want to be sure I understand feature scope:
>
> - all Fedora 30 editions and spins and archs, *except* 32-bit ARM
Yes, because
On Tue, Feb 12, 2019 at 5:08 AM Javier Martinez Canillas
wrote:
> You are correct, we will work on more documentation and also better
> tooling to manage the BLS snippets, grubenv file, etc. For example
> grub2-editenv is very fragile as was mentioned in this thread.
I'm looking at this:
I glossed over the fact upgrades to Fedora 30 will be converted to the
"bls way" of things. So I want to be sure I understand feature scope:
- all Fedora 30 editions and spins and archs, *except* 32-bit ARM
- new Fedora 30 installations, and upgrades of Fedora 28 and 29 to Fedora 30
- does not
On Tue, Feb 12, 2019 at 2:34 PM Chris Murphy wrote:
>
> If grubenv can be change from pre-boot environment, we can't correctly
> determine if boot has succeeded or failed.
s/can/can't
s/change/changed
(grubenv can't be changed in certain custom partitioning cases e.g.
/boot on Btrfs or /boot
On Tue, Feb 12, 2019 at 2:18 PM Chris Murphy wrote:
>
> In the short term it means any features depending on writing to grubenv from
> pre-boot GRUB (as opposed to Linux user space GRUB tools), can only be
> expected on UEFI (grubenv is always on FAT), or if on BIOS only with default
>
On Tue, Feb 12, 2019, 7:10 AM Javier Martinez Canillas
> I see, I would had thought that the advice would had been to use
> grub-editenv create instead. But still grub2-editenv create will only
> prevent removing the symlink, it won't help with the issue of the
> kernelopts variable not being
On 12/02/2019 14:10, Javier Martinez Canillas wrote:
I see, I would had thought that the advice would had been to use
grub-editenv create instead. But still grub2-editenv create will only
prevent removing the symlink, it won't help with the issue of the
kernelopts variable not being set.
We
Hello Nicolas,
On Tue, Feb 12, 2019 at 2:58 PM Nicolas Mailhot
wrote:
>
> Le 2019-02-12 13:32, Javier Martinez Canillas a écrit :
> Hi Javier
>
> > I didn't get how it will break the symlink.
>
> You get a "environment block too small" on kernel update
>
> You type "environment block too small"
Le 2019-02-12 13:32, Javier Martinez Canillas a écrit :
Hi Javier
I didn't get how it will break the symlink.
You get a "environment block too small" on kernel update
You type "environment block too small" in google because you want the
update to work
You get some ubuntu advice that says
On Mon, Feb 11, 2019 at 8:53 PM Chris Murphy wrote:
>
> On Mon, Feb 11, 2019 at 5:40 AM Nicolas Mailhot
> wrote:
> >
[snip]
> >
> > FYI I had to rescue two EFI rawhide system this week-end borked by grub
> > changes. As far as I could reconstruct:
> >
> > 1. the new grub needs the env file to
Hello Nicolas,
On Mon, Feb 11, 2019 at 1:41 PM Nicolas Mailhot
wrote:
>
> Le 2019-02-10 20:05, Chris Murphy a écrit :
> > On Wed, Feb 6, 2019 at 1:08 AM Javier Martinez Canillas
>
> > Between this feature for F30, and the F29 feature to hide the grub
> > menu which comes with boot success+fail
Hello Chris,
Sorry for the late response but I was on vacation last week.
On Sun, Feb 10, 2019 at 8:06 PM Chris Murphy wrote:
>
> On Wed, Feb 6, 2019 at 1:08 AM Javier Martinez Canillas
> wrote:
> >
> > On Wed, Feb 6, 2019 at 5:28 AM Chris Murphy wrote:
> > >
> > >
Le 2019-02-11 21:39, Chris Murphy a écrit :
On Mon, Feb 11, 2019 at 1:14 PM Nicolas Mailhot
wrote:
That was during dnf update to the result of the latest rawhide mass
rebuild, on two UEFI systems, one initially installed in september
2015,
the other in january 2019, with whatever was most
On Mon, Feb 11, 2019 at 1:14 PM Nicolas Mailhot
wrote:
>
> That was during dnf update to the result of the latest rawhide mass
> rebuild, on two UEFI systems, one initially installed in september 2015,
> the other in january 2019, with whatever was most current then and then
> switched to rawhide
Le lundi 11 février 2019 à 12:52 -0700, Chris Murphy a écrit :
> On Mon, Feb 11, 2019 at 5:40 AM Nicolas Mailhot
> wrote:
> > Le 2019-02-10 20:05, Chris Murphy a écrit :
> > > On Wed, Feb 6, 2019 at 1:08 AM Javier Martinez Canillas
> > > Between this feature for F30, and the F29 feature to hide
On Mon, Feb 11, 2019 at 5:40 AM Nicolas Mailhot
wrote:
>
> Le 2019-02-10 20:05, Chris Murphy a écrit :
> > On Wed, Feb 6, 2019 at 1:08 AM Javier Martinez Canillas
>
> > Between this feature for F30, and the F29 feature to hide the grub
> > menu which comes with boot success+fail marking by using
Le 2019-02-10 20:05, Chris Murphy a écrit :
On Wed, Feb 6, 2019 at 1:08 AM Javier Martinez Canillas
Between this feature for F30, and the F29 feature to hide the grub
menu which comes with boot success+fail marking by using the grubenv,
there are substantial changes in bootloading on Fedora
On Wed, Feb 6, 2019 at 1:08 AM Javier Martinez Canillas
wrote:
>
> On Wed, Feb 6, 2019 at 5:28 AM Chris Murphy wrote:
> >
> > https://fedoraproject.org/wiki/Changes/BootLoaderSpecByDefault
> >
> > I want this change to succeed but I'm experiencing a regression, and
> > while trying to
Hello Chris,
On Wed, Feb 6, 2019 at 5:28 AM Chris Murphy wrote:
>
> https://fedoraproject.org/wiki/Changes/BootLoaderSpecByDefault
>
> I want this change to succeed but I'm experiencing a regression, and
> while trying to troubleshoot it I'm finding it difficult to understand
> the myriad
26 matches
Mail list logo
