Re: Debian conflicts with FHS on /usr/include/{linux,asm}
- To: Marcus Brinkmann <Marcus.Brinkmann@ruhr-uni-bochum.de>
- Cc: joey@kitenet.net, shaleh@varesearch.com, fhs-discuss@ucsd.edu, debian-policy@lists.debian.org, quinlan@transmeta.com, t.sippel-dau@ic.ac.uk, moth@magenta.com
- Subject: Re: Debian conflicts with FHS on /usr/include/{linux,asm}
- From: "Theodore Y. Ts'o" <tytso@mit.edu>
- Date: Wed, 14 Jul 1999 08:28:29 -0400
- Message-id: <[🔎] 199907141228.IAA00937@tsx-prime.MIT.EDU>
- In-reply-to: Marcus Brinkmann's message of Wed, 14 Jul 1999 13:28:27 +0200, <[🔎] 19990714132827.B1016@ulysses.ulysses.de>
Date: Wed, 14 Jul 1999 13:28:27 +0200
From: Marcus Brinkmann <Marcus.Brinkmann@ruhr-uni-bochum.de>
IMHO, any kernel module should be able to accept the path to the version of
the kernel tree that it shall be compiled for. This is also important if I
have several versions of the kernel, or if I want to compile for a kernel
version that I don't have installed (in binary) on this system.
I agree, and I do accept the path to a version of the kernel tree it
shall be compiled for. It requires editing the Makefile, though, and
this is not pleasant for naive users. Even if you make it a nice shell
script, merely asking this question and demanding the user to answer is
scary.
This path can be /usr/src/linux by default. Kernel modules should probably
not include /usr/include/{asm,linux} at all.
I can live with this. But /usr/src/linux needs to be a valid default
that works for naive users.
- Ted
Reply to: