Packet size & number of windows in UUCP

Phil Ngai phil at amdcad.AMD.COM
Thu Feb 25 15:10:48 AEST 1988


In article <4684 at mcdchg.UUCP> heiby at mcdchg.UUCP (Ron Heiby) writes:
<Carl S. Gutekunst (csg at pyramid.UUCP) writes:
<< And any site that has a source license can compile it for a neighboring
<< site that has only a binary license, and give them the binary.
<
<I think that this should be checked before being acted upon.  Once upon a time,
<I asked about doing just such a thing.  (It was even in the context of UUCP!)
<The answer I got was that the source site must have a Binary Redistribution
<Agreement (called "Customer Provisions", I believe, whatever that means) with
<AT&T in order to distribute binaries derived from licensed software.  Not only
<that, but said source site would be liable to AT&T for an additional binary
<royalty, even if the recipient of the program already had a copy from a
<different vendor and had already paid a binary royalty.

I have asked AT&T about this also and Ron is correct. Quite simply,
_you_ must license a machine before _you_ put any AT&T Unix code on
it, whether source or binary, it must be licensed appropriately. The
fact that someone else has already licensed the same machine for Unix
is as irrelevant as the same machine having an MSDOS license. Think of
it as a license for you to perform the act of putting the code on the
machine, not as a license for the machine. 

Only the license holder is permitted to install a Unix derived program.

I do not know how well such a policy can be enforced.  But we play by
the rules at my company. Who wants to tangle with AT&T lawyers? 

If it seems like a rip off, complain to AT&T.

-- 
I speak for myself, not the company.

Phil Ngai, {ucbvax,decwrl,allegra}!amdcad!phil or phil at amd.com



More information about the Comp.unix.questions mailing list