| 1 |
On Sun, 2008-01-06 at 17:15 -0600, reader@×××××××.com wrote: |
| 2 |
> Florian Philipp <lists@f_philipp.fastmail.net> writes: |
| 3 |
> |
| 4 |
> >> There's a reason for the existence of genkernel - it's so that you don't |
| 5 |
> >> have to go through all this pain and suffering, and can instead remove |
| 6 |
> >> stuff a bit at a time with reasonable confidence it won;t blow up in |
| 7 |
> >> your face :-) |
| 8 |
> >> |
| 9 |
> > |
| 10 |
> > There is a fairly easy trick to get rid of pointless options like unused |
| 11 |
> > drivers even if you are not sure about your hardware or the kernel |
| 12 |
> > options themselves: |
| 13 |
> > Compile them as modules, then boot the new kernel. If the modules don't |
| 14 |
> > get loaded (lsmod is your friend) and everything works fine, throw them |
| 15 |
> > out of your configuration. |
| 16 |
> |
| 17 |
> Nice... a small question: how do you keep up with what gets installed? |
| 18 |
> Do you ferret them out at /lib/modules with cmds like |
| 19 |
> find . -name '*.ko' |
| 20 |
> |
| 21 |
> Or is there a log created at compile time.. or maybe create one like |
| 22 |
> make modules_intall >mymod.log. Just thinking outload. |
| 23 |
> |
| 24 |
> Following a `genkernal all' I saw a very big list get installed but didn't |
| 25 |
> think to log them. |
| 26 |
> |
| 27 |
> I guess it would be harmless to just run the `make modules_intall' part |
| 28 |
> again and catch a list. |
| 29 |
> |
| 30 |
|
| 31 |
I think you search for "modprobe -l" :) |
| 32 |
|
| 33 |
Have a nice day! |
Archives