Re: F38 proposal: Unified Kernel Support Phase 1 (System-Wide Change proposal)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Jan 2, 2023 at 4:40 PM Zbigniew Jędrzejewski-Szmek
<zbyszek@xxxxxxxxx> wrote:
>
> On Mon, Jan 02, 2023 at 05:59:07PM +0100, mkolman@xxxxxxxxxx wrote:
> > On Mon, 2023-01-02 at 15:42 +0100, Gerd Hoffmann wrote:
> > > On Thu, Dec 22, 2022 at 04:53:47PM +0100, Jiri Konecny wrote:
> > > > Hi all,
> > > >
> > > > > == Benefit to Fedora ==
> > > > > * Better secure boot support (specifically the initrd is covered
> > > > > by
> > > > > the signature).
> > > > > * Better confidential computing support (measurements are much
> > > > > more
> > > > > useful if we know what hashes to expect for the initrd).
> > > > > * More robust boot process (generating the initrd on the
> > > > > installed
> > > > > system is fragile, root cause for kernel bugs reported is simply
> > > > > a
> > > > > broken initrd sometimes).
> > > > Just want to add Anaconda installation environment is also fighting
> > > > with the
> > > > second point.
> > >
> > > Third point I assume, i.e. initrd generation problems being reported
> > > as
> > > anaconda bugs?
> > >
> > > While being at it: anaconda seems to explicitly call dracut to
> > > generate
> > > the initrd (according to the messages it prints).  What is the reason
> > > for this?  Shouldn't this already happen as part of the rpm
> > > transaction,
> > > when the kernel install scripts are running?
> > IIRC the main reason is the esentially random package installation
> > order during the RPM transaction.
>
> kernel-core scriptlets call 'kernel-install add' (which in turns calls dracut at
> some point) from %posttrans. So package installation order is not relevant, that
> all happens after all packages are in place. Maybe anaconda doesn't need to call
> dracut a second time.
>

It does need to call it for non-package transaction based
installations (live OS, ostree, etc.).



-- 
真実はいつも一つ!/ Always, there's only one truth!
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux