From owner-freebsd-current@FreeBSD.ORG Sat May 14 17:20:49 2005 Return-Path: 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 CC95116A4CE for ; Sat, 14 May 2005 17:20:49 +0000 (GMT) Received: from vms044pub.verizon.net (vms044pub.verizon.net [206.46.252.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id A884643D48 for ; Sat, 14 May 2005 17:20:49 +0000 (GMT) (envelope-from david.freebsd@verizon.net) Received: from [192.168.2.102] ([68.161.118.114])0.04 <0IGH007ASPIK1QUD@vms044.mailsrvcs.net> for freebsd-current@freebsd.org; Sat, 14 May 2005 12:20:45 -0500 (CDT) Date: Sat, 14 May 2005 12:23:33 -0400 From: David Gurvich To: freebsd-current@freebsd.org Message-id: <200505141223.33891.david.freebsd@verizon.net> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit Content-disposition: inline User-Agent: KMail/1.8 Subject: workaround ssh and login breakage X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 May 2005 17:20:49 -0000 Put a normal user into the wheel group from single-user mode, then login as that user and #su root. Give your root password and you should be able to do rootly things. That should allow application of the patch without too much trouble.