Next question though... I wonder how I can work out which pieces of my kernel aren't actually being used by my hardware? That would also make me happy, removing everything that isn't actually applicable to the hardware I have.
Having things as a modules means you KNOW it's not being used, coz it's not in 'lsmod'.
I believe that step involves two things:
1) Understanding the output of lcpci 2) Knowing in depth what hardware you actually have
For example, because I built my system from scratch and know exactly the system board and attached peripherals, I am able to configure the kernel with very few modules (I believe I use two, and the nvidia module). I do this because I know what I have (thus it's not bloated), and it saves me a slight headache of remembering which modules I needed for what.
I take this to another step with lspci, which allows me to compile kernels on systems I've never touched before that still run perfectly fine without many modules (again, I think I generally use around two). There might be a few extra things that they didn't need, but on the whole I think it's kept to a minimum.
-- We are Pentium of Borg. Division is futile. You will be approximated.
-- [email protected] mailing list
