Bunyan said:Hey, man.
Just a question:
-Why should I not remove from the kernel ALL code that I'll NEVER need?
fluca1978 said:this could sound trivial, but when I configure a new kernel how can I decide (if possible) what is going to be a loadable module and what is going to be included into the kernel itself?
#device ispfw # Firmware for QLogic HBAs- normally a module
You don't. Actually everything is built as a module, including the stuff that's built into the kernel.Now, how can I force this to be a module instead of being built into the kernel?
jalla said:@fluca1978 I think you misunderstand. If you put, say ispfw, in the kernel config it is linked directly into the kernel and also built as a loadable module (totally useless, but thats a different matter).
fluca1978 said:So in order to not allow a module to be loaded I have to not include such option in the kernel config and remove the module from the disk, right? Or is there another way to config a kernel to not accept at all modules?