From owner-freebsd-questions Mon Aug 25 13:20:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA06968 for questions-outgoing; Mon, 25 Aug 1997 13:20:12 -0700 (PDT) Received: from srv.net (snake.srv.net [199.104.81.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA06871 for ; Mon, 25 Aug 1997 13:19:59 -0700 (PDT) Received: from darkstar.home (pmif112.ida.net [204.228.203.112]) by srv.net (8.8.5/8.8.5) with SMTP id OAA18184 for ; Mon, 25 Aug 1997 14:19:46 -0600 (MDT) Date: Mon, 25 Aug 1997 13:19:13 -0700 (MST) From: Charles Mott X-Sender: cmott@darkstar.home To: freebsd-questions@FreeBSD.ORG Subject: bash as root login shell (was Re: su and PS1) In-Reply-To: <9035.872539774@axl.iafrica.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I don't see the problem using bash for the root shell. If there is damage to repair, then it is possible to boot up in the single user mode, remount the file system read/write and do what ever fixup work is necessary. I actually had a situation where I messed up the password file and had to do exactly this because I couldn't login on any account at all. Charles Mott On Mon, 25 Aug 1997, Sheldon Hearn wrote: > > > Now, my question is this: can I include a line to execute bash at the > > end of the .cshrc file to switch to bash without causing the > > above-mentioned problem? > > Shouldn't be a problem so long as you don't exec the shell. This means > that, in extremely ugly situations, you'll be using more memory than > necessary. > > If you exec bash and bash fails for some reason, you'll lose your > existing csh too, so *poof* no root login. :) > > Cheers, > Sheldon. > >