module sizes

[0be1]

I am looking for a document that has a generalization of how big each function may or may not be when compiling a kernel. IE.) How much I save with no sound or SCSI, etc. It does not have to be disto specific, just enough to let me know of a more in depth of the pro and cons of what to exclude or what to make as a module and the consequences either way. That way I can predict how big my kernel might be before actually going through the process.

TIA,

0be1

------------------
Linux, is there really any other OS worth using?

[conman]

That's virtually impossible to tell because it will depend on all the other flags you set when compiling the kernel, what your hardware is and which compiler you're using.

[Strike]

Make things into a module that you don't use every time (and are allowed to be made modules, oc course). Things that are always used can be compiled into the kernel.

For me, that pretty much means compiling just about everything I can as a module.

This, of course, is not written in stone - it's just one way of thinking of it.