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

On Wed, 2004-10-13 at 19:24 -0400, Robert Love wrote:
> 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 would tend to agree with that statement.

> 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.
> 

   Part of the problem is knowing which things to request.  I've
envisioned a database that has the matrix of tests and packages  so that 
people like ISV's and system integrators will be able to look
up what has been tested and passed. I think that this database
is the crucial portion of the new development.

   I also expect that part of this process will be the finding that
an ISV used the API in a way that could of got them in trouble 
and that the new version closes that hole.  In this case it would
be a bug on the ISVs side but it would be known long before
it got deployed and the ISV could schedule the development and
testing of the patch to their software as part of their normal 
deployment schedule.


> 	Robert Love
> 

Tim

-- 
Timothy D. Witham - Chief Technology Officer - wookie@osdl.org
Open Source Development Lab Inc - A non-profit corporation
12725 SW Millikan Way - Suite 400 - Beaverton OR, 97005
(503)-626-2455 x11 (office)    (503)-702-2871     (cell)
(503)-626-2436     (fax)


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

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-13 22:16 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
2004-10-13 23:36     ` Timothy D. Witham [this message]
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=1097710592.6077.79.camel@wookie-zd7 \
    --to=wookie@osdl.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@novell.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®