The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: segaloco <segaloco@protonmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: PWB 1.0 Distro and Licensing Timeframe
Date: Fri, 10 Mar 2023 16:06:51 -0500	[thread overview]
Message-ID: <CAC20D2O9TwAxZGXH-RMErF=HD_hZuhPcMJ=NK02=W9gLOean4A@mail.gmail.com> (raw)
In-Reply-To: <9QXzG1pmIgoHdlkiU-ljIDoco5SPzWKEudlEu8W26K28NXD_2bgCijSQmWAn7CBthISuVyzSuxvPGUKmv6A5Gsc-GoNrDb8SA1D5_m449nA=@protonmail.com>

[-- Attachment #1: Type: text/plain, Size: 2275 bytes --]

On Fri, Mar 10, 2023 at 2:51 PM segaloco via TUHS <tuhs@tuhs.org> wrote:

> Was there a particular "public release" date for PWB 1.0 or would it have
> just been whenever folks started getting tapes out of Bell?

No PWB 1.0, 2.0, and 4.0 were private to the Bell System ... however

The Bell OYOC (one year on campus) program meant that all the new BS hires,
spent the summer at their Bell Labs site, then were enrolled for a year at
one of the participating schools.  Many of the OYOCs brought things from
the labs to their schools - i.e. pieces of PWB 'leaked' from BTL to the
schools.

Remember, until the System III license, the only license was a research
system license.

The other really important piece is that the V7 redistribution license was
the first that allowed vendors to ship binaries, and this is all pre-Judge
Green.    The vendors started the negotiation for the replacement of the V7
license almost at day one [December 1979 was the first meeting at Ricki's
Hyatt - which I have described earlier].

PWB 3.0 was not yet released when the negotiation started but AT&T was
offering that technology, not what was in Research. By the time the new
license was agreed, AT&T Summit had already released PWB 4.0 inside of the
labs and Judge Green had done his thing.  Al Arms (AT&T's legal head) and
Otis Wilson (who was taking over the legal interface with us on the vendor
side), was afraid trying to switch to PWB 4.0 at that point would delay
things even more and the vendors were so upset wit the V7 terms (and they
all had their own private versions of UNIX by then), they did not want the
bits -- they wanted the new license terms.





> Also, was PWB held as something that would be "marketable" from the
> get-go,

No, Summit -- the Unix Support Group -- was originally to support UNIX for
the Bell System. Remember 1956 content decree -- AT&T can not "market"
anything.   They can support their own technologies for the operating
companies and other Labs.

As I said, yesterday -- PWB 1.0 (Piscataway) is set up >>before<< USG.
Mashey and team are running a UNIX based data center -- they are trying to
make what Ken and Dennis give then more 'bullet proof' because they care of
production users.
ᐧ

[-- Attachment #2: Type: text/html, Size: 4221 bytes --]

  reply	other threads:[~2023-03-10 21:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-10 19:50 [TUHS] " segaloco via TUHS
2023-03-10 21:06 ` Clem Cole [this message]
2023-03-10 21:24   ` [TUHS] " Warner Losh
2023-03-10 21:44     ` Clem Cole
2023-03-11 11:12     ` Jonathan Gray
2023-03-11 16:40       ` Clem Cole
2023-03-11 17:06         ` Jon Forrest
2023-03-11 17:20         ` Rich Salz
2023-03-11 18:39         ` Warner Losh
2023-03-11 19:24           ` segaloco via TUHS
2023-03-12  2:02           ` Heinz Lycklama
2023-03-12  1:44         ` Jonathan Gray
2023-03-12  4:42           ` Jonathan Gray
2023-03-13 10:25           ` [TUHS] Boston Children's Museum (was: PWB 1.0 Distro and Licensing Timeframe) Jonathan Gray
2023-03-11 18:05       ` [TUHS] Re: PWB 1.0 Distro and Licensing Timeframe Warner Losh

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='CAC20D2O9TwAxZGXH-RMErF=HD_hZuhPcMJ=NK02=W9gLOean4A@mail.gmail.com' \
    --to=clemc@ccc.com \
    --cc=segaloco@protonmail.com \
    --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).