All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@debian.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Userland headers available
Date: Sun, 25 Jan 2004 18:30:00 -0500	[thread overview]
Message-ID: <20040125233000.GA3319@nevyn.them.org> (raw)
In-Reply-To: <busi9u$fd7$1@terminus.zytor.com>

On Sat, Jan 24, 2004 at 01:38:06AM +0000, H. Peter Anvin wrote:
> Followup to:  <4011788D.3070606@nortelnetworks.com>
> By author:    Chris Friesen <cfriesen@nortelnetworks.com>
> In newsgroup: linux.dev.kernel
> >
> > Friesen, Christopher [CAR:7Q28:EXCH] wrote:
> > 
> > > The obvious way is to have the kernel headers include the userland
> > > headers, then everything below that be wrapped in "#ifdef __KERNEL__". 
> > > Userland then includes the normal kernel headers, but only gets the 
> > > userland-safe ones.
> > 
> > I just realized this wasn't clear.  I envision a new set of headers in 
> > the kernel that are clean to export to userland.  The current headers 
> > then include the appropriate userland-clean ones, and everything below 
> > that is kernel only.
> > 
> > This lets the kernel maintain the userland-clean headers explicitly, and 
> > we don't have the work of cleaning them up for glibc.
> > 
> 
> We've referred to this for quite a while as the "ABI header project";
> it's been targetted for 2.7, since it missed the 2.6 freeze.
> 
> We have set up a mailing list at:
> 
> 	http://zytor.com/mailman/listinfo/linuxabi
> 
> The goal is to get a formal exportable version of the kernel ABI that
> user-space libraries can use.

Are the list archives broken, or has there never been traffic on this
list?

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

  reply	other threads:[~2004-01-25 23:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-23 18:07 Userland headers available Mariusz Mazur
2004-01-23 18:47 ` Daniel Jacobowitz
2004-01-23 19:04   ` Mariusz Mazur
2004-01-23 19:15   ` Chris Friesen
2004-01-23 19:39     ` Chris Friesen
2004-01-23 23:47       ` jw schultz
2004-01-24  1:38       ` H. Peter Anvin
2004-01-25 23:30         ` Daniel Jacobowitz [this message]
2004-01-26  0:09           ` H. Peter Anvin
2004-01-23 20:28   ` Sam Ravnborg

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=20040125233000.GA3319@nevyn.them.org \
    --to=dan@debian.org \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.