From owner-freebsd-arch Mon Apr 17 2:58:53 2000 Delivered-To: freebsd-arch@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id 6EE8637B9F0 for ; Mon, 17 Apr 2000 02:58:50 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.3/8.9.3) with ESMTP id LAA10984 for ; Mon, 17 Apr 2000 11:58:48 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id LAA00647 for freebsd-arch@freebsd.org; Mon, 17 Apr 2000 11:58:46 +0200 (CEST) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 53D6737B524 for ; Sun, 16 Apr 2000 16:31:22 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA70732 for ; Sun, 16 Apr 2000 16:32:31 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: arch@freebsd.org Subject: since this csh issue seems to be such a hot potato... Date: Sun, 16 Apr 2000 16:32:30 -0700 Message-ID: <70728.955927950@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What I propose is that we simply decide to finish the process and move on: 1. Fix the tcsh build so that it creates a symlink to /bin/csh 2. Remove the csh sources from -current. They are now redundant. Then root's shell is tcsh and at least a non-zero number of people are happy. I also don't think that this will "confuse new users" since tcsh is a superset of csh and said new users can still follow their nutshell guides on using csh to write non-portable shell scripts or use their history substitution commands. I've never seen anything in tcsh which prevented that and even though I don't personally use tcsh anymore (I'm an evil bash user), I think it's high time we just moved on. Raising the issue of /bin/sh vs bash was, of course in retrospect, a bad mistake on my and other people's parts and we should have known better than to widen a war rather than attempting to settle it. We were stupid, our bad. Let's now just stick for now to settling the [t]csh issue and, if necessary, referring it to our principal architect for a binding decision. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message