| 1 |
On 2013-01-08, Stefan G. Weichinger wrote: |
| 2 |
|
| 3 |
[...] |
| 4 |
> * I remember a thread here where this was discussed already: |
| 5 |
> |
| 6 |
> How do you guys get to your .config for a recent kernel? "make |
| 7 |
> oldconfig" doesn't always work out best, I recall? |
| 8 |
> |
| 9 |
> My kernel config is maintained along for years now and has survived |
| 10 |
> several hardware changes. I don't have any obvious problems but I wonder |
| 11 |
> if I have something in there that is deprecated and might be better |
| 12 |
> thrown out. |
| 13 |
|
| 14 |
I don't use anything other than stable code releases from portage, but |
| 15 |
even then I usually do make oldconfig, followed by a by-hand inspection |
| 16 |
of the options with make menuconfig, to catch stuff that got through me |
| 17 |
in make oldconfig, and to see if there's any change in other options |
| 18 |
that I want to tune. |
| 19 |
|
| 20 |
> Does it make sense to take the .config from the gentoo install dvd for |
| 21 |
> example and remove all the stuff I don't have? Maybe still too much |
| 22 |
> enabled options in the end. |
| 23 |
|
| 24 |
Even then, if you do that and tune the config several times, you'll |
| 25 |
likely end up with a lighter kernel. Just drop anything you don't need |
| 26 |
from the device drivers. |
| 27 |
|
| 28 |
> "make allnoconfig" as a start? |
| 29 |
|
| 30 |
That is probably much better than the config from the install dvd, yes, |
| 31 |
in fact most of the work coming from an "Add-It-All" config is that you |
| 32 |
have to disable many, many entries. |
| 33 |
|
| 34 |
> allmodconfig ? |
| 35 |
|
| 36 |
I'd go with allnoconfig, although if you compile lots of stuff as |
| 37 |
modules, you can then check lsmod to see what does, in fact, get loaded. |
| 38 |
|
| 39 |
> I'd be happy to hear your opinions. |
| 40 |
|
| 41 |
-- |
| 42 |
Nuno Silva (aka njsg) |
| 43 |
http://njsg.sdf-eu.org/ |
Archives