From owner-freebsd-chat Wed Jul 2 03:48:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA28069 for chat-outgoing; Wed, 2 Jul 1997 03:48:53 -0700 (PDT) Received: from andrsn.stanford.edu (root@andrsn.Stanford.EDU [36.33.0.163]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA28064 for ; Wed, 2 Jul 1997 03:48:50 -0700 (PDT) Received: from localhost (andrsn@localhost.stanford.edu [127.0.0.1]) by andrsn.stanford.edu (8.8.5/8.6.12) with SMTP id DAA04943; Wed, 2 Jul 1997 03:48:47 -0700 (PDT) Date: Wed, 2 Jul 1997 03:48:46 -0700 (PDT) From: Annelise Anderson To: Francisco Reyes cc: FreeBSD Chat List Subject: Re: Why Not Make tcsh the default shell? In-Reply-To: <199707011843.OAA06202@federation.addy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-chat@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 1 Jul 1997, Francisco Reyes wrote: > I would also like to add to what others have said that it is probably > not a good idea to make tcsh the default. > I figure if someone knows enough not to like the default and know > there is something better, they probably know enough to get whatever > shell they like and get it installed. I am of course convinced by the universal opposition to this idea that it would not be good to make tcsh the default shell. There are unquestionably many competing demands on limited space for a default system, both on disk and in memory; tcsh seems to be about 274K, and maybe 30K or so larger than csh. However, new users do not know enough not to like the default; they do not know that there is something better that is not entirely different but merely enhanced; and they don't know enough to get whatever shell they like. And in fact the process of adding a shell to /etc/shells, changing the default shell for a user, and installing the shell is a three-part process that is, indeed, in all its individual parts, simple-- and yet implies some sophistication about how the operating system works; and some investigation into what sort of a substitute for .cshrc may be needed (again simple, but not obvious). Meanwhile the new user is trying to get the right stuff in sysconfig or rc.conf, trying to make it dial in and dial out, trying to make it telnet, getting the web server set up, trying to make the printer print, maybe worrying about dot clocks, ppp, reconfiguring the kernel to get the sound card working, etc. etc. etc., and is stuck with csh...because ........ Obviously a minority view.... Annelise