From: Helge Hafting <helge.hafting@hist.no>
To: Joerg Schilling <schilling@fokus.fraunhofer.de>
Cc: alan@lxorguk.ukuu.org.uk, axboe@suse.de,
linux-kernel@vger.kernel.org, vonbrand@inf.utfsm.cl
Subject: Re: Linux Kernel bug report (includes fix)
Date: Tue, 10 Aug 2004 11:24:19 +0200 [thread overview]
Message-ID: <41189443.3040504@hist.no> (raw)
In-Reply-To: <200408091420.i79EKBEu010574@burner.fokus.fraunhofer.de>
Joerg Schilling wrote:
>
>>Linux kernel include files are not meant to be used by user
>>applications. He's perfectly correct. Glibc has its own exported set.
>>This is intentional to seperate internals from user space.
>>
>>
>
>You should know that GLIBc is unrelated to the Linux kernel interfaces we are
>talking about. Start using serious arguments please.
>
>
The kernel headers are _still_ not meant to be used by userspace,
so don't try that. If you don't want to use glibc headers - you get to
write
your own headers. You can extract info from the kernel headers, but they
cannot be used directly from userspace programs. They are not designed to
be used that way.
Helge Hafting
next prev parent reply other threads:[~2004-08-10 9:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-09 14:20 Linux Kernel bug report (includes fix) Joerg Schilling
2004-08-09 15:50 ` Paolo Ciarrocchi
2004-08-10 5:17 ` Matt Mackall
2004-08-10 9:24 ` Helge Hafting [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-11 11:49 Joerg Schilling
2004-08-10 12:34 Joerg Schilling
2004-08-10 16:24 ` Jim Gifford
2004-08-12 15:35 ` Bill Davidsen
2004-08-09 12:03 Joerg Schilling
2004-08-09 13:05 ` Alan Cox
2004-08-10 22:58 ` Horst von Brand
2004-08-07 12:51 Joerg Schilling
2004-08-07 13:26 ` Måns Rullgård
2004-08-07 19:32 ` Bernd Schubert
2004-08-08 1:18 ` Horst von Brand
2004-08-08 5:22 ` Alexander E. Patrakov
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=41189443.3040504@hist.no \
--to=helge.hafting@hist.no \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=schilling@fokus.fraunhofer.de \
--cc=vonbrand@inf.utfsm.cl \
/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