Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!husc6!harvard!spdcc!dyer From: dyer@spdcc.COM (Steve Dyer) Newsgroups: comp.sys.att Subject: Re: "public domain" csh Message-ID: <195@spdcc.COM> Date: Thu, 16-Jul-87 22:52:57 EDT Article-I.D.: spdcc.195 Posted: Thu Jul 16 22:52:57 1987 Date-Received: Sat, 18-Jul-87 10:21:48 EDT References: <4069@elroy.Jpl.Nasa.Gov> <7400001@fthood> <296@cbstr1.att.com> <1301@chinet.UUCP> <301@cbstr1.att.com> <1308@chinet.UUCP> Reply-To: dyer@spdcc.COM (Steve Dyer) Organization: S.P. Dyer Computer Consulting, Cambridge MA Lines: 18 I think there's no reason to get on K-K's case about his warning about a the possibility that a "public domain" csh might not actually be. The C shell, when it was first developed at Berkeley in the mid-70's, was heavily based on the V6 shell, and incorporated a lot of its code. Now, it's possible that you could have a "C shell" done from scratch, without any AT&T or Berkeley code, but I would be suspicious, too. Too often, such "public domain" code has turned out to be code which was dropped into the "public domain" by someone who had had source access in an earlier job. There was a problem along these lines with a DECUS version of YACC a few years ago. Like it or not, the onus is probably on you to verify that it isn't derived from proprietary code before distributing it. What's its pedigree? At least, getting pissed at someone who expresses a concern isn't an appropriate response. -- Steve Dyer dyer@harvard.harvard.edu dyer@spdcc.COM aka {ihnp4,harvard,linus,ima,bbn,m2c}!spdcc!dyer