From owner-freebsd-chat Tue Jul 1 05:27:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA26689 for chat-outgoing; Tue, 1 Jul 1997 05:27:05 -0700 (PDT) Received: from bitbox.follo.net (eivind@bitbox.follo.net [194.198.43.36]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA26683 for ; Tue, 1 Jul 1997 05:26:58 -0700 (PDT) Received: (from eivind@localhost) by bitbox.follo.net (8.8.5/8.7.3) id OAA14311; Tue, 1 Jul 1997 14:26:46 +0200 (MET DST) Date: Tue, 1 Jul 1997 14:26:46 +0200 (MET DST) Message-Id: <199707011226.OAA14311@bitbox.follo.net> From: Eivind Eklund To: Annelise Anderson CC: freebsd-chat@FreeBSD.ORG In-reply-to: Annelise Anderson's message of Tue, 1 Jul 1997 01:05:30 -0700 (PDT) Subject: Re: Why Not Make tcsh the default shell? References: Sender: owner-chat@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Why does FreeBSD install csh as the default shell instead of tcsh? > > Stanford University provides tcsh as the default shell....apparently > not being concerned about confusing all the hics from Iowa with > its added features..... Bloat. We've got sh and csh due to the POSIX requirement that they both should be present, as many scripts use them. For interactive shells, there are a lot of different preferences, and we provide many of them as ports - so you can mix'n'match just those of them you want. A lot of people prefer bash or zsh over tcsh; some don't even feel bothered by csh, e.g. due to using emacs around the shell anyway. Eivind.