From: cowan@mercury.ccil.org (John Cowan)
Subject: [TUHS] Microkernels (was: OS for IBM PC (was: Algol68 vs. C at Bell Labs))
Date: Thu, 7 Jul 2016 06:51:08 -0400 [thread overview]
Message-ID: <20160707105108.GC24016@mercury.ccil.org> (raw)
In-Reply-To: <20160707022020.GB78278@eureka.lemis.com>
Greg 'groggy' Lehey scripsit:
> Tandem's Guardian was a microkernel, and a very successful one at
> that.
I doubt if anyone knew or knows that who didn't work there. I did a
lot of TAL programming on those machines, and I had no clue about the
structure of the kernel.
--
John Cowan http://www.ccil.org/~cowan cowan at ccil.org
The work of Henry James has always seemed divisible by a simple dynastic
arrangement into three reigns: James I, James II, and the Old Pretender.
--Philip Guedalla
next prev parent reply other threads:[~2016-07-07 10:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 16:54 [TUHS] OS for IBM PC (was: Algol68 vs. C at Bell Labs) Norman Wilson
2016-07-04 18:13 ` Larry McVoy
2016-07-04 21:12 ` Clement T. Cole
2016-07-07 2:20 ` [TUHS] Microkernels (was: OS for IBM PC (was: Algol68 vs. C at Bell Labs)) Greg 'groggy' Lehey
2016-07-07 10:51 ` John Cowan [this message]
2016-07-07 23:36 ` Greg 'groggy' Lehey
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=20160707105108.GC24016@mercury.ccil.org \
--to=cowan@mercury.ccil.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).