Please revert some .config changes and/or add UNR flavors
Christian Pernegger
pernegger at gmail.com
Wed May 13 15:45:39 UTC 2009
Hi list!
I'm running jaunty UNR on a Dell Mini 9 since release, please be
advised that the following is rather netbook-centric.
The jaunty kernel seems to have everything but the kitchen sink built
in, which is about the only thing I don't like about the release. It's
just too bloated and makes it impossible to disable stuff that a
simple blacklist entry would have taken care of before. I'm going to
list a few that really bug me, in the hope that the .config will be
changed for karmic and/or the UNR variant will get their own kernel
flavor with more modularity.
General: many compiled-in features -> many running kernel threads. Why
does the entire bt stack have to be built in? ecryptfs? SCSI? ...
These in turn are the only reason I can think of for the 8-10
wakeups/sec powertop gives me in single user mode on a raw fb-console.
IPv6: Yes, I know it should be tested. Even though it looks rather
stillborn to me as an IPv4 replacement. Enabling it by default is
fine, but why take away the ability to disable it? Lots of routers,
particularly of the wireless variety choke on it. What's more, I just
don't feel comfortable with it from a security pov. I simply don't
know about it to even try to firewall it effectively.
USB1: The USB1 controllers that are provided for backwards
compatibility in USB2 systems have rotten power management, which is
why one might like to turn them off by unloading the module. How about
modularizing the *_hcd modules again?
Cheers,
Christian
More information about the kernel-team
mailing list