The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] A repository with 44 years of Unix evolution gets the MSR '15 Best Data Showcase Award
Date: Tue, 19 May 2015 13:30:21 -0400	[thread overview]
Message-ID: <CAC20D2M4G0ibM6o=CVV8eg=fHC3gSyQM=osH3z7yf3dv8Hodgw@mail.gmail.com> (raw)
In-Reply-To: <m2d21wh5tl.fsf@athene.hamartun.priv.no>

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

On Tue, May 19, 2015 at 12:48 PM, Tom Ivar Helbekkmo <tih at hamartun.priv.no>
wrote:

> And, while it's a subject: the split was on very friendly terms.  :)


​Yes, they had different goals.   Jordan wanted to create a 386/PC friendly
install - be a low/no cost answer to MSFT when the target was Intel HW that
could be bought anywhere - i.e. HW purchased from "computer shopper".
[The port to other HW like Alpha would not come until much later]

NetBSD wanted to take the CRSG token make a solid system for research that
ran everywhere - i.e. lots of different target HW - 68K many different
vendors, Vax, Power, sparc, much less x86.  In fact, they would take back
from FreeBSD a lot of the 386 work eventually.

The NetBSD/OpenBSD fork would happen much later in time and that was based
on personalities and group management [that one was sad, but knowing both
group of people, understandable].

BTW: Linux would eventually take much of the install work that FreeBSD
originally developed - particularly in set up/install provisioning.​  At
the time, the Linux installs were pretty weak.

I know in my own case, many of us were worried that the AT&T/BSDi/UCB case
was going to make a "freely available" UNIX unable to happen.  Little did
we know that if AT&T had won, Linux (and all of the "clones") would have
been in violation of the AT&T IP - the trade secrets - and they would have
had to be removed from the market also.   I've often wondered what would
have really happened if that had occurred.

Instead, of course, a lot of hackers (myself included) quickly downloaded
Linux and started hacking and moving linux from toy to something real.

That said, I run the MacOS Unix flavor on my desk (and my wife, and each
child), FreeBSD & OpenBSD on my servers at home, but progam Linux for my
job these days.

Clem
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20150519/bc174265/attachment.html>


  reply	other threads:[~2015-05-19 17:30 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-18 20:07 Diomidis Spinellis
2015-05-19  9:24 ` Tom Ivar Helbekkmo
2015-05-19 10:04   ` Erik E. Fair
2015-05-19 13:19     ` Jacob Goense
2015-05-19 13:48       ` Steffen Nurpmeso
2015-05-19 14:36         ` SPC
2015-05-19 15:55   ` Warner Losh
2015-05-19 16:48     ` Tom Ivar Helbekkmo
2015-05-19 17:30       ` Clem Cole [this message]
2015-05-19 18:06         ` Tom Ivar Helbekkmo
2015-05-19 18:55         ` cowan
2015-05-20  3:07           ` Andy Kosela
2015-05-19 14:53 ` Clem Cole
2015-05-21  1:42 ` Derrik Walker v2.0
2015-05-21 11:50   ` Diomidis Spinellis
2015-05-21 15:09     ` cowan
2015-05-21 15:49       ` Clem Cole
2015-05-21 17:03         ` Jacob Ritorto
2015-05-21 18:04           ` Clem Cole
2015-05-25 16:46             ` Mary Ann Horton
2015-05-25 17:21               ` John Cowan
2015-05-25 21:15               ` Cory Smelosky
2015-05-26 17:55               ` Scot Jenkins
2015-05-29 14:14                 ` Mary Ann Horton
2015-05-22  0:17         ` John Cowan
2015-05-26 19:12   ` Doug McIntyre
2015-05-21 19:54 ` scj
2015-05-19 15:40 Doug McIlroy
2015-05-19 16:26 ` cowan
2015-05-19 17:29   ` Doug McIlroy
2015-05-21 19:41     ` scj
2015-05-25 19:05 Noel Chiappa
2015-05-26 10:07 Berny Goodheart

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='CAC20D2M4G0ibM6o=CVV8eg=fHC3gSyQM=osH3z7yf3dv8Hodgw@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).