From: Greg KH <greg@kroah.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Nikita Danilov <nikita@clusterfs.com>,
gregkh@suse.de,
Linux Kernel Mailing List <Linux-Kernel@vger.kernel.org>,
Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: [RFC] Add kernel<->userspace ABI stability documentation
Date: Wed, 1 Mar 2006 12:56:47 -0800 [thread overview]
Message-ID: <20060301205647.GA16331@kroah.com> (raw)
In-Reply-To: <1141198077.3866.5.camel@laptopd505.fenrus.org>
On Wed, Mar 01, 2006 at 08:27:52AM +0100, Arjan van de Ven wrote:
> On Tue, 2006-02-28 at 16:23 -0800, Greg KH wrote:
> > On Tue, Feb 28, 2006 at 02:39:29PM +0300, Nikita Danilov wrote:
> > > Greg KH writes:
> > >
> > > [...]
> > >
> > > > +
> > > > + stable/
> > > > + This directory documents the interfaces that have determined to
> > > > + be stable. Userspace programs are free to use these interfaces
> > > > + with no restrictions, and backward compatibility for them will
> > > > + be guaranteed for at least 2 years. Most simple interfaces
> > > > + (like syscalls) are expected to never change and always be
> > > > + available.
> > >
> > > What about separating "stable" ("guaranteed for at least 2 years") and
> > > "standard" (core unix interface is not going to change ever)?
> >
> > Why? Would that mean that the POSIX-like syscalls would only be in
> > "standard"? What else would you think would be in that category?
>
> that sounds wrong. If you want posix behavior, use glibc. Not the kernel
> directly. It's that simple. The kernel tends to follow posix mostly, to
> allow glibc to do this job without too much hoops, but it's glibc that
> provides the final posix API to the application. And it should be that
> way.
Yes, sorry, that is much more correct.
greg k-h
next prev parent reply other threads:[~2006-03-01 20:56 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-27 19:01 [RFC] Add kernel<->userspace ABI stability documentation Greg KH
2006-02-27 19:08 ` Arjan van de Ven
2006-02-27 19:11 ` Greg KH
2006-02-27 19:17 ` Arjan van de Ven
2006-02-27 19:22 ` Kumar Gala
2006-02-27 19:30 ` Greg KH
2006-02-27 19:31 ` Andi Kleen
2006-02-27 19:44 ` Greg KH
2006-03-01 13:53 ` Lars Marowsky-Bree
2006-03-01 14:10 ` Gabor Gombas
2006-03-01 14:35 ` Jes Sorensen
2006-03-01 16:30 ` Lars Marowsky-Bree
2006-02-27 20:06 ` Jesper Juhl
2006-02-27 19:35 ` Diego Calleja
2006-02-27 19:49 ` Greg KH
2006-02-27 19:57 ` Diego Calleja
2006-02-27 20:00 ` Greg KH
2006-02-27 20:13 ` Diego Calleja
2006-02-28 0:26 ` Greg KH
2006-02-27 19:36 ` Benjamin LaHaise
2006-02-27 19:46 ` Greg KH
2006-02-27 20:01 ` Benjamin LaHaise
2006-02-27 20:13 ` Greg KH
2006-02-27 20:22 ` John W. Linville
2006-02-27 22:00 ` Greg KH
2006-02-27 20:10 ` Arjan van de Ven
2006-02-27 22:58 ` Olivier Galibert
2006-02-27 20:20 ` Linus Torvalds
2006-02-27 21:04 ` Al Viro
2006-02-27 23:33 ` Nicholas Miell
2006-02-27 23:45 ` Greg KH
2006-02-28 1:52 ` Jason Lunz
2006-02-28 6:32 ` Theodore Ts'o
2006-02-28 6:41 ` Dave Jones
2006-03-01 0:34 ` Greg KH
2006-03-01 1:17 ` Nicholas Miell
2006-03-02 4:24 ` Greg KH
2006-03-05 16:17 ` Eric W. Biederman
2006-03-05 23:23 ` Benjamin LaHaise
2006-03-06 0:12 ` Eric W. Biederman
2006-03-06 0:39 ` Benjamin LaHaise
2006-03-06 2:15 ` Eric W. Biederman
2006-03-07 3:56 ` Greg KH
2006-02-27 19:52 ` Alistair John Strachan
2006-02-27 19:57 ` Greg KH
2006-02-27 20:05 ` Alistair John Strachan
2006-02-27 20:12 ` Greg KH
2006-02-27 20:15 ` Greg KH
2006-02-27 22:56 ` Olivier Galibert
2006-02-28 0:11 ` Greg KH
2006-02-27 20:01 ` Jesper Juhl
2006-03-01 0:21 ` Greg KH
2006-02-28 11:39 ` Nikita Danilov
2006-03-01 0:23 ` Greg KH
2006-03-01 7:27 ` Arjan van de Ven
2006-03-01 20:56 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-07 14:44 Al Boldi
2006-03-07 15:21 ` Josh Boyer
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=20060301205647.GA16331@kroah.com \
--to=greg@kroah.com \
--cc=Linux-Kernel@vger.kernel.org \
--cc=arjan@infradead.org \
--cc=gregkh@suse.de \
--cc=kay.sievers@vrfy.org \
--cc=nikita@clusterfs.com \
/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.