From: Al Kossow <aek@bitsavers.org>
To: tuhs@tuhs.org
Subject: [TUHS] Unix single-machine licensing (was Re: Re: ACM Software System Award to Andrew S. Tanenbaum for MINIX)
Date: Wed, 19 Jun 2024 09:00:44 -0700 [thread overview]
Message-ID: <1c8abcf6-5997-3c9e-7d08-b941b34089db@bitsavers.org> (raw)
In-Reply-To: <CAC20D2M38z+p4C-PqiZxqXJHKwd=gonDDNZS7xoWu_z0Ei7eFg@mail.gmail.com>
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
next prev parent reply other threads:[~2024-06-19 16:00 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 ` Al Kossow [this message]
2024-06-19 16:44 ` [TUHS] Re: Unix single-machine licensing (was Re: Re: ACM Software System Award to Andrew S. Tanenbaum for MINIX) 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
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=1c8abcf6-5997-3c9e-7d08-b941b34089db@bitsavers.org \
--to=aek@bitsavers.org \
--cc=tuhs@tuhs.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).