From owner-freebsd-questions@FreeBSD.ORG Thu Oct 19 13:03:03 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 947FD16A403 for ; Thu, 19 Oct 2006 13:03:03 +0000 (UTC) (envelope-from martin@dc.cis.okstate.edu) Received: from dc.cis.okstate.edu (dc.cis.okstate.edu [139.78.100.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2A8A43D6A for ; Thu, 19 Oct 2006 13:03:02 +0000 (GMT) (envelope-from martin@dc.cis.okstate.edu) Received: from dc.cis.okstate.edu (localhost.okstate.edu [127.0.0.1]) by dc.cis.okstate.edu (8.13.3/8.13.3) with ESMTP id k9JD322j081114 for ; Thu, 19 Oct 2006 08:03:02 -0500 (CDT) (envelope-from martin@dc.cis.okstate.edu) Message-Id: <200610191303.k9JD322j081114@dc.cis.okstate.edu> To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <81111.1161262982.1@dc.cis.okstate.edu> Date: Thu, 19 Oct 2006 08:03:02 -0500 From: Martin McCormick Subject: 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: Thu, 19 Oct 2006 13:03:03 -0000 Is there any particular reason why FreeBSD has csh as the default root shell? Nothing really wrong with it except that I quit using csh about twelve years ago and so am a little rusty about the finer details when I come across a csh shell. On a number of FreeBSD4.x systems, I used chsh to change root's shell after installing bash and the only thing I noticed was that one should be careful of the $PATH variable and make sure it at least hits all the same directories in the same order. Other than that, it worked. On a recent upgrade to 5.4, I noticed the C shell is still default so I figured I would ask before changing it so as not to introduce hidden problems later. Basically, I like bash better and also add a couple more paths such as /usr/local/etc for home-grown applications. Thanks for your thoughts. Martin McCormick WB5AGZ Stillwater, OK Systems Engineer OSU Information Technology Department Network Operations Group