[EMAIL PROTECTED] wrote:
I would appreciate some elaboration on what kernel module loader does
exactly, since none of the modules get loaded automatically during
runtime. Understanding this will perhaps help to decide which
features will stay as a module and which are the ones that will be
built
When configuring the kernel (via make xconfig), what is the general
guideline as to what should be kept as modules, and what should be
built-in?
Thanks !
Message posted via www.linuxforums.org
.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
[EMAIL PROTECTED] wrote:
When configuring the kernel (via make xconfig), what is the general
guideline as to what should be kept as modules, and what should be
built-in?
It depends upon what you are compiling the kernel for.
But generally if you are compiling a kernel for a single system, you can
[EMAIL PROTECTED] wrote:
When configuring the kernel (via make xconfig), what is the general
guideline as to what should be kept as modules, and what should be
built-in?
Support for your IDE/SCSI chipset(s) should be built-in, as well as support
for whatever filesystems you are using.
During the customisation of the kernel, under loadable module support,
I have kernel module loader built in. Kernel Module Loader is
described under help as :
CONFIG_KMOD:
Normally when you have selected some drivers and/or file systems to
be created as loadable modules, you also have the
5 matches
Mail list logo