Xref: utzoo news.admin:2999 news.sysadmin:821 comp.sources.wanted:4540 comp.sources.d:2476 comp.unix.xenix:2672
Path: utzoo!attcan!uunet!lll-winken!lll-tis!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: <140@dcs.UUCP>
Date: 12 Jul 88 12:35:56 GMT
References: <3532@rpp386.UUCP> <135@dcs.UUCP> <235@pigs.UUCP> <4765@killer.UUCP> <4775@killer.UUCP>
Reply-To: wnp@dcs.UUCP (Wolf N. Paul)
Organization: DCS, Dallas, Texas
Lines: 21

In article <4775@killer.UUCP> chasm@killer.UUCP (Charles Marslett) writes:
>Actually, I seem to recall that the MKS version of yacc is in fact a
>licensed port of the real AT&T yacc -- I do not remember why or who led
>me to this belief, is there any contradictory (or supporting) information
>out there to clear up the confusion?  That would clear up why AT&T is not
>after them!

A couple of weeks ago Alex White, one of the officers of MKS, stated
categorically that NONE of the programs which make up the MKS toolkit
are ported, derived, or licensed from AT&T code. Since MKS YACC is part of
the Toolkit, this statement would seem to apply to it, too.

MKS RCS is licensed from Walter Tichy, and the MKS Text formatting package
(whose exact name I can't recall) is a repackaging from SoftQuad's DWB
port, and is thus licensed from AT&T, but neither of these are part of the 
MKS Toolkit but are separately sold products.

Wolf Paul
-- 
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