From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Christoph Hellwig <hch@infradead.org>,
mocm@mocm.de, Michael Hunold <hunold@convergence.de>,
Sam Ravnborg <sam@ravnborg.org>,
linux-kernel@vger.kernel.org
Subject: Re: DVB Include files
Date: Wed, 25 Jun 2003 19:27:03 +0200 [thread overview]
Message-ID: <20030625172703.GC1770@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <20030625175513.A28776@infradead.org>
On Wed, 25 June 2003 17:55:13 +0100, Christoph Hellwig wrote:
> On Wed, Jun 25, 2003 at 06:49:50PM +0200, Marcus Metzler wrote:
> > You mean include/linux/dvb, I hope. Otherwise, it will break all user space
> > applications.
>
> No. At least I hope he didn't mean it :) Userspace has no _goddamn_
> business to look at kernel headers. Just stick a copy of those into
> /usr/include/dvb/ for your applications that's in the dvb-dev or whatever
> package.
Christoph, while I agree with you, I also see why a lot of people just
symlink /usr/include/linux to /usr/src/.../include/linux. Pure
convenience and the lack of a dedicated collection of userspace
headers outside a distributions scope.
Seperating userspace headers from kernel headers would also be a good
thing, as the #ifdef __KERNEL__ #else #endif orgy could finally be
reduced a bit.
Since these headers do depend on the kernel version and should be the
official interface between kernel and userspace, maintaining them
inside the kernel tree would also, imho, be a Good Thing.
So imnsho the "don't use the kernel headers" comment I read on a
common basis is not a very helpful advice, as long as we are missing
in this respect.
Or did I miss something important and just exposed my stupidity?
Jörn
--
Public Domain - Free as in Beer
General Public - Free as in Speech
BSD License - Free as in Enterprise
Shared Source - Free as in "Work will make you..."
next prev parent reply other threads:[~2003-06-25 17:15 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-25 15:06 DVB Include files Sam Ravnborg
2003-06-25 15:08 ` Christoph Hellwig
2003-06-25 15:42 ` Sam Ravnborg
2003-06-25 16:17 ` Michael Hunold
2003-06-25 16:49 ` Marcus Metzler
2003-06-25 16:55 ` Christoph Hellwig
2003-06-25 17:13 ` Marcus Metzler
2003-06-25 17:16 ` Christoph Hellwig
2003-06-25 17:22 ` Marcus Metzler
2003-06-25 17:24 ` Christoph Hellwig
2003-06-25 17:30 ` Marcus Metzler
2003-06-25 17:50 ` Christoph Hellwig
2003-06-25 18:09 ` Marcus Metzler
2003-06-25 18:15 ` Christoph Hellwig
2003-06-25 18:43 ` Marcus Metzler
2003-06-25 19:42 ` Jörn Engel
2003-06-25 20:09 ` Marcus Metzler
2003-06-25 20:23 ` Jörn Engel
2003-06-25 20:48 ` Marcus Metzler
2003-06-25 21:03 ` Christoph Hellwig
2003-06-25 21:38 ` Marcus Metzler
2003-06-26 13:54 ` Henning P. Schmiedehausen
2003-06-25 23:08 ` Alan Cox
2003-06-26 8:18 ` Michael Hunold
2003-06-26 8:24 ` Christoph Hellwig
2003-06-26 13:20 ` Johannes Stezenbach
2003-06-25 21:03 ` Christoph Hellwig
2003-06-25 17:27 ` Jörn Engel [this message]
2003-06-25 17:49 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030625172703.GC1770@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=hch@infradead.org \
--cc=hunold@convergence.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mocm@mocm.de \
--cc=sam@ravnborg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).