From: Peter <pete4abw@comcast.net>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: modules built post kernel install (on the fly)
Date: Sat, 04 Mar 2006 10:23:45 -0500 [thread overview]
Message-ID: <pan.2006.03.04.15.23.45.418147@comcast.net> (raw)
In-Reply-To: 87ek1ickcn.fsf@newsguy.com
On Sat, 04 Mar 2006 09:15:04 -0600, Harry Putnam wrote:
> Is this possible:
>
> Compile a module by itself (not during kernel compile) and insert that
> module into a running kernel.
>
> I'm pretty sure this is possible but have no idea how to do it. Pawing
> thru google. `site:gentoo.org modules "on the fly" ' and similar strings
> .... even just `kernel module'
>
> Turns up scads of stuff but none of it is hitting this head on.. or I
> didn't paw far enough.... so asking here for pointers to documentation
> that will cover this.
Yes.
cd /usr/src/linux
make menuconfig or make xconfig
choose the module option you wish to enable
Select whether to build into the kernel or as a module.
exit and save
make
make modules_install
You should not have to copy bzImage unless you built your new modules into
the kernel.
Then edit your /etc/autoload directory to include the module you want to
modprobe into the system.
easy!
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-03-04 15:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-04 15:15 [gentoo-user] modules built post kernel install (on the fly) Harry Putnam
2006-03-04 15:23 ` Peter [this message]
2006-03-04 15:35 ` [gentoo-user] " Harry Putnam
2006-03-04 16:16 ` Peter
2006-03-05 4:03 ` Harry Putnam
2006-03-05 4:08 ` Brett I. Holcomb
2006-03-05 4:34 ` Holly Bostick
2006-03-05 5:11 ` Harry Putnam
2006-03-05 7:19 ` Ryan Tandy
2006-03-04 15:40 ` Masood Ahmed
2006-03-04 15:28 ` [gentoo-user] " Masood Ahmed
2006-03-04 15:41 ` [gentoo-user] " Harry Putnam
2006-03-04 16:07 ` Masood Ahmed
2006-03-05 22:18 ` Boyd Stephen Smith Jr.
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=pan.2006.03.04.15.23.45.418147@comcast.net \
--to=pete4abw@comcast.net \
--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