From owner-freebsd-questions  Fri Feb 28 21:33:11 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id VAA11437
          for questions-outgoing; Fri, 28 Feb 1997 21:33:11 -0800 (PST)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA11430
          for <freebsd-questions@freebsd.org>; Fri, 28 Feb 1997 21:33:08 -0800 (PST)
Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id VAA01501; Fri, 28 Feb 1997 21:33:00 -0800 (PST)
To: Ravi Pina <falcon@gersh.org>
cc: freebsd-questions@freebsd.org
Subject: Re: Invalid Shell Lockout 
In-reply-to: Your message of "Fri, 28 Feb 1997 19:01:05 EST."
             <331771C1.FF6D5DF@gersh.org> 
Date: Fri, 28 Feb 1997 21:33:00 -0800
Message-ID: <1498.857194380@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> Well, I seemt o have supplied an invalid shell for root, so when I want
> to su over it gives me a Permission denied!  I appear to be completely

boot with the -s flag to come up single-user, remount the / partition
read/write (mount -u /), mount /usr (so you have the passwd command)
and then change the root password.

> locked out of the system as a result... any idea what I can do to
> overcome this problem?  It owuld be nice if it just fell back to /bin/sh
> or something so you can login even if you're a dork like me.

Or if anyone were intent on attacking your machine and looking for a
really easy way to do it, yes, this would definitely help them. :-)

						Jordan