From: drb@msu.edu (Dennis Boone)
Subject: [TUHS] And now ... Weirdnix?
Date: Sun, 17 Sep 2017 10:49:09 -0400 [thread overview]
Message-ID: <20170917144909.DB27FA585CB@yagi.h-net.msu.edu> (raw)
In-Reply-To: (Your message of Sun, 17 Sep 2017 17:03:16 +1000.) <8AA943A2-D6C0-4812-9C16-C09D1298754F@tuhs.org>
> 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.
Guess I can more or less tick two of the above boxes. The Prime minis
had a layered product called Primix that provided a unix userland of
sorts. Dog slow, at least in its earlier releases. Null pointers were
not zero on the Prime machines.
De
next prev parent reply other threads:[~2017-09-17 14:49 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
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 [this message]
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=20170917144909.DB27FA585CB@yagi.h-net.msu.edu \
--to=drb@msu.edu \
/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).