From owner-freebsd-current  Mon Feb 19 10: 6:56 2001
Delivered-To: freebsd-current@freebsd.org
Received: from feral.com (feral.com [192.67.166.1])
	by hub.freebsd.org (Postfix) with ESMTP id 4B3D237B6A3
	for <current@FreeBSD.org>; Mon, 19 Feb 2001 10:06:54 -0800 (PST)
Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71])
	by feral.com (8.9.3/8.9.3) with ESMTP id KAA06606;
	Mon, 19 Feb 2001 10:06:45 -0800
Date: Mon, 19 Feb 2001 10:06:45 -0800 (PST)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: Warner Losh <imp@harmony.village.org>
Cc: current@FreeBSD.org
Subject: Re: got stuck in the current __sF foo... 
In-Reply-To: <200102180157.f1I1vKW93062@harmony.village.org>
Message-ID: <Pine.LNX.4.21.0102191005480.19274-100000@zeppo.feral.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


> In message <Pine.BSF.4.21.0102171535350.24221-100000@beppo.feral.com> Matthew Jacob writes:
> : One system got stuck in the current __sF bork... I'm not stuck with:
> 
> : Any advice?
> 
> Copy a pre Feb 10th libc.so.5 to this box.  Alternatively, copy a Feb
> 17 or later one.

It turns out that no matter what I seem to do, I can't rebuild.

I think I'll just do the big bomb approach and take another alpha (the Alpha
4100, of all things!) that managed to make it through unscathed and just clone
it's disk.

-matt




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message