| 1 |
On 8 January 2013, at 12:14, Stefan G. Weichinger wrote: |
| 2 |
> … |
| 3 |
> * I remember a thread here where this was discussed already: |
| 4 |
> |
| 5 |
> How do you guys get to your .config for a recent kernel? "make |
| 6 |
> oldconfig" doesn't always work out best, I recall? |
| 7 |
> |
| 8 |
> My kernel config is maintained along for years now and has survived |
| 9 |
> several hardware changes. I don't have any obvious problems but I wonder |
| 10 |
> if I have something in there that is deprecated and might be better |
| 11 |
> thrown out. |
| 12 |
> |
| 13 |
> Does it make sense to take the .config from the gentoo install dvd for |
| 14 |
> example and remove all the stuff I don't have? |
| 15 |
|
| 16 |
I most always take the .config from a recent systemrescuecd and it has always worked well for me. |
| 17 |
|
| 18 |
I change "processor type and features" and disable the initrd. |
| 19 |
|
| 20 |
There may be some stuff on a LiveCD based distro which is optimised for running off an optical disk, so I guess a RedHat or Ubuntu default .config might be better. |
| 21 |
|
| 22 |
These should provide everything you need to boot, and most everything else as modules, which will be automatically loaded. IMO this is pretty much optimal. |
| 23 |
|
| 24 |
The engineers at RedHat and Ubuntu know a heck of a lot more about kernels than I do. One might be able to make one's kernel milliseconds more efficient by tuning it by hand, but it will surely take hours of tinkering to attain that. |
| 25 |
|
| 26 |
I do not believe you can properly understand the consequences of any given kernel option merely by reading the one- or two-line description in makeconfig's help. To *properly* customise a kernel for oneself will take more research than that, I reckon. |
| 27 |
|
| 28 |
Stroller. |
Archives