Technology and Trends
 USENET Archives
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 GARFIELD 20/11/84; site garfield.UUCP
Path: utzoo!utcsrgv!garfield!andrew
From: and...@garfield.UUCP (Andrew Draskoy)
Newsgroups: net.unix-wizards
Subject: Public Domain software in UN*X?
Message-ID: <2243@garfield.UUCP>
Date: Wed, 19-Dec-84 22:50:21 EST
Article-I.D.: garfield.2243
Posted: Wed Dec 19 22:50:21 1984
Date-Received: Thu, 20-Dec-84 01:59:17 EST
Distribution: net
Organization: Memorial U. of Nfld. C.S. Dept., St. John's
Lines: 10

I seem to remember someone saying that the string(3) routines distributed
by Berkley were public domain, and that indeed so were several other library
routines.  If anyone knows *for sure* of something in a UN*X variant that
is public domain, I would like to hear about it - I am trying to compile
a list.  Please reply via mail, I will summarise if there is interest.
Andrew Draskoy
The opinions expressed above may not represent those of the author
after he has had some sleep.

Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site hcradm.UUCP
Path: utzoo!hcrvax!hcradm!mike
From: m...@hcradm.UUCP (Mike Tilson)
Newsgroups: net.unix-wizards
Subject: Re: Public Domain software in UN*X?
Message-ID: <1607@hcradm.UUCP>
Date: Mon, 24-Dec-84 14:55:09 EST
Article-I.D.: hcradm.1607
Posted: Mon Dec 24 14:55:09 1984
Date-Received: Tue, 25-Dec-84 00:24:08 EST
References: <2243@garfield.UUCP>
Distribution: net
Organization: Human Computing Resources, Toronto
Lines: 41

Before people start assuming that this or that item of software from 4.2BSD
is "public domain", it would be useful to read the license agreement you
(or your organization) has with the Regents of the University of California.
Essentially you had to agree that the entire UCB distribution is covered
under your *AT&T UNIX license*.  The only way to get something from 4.2BSD
into the "public domain" is to find the person who *owns* it, and have that
person give it to you free of restrictions.  The "owner" is often not the same
as the "author".  If you are going to use any "public domain" software in a
commercial application, you might want to investigate whether the author of
the software actually has the right to give it to you.  (The software might
actually belong to the author's institution or employer -- if the author works
for a commercial entity, this is almost invariably the case.)

Many people forget that various software packages incorporate the intellectual
property of some other organization (like AT&T).  A recent news posting
speculated that David Tilbrook's QED/TIPS package might be public domain.
In fact, deep in the heart of the QED package is the Version 6 "ed.c".
(At least this was the case some time ago -- I haven't looked lately.)

If a software package has lifted source code from various licensed sources,
then the package is covered by the *union* of licensing restrictions, and
by the *intersection* of licensing rights.  This should be kept in mind
when building new applications.  It is often better to use existing software
as a tool through a well-defined interface, rather than modifying and
incorporating source code into a package.  E.g. if you need a special
stdio routine, write one which operates by calling the standard unchanged
routines, rather than by hacking some AT&T source code into your program
with changes.  This approach will save future licensing hassles, and as
a by-product it also helps portability and maintainability.

It isn't enough to say that some software "ought to be" in the public domain.
People feel this way especially about the UCB stuff.  However, AT&T in good
faith provided UNIX to universities at nominal charge, and it was UCB's
decision (along with Darpa) to make use of UNIX in the 4.2BSD effort.  The
*changes* to UNIX may somehow end up in the public domain, but UNIX itself
is not.  The only way to "uncontaminate" 4.2BSD would be to re-do the whole
thing without reference to any UNIX source code (and also with an independent
re-write of all the manuals).  If you think about how hard that is, you'll
realize how much 4.2BSD still owes to UNIX.

/Michael Tilson, Human Computing Resources Corp.