From: "Alexander E. Patrakov" <patrakov@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: sanitized kernel headers
Date: Sat, 07 Jan 2006 14:59:48 +0500 [thread overview]
Message-ID: <43BF9114.7040102@gmail.com> (raw)
Hello,
almost two years ago, a decision has been made that raw kernel headers
are for the kernel only, and that userspace should be built against some
"sanitized" kernels. Linux-Libc-Headers
(http://ep09.pld-linux.org/~mmazur/linux-libc-headers/) were one of the
implementations of such sanitized headers, and they worked well and were
used e.g. in Linux From Scratch.
But now, the Linux-Libc-Headers project looks dead: no commits in the
SVN for the last two months, and the only changes in SVN as compared to
LLH 2.6.12.0 are addition of inotify.h, removal of some kernel-only
headers and some minor fix for non-glibc systems.
What is the recommended (non-dead) alternative implementation of such
"sanitized" headers? Where is the roadmap for this area?
--
Alexander E. Patrakov
Don't mail to patrakov@ums.usu.ru: the server is off until 2006-01-11
Use my GMail or linuxfromscratch address instead
next reply other threads:[~2006-01-07 9:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-07 9:59 Alexander E. Patrakov [this message]
2006-01-08 10:31 ` sanitized kernel headers Andrew Walrond
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=43BF9114.7040102@gmail.com \
--to=patrakov@gmail.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