All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@novell.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: "Timothy D. Witham" <wookie@osdl.org>,
	Linux Kernel ML <linux-kernel@vger.kernel.org>
Subject: Re: Announcing Binary Compatibility/Testing
Date: Wed, 13 Oct 2004 19:24:15 -0400	[thread overview]
Message-ID: <1097709855.5411.20.camel@localhost> (raw)
In-Reply-To: <416DAEB7.4050108@pobox.com>

On Wed, 2004-10-13 at 18:39 -0400, Jeff Garzik wrote:

> Userland ABI compatibility has always been a strongly held value in 
> Linux, I don't think we would flame any efforts to support that...

Yah.  With the exception of maybe changing something in /proc (which has
been rare, and hopefully will never happen with /sys) the kernel-to-user
ABI is really stable.

I'd venture, in fact, to say that this effort is very important but does
not affect the kernel at all.  Current "fault" lies in things e.g. like
the C++ ABI, which is constantly fluctuating (rightly so, to fix bugs,
but still).

Any other incompatibility lies in libraries, but we have library
versioning.  There is nothing wrong with newer libs breaking
compatibility so long as they have a different soname.  Vendors just
need to ship compat libs and ISV's need to make sure they request the
right lib and don't touch internals.

	Robert Love



  parent reply	other threads:[~2004-10-13 23:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-13 22:16 Announcing Binary Compatibility/Testing Timothy D. Witham
2004-10-13 22:38 ` Timothy D. Witham
2004-10-13 22:39 ` Jeff Garzik
2004-10-13 22:55   ` Timothy D. Witham
2004-10-13 23:24   ` Robert Love [this message]
2004-10-13 23:36     ` Timothy D. Witham
2004-10-14 18:32     ` Linus Torvalds
2004-10-14 21:57       ` Diego Calleja
2004-10-15 19:49     ` Matthias Urlichs
2004-10-17 21:44     ` Kurt Garloff

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=1097709855.5411.20.camel@localhost \
    --to=rml@novell.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wookie@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.