I use /root/src/linux. /usr/src is meant to store the kernelheaders used to compile glibc
Actually, the kernel headers used for glibc are in /usr/include/linux, check out glibc's PKGBUILD for more info. If you "#include <linux/if_ether.h>" from a .c file, it reads /usr/include/linux/if_ether.h.
/usr/src/* is just for source trees like the kernel, the compiler won't look there unless you tell it to.
]]>yes "" |make config
with
make menuconfig
I use /root/src/linux. /usr/src is meant to store the kernelheaders used to compile glibc
You can keep any sourcecode in /usr/src
/usr/src/linux is for the kernelheaders used to compile glibc. /usr/src/linux-2.6.5 or any other folder can contain any file, logically source code.
Dusty
]]>But this idea has some disadvantages, too. F.e., if you compile a minor upgrade, you may construct a modules mess, as a lot of files are already existing. Therefore, all cases must be thoroughly considered and configurated. Kernel addicts would prefer to patch the kernel instead of fully refetch the source.
After playing around with the idea for a while, I decided the work of configurating all possible eventuallities in compiling kernels by using abs was to difficult. Using the standard procedures seemed straight and easy to me.
So I removed my 'arch way' section in the kernel compiling wiki. Nevertheless, another user started an abs kernel wiki, redevelopping and enhancing my idea.
The idea is still attractive.
]]>I have not tried ABS, cannot vote. The /usr/src is the common way but don't like it..... requires too much technical knowledge.
The question is how you compile the kernel, not if you use a precompiled one or not. I didn't try the ABS way (I see no advantages), but I assume you still have to configure it. Configuring the kernel requires the most knowledge, how you get the source doesn't matter that much (I don't know what's easier, to use ABS or wget + tar).
]]>But given the right documentation I would love to have a go at custom kernel :-)
Mr Green
]]>