From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: David Woodhouse <dwmw2@infradead.org>, Dave Jones <davej@suse.de>,
Linus Torvalds <torvalds@transmeta.com>,
Linux-Kernel list <linux-kernel@vger.kernel.org>
Subject: including kernel headers (was Re: PATCH 2.5.2.7: io.h cleanup and userspace nudge)
Date: Fri, 04 Jan 2002 13:46:54 -0500 [thread overview]
Message-ID: <3C35F89E.2EA5E811@mandrakesoft.com> (raw)
In-Reply-To: <E16MZFt-000548-00@the-village.bc.nu>
Alan Cox wrote:
>
> > Just putting it asm-*/types.h should just about be enough.
>
> That is one of the headers glibc wants to import however. It wants to be
> hard for applications to do something stupid but easy for glibc to extract
> the relevant data that it actually needs (because glibc needs the kernel to
> user information to make syscalls even if it doesnt expose them to apps)
Thinking -long term- here, I wonder what a good solution for glibc would
be? Userspace including glibc should never include kernel headers but I
100% agree we should make it as easy as possible for glibc (and other
libc's) to stay in sync with the kernel<->userspace API.
I am betting glibc does not require as much work to become independent
of kernel headers... it is more work to get all the userspace apps that
reference ioctl structures and constants not using kernel headers.
Jeff
--
Jeff Garzik | Only so many songs can be sung
Building 1024 | with two lips, two lungs, and one tongue.
MandrakeSoft | - nomeansno
next prev parent reply other threads:[~2002-01-04 18:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-04 17:47 PATCH 2.5.2.7: io.h cleanup and userspace nudge Jeff Garzik
2002-01-04 18:00 ` Dave Jones
2002-01-04 18:12 ` Jeff Garzik
2002-01-04 18:18 ` Dave Jones
2002-01-04 18:20 ` David Woodhouse
2002-01-04 18:39 ` Alan Cox
2002-01-04 18:46 ` Jeff Garzik [this message]
2002-01-04 18:21 ` Jeff Garzik
2002-01-04 18:24 ` Dave Jones
2002-01-04 18:31 ` Richard Gooch
2002-01-04 18:35 ` Jeff Garzik
2002-01-04 18:40 ` Dave Jones
2002-01-04 18:41 ` Richard Gooch
2002-01-04 19:16 ` Mike Castle
2002-01-04 23:28 ` Reid Hekman
2002-01-04 18:19 ` Oliver Xymoron
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=3C35F89E.2EA5E811@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davej@suse.de \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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