The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: wes.parish@paradise.net.nz (Wesley Parish)
Subject: [TUHS] Unix clones
Date: Thu, 06 Apr 2017 21:40:56 +1200 (NZST)	[thread overview]
Message-ID: <1491471656.58e60d2874425@www.paradise.net.nz> (raw)
In-Reply-To: <ea552ded-b728-4c14-7909-59b9d3ed8e1b@gmail.com>

Thanks. I'm thinking we could classify the Unix clones under three categories:
the commercial, such as UniFlex, Idris, UNOS
the academic, such as Minix and Tunix
and the hobbyist such as Linux at its beginning

Then it strikes me that that could probably apply to Unix at various stages in
its history:
v1, v2, v3 hobbyist v4?
v5, v6, *BSD academic
SysIII, SysV commercial

FWVLIW

Wesley Parish

Quoting William Pechter <pechter at gmail.com>:

> Wesley Parish wrote:
> > The mention of UNOS a realtime "clone" of Unix in a recent thread
> raises a question for me. How many 
> > Unix clones are there?
<snip>
> > Thanks
> >
> > Wesley Parish
<snip>
> Idris from Whitesmiths once passed through my hands... I actually
> skipped that one for UniPlus SysIII and SysV on the
> Perkin-Elmer 7350 box with a dip packaged 68000...
> 
> I ran Coherent until I got the hardware to go 386-BSD, NetBSD, FreeBSD,
> and Linux 0.99.xx (SLS and later Slackware).
> 
> Before the UniPlus I ran Xenix-86 on an AT&T 6300 with a Nec V30 (not a
> 6300+ 286 box).
> 
> https://en.wikipedia.org/wiki/Unix-like
> 
> Bill
>  



"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


  reply	other threads:[~2017-04-06  9:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-06  1:18 Wesley Parish
2017-04-06  1:30 ` William Pechter
2017-04-06  9:40   ` Wesley Parish [this message]
2017-04-06 18:00 Clem Cole
2017-04-06 18:02 ` Clem Cole
2017-04-06 18:09   ` Clem Cole
2017-04-07  1:12     ` Wesley Parish
2017-04-07 21:58       ` Steve Johnson
2017-04-07 23:18         ` Steve Nickolas
2017-04-08  1:26           ` Jason Stevens
2017-04-08 15:22 Doug McIlroy

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=1491471656.58e60d2874425@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).