From owner-freebsd-hackers@FreeBSD.ORG Fri Nov 12 15:46:35 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 7473C16A4D2 for ; Fri, 12 Nov 2004 15:46:35 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9761043D45 for ; Fri, 12 Nov 2004 15:46:34 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (harmony.village.org [10.0.0.6]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iACFk6DL029029; Fri, 12 Nov 2004 08:46:06 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Fri, 12 Nov 2004 08:46:14 -0700 (MST) Message-Id: <20041112.084614.63902502.imp@bsdimp.com> To: klyons@corserv.com From: "M. Warner Losh" In-Reply-To: <4194D4BC.3060103@corserv.com> References: <419406E5.6050902@corserv.com> <4194CA3E.4010601@gamersimpact.com> <4194D4BC.3060103@corserv.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Nov 2004 15:46:35 -0000 In message: <4194D4BC.3060103@corserv.com> Kevin Lyons writes: : > 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. : : And the microsoft mentality lives on. God help freebsd. Mind your P's and Q's on this mailing list, or you will be ejected. You are more than welcome to your negative opinions, but expressing them in such a disrespectful way is counter productive. It will not be tolerated, so clean it up. Just install shells/44bsd-csh and make whatever symlinks your csh shell scripts need and it will work. Alternatively, report the problem to the very responsive tcsh maintainers and the fixes for your problems will be incorporated back into freebsd automatically. Warner