The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: bakul@bitblocks.com (Bakul Shah)
Subject: [TUHS] Early Clones / Rewrites for TUHS archives
Date: Mon, 18 Dec 2017 10:32:27 -0800	[thread overview]
Message-ID: <838A8C87-68EB-4757-9415-8D7D09F058F6@bitblocks.com> (raw)
In-Reply-To: <20171218154638.GP11683@mcvoy.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2363 bytes --]



> On Dec 18, 2017, at 7:46 AM, Larry McVoy <lm at mcvoy.com> wrote:
> 
>> On Mon, Dec 18, 2017 at 09:10:55PM +1100, Peter Jeremy wrote:
>>> On 2017-Dec-12 09:40:31 -0500, Clem Cole <clemc at ccc.com> wrote:
>>> 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.
>> 
>> 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.  
> 
> I've used it in that timeframe.  It was pretty amazing on a 286, you could
> have multiple people logged in via terminals and get work done.
> 
> I became friends with one of the people who did the OS:
> 
> Dan Hildebrandt (QNX)           613-591-0931 x204 (RIP 1998)
> 
> I can't remember how we crossed paths, but we both cared about design
> a lot and liked bouncing ideas off of each other.
> 
> QNX was an actual microkernel, the kernel part neatly fit in a 4K
> instruction cache.  I remember Dan telling me that it worked because
> only a few people were allowed to touch the actual kernel, they wanted
> to keep it small and fast.
> 
> This was all pre-posix, it was Unix-like but porting stuff was much
> harder than going from SunOS to IRIX.
> 
> I think that it lives on in cars, someone told me that QNX is the basis
> for a lot of the car stuff.  Anyone know?

OKL4 (a variant of L4 micro kernel) is supposedly in billions of mobile
devices. Apple’s “Secure Enclave” runs a modified version of L4. Likely
OKL4. Their claim to fame is that it is “provably correct”. L4 is derived
from Liedke’s L3 and is much more portable than L3. OKL4 and seL4
we’re both owned by Open Kernel Labs, which is now owned by General
Dynamics. Now seL4 has been open sourced. There have been a few
variations of L4 over time with names like fiasco & Pistachio etc. L4 is
simpler than Mach or QNX. What I like about seL4 is that it is capability
based. 

A contract I did ages ago was for a company that used QNX on their
text to speech 286 based board. It had a peculiar crash only when
used in a complex setup. After about a month of close study
and experiments I guessed it was an Intel bug. Intel refused to
help so then I had to catch it in action in a live setup, at which point
Intel fessed up! Any way, I learned a bunch about QNX back then. 


  parent reply	other threads:[~2017-12-18 18:32 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 [this message]
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=838A8C87-68EB-4757-9415-8D7D09F058F6@bitblocks.com \
    --to=bakul@bitblocks.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).