From owner-freebsd-sparc64@FreeBSD.ORG  Thu Feb 26 14:14:33 2004
Return-Path: <owner-freebsd-sparc64@FreeBSD.ORG>
Delivered-To: freebsd-sparc64@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 61FFC16A4CE
	for <freebsd-sparc64@freebsd.org>;
	Thu, 26 Feb 2004 14:14:33 -0800 (PST)
Received: from blake.polstra.com (blake.polstra.com [64.81.189.66])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0E11F43D1D
	for <freebsd-sparc64@freebsd.org>;
	Thu, 26 Feb 2004 14:14:33 -0800 (PST)	(envelope-from jdp@polstra.com)
Received: from strings.polstra.com (dsl081-189-067.sea1.dsl.speakeasy.net
	[64.81.189.67])
	by blake.polstra.com (8.12.9p2/8.12.9) with ESMTP id i1QMEWtC051003;
	Thu, 26 Feb 2004 14:14:32 -0800 (PST)	(envelope-from jdp@polstra.com)
Message-ID: <XFMail.20040226141432.jdp@polstra.com>
X-Mailer: XFMail 1.5.4 on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <20040226220817.GA7995@xor.obsecurity.org>
Date: Thu, 26 Feb 2004 14:14:32 -0800 (PST)
From: John Polstra <jdp@polstra.com>
To: Kris Kennaway <kris@obsecurity.org>
X-Bogosity: No, tests=bogofilter, spamicity=0.409931, version=0.14.5
cc: freebsd-sparc64@freebsd.org
Subject: Re: 64btt cvsup?
X-BeenThere: freebsd-sparc64@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting FreeBSD to the Sparc <freebsd-sparc64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>,
	<mailto:freebsd-sparc64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-sparc64>
List-Post: <mailto:freebsd-sparc64@freebsd.org>
List-Help: <mailto:freebsd-sparc64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>,
	<mailto:freebsd-sparc64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Feb 2004 22:14:33 -0000

On 26-Feb-2004 Kris Kennaway wrote:
> On Thu, Feb 26, 2004 at 02:02:42PM -0800, John Polstra wrote:
>> 
>> Lots of things can go wrong here.
> 
> Note that there has just been a flag day in 5.2-CURRENT that required
> everyone to rebuild everything linked to libc_r (or take libmap
> countermeasures).  Before that, in 5.1-CURRENT the change to fstatfs()
> required everyone to rebuild everything that called that function
> (with no workarounds available).
> 
> The impact of this change is hardly unprecedented, and when discussed
> here there was strong consensus that we should just take the hit and
> do it now before 5.x-STABLE comes along and we lose the justification
> for breaking binary compatibility.

OK, this wouldn't be the first time I'd been overly cautious. :-}

John