On Saturday 04 March 2006 10:07, Masood Ahmed [EMAIL PROTECTED] wrote
about 'Re: [gentoo-user] Re: modules built post kernel install (on the
fly)':
Harry Putnam wrote:
Masood Ahmed [EMAIL PROTECTED] writes:
Thanks Masood, for the pointers.. I have a question about your sig.
Do you get
Peter wrote:
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.
Yes.
cd /usr/src/linux
make menuconfig or make xconfig
choose the module option you
Harry Putnam wrote:
Masood Ahmed [EMAIL PROTECTED] writes:
[...]
Thanks Masood, for the pointers.. I have a question about your sig.
()
Do you get that info from a single command or several?
The answer is several,
for kernel version i did 'uname -r'
for gcc-version i did 'gcc -v'
Builtin means it's built into the kernel - the * indicates that.
On Saturday March 4 2006 23:03, Harry Putnam wrote:
Peter [EMAIL PROTECTED] writes:
That is correct. Unless you alter bzImage, modprobe newmodule should work
just fine. If your new module is built in, you will need to reload
Harry Putnam schreef:
Peter [EMAIL PROTECTED] writes:
That is correct. Unless you alter bzImage, modprobe newmodule
should work just fine. If your new module is built in, you will
need to reload the kernel (reboot).
Ok, this is confusing to me... What do you mean by `built in'. I'm
Harry Putnam wrote:
I guess I sort of thought there was some trick way to just compile a
module and not do all the linking and grinding of `make' against the
whole tree.
Unless you've done 'make clean' previously, 'make' will only compile
required files based on changes you've made to your
6 matches
Mail list logo
