So, I'm sorta following you here. However, I never touched /usr/include/linux. Its not linked at all to /usr/src/linux.
Futhermore, I don't exactly understand the problem why one shouldn't have a /usr/src/linux directory. I mean, after all, when I installed the kernel-source package, it dumps the .bzip2 archive into /usr/src. So too with kernel-headers. This leads me to think that both belonged in /usr/src and not in my home directory. I also understood that I am supposed to create a symbolic linux called "linux" to the kernel-source directory. If these shouldn't be in /usr/src, then are the debs for the kernel source package broken then too because they deposit them there? On Sun, Nov 24, 2002 at 05:54:45PM -0500, Albert D. Cahalan wrote: > The usual junk: some people mistakenly think that /usr/include/linux > is supposed to contain a link into /usr/src/linux and that that is > supposed to be source code for the kernel you are running. > > Reality: > > The /usr/include/linux files are derived from kernel source when > the glibc package is created. Don't touch them. They get upgraded > when you upgrade glibc. Treat /usr/include/asm the same way. > > That's just the way it is. Linus said so. IMHO these files > ought to be a separate package, but that isn't the case. > > You should not have a /usr/src/linux directory. You might put > something there to help you avoid temptation: > > rm -rf /usr/src/linux > echo "never use this" > /usr/src/linux > chmod 444 /usr/src/linux > chattr +i /usr/src/linux > > If you need kernel source, put it in your home directory. > > Now look in the MOL source. If you see /usr/src/linux or > /usr/src/asm, then MOL is most likely broken. Fix it by > adding a -I option to the gcc command line, by editing > the source, or by doing both. You'll need to point MOL to > the kernel source in your home directory. > -- wcrowshaw
