modules, firmware, kernel size (was Re: systemd requires HTTP server and serves QR codes)

Justin M. Forbes jmforbes at
Thu Oct 18 15:56:21 UTC 2012

On Thu, Oct 18, 2012 at 11:34:00AM -0400, Josh Boyer wrote:
> On Thu, Oct 18, 2012 at 11:15 AM, Matthew Miller
> <mattdm at> wrote:
> > On Thu, Oct 18, 2012 at 10:44:58AM -0400, Josh Boyer wrote:
> >> At the moment though, all of this is just talk anyway.  If something
> >> like this is to happen, someone actually has to do work.
> >
> > Start with an idea, discuss it, come up with a plan, find resources for that
> > plan, and then implement. Sometimes things happen the other way around, but
> > only when we happen to be lucky, and it often has consequences like extra
> > ongoing work with no support. So, just talk is an important place to start.
> OK.  So here's a more blunt response.
> I'm really against splitting the modules up into more subpackages,
> regardless of how many it is.  I will not spend any time looking at how
> to do that.  I won't spend time discussing further plans to do something
> I don't feel is maintainable.  If you find someone willing to, great.
> Post patches to the kernel list and we'll review them.  But I'm telling
> you now that it will be an uphill battle.
Just to be clear on this, if someone feels it is worthwhile and wants to
step up and do the work, it can't just be someone who will send patches to
change the current kernel and leave. It has to be someone willing to sign
up to maintain the solution in the rawhide kernel. Modules change, get added
or removed, and/or have deps change pretty much every single release.  3.7
just moved the nat modules.  This is why we are saying that it is much
easier to do a different build of another flavor than to split out the
modules into more subpackages.


More information about the devel mailing list