From owner-freebsd-hackers@FreeBSD.ORG Fri Nov 12 02:30:26 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BC65416A4CE for ; Fri, 12 Nov 2004 02:30:26 +0000 (GMT) Received: from keylime.silverwraith.com (keylime.silverwraith.com [69.55.228.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9FD0443D58 for ; Fri, 12 Nov 2004 02:30:26 +0000 (GMT) (envelope-from lists-freebsd@silverwraith.com) Received: from keylime.silverwraith.com ([69.55.228.10]) by keylime.silverwraith.com with esmtp (Exim 4.41 (FreeBSD)) id 1CSRCk-000LA6-98; Thu, 11 Nov 2004 18:30:26 -0800 Received: (from avleen@localhost)iAC2UOtl081202; Thu, 11 Nov 2004 18:30:24 -0800 (PST) (envelope-from lists-freebsd@silverwraith.com) X-Authentication-Warning: keylime.silverwraith.com: avleen set sender to lists-freebsd@silverwraith.com using -f Date: Thu, 11 Nov 2004 18:30:23 -0800 From: Avleen Vig To: Kevin Lyons Message-ID: <20041112023023.GG19417@silverwraith.com> References: <41940880.7070409@corserv.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41940880.7070409@corserv.com> User-Agent: Mutt/1.5.6i cc: freebsd-hackers@freebsd.org Subject: Re: tcsh fix X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Nov 2004 02:30:26 -0000 On Thu, Nov 11, 2004 at 06:49:04PM -0600, Kevin Lyons wrote: > I think the problem can still be fixed. Simply put in /bin/tcsh and let > /bin/csh be what it actually is, which is to say /bin/csh. I realize > that will add all of 300kB to the system. And there would also have to > be an entry for tcsh in /etc/shells. Should I send a patch? > > Developers have a right to expect a certain basic level of functionality > on a system. When he calls fopen() he should get fopen, when he calls > /bin/bash he should get /bin/bash not zsh nor sh nor ksh. I have to agree with Kevin's sentiments on principle. 'csh' should run pure csh, not anything else. 'sh' should be pure sh, not what Linux does and bastardize it as /bin/bash If someon wants a more powerful shell, they can install it themselves. -- Avleen Vig Systems Administrator Personal: www.silverwraith.com EFnet: irc.mindspring.com (Earthlink user access only)