begin quote
On Thu, 19 Jun 2003 01:54:37 +0200
Juan Ángel [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
As a module, you can load it and remove it as you please, but not if
it's builtin. Usually, drivers go as modules, and other features don't
(that's your
I've been using linux full time for about 6 months now, but I haven't
found anything on the pros and cons of compiling the kernel with
features built-in vs built as modules? What are the advantages of either
case?
curious,
-chris
--
[EMAIL PROTECTED] mailing list
On Wed, Jun 18, 2003 at 04:38:59PM -0700, Chris Graves wrote:
I've been using linux full time for about 6 months now, but I haven't
found anything on the pros and cons of compiling the kernel with
features built-in vs built as modules? What are the advantages of either
case?
Depends if you
Probably, it's a matter of personal preference - like vi vs emacs G. From
what I see modules allow you to reduce the size of the kernel and let you
load drivers, only if you need them. However, if a module needed for boot
isn't built in you have to use an initrd to start the system.
Just my opinion, unless you change hardware a lot, I don't think there is an
advantage.
Some things though, like I2c support, you want as modules because you might
not be sure which one your hardware supports and you can auto-detect it.
I've been using linux full time for about 6 months now,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
As a module, you can load it and remove it as you please, but not if it's
builtin. Usually, drivers go as modules, and other features don't (that's
your choice). But if you need something (such as ext2 suport, for example)
available at boot time,
