mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Olivier Galibert" <galibert@pobox.com>,
	"Jesper Juhl" <jesper.juhl@gmail.com>,
	"Arjan van de Ven" <arjan@infradead.org>,
	"Hack inc." <linux-kernel@vger.kernel.org>
Subject: Re: Is that an acceptable interface change?
Date: Mon, 6 Mar 2006 17:20:12 +0100	[thread overview]
Message-ID: <9a8748490603060820l6bb23a7fna032b8f0a022c458@mail.gmail.com> (raw)
In-Reply-To: <20060306161512.GB23513@dspnet.fr.eu.org>

On 3/6/06, Olivier Galibert <galibert@pobox.com> wrote:
> On Mon, Mar 06, 2006 at 04:55:02PM +0100, Jesper Juhl wrote:
> > Userspace apps should not include kernel headers, period.
> > So, userspace applications really shouldn't care.
>
> Please excuse me if I'm a little dense here, but the kernel headers
> _define_ the userspace-kernel interface.  If you don't have them or a
> sanitized copy of them you just can't talk with the kernel at all.
>

Well, stuff like glibc, the alsa lib etc are exceptions, but the
exceptions are few and far between.
Random userspace apps should not use the kernel headers directly, they
should instead talk to things like glibc and let glibc handle the
userspace<->kernel bit.

--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html

  reply	other threads:[~2006-03-06 16:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-06  1:17 Olivier Galibert
2006-03-06  7:52 ` Arjan van de Ven
2006-03-06 15:50   ` Olivier Galibert
2006-03-06 15:55     ` Jesper Juhl
2006-03-06 16:15       ` Olivier Galibert
2006-03-06 16:20         ` Jesper Juhl [this message]
2006-03-06 16:25         ` Randy.Dunlap
2006-03-06 17:00         ` Paul Jackson
2006-03-06 17:23       ` Christopher Friesen

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=9a8748490603060820l6bb23a7fna032b8f0a022c458@mail.gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=arjan@infradead.org \
    --cc=galibert@pobox.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®