The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] SunOS vs Linux
Date: Mon, 9 Jan 2017 10:57:59 -0500	[thread overview]
Message-ID: <CAC20D2Pan-p3cp_+uJh_pz4NRVLzcmYk7nxqpah=mZ9pLfVscQ@mail.gmail.com> (raw)
In-Reply-To: <20170109063225.7imw2tuiomsekvtn@ancienthardware.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2104 bytes --]

On Mon, Jan 9, 2017 at 1:32 AM, Arno Griffioen <arno.griffioen at ieee.org>
wrote:

> Buying a BSD license was way outside a student's budget at that time
> and universities were not very forthcoming in giving them access.
>

​A little strange statement... student did not have to buy it and
Universities got it for $100 tape copying fee ( and were free to do with it
at they wanted - i.e. "dead-fish license").  FYI: CMU made us sign a
document of some type stating it was AT&T's IP to take the undergrad OS
course in 1976, but they certainly did not try to keep the code under lock
and key with a guard on the door.  Also, the whole idea of the 1956 AT&T
consent decree was that AT&T >>had<< to make the IP available -- by law (so
they did - which is why they later lost the BSDi/UCB case).   They were
given a monopoly if the world access to their patents.

Also by the late 1980s, early 1990's - i.e. Linus' time for early Linux,
most Universities world wide were using Vaxen and Sun systems.   On the
Vaxen, then tended to have BSD which is what the 386 code was based.   To
get a copy of it you needed a BSD license and almost all Universities had
them by that point in the USA and the EU.   Hey were were having USENIX
conferences hosted in the the EU pretty regularly, and lots of development.


Your comment about not being "forthcoming" I get, as people that power
often take a conservative approach if they are not sure.   But the US Gov's
deal with AT&T was certainly not supposed to have been that way.

I just don't buy it that the code was not available to Linus.    Linus'
school had access to the code base.  He has gone on record as saying he had
used Sun systems there before he started hacking and they had BSD based
Vaxen.   I think it was purely and situation of "not knowing" who or how to
ask.

Not the it matters now.   But it certainly made for a large fork, confusion
 and much unnecessary churn.

Clem
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170109/0c427870/attachment-0001.html>


  parent reply	other threads:[~2017-01-09 15:57 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-04 17:08 Clem Cole
2017-01-06  2:32 ` ron minnich
2017-01-06  3:56 ` Dan Cross
2017-01-06  3:58   ` Larry McVoy
2017-01-06 14:27   ` Clem Cole
2017-01-07  2:58     ` Greg 'groggy' Lehey
2017-01-07  3:09       ` Warner Losh
2017-01-07  3:13         ` Larry McVoy
2017-01-07  3:12       ` Larry McVoy
2017-01-08 16:28   ` Angus Robinson
2017-01-08 18:02     ` Kay Parker   
2017-01-08 20:51       ` Clem cole
2017-01-09  3:00         ` Greg 'groggy' Lehey
2017-01-09  6:32           ` Arno Griffioen
2017-01-09  8:27             ` Wesley Parish
2017-01-09 13:07             ` Joerg Schilling
2017-01-09 15:57             ` Clem Cole [this message]
2017-01-09 16:08               ` ron minnich
2017-01-09 17:40                 ` Dan Cross
2017-01-09 17:32               ` Rico Pajarola
2017-01-10 11:02                 ` Joerg Schilling
2017-01-08 22:52     ` Wesley Parish
2017-01-09 19:45   ` Jacob Goense
2017-01-08  6:10 Kirk McKusick
2017-01-08 14:52 ` Ron Natalie

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='CAC20D2Pan-p3cp_+uJh_pz4NRVLzcmYk7nxqpah=mZ9pLfVscQ@mail.gmail.com' \
    --to=clemc@ccc.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).