From: wes.parish@paradise.net.nz (Wesley Parish)
Subject: [TUHS] SunOS vs Linux
Date: Mon, 09 Jan 2017 21:27:21 +1300 (NZDT) [thread overview]
Message-ID: <1483950441.58734969d08cd@www.paradise.net.nz> (raw)
In-Reply-To: <20170109063225.7imw2tuiomsekvtn@ancienthardware.org>
I can second that. At the time I was asking about an OS suitable for my
brand-new 486 while I was at the U of Canterbury NZ, I was told I'd need to get
an AT&T license for BSD, and those cost a king's ransom.
Does anybody have copies of the kind of legal guff AT&T put these universities
through? It would make interesting reading.
Wesley Parish
Quoting Arno Griffioen <arno.griffioen at ieee.org>:
> On Mon, Jan 09, 2017 at 02:00:22PM +1100, Greg 'groggy' Lehey wrote:
> > > load it. Which is sort of funny because it was not particularly
> > > secret between most BSD users.
> >
> > Given that the first person he mentions in the article is Bruce
> Evans,
> > it's difficult to understand how he hadn't heard of it.
>
> Have to keep in mind that Linus was at the time of course a student in
> Finland, so outside the USA.
>
> Outside the USA such BSD (or other *IX) source-code access on
> universities
> and technical schools was not common is my personal experience.
>
> At that time I was a student too and apart from MINIX there really was
> little to no *IX source access available to anyone (BSD or otherwise)
> unless
> for very specific research applications and needing to sign all sorts of
> NDA
> stuff.
>
> Buying a BSD license was way outside a student's budget at that time
> and universities were not very forthcoming in giving them access.
>
> As a result MINIX was actually making quite a few strides to get more
> complex, but Andrew Tanenbaum always actively resisted turning it into a
>
> 'production' system as he wanted to retain it as an educational tool
> (and the license agreement was quite limited to this purpose) pushing a
>
> lot of european hackers towards this initially very rudimentary minix
> userland-compatible new little kernel made by some finnish dude ;)
>
> Quite a few strong discussions between Linus and Andrew at the time
> on Usenet in comp.os.minix about the monolithic vs. microkernel
> ideas.
>
> Bye, Arno.
>
"I have supposed that he who buys a Method means to learn it." - Ferdinand Sor,
Method for Guitar
"A verbal contract isn't worth the paper it's written on." -- Samuel Goldwyn
next prev parent reply other threads:[~2017-01-09 8:27 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 [this message]
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
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=1483950441.58734969d08cd@www.paradise.net.nz \
--to=wes.parish@paradise.net.nz \
/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).