on a recent thread, someone explained how to get your linux box to readIf you compile it into your kernel the part doesn't need to be loaded when used. That probably is faster, though I do not think you will notice it. On the other hand your kernel will get bigger and use more memory (though kernel size does matter much less now than some years ago).
a windows partition by compiling your kernel for vfat/ntfs support. they then went on to explain how to set it up so that your kernel can
either (a) compile this stuff in, or (b) compile them as modules and
load them automatically.
so my question then is: why compile something as a module if you're going to load it into the kernel at boot anyway? what are the (dis)advantages?
thanks
-- [EMAIL PROTECTED] mailing list
The main advantage in modules is when making something like a live CD that runs on different machines, so you can use any kind of e.g. SCSI controller.
In addition some things must be used as a module.
I normally compile everything into my kernel that is needed to boot (hate those initrds) and what will be used anyway when running my computer (e.g. networking).
Everything I will not need all the time (FAT, USB,...) will be compiled as modules.
Chris
-- [EMAIL PROTECTED] mailing list
