The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: davida@pobox.com (David Arnold)
Subject: [TUHS] And now ... Weirdnix?
Date: Sun, 17 Sep 2017 18:10:37 +1000	[thread overview]
Message-ID: <DF8CEB2A-53A7-4513-B794-763CCA635B1B@pobox.com> (raw)
In-Reply-To: <201709170728.v8H7SvbH014339@freefriends.org>

Helios: a Unix-like system running on Transputers (and TI C40, and a few others).

It had a similar notion of a universal protocol for servers to hook into the "file" namespace as Plan9 / 9P, and a shell that included operators for spawning tasks on other CPUs, parallel execution, and so on.

They'd ported some basic GNU userland: GCC, GMake, etc, as well as the basic sources (ls, and co -- not sure where they came from or if they were written from scratch).  There was even an X11R5 (maybe R4?) server that would work with a few of the framebuffers that some of the Transputer boards had.

All good fun.  Sadly didn't last too long: likely killed off by Inmos' late delivery of the second gen T9000 processor like most of the Transputer world, but they disappeared after trying to move onto other CPUs seemingly unsuccessfully.



d


> On 17 Sep 2017, at 17:28, arnold at skeeve.com wrote:
> 
> Warren Toomey <wkt at tuhs.org> wrote:
> 
>> To kick a more relevant thread off, what was the "weirdest" Unix system
>> you used & why? Could be an emulation like Eunice, could  be the hardware
>> e.g NULL was not zero, NUXI byte ordering etc.
> 
> AT&T 3B20 - *0 didn't segfault but brought in some weird value.
> 
> Pyramid Dual Universe - System V vs. BSD - why be forced to decide when
> you can have your cake and eat it too?
> 
> Whatever Data General called their Unix layer on top of their native
> OS for the Eclipse or whatever it was (32 bit system).
> 
> Eunice - we had it one place I worked but I didn't use it much.
> 
> I never got to work on more exotic systems such as Interdata
> or Series 1.
> 
> Arnold



  reply	other threads:[~2017-09-17  8:10 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-17  7:03 Warren Toomey
2017-09-17  7:28 ` arnold
2017-09-17  8:10   ` David Arnold [this message]
2017-09-17 12:52     ` Adam Sampson
2017-09-17 14:23     ` Steve Simon
2017-09-17 18:50   ` Chet Ramey
2017-09-17 19:01     ` Derrik Walker v2.0
2017-09-18 12:02     ` arnold
2017-09-17 14:49 ` Dennis Boone
2017-09-18  7:27   ` Nigel Williams
2017-09-18  8:31     ` arnold
2017-09-18 10:39       ` Andreas Kusalananda Kähäri
2017-09-18 11:59         ` Michael Kjörling
2017-09-19  1:54       ` Dave Horsfall
2017-09-19  7:07         ` Ian Zimmerman
2017-09-19 14:09         ` [TUHS] PR1ME - was " Toby Thain
2017-09-17 15:08 ` [TUHS] " Nemo
2017-09-18 23:57 ` Dave Horsfall
2017-10-04  5:58 ` Tom Ivar Helbekkmo
2017-10-04 16:15   ` George Michaelson
     [not found] <mailman.1035.1505674910.3779.tuhs@minnie.tuhs.org>
2017-09-18 11:41 ` [TUHS] " David
2017-09-18 13:15   ` Chet Ramey

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=DF8CEB2A-53A7-4513-B794-763CCA635B1B@pobox.com \
    --to=davida@pobox.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).