public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: glibc compiling with kernel 2.5.70-bk17
Date: 18 Jun 2003 23:16:00 -0700	[thread overview]
Message-ID: <bcrkf0$dsf$1@cesium.transmeta.com> (raw)
In-Reply-To: 3EF12031.8020709@hereintown.net

Followup to:  <3EF12031.8020709@hereintown.net>
By author:    Chris Meadors <clubneon@hereintown.net>
In newsgroup: linux.dev.kernel
> 
> Your first comment is something I had wondered about for a while. A 
> stable set of userspace kernel headers. That would be nice.  Of course 
> changes could be made to reflect new kernel interfaces.  So they should 
> still be distributed with the kernel source.  Then glibc could be 
> compiled against those updates, and the headers installed as the system 
> default.  But it wouldn't be so forbidden for userspace to touch them.
> 

Yes, this is the "ABI headers" project that has been discussed
extensively on this list.  It's pretty important, but unlikely to
happen in time for 2.6.

	-hpa
-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64

      reply	other threads:[~2003-06-19  6:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-19  1:17 glibc compiling with kernel 2.5.70-bk17 Riccardo-Maria Bianchi
2003-06-19  1:23 ` Kevin P. Fleming
2003-06-19  2:30   ` Chris Meadors
2003-06-19  6:16     ` H. Peter Anvin [this message]

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='bcrkf0$dsf$1@cesium.transmeta.com' \
    --to=hpa@zytor.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