From: Evan Thompson <evaner@bigfoot.com>
To: linux-kernel@vger.kernel.org
Subject: The advantage of modules?
Date: Fri, 5 Jan 2001 22:50:20 -0600 [thread overview]
Message-ID: <20010105225020.A1188@evaner.penguinpowered.com> (raw)
I'd like to know (I know, I'm being slightly off topic, while still
staying on topic, so I'm on topic...er...yes) if there is any
advantage, be it memory-wise or architectuarally wise, to use modules?
I already know the obvious points of if you are creating a distro that
it is usually good to make a very modular kernel for those wishing not
to recompile their kernel, but I was wondering if there were any other
advantages to using modules vs. making a monolithic kernel for a
kernel to be used only on one machine (with no other hardware support
at all)?
Thanks, and sorry if I'm being slightly off topic...
Kernels are fun! I wish I could learn more!
--
+----------------------------------+-----------------------------------+
| Evan Thompson | POWERED BY: |
| evaner@bigfoot.com | Linux cd168990-a 2.4.0-ac2 #1 Fri |
| Freelance Computer Nerd | Jan 5 11:58:30 CST 2001 i686 |
| http://evaner.penguinpowered.com | unknown |
+----------------------------------+-----------------------------------+
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-01-06 4:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-06 4:50 Evan Thompson [this message]
2001-01-06 5:31 ` The advantage of modules? Drew Bertola
2001-01-06 10:02 ` J . A . Magallon
2001-01-08 16:49 ` Michael Meissner
2001-01-08 16:47 ` Michael Meissner
2001-01-08 18:26 ` Ookhoi
2001-01-08 19:05 ` Michael Meissner
2001-01-08 21:50 ` Russell King
2001-01-08 22:16 ` Dan Hollis
2001-01-08 22:14 ` Russell King
2001-01-08 22:40 ` Dan Hollis
2001-01-08 23:06 ` Richard B. Johnson
2001-01-08 23:49 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010105225020.A1188@evaner.penguinpowered.com \
--to=evaner@bigfoot.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox