[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Debian conflicts with FHS on /usr/include/{linux,asm}

>>>>> "Theodore" == Theodore Y Ts'o <tytso@mit.edu> writes:

    Theodore> I agree, and I do accept the path to a version of the
    Theodore> kernel tree it shall be compiled for.  It requires
    Theodore> editing the Makefile, though, and this is not pleasant
    Theodore> for naive users.  Even if you make it a nice shell
    Theodore> script, merely asking this question and demanding the
    Theodore> user to answer is scary.

    Theodore>    This path can be /usr/src/linux by default. Kernel
    Theodore> modules should probably not include
    Theodore> /usr/include/{asm,linux} at all.

    Theodore> I can live with this.  But /usr/src/linux needs to be a
    Theodore> valid default that works for naive users.

Assuming you mean /usr/include/{linux,asm} need to be a valid default,
I totally agree. The current Debian system is immensely insatisfactory
in that it's pretty much impossible for any non-C-literate user to
compile a standalone module by themselves.

However, the problem is that it's not always possible to insure the
system's in this state. For example, you can install a Debian package
of just a kernel and modules; no source is included, not even
modversions.h. How can we possibly ensure that all the header files
are up-to-date (ignoring for now the case of multiple kernels

Do we have to include the entire kernel source (rather large!) with
every kernel package? Can we possibly get away with just including
the headers used to build that kernel?


Brought to you by the letters H and U and the number 2.
"It is sad. *Campers* cannot *dance*. Not even a *party*."
Debian GNU/Linux maintainer of Gimp and GTK+ -- http://www.debian.org/

Reply to: