From owner-freebsd-hackers  Wed Jun 26 23:18:19 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id XAA04164
          for hackers-outgoing; Wed, 26 Jun 1996 23:18:19 -0700 (PDT)
Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA04157
          for <hackers@freebsd.org>; Wed, 26 Jun 1996 23:18:16 -0700 (PDT)
Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.5/CET-v2.1) with SMTP id GAA14802 for <hackers@freebsd.org>; Thu, 27 Jun 1996 06:18:13 GMT
Date: Thu, 27 Jun 1996 15:18:13 +0900 (JST)
From: Michael Hancock <michaelh@cet.co.jp>
To: hackers@freebsd.org
Subject: sh understands set -o vi
Message-ID: <Pine.SV4.3.93.960627141202.14324A-100000@parkplace.cet.co.jp>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Boy, have I been out of it.

I've been putting the following into root's .login to get ksh/bash vi
functionality.

if ( -x /usr/local/bin/bash & -x /usr/local/bin/ssh-agent ) then
	setenv ENV "$HOME/.bashrc
	setenv SHELL "/usr/local/bin/bash"
	exec /usr/local/bin/ssh-agent /usr/local/bin/bash
endif

But sh seems to have a lot the features of bash and it's statically linked
and lives in /bin, so I'm now using it for the root shell. 

.profile has this at the end now to get the ssh stuff going...

[ -x /usr/local/bin/ssh-agent -a -s /usr/lib/libc.so.3.0 ] && {
	export ENV SHELL
	ENV=$HOME/.shrc
	SHELL=/bin/sh
	exec /usr/local/bin/ssh-agent /bin/sh
}

sh does the set -o vi thing and has job control.  I think it makes a good
safe root shell.


mike hancock