From owner-freebsd-questions@FreeBSD.ORG Fri Oct 20 09:58:34 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BBA2C16A403 for ; Fri, 20 Oct 2006 09:58:34 +0000 (UTC) (envelope-from xfb52@dial.pipex.com) Received: from smtp-out3.blueyonder.co.uk (smtp-out3.blueyonder.co.uk [195.188.213.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3089143D5D for ; Fri, 20 Oct 2006 09:58:33 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from [172.23.170.145] (helo=anti-virus03-08) by smtp-out3.blueyonder.co.uk with smtp (Exim 4.52) id 1Gar96-0003iJ-5P; Fri, 20 Oct 2006 10:58:32 +0100 Received: from [82.41.251.32] (helo=[192.168.0.2]) by asmtp-out2.blueyonder.co.uk with esmtp (Exim 4.52) id 1Gar95-0008MK-DW; Fri, 20 Oct 2006 10:58:31 +0100 Message-ID: <45389DC7.70208@dial.pipex.com> Date: Fri, 20 Oct 2006 10:58:31 +0100 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.13) Gecko/20060515 X-Accept-Language: en MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <200610191303.k9JD322j081114@dc.cis.okstate.edu> <20061020013833.35ae8f1b@loki.starkstrom.lan> In-Reply-To: <20061020013833.35ae8f1b@loki.starkstrom.lan> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Why csh on Root? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Oct 2006 09:58:34 -0000 Joerg Pernfuss wrote: >/bin/sh is actually an ash. Minimal POSIX sh with a few additions that >don't help it anyway near a friendly shell for interactive use. > > With "set -o emacs" or "set -o vi", and the existence of job control, sh is a perfectly adequate *root* shell, IMHO - though I'm a csh person myself. If you do a lot of maintenance in multi-user mode then you can set yourself up another id 0 account with a different name, and use any shell you like, and even make it's home directory somewhere other that /root. If you have multiple individuals needing superuser accounts each can have their own separate superuser account, personal setup preferences etc. and you get a limited amount of accountability, too. --Alex