From owner-freebsd-hackers Fri Dec 5 18:00:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA04787 for hackers-outgoing; Fri, 5 Dec 1997 18:00:22 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA04777 for ; Fri, 5 Dec 1997 18:00:17 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id RAA14080 for ; Fri, 5 Dec 1997 17:53:26 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd014071; Fri Dec 5 17:53:09 1997 Date: Fri, 5 Dec 1997 17:49:48 -0800 (PST) From: Julian Elischer To: hackers@freebsd.org Subject: The 'Stable' status of freeBSD-stable Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk 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.. ok, so I've built a new kernel for that machine and hopefully that will be the end of it, but even though people have complained about thigs I have added to -stable, I've always been careful that they were completely transparrent. just a grumble.... (overrall I'm quite pleased with the stability, and we have LOTS of FreeBSD machines out there, all running 2.2.x kernels) julian