I've used Linux as primary OS for about 3 years but I have used it as a normal user (i.e. not power user) so I don't understand exactly what you mean. Do you mean something like the kernel can have extra "options" added to it and that these options can either be "baked-in" or put on the side (then called "modules"), when they are put on the side as modules they can be then be swapped out? Or am I misunderstanding what you mean?
I managed to solve my memory problem in this case by making the software I needed to run require less memory, but learning to make Linux itself require less memory still seems worthwhile.
Do you mean something like the kernel can have extra "options" added to it and that these options can either be "baked-in" or put on the side (then called "modules"),
Precisely. You can put the sound driver in the kernel or select module instead. There are heaps of options in kernel configuration and many can be modules.
Give it a go, you can figure it out after a few tries. Just be sure it has a separate grub entry so you can boot the working kernel.
Very interesting. Seems stock Ubuntu server has all kinds of probably totally unneeded "crap". Will spends some time looking at this. Thanks!
I was good at this in the past. I tried all modules, no modules, etc. In the end it was modules, but only the ones I needed. Your distribution will include a module for basically everything.
There is probably some cost to configuring the kernel to support modules for devices you do not have, which is what vendors need to do to have broad hardware support.
lspci -vv is helpful to figure out exactly what you need to have support for.
Also, don't work through autoloading unless you want to. Use modprobe -a to load every module and let Linux swap them out. That is the easy way.
(post is archived)