From owner-freebsd-stable Thu Sep 7 8:30:26 2000 Delivered-To: freebsd-stable@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 2E92737B422 for ; Thu, 7 Sep 2000 08:30:25 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id IAA33459; Thu, 7 Sep 2000 08:29:59 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: eps@sirius.com (Eric P. Scott) Cc: freebsd-stable@FreeBSD.ORG Subject: Re: NO_TCSH issue In-Reply-To: Message from eps@sirius.com (Eric P. Scott) of "Wed, 06 Sep 2000 21:26:52 PDT." <200009070426.VAA96776@mail1.sirius.com> Date: Thu, 07 Sep 2000 08:29:58 -0700 Message-ID: <33455.968340598@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > No, it isn't. And not including a 44bsd-csh package on > 4.1-RELEASE's CD #1 (note that 44bsd-more is there) was downright > malicious. Hyperbole will get you nowhere. Perhaps you could try to exhibit some actual signs of intelligence for the audience instead and let us know HOW it's not compatible with csh. Then perhaps someone could rectify those issues and we could actually get somewhere rather than waving our arms around and shouting. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message