The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: rp@servium.ch (Rico Pajarola)
Subject: [TUHS] SunOS vs Linux
Date: Mon, 9 Jan 2017 18:32:21 +0100	[thread overview]
Message-ID: <CACwAiQ=OLbvque4Jg_byK9c7O+h7_3zav40euCzDzCGfKT2tug@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2Pan-p3cp_+uJh_pz4NRVLzcmYk7nxqpah=mZ9pLfVscQ@mail.gmail.com>

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

On Mon, Jan 9, 2017 at 4:57 PM, Clem Cole <clemc at ccc.com> wrote:

>
> 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").
>

Now stop picking on Joerg already. Not every university was invested in
Unix. In practice Unix source was pretty much unobtainable if you happened
to live outside of the "Unix bubble".

I grew up and went to school/university in Switzerland, and getting access
to UNIX source was nothing but a crazy pipe dream at the time. I don't even
know if my university had a source license (I can't imagine they didn't),
but in any case it wasn't something that they would let you use as a normal
student. None of my inquiries at the time resulted in anything that would
allow me to get access to Unix source. If the university had it, this
wasn't public information, and they didn't share. I couldn't prove that my
university had a license, and I had no way to get the actual bits. This was
the 90ies btw.

We had Sun workstations (Solaris, without source), Windows (blech, but
funnily enough there were source kits. No, you couldn't get access to that
either), and of course the locally developed Oberon machines (Lilith) and
later Bluebottle. I also saw some VAXen running VMS (on their way out).
Some departments had RS/6000s, Alphas and SGIs and other random stuff (do I
need to mention that they came without source?). I've never seen any trace
of Unix source or even BSD.

We all longed for some Unix that was available for personal use, and Linux
absolutely filled that gap. While 386BSD was theoretically available, it
came out almost a year after Linus announced his first version of Linux.
386BSD seemed to have a lot of strings attached, and it wasn't really
usable until FreeBSD/NetBSD. By that time, Linux had gained a lot of
momentum already.

Rico
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170109/9b13ab99/attachment.html>


  parent reply	other threads:[~2017-01-09 17:32 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
2017-01-09 16:08               ` ron minnich
2017-01-09 17:40                 ` Dan Cross
2017-01-09 17:32               ` Rico Pajarola [this message]
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='CACwAiQ=OLbvque4Jg_byK9c7O+h7_3zav40euCzDzCGfKT2tug@mail.gmail.com' \
    --to=rp@servium.ch \
    /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).