| 1 |
Harry Putnam wrote: |
| 2 |
> Nikos Chantziaras <realnc@×××××.de> writes: |
| 3 |
> [...] |
| 4 |
> |
| 5 |
>>>> Well, my bit of wisdom here: Don't use modules. Do a "make |
| 6 |
>>>> menuconfig", disable everything you don't need, and compile |
| 7 |
>>>> everything you need in-kernel instead of as a module. |
| 8 |
>>> I'd say the "disable everything you don't need" part is what Harry's |
| 9 |
>>> mail is all about. |
| 10 |
>> Well, finding out what every installed module does isn't going to |
| 11 |
>> help anyway. I'd start with only the modules currently used after a |
| 12 |
>> fresh boot (lsmod). If you compile those in-kernel, it will boot. |
| 13 |
>> Everything else can be tweaked later. |
| 14 |
> |
| 15 |
> Yeah, I talked about that in OP. But the only kernel I've got working |
| 16 |
> at the moment is a genkernel and it installs 80+ modules. |
| 17 |
|
| 18 |
The way I do it, is to simply know what hardware is in the machine |
| 19 |
(dmesg, lspci and hwinfo for things I'm not sure about) and look for it |
| 20 |
in the kernel configuration. For the few modules that remain where I |
| 21 |
don't know what they do, I just google their names. The important stuff |
| 22 |
is just the PATA/SATA controller, SCSI disk support and keyboard/mouse |
| 23 |
though. The rest I add later. |
Archives