From: jsteve@superglobalmegacorp.com (Jason Stevens)
Subject: [TUHS] Early Clones / Rewrites for TUHS archives
Date: Wed, 13 Dec 2017 12:16:25 +0800 [thread overview]
Message-ID: <2b92d6c7-d67c-4029-a25e-b344f8c0afb9@HK2APC01FT050.eop-APC01.prod.protection.outlook.com> (raw)
In-Reply-To: <CAC20D2O=8BNUkxF6C3-T+EydQAjp-sCo=MTkcFvmxwFx3CKVOg@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1712 bytes --]
And then in the early 90’s (91 or 92) we had ixemul on the Amiga, and EMX on MS-DOS and OS/2. Although I guess that is too new?
Sent from Mail for Windows 10
From: Clem Cole
Sent: Tuesday, 12 December 2017 10:41 PM
To: The Eunuchs Hysterical Society
Subject: [TUHS] Early Clones / Rewrites for TUHS archives
My question about SOL got me thinking a bit. It would be nice to have section in TUHS of any early clones that could be collected. The two that I can think of that probably should be there are (other feel free to point ones that we should try to find):
1.) Idris, which was fairly true to V6 (enough that the one time I test it, things from pretty much just worked). It was notable from being first. Although the C compiler and the 'anat' (the assembler) were a tad different. It the system that got Bill Plauger in trouble @ USENIX @ UDEL when he was booed for a 'marketing' talk.
2.) CRDS (pronounced Cruds by those of use that use it at the time) - Charles River Data Systems. It was a UNIX-like system, although I do not think really attempted to hold to a V7 API much more than intent. Although if my memory serves me, one of the unique features was the use of Reed & Kanodia synchronization in its kernel [REED79], which I was a always a fan. The system was slow as sin bit it ran on a 68000. [CRUDS system, a Fortune box and our Vax/750 running BSD4.1 were the systems Masscomp used to bootstrap].
Clem
[REED79] D.P. Reed and R.K. Kanodia, "Synchronization with Eventcounts and Sequencers"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20171213/d6d9fb61/attachment.html>
next prev parent reply other threads:[~2017-12-13 4:16 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 14:40 Clem Cole
2017-12-12 16:29 ` Random832
2017-12-12 16:41 ` Random832
2017-12-13 4:16 ` Jason Stevens [this message]
2017-12-13 21:22 ` Nemo
2017-12-14 0:26 ` Robert Swierczek
2017-12-18 10:10 ` Peter Jeremy
2017-12-18 15:46 ` Larry McVoy
2017-12-18 15:57 ` Steve Nickolas
2017-12-18 15:59 ` Larry McVoy
2017-12-18 16:13 ` Steve Simon
2017-12-18 16:18 ` Arthur Krewat
2017-12-18 16:15 ` Henry Bent
2017-12-18 16:34 ` Andy Kosela
2017-12-18 16:39 ` Gregg Levine
2017-12-18 17:35 ` Steve Simon
2017-12-18 17:41 ` Toby Thain
2017-12-18 18:41 ` Brad Spencer
2017-12-18 16:37 ` Gregg Levine
2017-12-18 18:32 ` Bakul Shah
2017-12-18 16:53 ` Clem Cole
2017-12-18 17:08 ` Kurt H Maier
2017-12-12 15:16 Noel Chiappa
2017-12-12 16:01 ` Warner Losh
2017-12-13 2:15 ` Nigel Williams
2017-12-13 13:46 ` Clem Cole
2017-12-13 16:58 ` Larry McVoy
2017-12-13 19:03 ` Clem Cole
2017-12-16 4:50 ` Dave Horsfall
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=2b92d6c7-d67c-4029-a25e-b344f8c0afb9@HK2APC01FT050.eop-APC01.prod.protection.outlook.com \
--to=jsteve@superglobalmegacorp.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).