Date: Thu, 11 Nov 2004 18:30:23 -0800 From: Avleen Vig <lists-freebsd@silverwraith.com> To: Kevin Lyons <klyons@corserv.com> Cc: freebsd-hackers@freebsd.org Subject: Re: tcsh fix Message-ID: <20041112023023.GG19417@silverwraith.com> In-Reply-To: <41940880.7070409@corserv.com> References: <41940880.7070409@corserv.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041112023023.GG19417>