1 |
On 5 Jan 2008, at 16:05, reader@×××××××.com wrote: |
2 |
|
3 |
> Configuring a new kernel is a dreaded task here. It seems I walk |
4 |
> through a bewildering array of stuff that when pressing F1 on them I |
5 |
> get more bewildering information I barely understand a word of. |
6 |
> |
7 |
> For 8 or 9 yrs now I've mostly skirted the issue by using |
8 |
> defaults. ... |
9 |
|
10 |
I'm not going to read all the details of all of the responses which |
11 |
have appeared here already, so here's my take. |
12 |
|
13 |
1) The people who configure the kernel options for commercial distros |
14 |
are very experienced geeks. |
15 |
2) I am unlikely to make sufficient performance savings by funroll- |
16 |
looping my own kernel to justify the time I'll spend doing so. |
17 |
|
18 |
Now I periodically grab a copy of the latest knoppix CD I can find - |
19 |
I use these a lot, anyway - and take a copy the kernel .config from |
20 |
there. Chances are the kernel I want to compile on my Gentoo system |
21 |
is a little newer than the one from the Knoppix CD, so I run `make |
22 |
oldconfig` and add in most everythign as modules. I take a couple of |
23 |
minutes to look for my network card's driver in `make menuconfig` and |
24 |
compile it in statically. This results in a kernel config which |
25 |
surely supports all the hardware in my system. An awful lot of the |
26 |
drivers & also additional drivers that I don't need compiled as |
27 |
modules - perfect! If I need them they're loaded in dynamically at |
28 |
boot time, if not they don't consume any system resources. |
29 |
|
30 |
Stroller. |
31 |
|
32 |
-- |
33 |
gentoo-user@l.g.o mailing list |