From owner-freebsd-current@FreeBSD.ORG  Thu Mar 10 05:40:15 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 41DC316A4CE
	for <current@freebsd.org>; Thu, 10 Mar 2005 05:40:15 +0000 (GMT)
Received: from pit.databus.com (p70-227.acedsl.com [66.114.70.227])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 75A3A43D54
	for <current@freebsd.org>; Thu, 10 Mar 2005 05:40:14 +0000 (GMT)
	(envelope-from barney@databus.com)
Received: from pit.databus.com (localhost [127.0.0.1])
	by pit.databus.com (8.13.1/8.13.1) with ESMTP id j2A5eDOR006065
	for <current@freebsd.org>; Thu, 10 Mar 2005 00:40:13 -0500 (EST)
	(envelope-from barney@pit.databus.com)
Received: (from barney@localhost)
	by pit.databus.com (8.13.1/8.13.1/Submit) id j2A5eDB4006064
	for current@freebsd.org; Thu, 10 Mar 2005 00:40:13 -0500 (EST)
	(envelope-from barney)
Date: Thu, 10 Mar 2005 00:40:13 -0500
From: Barney Wolff <barney@databus.com>
To: current@freebsd.org
Message-ID: <20050310054013.GA5193@pit.databus.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.8i
X-Scanned-By: MIMEDefang 2.51 on 66.114.72.185
Subject: 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 05:40:15 -0000

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