From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] Early Clones / Rewrites for TUHS archives
Date: Mon, 18 Dec 2017 11:53:50 -0500 [thread overview]
Message-ID: <CAC20D2N0CDNk4e7zSrMyxWwQZ08HiRFXgrKziNfCUJLYt2fqzA@mail.gmail.com> (raw)
In-Reply-To: <20171218101055.GA46385@server.rulingia.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2383 bytes --]
On Mon, Dec 18, 2017 at 5:10 AM, Peter Jeremy <peter at rulingia.com> wrote:
>
> One thing I haven't seen mentioned is QNX - I didn't directly use it but a
> colleague was using it in the mid-1980s on PC-AT class hardware. ISTR one
> of my colleague's whinges was the 256-byte command-line limit.
QNX, indeed a cool system. It's predecessor was Thoth and successor, the
Stanford V-Kernel; QNX was the same timeframe as Mach.
RIG/Accent and Thoth were all contemporaries and at the time, "UNIX"
interface was not yet standard, nor C as the system language of choice,
Thoth was in B IIRC, RIG assembler & Pascal, Accent / Pascal. Tunis was
similar, although, like SOL was a rewrite, in that case Concurrent-Pascal;
like UNIX, targeting the PDP-11.
Both QNX and Mach were in C and tried to be more friendly to import UNIX
code. QNX was definitely, Intel architecture target. Mach was trying to
be all things on any HW target like UNIX., I got the impression some/much
of QNX's kernel was assembler, but the 'servers' for the things like the
FS, the IP stack, et al where 100% C.
QNX, was clean, an extremely small, and was fairly good at real-time (
like Thoth had been before it, V gave up real-time to be more portable
distribute better).
I used a QNX on a PC/AT (286) that was, V7-ish and code from the PDP-11
pretty much just worked. The compiler was very slow, but it was 5.25"
floppy based system so it may have been a lot to do with the disks I have.
I remember they then add a POSIX subsystem when that was in vogue, but I
never used it or their ANSI-C compiler.
When 'embedded' types needed a RTOS, the QNX folks definitely had a
following; particularly because the kernel was so small and efficient. I
know a number of industrial robots from the 'Rust Belt' that had Mech-E
types that swore by it (i.e. Millacron, Intelligrated to think of two). I
understand that a number of folks/alumni are a lot of the current
autonomous car people, and I had heard the brought that code base with
them. Again, if I understand it correctly (and its been years since I
played with it), the RTOS features are not POSIX conformant and mixing the
different APIs could cause interesting effects.
ᐧ
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20171218/57216477/attachment-0001.html>
next prev parent reply other threads:[~2017-12-18 16:53 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
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 [this message]
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=CAC20D2N0CDNk4e7zSrMyxWwQZ08HiRFXgrKziNfCUJLYt2fqzA@mail.gmail.com \
--to=clemc@ccc.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).