The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: norman@oclsc.org (Norman Wilson)
Subject: [TUHS] Caldera ancient UNIX license question
Date: Sun, 12 Aug 2012 22:59:50 -0400 (EDT)	[thread overview]
Message-ID: <1344826817.1674.for-standards-violators@oclsc.org> (raw)

Werner Losh:

  However, the complicating factor here is, I think, that SYS V uses a
  lot of code from the later editions of Unix, so relicensing the newer
  research versions might cut into the license streams from them in
  some way.  At least that was reported at the time of the only through
  7th edition licensing.

=======

I'm not sure who would have reported that `System V uses a lot of
code from [post-7th] editions of UNIX.'  I may be misled by having
had my hands and eyes mainly on the kernel and the most-basic commands
like the shell, but offhand I can't think of any System V code at all
that was adopted directly from the Research systems in the 8th, 9th,
or 10th Edition eras.

There were certainly ideas that were picked up, mulled over, and
re-implemented in changed form by the System V people, sometimes
better and sometimes worse than the original; but not straight
code transplants.  The systems had diverged far too much for that
to be easy.

If anything, the licensing problem runs the other way: System V
code taken in by the Research system.  For example, the C compiler
we used most was based on pcc2, developed on the System V side of
the company after Steve Johnson moved there.  I think our version
of make may have been based on a System V version as well.  I'm
sure there are other (mainly smaller) examples, though since we
used no source-code control mechanism, tracing the details is
non-trivial.

None of which invalidates the basic point: there's certainly
plenty of entanglement, whether because 10/e includes ideas that
were used commercially in System V and whose mutant descendants
are still present in Solaris, or because 10/e includes some
source code directly descended from System V.

It's a shame we didn't get the several companies whose lawyers
might care to agree that there's nothing of commercial value in
the latter-day Research systems back when it was simpler to figure
out who those companies were.  As I've reported here before, there
was actually some thought by certain persons here (and one who is,
alas, no longer able to be here) of doing that, some years back,
but a certain irksome legal circus about UNIX IP got going too
quickly for that to happen, and left us with the confused situation
we have today.

Norman Wilson
Toronto ON



             reply	other threads:[~2012-08-13  2:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-13  2:59 Norman Wilson [this message]
2012-08-13  4:02 ` Larry McVoy
2012-08-13  8:28   ` arnold
2012-08-13 11:52     ` Brantley Coile
2012-08-13 13:05     ` Ronald Natalie
2012-08-13 14:24     ` Warner Losh
  -- strict thread matches above, loose matches on Subject: below --
2012-08-10 19:30 סטֵפָן פָּבִיקֵבִיק
2012-08-10 20:47 ` ron
2012-08-10 21:42   ` Benjamin Huntsman
2012-08-11  7:51     ` Wesley Parish
2012-08-11 18:33       ` Tim Newsham
2012-08-11 19:08         ` Warner Losh
2012-08-11 23:04           ` A. P. Garcia

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1344826817.1674.for-standards-violators@oclsc.org \
    --to=norman@oclsc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).