Re: Debian conflicts with FHS on /usr/include/{linux,asm}
- To: "Theodore Y. Ts'o" <tytso@mit.edu>
- Cc: Sean 'Shaleh' Perry <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: Raul Miller <moth@magenta.com>
- Date: Tue, 13 Jul 1999 20:08:15 -0400
- Message-id: <[🔎] 19990713200815.R21210@rdm.legislate.com>
- Mail-followup-to: "Theodore Y. Ts'o" <tytso@mit.edu>, Sean 'Shaleh' Perry <shaleh@varesearch.com>, fhs-discuss@ucsd.edu, debian-policy@lists.debian.org, quinlan@transmeta.com, t.sippel-dau@ic.ac.uk, moth@magenta.com
- In-reply-to: <[🔎] 199907130915.FAA16237@tsx-prime.MIT.EDU>; from Theodore Y. Ts'o on Tue, Jul 13, 1999 at 05:15:16AM -0400
- References: <[🔎] XFMail.990712155410.shaleh@varesearch.com> <[🔎] 199907130915.FAA16237@tsx-prime.MIT.EDU>
Theodore Y. Ts'o <tytso@mit.edu> wrote:
> ... Since building kernel modules require that header files match
> exactly (think /usr/include/linux/modversions.h), that means that I
> would have to tell naive, non-developer users that they first have to:
>
> 1) download kernel sources from ftp.kernel.org,
> 2) configure a kernel to match their hardware configuration,
> 3) build their own kernel
> 4) install their own kernel, and only then can they
> 5) build my device driver
>
> I hope people can understand why this would be a complete non-starter
> for a certain class of users, and why I might refuse to support my a
> kernel module on any distribution that made such a user-hostile design
> decision....
But for the general case, that's exactly what you have to do.
Even naive users can download a new kernel version and try building it.
At which point...
[But, hey, for only another 600k (significantly less if comments are
stripped) you could put the compressed include files in the kernel
itself... </joke>]
--
Raul
Reply to: