The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: segaloco via TUHS <tuhs@tuhs.org>
To: tuhs@tuhs.org
Subject: [TUHS] Re: Unix single-machine licensing (was Re: Re: ACM Software System Award to Andrew S. Tanenbaum for MINIX)
Date: Thu, 20 Jun 2024 04:08:45 +0000	[thread overview]
Message-ID: <hR1Do7FyKq_mhPvuvVa7GDxie4B84yNUq8hc5ETINt28Dv7xdkA0MYClxj7a2nmkknmKWDctHynvHbQz-aXpq_MrvNtEapfpEcyE82ChSb8=@protonmail.com> (raw)
In-Reply-To: <Ghne-kwY403fIwmCFUn59gziDyVrXhDLbFp8tOYqUjzpsQGdXadebt-x1OCy2isF0UFAIZviiSzd2P8EN-_LI9SobCRLWlxNhzovwjRk2pk=@protonmail.com>

On Wednesday, June 19th, 2024 at 12:10 PM, segaloco via TUHS <tuhs@tuhs.org> wrote:

> On Wednesday, June 19th, 2024 at 9:00 AM, Al Kossow aek@bitsavers.org wrote:
> 
> > On 6/19/24 8:47 AM, Clem Cole wrote:
> > 
> > > That's how I remember Otis Wilson explaining it to us as commercial licensees at a licensing meeting in the early 1980s.
> > > We had finally completed the PWB 3.0 license to replace the V7 commercial license (AT&T would rename this System III - but we knew it as PWB
> > > 3.) during the negociations Summit had already moved on to the next version - PWB 4.0. IMO: Otis was not ready to start that process again.
> > 
> > Is the really early history of Unix licensing documented anywhere?
> > The work on reviving a Plexus P20 prompted me to put up the history of Onyx and Plexus at
> > http://bitsavers.org/pdf/plexus/history and a long time ago someone who worked at Fortune
> > told me we can all thank Onyx in 1980 for working out the single machine licensing with
> > AT&T
> 
> 
> I've got a stack of license specimens as well as a bit of correspondence between
> MIT Lincoln Laboratory, Raytheon, and Western Electric discussing UNIX licenses
> for single CPUs. The correspondence (circa 1980) concerns V7 licenses for a
> PDP-11/44 (MIT LL) and PDP-11/45 (Raytheon). The license specimens are in two
> groups, one set that has blanks and/or generic language describing
> "Licensed Software" and a second set specifically issued for UNIX System III.
> 
> The licenses have document codes:
> 
> - Software-Corp.-020173-020182-2 - Software Agreement between AT&T and <Blank>
> 
> - Software-Customer CPU-052776-090180-2 - Customer CPU Agreement between <Blank> and <Blank>
> 
> - Supp. Ag.-Time Sharing-020178-010180-2 - Supplemental Agreement (Time Sharing) between Western Electric Company, Incorporated and <Blank>
> 
> - Supp. Ag.-Customer CPU-020178-010180-2 - Supplemental Agreement (Customer CPU) between Western Electric Company, Incorporated and <Blank>
> 
> - Supp. Ag.-Cust. Spec.-020181-2 - Supplemental Agreement (Customer Software, Specified Number of Users) between Western Electric Company, Incorporated and <Blank>
> 
> - Cont. CPU-060181-1 - Contractor CPU Agreement between <Blank> and <Blank>
> 
> - Sys. III-Corp.-110181-040182-2 - Software Agreement between AT&T and <Blank> for UNIX System III
> 
> - Sys. III-Cust.-010182-041582-2 - Supplemental Agreement (Customer Provisions) between AT&T and <Blank> for UNIX System III
> 
> 
> Would scans of these documents help? The licenses at least should be fine as they're specimen copies with no PII. Regarding the correspondence, there is one letter on DARPA letterhead (from MIT LL to WECo), two on WECo letterhead (one back to MIT LL, the other to Raytheon) and then one on AT&T letterhead responding generically to an uinquiry regarding UNIX System III licensing. Does anyone foresee issues with scanning the correspondence, or is that the sort of thing that might get me shipped off to some black site?
> 
> - Matt G.

And now these are up here: https://archive.org/details/att_unix_licenses_1982

Included is misc.pdf, which is the couple letters as well as a packing slip from Bell Laboratories for a shipment of V7.  Also a revision to my last listing of their document codes, the "-2" on the end is a page number...whoops...the document names in the archive posting reflect the document codes sans this oversight.  I labeled the posting 1982 as that's the date on the latest of the license specimens, the letters were in the same batch of documents but not adjacent.

- Matt G.

      parent reply	other threads:[~2024-06-20  4:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-18 15:41 [TUHS] ACM Software System Award to Andrew S. Tanenbaum for MINIX Nelson H. F. Beebe
2024-06-18 17:21 ` [TUHS] " Clem Cole
2024-06-18 17:38 ` segaloco via TUHS
2024-06-18 20:59   ` Dave Horsfall
2024-06-18 21:15     ` segaloco via TUHS
2024-06-18 22:00       ` Dave Horsfall
2024-06-19  6:55         ` arnold
2024-06-19 15:47           ` Clem Cole
2024-06-19 16:00             ` [TUHS] Unix single-machine licensing (was Re: Re: ACM Software System Award to Andrew S. Tanenbaum for MINIX) Al Kossow
2024-06-19 16:44               ` [TUHS] " Clem Cole
2024-06-26  8:42                 ` Al Kossow
2024-06-26 20:57                   ` Clem Cole
2024-06-27 14:10                 ` Jonathan Gray
2024-06-19 19:10               ` segaloco via TUHS
2024-06-19 19:35                 ` Jacobson, Doug W [E CPE]
2024-06-20  4:08                 ` segaloco via TUHS [this message]

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='hR1Do7FyKq_mhPvuvVa7GDxie4B84yNUq8hc5ETINt28Dv7xdkA0MYClxj7a2nmkknmKWDctHynvHbQz-aXpq_MrvNtEapfpEcyE82ChSb8=@protonmail.com' \
    --to=tuhs@tuhs.org \
    --cc=segaloco@protonmail.com \
    /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).