Re: toplevel Makefile bug and simple fix

Raul Miller (moth@magenta.com)
Mon, 8 Nov 1999 08:20:04 -0500


Theodore Y. Ts'o <tytso@mit.edu> wrote:
> Note, though, that it is **very** important that /usr/include/linux and
> /usr/include/asm correspond to the default kernel that you are booting.
>
> This is because if you are building stand-alone linux kernel modules
> from source, they need an easy way of finding the linux kernel headers
> of the kernel you are booting; otherwise, they can't get the right
> modversions.h information (for example).

Meaning that all binary distributions of the kernel should come with
include files? And that /usr/include/linux should really be a symlink
to /var/run/linux, and that the /var/run links should be managed at
boot time?

This is doable, but since it breaks some other things (and kernel make
install doesn't support this) it would be a good thing to have more than
one reputable person suggesting it.

> P.S. And we really *have* to be able to support stand-alone source
> distribution of drivers. The Linux kernel sources are still growing
> expenontially, with a time constant of roughly 18 months. This is
> mostly due to new drivers. Sooner or later, we will need to address
> the question of how to distribute drivers independently of the kernel,
> in source form at the very least.

XFree86 seems to manage.

[Yeah, I know, xfree86 isn't bttv... but I think what you're talking
about here is a layering problem as much as anything. Or is that too
obvious of a comment?]

-- 
Raul

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/