From: david@kdbarto.org (David)
Subject: [TUHS] Weird nix? Regulus
Date: Sun, 17 Sep 2017 10:27:00 -0700 [thread overview]
Message-ID: <601911ED-162B-47E6-ADB5-4BB31EE6D733@kdbarto.org> (raw)
In-Reply-To: <mailman.1029.1505658197.3779.tuhs@minnie.tuhs.org>
What a pain, almost like Unix, and not quite. l It was a clone of Unix for the 68k. The APIs were ever so slightly different because the authors were concerned about copyright infringement. libc calls had different argument orders or types and in general it was just off enough that you wanted to claw at the screen every time something went wrong.
To top it off, the system we were hosting it on was so slow that a full rebuild of our meager (10k lines) software took overnight.
I eventually ported all the software to a SparcStation-2 cross compiling to the 68k target we were embedded on.
> 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.
>
> Cheers, Warren
next parent reply other threads:[~2017-09-17 17:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1029.1505658197.3779.tuhs@minnie.tuhs.org>
2017-09-17 17:27 ` David [this message]
2017-09-17 17:55 ` Ron Natalie
2017-09-17 18:07 ` Derrik Walker v2.0
2017-09-18 16:41 ` Paul Winalski
2017-09-18 19:54 Derek Fawcus
2017-09-19 11:53 ` David
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=601911ED-162B-47E6-ADB5-4BB31EE6D733@kdbarto.org \
--to=david@kdbarto.org \
/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).