Xref: utzoo news.admin:2954 news.sysadmin:788 comp.sources.wanted:4475 comp.sources.d:2398 comp.unix.xenix:2602 Path: utzoo!attcan!uunet!husc6!mailrus!ames!killer!dcs!wnp From: wnp@dcs.UUCP (Wolf N. Paul) Newsgroups: news.admin,news.sysadmin,comp.sources.wanted,comp.sources.d,comp.unix.xenix Subject: Re: Please remove PD-YACC sources from your machine IMMEDIATELY Message-ID: <135@dcs.UUCP> Date: 4 Jul 88 20:25:00 GMT References: <3532@rpp386.UUCP> Organization: DCS, Dallas, Texas Lines: 36 In article <3532@rpp386.UUCP> jfh@rpp386 (John F. Haugh III) writes: > >Below is a copy of a letter which was received recently from AT&T. This >letter explains the status of the ``Public Domain'' YACC which I >recently posted about. >-- >Dear Mr. Haugh: > >There was a netnews article on April 19, 1988 announcing >that you had a list of files that [ are ] public domain. One >of the files listed [ was ] YACC. YACC is not public domain >software. The software is AT&T's intellectual property >obtainable by licensing only. This raises a couple of questions: 1. Are they reacting to the _name_ YACC, or did they look at the actual files John had on his system and determine that they consisted of or contained AT&T-owned source? 2. If they are reacting to the name YACC, does this mean that they ARE moving towards considering the names of *NIX utilities their property which no-one else may use? If so, where does this leave such products as MINIX, MKS, etc.? It might be useful if Mr. Wilson of AT&T could address these two questions; he or his colleagues obviously read news or they would not have known about John's posting. -- Wolf N. Paul * 3387 Sam Rayburn Run * Carrollton TX 75007 * (214) 306-9101 UUCP: killer!dcs!wnp ESL: 62832882 DOMAIN: wnp@dcs.UUCP TLX: 910-380-0585 EES PLANO UD -- Wolf N. Paul * 3387 Sam Rayburn Run * Carrollton TX 75007 * (214) 306-9101 UUCP: killer!dcs!wnp ESL: 62832882 DOMAIN: wnp@dcs.UUCP TLX: 910-380-0585 EES PLANO UD