The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: arnold@skeeve.com
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: ACM Software System Award to Andrew S. Tanenbaum for MINIX
Date: Wed, 19 Jun 2024 11:47:44 -0400	[thread overview]
Message-ID: <CAC20D2M38z+p4C-PqiZxqXJHKwd=gonDDNZS7xoWu_z0Ei7eFg@mail.gmail.com> (raw)
In-Reply-To: <202406190655.45J6tkVP902384@freefriends.org>

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

👍

On Wed, Jun 19, 2024 at 2:56 AM <arnold@skeeve.com> wrote:

> The "odd only" policy may be true, but it's not what I was told; I
> was told that the policy was to release externally one version behind
> what was being run internally.
>
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.




> With the consent decree done and Divestiture in the works, AT&T was
> going to be allowed get into the computer business.

Exactly, and Charlie Brown wanted to compete with IBM in particular—which
was an issue—by the time of Judge Green, the microprocessor-based
workstations had started to make huge inroads against the mini-computers.
AT&T management (Brown *et al*), still equated the "computer business" with
mainframes running Wall Street.



> So at some point, someone decided that for System V, the current system
> would be released externally.
>
Right—that would have had to have been someone(s) in AT&T UNIX marketing in
North Carolina—the folks that gave us the "*Consider it Standard*" campaign.


> I doubt we'll ever know the exact truth.
>
I agree.  I take a WAG, though.   I >>suspect<< it was linked to the
attempt to sell the 3B20S against the DEC Vax family and the then IBM model
140 (which was the "minicomputer" size IBM mainframe system).   By that
time, System V was the OS Summit had supplied for it. If there were going
to be in the commercial hardware business, the OS SW had to match what the
HW used.

Clem

ᐧ
ᐧ

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

  reply	other threads:[~2024-06-19 15:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-18 15:41 [TUHS] " 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 [this message]
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

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='CAC20D2M38z+p4C-PqiZxqXJHKwd=gonDDNZS7xoWu_z0Ei7eFg@mail.gmail.com' \
    --to=clemc@ccc.com \
    --cc=arnold@skeeve.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).