From: "Anthony E. Caudel" <acaudel@gt.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Module philosophy: Compile-in or Load
Date: Mon, 12 Jun 2006 16:47:12 -0500 [thread overview]
Message-ID: <448DE0E0.3010207@gt.rr.com> (raw)
In-Reply-To: <448D284E.2040705@gmx.de>
Michael Weyershäuser wrote:
> I usualy start with a kernel with almost everything compiled in (but
> only things I definitely need), only using modules when I have to
> (USB for suspend2 comes to my mind). Over time whenever I need
> something new (filesystem, hardware driver,...) I tend to compile it
> as a module to avoid a reboot. As I do not upgrade my kernel very
> often this happens more often than you might think (last upgrade was
> from 2.6.11 to 2.6.16, on my laptop from 2.6.10 to 2.6.16).
>
> I don't really care about the 300k more used memory (hardly worth a
> thought on systems with 1 GB RAM and more) or the 0.3 seconds faster
> boot process. Modules just come in handy when it comes to avoiding a
> reboot.
OK, this seems to confirm something I had suspected but never
investigated: - that you can compile just a module without the need to
recompile and install a revised kernel. This is possible?
How? "make modules_install" or the whole thing: "make && make
modules_install" then just modprobe the new module?
Tony
--
Those who would give up essential Liberty, to purchase a little temporary
Safety, deserve neither Liberty nor Safety.
-- Benjamin Franklin
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-06-12 22:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-12 5:24 [gentoo-user] Module philosophy: Compile-in or Load Anthony E. Caudel
2006-06-12 5:30 ` Teresa and Dale
2006-06-12 6:20 ` Anthony E. Caudel
2006-06-13 3:35 ` Teresa and Dale
2006-06-12 5:37 ` gentuxx
2006-06-12 5:44 ` Steven Susbauer
2006-06-12 6:31 ` Mike Huber
2006-06-12 6:33 ` Mike Huber
2006-06-12 6:23 ` Kristian Poul Herkild
2006-06-12 8:39 ` Michael Weyershäuser
2006-06-12 14:05 ` Daniel da Veiga
2006-06-12 21:47 ` Anthony E. Caudel [this message]
2006-06-12 23:10 ` Mike Huber
2006-06-13 0:40 ` Ryan Tandy
2006-06-17 11:17 ` Mick
2006-06-17 13:40 ` Michael Weyershäuser
2006-06-17 13:42 ` Anthony E. Caudel
2006-06-17 17:08 ` Mick
2006-06-17 17:28 ` Erik Westenbroek
2006-06-18 12:46 ` Michael Weyershäuser
2006-06-12 18:16 ` Evan Klitzke
2006-06-12 18:38 ` Jarry
2006-06-12 19:16 ` Neil Bothwick
2006-06-12 21:00 ` kashani
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=448DE0E0.3010207@gt.rr.com \
--to=acaudel@gt.rr.com \
--cc=gentoo-user@lists.gentoo.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