From owner-freebsd-current@FreeBSD.ORG  Thu Mar 10 06:20:27 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 48E5616A4CE
	for <current@freebsd.org>; Thu, 10 Mar 2005 06:20:27 +0000 (GMT)
Received: from critter.freebsd.dk (f170.freebsd.dk [212.242.86.170])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 44BAE43D2D
	for <current@freebsd.org>; Thu, 10 Mar 2005 06:20:26 +0000 (GMT)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id j2A6KHLN006180;
	Thu, 10 Mar 2005 07:20:17 +0100 (CET)
	(envelope-from phk@critter.freebsd.dk)
To: Barney Wolff <barney@databus.com>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Thu, 10 Mar 2005 00:40:13 EST."
             <20050310054013.GA5193@pit.databus.com> 
Date: Thu, 10 Mar 2005 07:20:17 +0100
Message-ID: <6179.1110435617@critter.freebsd.dk>
Sender: phk@critter.freebsd.dk
cc: current@freebsd.org
Subject: Re: current repair? 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Mar 2005 06:20:27 -0000


I posted a patch here yesterday should try.

In message <20050310054013.GA5193@pit.databus.com>, Barney Wolff writes:
>Is there a suggested mechanism for repairing a very -current system
>that exhibits the "unable to log in via ssh or console" problem?
>Presumably I can boot it single-user, but then what?
>Thanks,
>Barney Wolff
>_______________________________________________
>freebsd-current@freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-current
>To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
>

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.