From owner-freebsd-hackers  Sat Dec  6 03:24:16 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id DAA08823
          for hackers-outgoing; Sat, 6 Dec 1997 03:24:16 -0800 (PST)
          (envelope-from owner-freebsd-hackers)
Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA08814
          for <hackers@freebsd.org>; Sat, 6 Dec 1997 03:24:10 -0800 (PST)
          (envelope-from rkw@dataplex.net)
Received: from [208.2.87.4] (user4.dataplex.net [208.2.87.4])
	by shrimp.dataplex.net (8.8.5/8.8.5) with ESMTP id FAA05609;
	Sat, 6 Dec 1997 05:24:05 -0600 (CST)
X-Sender: rkw@mail.dataplex.net
Message-Id: <l03110701b0aee43bb353@[208.2.87.4]>
In-Reply-To: 
 <Pine.BSF.3.95.971205173721.16057A-100000@current1.whistle.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Sat, 6 Dec 1997 05:19:35 -0600
To: Julian Elischer <julian@whistle.com>
From: Richard Wackerbarth <rkw@dataplex.net>
Subject: Re: The 'Stable' status of freeBSD-stable
Cc: hackers@freebsd.org
Sender: owner-freebsd-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

At 7:49 PM -0600 12/5/97, Julian Elischer wrote:
>So today I got bitten by another API change in the 2.2 stream.
>old machines (2.2.1 vintage) can't run cpio from new
>images..
>
>the now binaries use 'lchown(2)'
>We really need to make a clear policy about this..
>I was under the impression (and so was Mike Smith)
>that the 2.2 series was supposed to have a STABLE interface!
>
>being able to add a binary from 2.2.5 to a 2.2.1 machine SHOULD work..

I agree. The change of interface should have been caused a bump to 2.3.
If I need the latest kernel patch (eg the Intel bug fix), I should
be able to simply update my source tree and compile a new kernel. PERIOD.
NOTHING else should have to be changed.

Richard Wackerbarth