Chris Snook (csnook(a)redhat.com) said:
> See various and sundry plumber's conf discussions.
Not sure where things are being posted. Summary:
- modules are wasteful (you lose a good chunk of code size savings in
page round up)
- modules are slow (well, modprobe is)
- for the modules that are used by 90% of machines, what's the point
of having them static?
- killing the initrd for that general 90% case can be a big win
> Comments? (The netfilter stuff needs further investigation.)
If this is going to make it easier to do fancy things in the initrd, I'm
all for it. If it's just a TLB thing, I don't think it's worth it.
Fancy things by not having the initrd.
Won't this make it harder for people to test experimental wireless
drivers? Unless the vendors start opening specs, we're going to have a
perpetual need to play around in this area with each new hardware rev.
How so? There's one version shared among all the in-tree modules. If
you're developing the kernel, you're already rebuilding, so you can
For the love of god, no. We have lots of sound problems that require
modprobe magic to troubleshoot and work around.
Fix the $*@* driver, then!
(FWIW, the only sound problems I've seen recently is that the volume
restore scripts got broken.)
This will require people
to rebuild their kernel just to test sound fixes, which will scare away
an awful lot of testers and inconvenience the rest.
How often are we shipping random source patches to Fedora users, who
would have to install kernel-devel and kernel-source anyway, causing
them to download just as much data as a new test kernel?