On Tue, Nov 15, 2022 at 7:02 PM Colin Walters wrote:
>
>
>
> On Fri, Nov 11, 2022, at 11:41 PM, Chris Murphy wrote:
> > On Thu, Nov 10, 2022, at 6:08 PM, Robbie Harwood wrote:
> >> Ben Cotton writes:
> >>
> >>> By design, ostree does not manage bootloader updates as they can not
> >>> (yet)
On Mon, Nov 21, 2022 at 05:08:40PM -0500, Colin Walters wrote:
>
>
> On Mon, Nov 21, 2022, at 3:52 PM, Zbigniew Jędrzejewski-Szmek wrote:
>
> > In particular, two reasons why an upgrade might be interrupted were raised:
> > power being cut and the system crashing. Bootupd (or any other daemon)
On Mon, 2022-11-21 at 16:39 -0500, Neal Gompa wrote:
> > >
> > > We could do the same thing SUSE does and switch to calling
> > > scripts/tools to install into /boot and /boot/efi rather than doing it
> > > directly from RPM. That would simplify the logic of bootupd and allow
> > > it to just
On Mon, Nov 21, 2022, at 3:52 PM, Zbigniew Jędrzejewski-Szmek wrote:
> In particular, two reasons why an upgrade might be interrupted were raised:
> power being cut and the system crashing. Bootupd (or any other daemon) cannot
> do much about crashes so this isn't a good motivation. For power,
On Mon, Nov 21, 2022 at 4:17 PM Zbigniew Jędrzejewski-Szmek
wrote:
>
> On Mon, Nov 21, 2022 at 03:55:45PM -0500, Neal Gompa wrote:
> > On Mon, Nov 21, 2022 at 3:53 PM Zbigniew Jędrzejewski-Szmek
> > wrote:
> > >
> > > > https://fedoraproject.org/wiki/Changes/FedoraSilverblueBootupd
> > > > ==
On Mon, Nov 21, 2022 at 03:55:45PM -0500, Neal Gompa wrote:
> On Mon, Nov 21, 2022 at 3:53 PM Zbigniew Jędrzejewski-Szmek
> wrote:
> >
> > > https://fedoraproject.org/wiki/Changes/FedoraSilverblueBootupd
> > > == Summary ==
> > >
> > > By design, ostree does not manage bootloader updates as they
On Mon, Nov 21, 2022 at 3:53 PM Zbigniew Jędrzejewski-Szmek
wrote:
>
> > https://fedoraproject.org/wiki/Changes/FedoraSilverblueBootupd
> > == Summary ==
> >
> > By design, ostree does not manage bootloader updates as they can not
> > (yet) happen in a transactional, atomic and safe fashion. Thus
> https://fedoraproject.org/wiki/Changes/FedoraSilverblueBootupd
> == Summary ==
>
> By design, ostree does not manage bootloader updates as they can not
> (yet) happen in a transactional, atomic and safe fashion. Thus bootupd
> (https://github.com/coreos/bootupd) was created to solve this issue
Thanks, updated.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
On Fri, Nov 18, 2022, at 12:35 PM, Timothée Ravier wrote:
>> No, the install script install script in an RPM trigger, so the write is
>> still carried out by RPM.
>>
>> I don't agree. Just because a user can mess with files on the system
>> doesn't mean the rpmdb is a lie, nor is it reasonable
> No, the install script install script in an RPM trigger, so the write is
> still carried out by RPM.
>
> I don't agree. Just because a user can mess with files on the system
> doesn't mean the rpmdb is a lie, nor is it reasonable to go recheck all
> paths on the filesystem just in case they've
"Colin Walters" writes:
> On Tue, Nov 15, 2022, at 12:00 PM, Robbie Harwood wrote:
>
>> If your model doesn't permit the system to cease execution during
>> bootloader updates, then I'm not sure why you need bootupd at all -
>> traditional RPM updating will work just fine (assuming the A/B
On Tue, Nov 15, 2022, at 12:00 PM, Robbie Harwood wrote:
> If your model doesn't permit the system to cease execution during
> bootloader updates, then I'm not sure why you need bootupd at all -
> traditional RPM updating will work just fine (assuming the A/B change
> we've been talking about).
On Fri, Nov 11, 2022, at 11:41 PM, Chris Murphy wrote:
> On Thu, Nov 10, 2022, at 6:08 PM, Robbie Harwood wrote:
>> Ben Cotton writes:
>>
>>> By design, ostree does not manage bootloader updates as they can not
>>> (yet) happen in a transactional, atomic and safe fashion.
>>
>> As we've talked
Timothée Ravier writes:
>> Bootloaders are not single files. Consider UEFI:
>>
>> For grub2, there's both a .efi and some configuration that I'll handwave
>> for purposes of this conversation. For shim, it's more like 4 things -
>> the main shim*64.efi, fallback.efi, boot.efi, and boot.csv.
On Thu, Nov 10, 2022 at 03:24:07PM -0500, Ben Cotton wrote:
> https://fedoraproject.org/wiki/Changes/FedoraSilverblueBootupd
>
> This document represents a proposed Change. As part of the Changes
> process, proposals are publicly announced in order to receive
> community feedback. This proposal
On 11/14/22 13:32, Robbie Harwood wrote:
> Timothée Ravier writes:
>
>>> As we've talked about before, it's not possible to make updates
>>> transactional. It involves, per spec and depending on processor
>>> architecture, updating multiple files in different directories,
>>> potentially on
> Bootloaders are not single files. Consider UEFI:
>
> For grub2, there's both a .efi and some configuration that I'll handwave
> for purposes of this conversation. For shim, it's more like 4 things -
> the main shim*64.efi, fallback.efi, boot.efi, and boot.csv. These all
> serve different
Timothée Ravier writes:
>> As we've talked about before, it's not possible to make updates
>> transactional. It involves, per spec and depending on processor
>> architecture, updating multiple files in different directories,
>> potentially on different filesystems entirely, one of which is
If I understood things correctly, that's not how this would work. We would not
touch the boot order at all.
See https://github.com/rhboot/shim/pull/502 &
https://mivehind.net/2022/08/17/shim-ab-booting-poc/.
___
devel mailing list --
On Thu, Nov 10, 2022, at 6:08 PM, Robbie Harwood wrote:
> Ben Cotton writes:
>
>> By design, ostree does not manage bootloader updates as they can not
>> (yet) happen in a transactional, atomic and safe fashion.
>
> As we've talked about before, it's not possible to make updates
>
> As we've talked about before, it's not possible to make updates
> transactional. It involves, per spec and depending on processor
> architecture, updating multiple files in different directories,
> potentially on different filesystems entirely, one of which is fat32.
I should probably have
Ben Cotton writes:
> By design, ostree does not manage bootloader updates as they can not
> (yet) happen in a transactional, atomic and safe fashion.
As we've talked about before, it's not possible to make updates
transactional. It involves, per spec and depending on processor
architecture,
https://fedoraproject.org/wiki/Changes/FedoraSilverblueBootupd
This document represents a proposed Change. As part of the Changes
process, proposals are publicly announced in order to receive
community feedback. This proposal will only be implemented if approved
by the Fedora Engineering Steering
https://fedoraproject.org/wiki/Changes/FedoraSilverblueBootupd
This document represents a proposed Change. As part of the Changes
process, proposals are publicly announced in order to receive
community feedback. This proposal will only be implemented if approved
by the Fedora Engineering Steering
25 matches
Mail list logo
