public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Thunder from the hill <thunder@ngforever.de>
Cc: David Woodhouse <dwmw2@infradead.org>, Dave Jones <davej@suse.de>,
	"Albert D. Cahalan" <acahalan@cs.uml.edu>,
	OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
	<linux-kernel@vger.kernel.org>, <chaffee@cs.berkeley.edu>
Subject: Re: [patch] fat/msdos/vfat crud removal
Date: 10 Jun 2002 07:51:22 -0600	[thread overview]
Message-ID: <m1zny3utr9.fsf@frodo.biederman.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0206091417250.8715-100000@hawkeye.luckynet.adm>

Thunder from the hill <thunder@ngforever.de> writes:

> Hi,
> 
> On Sun, 9 Jun 2002, David Woodhouse wrote:
> > Er, no. If you randomly reassign errno values, the world breaks.
> > Don't even contemplate it.
> 
> I meant adding. Not just errno, even PF_..., etc.
> 
> > To that end, we should put '#ifndef __KERNEL__ #error' into all kernel
> > headers, and C libraries should maintain a _separate_ set of headers which
> > contain only the ABI definitions and are suitable for userspace. I believe 
> > dietlibc already does this, and recent Red Hat distributions contain a 
> > 'glibc-kernheaders' package with a slightly-sanitised version of kernel 
> > headers, which should become more sanitised over time.
> 
> I wouldn't call dietlibc an HighEnd open end API.

All linux libc's do this.  glibc, dietlibc, and uclibc.

Beyond this if you really object you can come up with a set of header
that just describe the kernel/user space ABI, and build them so either
the kernel or user space can use them.  And then this ABI-headers
package can be used to hold the common definitions.

Until someone builds a kernel-abi-headers package everyone will do it
by copying the appropriate headers periodically.

Eric

  reply	other threads:[~2002-06-10 14:03 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-09  2:47 [patch] fat/msdos/vfat crud removal Albert D. Cahalan
2002-06-09  4:24 ` OGAWA Hirofumi
2002-06-09  4:32 ` OGAWA Hirofumi
2002-06-09  4:46   ` Albert D. Cahalan
2002-06-09  5:07     ` OGAWA Hirofumi
2002-06-09  6:03       ` Albert D. Cahalan
2002-06-09  6:32         ` OGAWA Hirofumi
2002-06-09  7:09           ` Albert D. Cahalan
2002-06-09  7:49             ` OGAWA Hirofumi
2002-06-09  9:46             ` Dave Jones
2002-06-09 17:52               ` Eric W. Biederman
2002-06-09 18:49                 ` H. Peter Anvin
2002-06-09 19:00                 ` Thunder from the hill
2002-06-09 19:29                   ` David Woodhouse
2002-06-09 20:19                     ` Thunder from the hill
2002-06-10 13:51                       ` Eric W. Biederman [this message]
2002-06-09 21:04                   ` Albert D. Cahalan
2002-06-10 13:55                     ` Eric W. Biederman
2002-06-11 16:49                       ` Jamie Lokier
2002-06-12  6:50                         ` Eric W. Biederman
2002-06-12 11:47                           ` Thunder from the hill
2002-06-09  9:00         ` OGAWA Hirofumi
2002-06-09 13:51         ` Martin Dalecki

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=m1zny3utr9.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --cc=acahalan@cs.uml.edu \
    --cc=chaffee@cs.berkeley.edu \
    --cc=davej@suse.de \
    --cc=dwmw2@infradead.org \
    --cc=hirofumi@mail.parknet.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thunder@ngforever.de \
    /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