All of lore.kernel.org
 help / color / mirror / Atom feed
From: Erik Andersen <andersen@codepoet.org>
To: Rob Landley <rob@landley.net>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
	Andries Brouwer <aebr@win.tue.nl>,
	Andries.Brouwer@cwi.nl, torvalds@osdl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] linuxabi
Date: Sat, 4 Oct 2003 00:31:15 -0600	[thread overview]
Message-ID: <20031004063114.GA18876@codepoet.org> (raw)
In-Reply-To: <200310032237.03431.rob@landley.net>

On Fri Oct 03, 2003 at 10:37:03PM -0500, Rob Landley wrote:
> > My point is that we need to cleanly handle the fact that glibc
> > defines it's own abi that is not equivalent to the kernel abi.
> > A linux specific namespace does that.  After libc is done with
> > the definitions users will still use MS_RDONLY.
> 
> Does anything other than glibc have this problem?  (Does uclibc have this 
> problem?  cdrecord?)

glibc presents the glibc ABI to its client applications, and
uclibc presents the uclibc ABI to its clients.  If they choose to
process things a bit before communicating with their clients that
is their business.  But that is certainly not a problem for the
kernel developer's to worry about.

The means by which the various C libs present their own ABI to
their clients is also their private business.  If the kernel
developers can provide a clean ABI to user space that is not
mingled with kernel internals, you can be sure the various C lib
developers will be overjoyed to use that for kernel communication
and will gladly address any needed ABI translation.

 -Erik

--
Erik B. Andersen             http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--

  reply	other threads:[~2003-10-04  6:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-01  0:01 [PATCH] linuxabi Andries.Brouwer
2003-10-01  2:05 ` Bernd Eckenfels
2003-10-01  3:34   ` viro
2003-10-01  4:52     ` H. Peter Anvin
2003-10-01  5:22       ` Philippe Troin
2003-10-01  5:50         ` Miles Bader
2003-10-01 14:33     ` Daniel Jacobowitz
2003-10-01 10:20 ` J.A. Magallon
2003-10-02 14:39 ` Eric W. Biederman
2003-10-02 15:33   ` Andries Brouwer
2003-10-03  7:36     ` Eric W. Biederman
2003-10-04  3:37       ` Rob Landley
2003-10-04  6:31         ` Erik Andersen [this message]
     [not found]   ` <fa.e2g5r6g.u3igb4@ifi.uio.no>
2003-10-03 16:49     ` Kai Henningsen
2003-10-03 17:32   ` Sam Ravnborg
     [not found] <BCSP.62t.7@gated-at.bofh.it>
     [not found] ` <CcWl.7kh.9@gated-at.bofh.it>
     [not found]   ` <CdIL.8ts.13@gated-at.bofh.it>
2003-10-03 14:02     ` Ihar 'Philips' Filipau

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=20031004063114.GA18876@codepoet.org \
    --to=andersen@codepoet.org \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=aebr@win.tue.nl \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob@landley.net \
    --cc=torvalds@osdl.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.