From owner-freebsd-hackers@FreeBSD.ORG  Fri Nov 12 14:35:42 2004
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
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 10FA516A4CE
	for <freebsd-hackers@freebsd.org>;
	Fri, 12 Nov 2004 14:35:42 +0000 (GMT)
Received: from node15.coopprint.com (node15.cooperativeprinting.com
	[208.4.77.15])	by mx1.FreeBSD.org (Postfix) with SMTP id 6400543D48
	for <freebsd-hackers@freebsd.org>;
	Fri, 12 Nov 2004 14:35:41 +0000 (GMT)
	(envelope-from ryans@gamersimpact.com)
Received: (qmail 31976 invoked by uid 0); 12 Nov 2004 14:33:45 -0000
Received: from unknown (HELO ?192.168.0.5?) (63.231.165.87)
  by node15.coopprint.com with SMTP; 12 Nov 2004 14:33:45 -0000
Message-ID: <4194CA3E.4010601@gamersimpact.com>
Date: Fri, 12 Nov 2004 08:35:42 -0600
From: Ryan Sommers <ryans@gamersimpact.com>
User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Kevin Lyons <klyons@corserv.com>
References: <419406E5.6050902@corserv.com>
In-Reply-To: <419406E5.6050902@corserv.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
cc: freebsd-hackers@freebsd.org
Subject: Re: Re; tcsh is not csh
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Nov 2004 14:35:42 -0000

Kevin Lyons wrote:

> >Dan Nelson wrote:
> >
> > but you're 4 years too late to affect
> >the outcome...
>
> 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. Oh and there would 
> also have to be an entry for tcsh in /etc/shells.  Should I send a patch?

(root@blue)~:cvs co -d etc src/etc
(root@blue)~:cd etc
(root@blue)~/etc:grep tcsh shells
/bin/tcsh
(root@blue)~/etc:

How many programs does this incompatability actually break? 
Realistically? If it hasn't been a problem in the last 4 years it makes 
me wonder if anyone is actually writing or using shell scripts written 
for this.

I'm not opposed to adding a real csh to /bin, but if we're only adding 
it to work around a minor incompatability that few if any programs rely 
on I don't see it as being a necessity.

-- 
Ryan Sommers
ryans@gamersimpact.com