FLAME____ Why is the kernel source not included
gene.heskett at verizon.net
Fri Oct 15 17:14:12 UTC 2004
On Friday 15 October 2004 11:42, Filippos Klironomos wrote:
>> As Jakob mentioned earlier, properly-written modules should be
>> built against the headers in /lib/modules/`uname -r`/build rather
>> than /usr/src; it may well be that lots of module providers don't
>> currently do this despite the fact that it's been the standard way
>> of doing things for some time time now, but if the module writers
>> can't keep up with the build system, they're hardly likely to be
>> able to keep up with changes in the underlying kernel either.
>I have another probably silly question. Doesn't /lib/modules/`uname
>-r`/build usually point to /usr/src/linux?
>I would swear it does, but I am away from my machine right now...
No it doesn't usually. It will look more like this:
/lib/modules/2.6.9-rc4/build, and which will contain (probably):
[root at coyote root]# ls /lib/modules/`uname -r`/build
arch crypto fs ipc MAINTAINERS mm
README security usr
COPYING Documentation include kernel Makefile Module.symvers
REPORTING-BUGS sound vmlinux
CREDITS drivers init lib makeit
The last 'makeit' is the script I alluded to earlier that builds a
newer kernel for me. Everything there is in fact the contents of
that src dirs root level since the 'build' is a link (in this case)
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.27% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attorneys please note, additions to this message
by Gene Heskett are:
Copyright 2004 by Maurice Eugene Heskett, all rights reserved.
More information about the users