On Tue, Oct 7, 2025 at 5:34 PM Neal Gompa <[email protected]> wrote:
>
> On Tue, Oct 7, 2025 at 11:30 AM Fabio Valentini <[email protected]> wrote:
> >
> > On Tue, Oct 7, 2025 at 2:16 PM Neal Gompa <[email protected]> wrote:
> > >
> > > On Tue, Oct 7, 2025 at 3:35 AM Michael J Gruber <[email protected]> 
> > > wrote:
> > > >
> > > > 07.10.2025 03:07:26 Neal Gompa <[email protected]>:
> > > >
> > > > > On Mon, Oct 6, 2025 at 8:41 PM Luya Tshimbalanga 
> > > > > <[email protected]> wrote:
> > > > >>
> > > > >> It seems like an opportunity to revisit integrating the /boot into 
> > > > >> btrfs (notably for Workstation) as subvolume for future release.
> > > > >>
> > > > >
> > > > > I'd like to, but it's blocked on getting a patch into our GRUB that
> > > > > lets the grubenv live in the btrfs bootloader space.
> > > > >
> > > > > There's a bug tracking this: https://bugzilla.redhat.com/2372973
> > > > >
> > > >
> > > > Nice. Before I get too excited:
> > > > (How) Does this work with luks?
> > > >
> > >
> > > LUKS will still require a dedicated /boot partition. When Btrfs native
> > > encryption lands in the near future, we'd encrypt each subvolume but
> > > leave /boot alone instead.
> >
> > Heh, hasn't this been "near future" for a while now? :)
> >
>
> Well, it was recently picked back up again just a couple weeks ago:
> https://github.com/btrfs/linux/issues/1000#issuecomment-3337123850
>
> > On another note, I've read that linux supports loading and merging
> > multiple initramfs images.
> > So ... it sounds as if it would be possible to deduplicate stuff like
> > "firmware", which right now is present 4 (?) times on /boot - by
> > putting it into a separate initramfs that is *shared* by all three
> > bootloader entries (maybe not the rescue boot entry)?
> >
>
> That only works if firmware isn't tied to specific driver versions,
> which is not how it works right now. Since driver versions and
> firmware blobs are tightly coupled (for at least NVIDIA), there's no
> deduplication wins right now.

I'm not sure I understand.

The firmware is shipped by linux-firmware* packages, which aren't tied
to specific "kernel*" package versions.
Doesn't that mean that stuff included in initramfs images from
linux-firmware* should be identical between initramfs images for
different kernels?

Fabio
-- 
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to