Hi
On Wed, Oct 28, 2026 at 10:41:15AM -0400, Noah Meyerhans wrote:
> How granular do you plan on making the modules packages?
In the first step it'll just be two conflicting packages, one with all,
one with just the virtualized stuff.
> Use cases for
> things like filesystems and network protocols are likely going to be the
> same across cloud and non-cloud deployments, so it might make sense to
> have a "common" modules package that's installed by default in just
> about all cases.
Maybe. But for now I don't see a usecase for that. It just saves a bit
of space on our mirrors, but instead of bloats the Packages files and
the dependency tree.
Fedora creates a -core package, but this is meant as standalone
installable and contains everything for a normal current system to work.
> The major differences between virtualization platforms
> is in the device models they expose to guests. Would it be feasible to
> offer dedicated "aws", "hyperv/azure", "gcp", etc driver packages that
> provide hardware support for those specific environments? Or is that
> too much work/overhead? The benefit of such disk space optimizations
> can be significant when scaled across hundreds or thousands of systems.
I don't think there would be a real benefit from splitting it this far.
We already shave 3/4 from the size of the kernel package, saving another
1% is IMHO not worth the hassle.
> For the record, I don't love the idea of eliminating the second kernel
> build. While we haven't taken advantage of this opportunity to this
> point, it allows us to provide build-time optimizations to best tune
> performance for specific deployment scenarios.
Noted. I currently consider this to not have a high enough value for
that. The current cloud kernel config got some larger problems in how
it tries to subtract config entries, not only add. This work done here
will also be folded back into what we do for the installer and reduce
the complexity also.
Bastian
--
I'm frequently appalled by the low regard you Earthmen have for life.
-- Spock, "The Galileo Seven", stardate 2822.3
