From: Greg 'groggy' Lehey <grog@lemis.com>
To: Larry McVoy <lm@mcvoy.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Xinu (was: In Memoriam: John Lions)
Date: Thu, 5 Dec 2019 15:31:59 +1100 [thread overview]
Message-ID: <20191205043159.GA42246@eureka.lemis.com> (raw)
In-Reply-To: <20191205041653.GO32688@mcvoy.com>
[-- Attachment #1: Type: text/plain, Size: 952 bytes --]
Hopefully this still fits the TUHS charter. I'd be happy to see
followups move to COFF.
On Wednesday, 4 December 2019 at 20:16:53 -0800, Larry McVoy wrote:
> Though I have to say that Doug Comer did an equally good job with
> his XINU books. Do you guys know of Doug? XINU stands for Xinu is
> not Unix but he wrote, by himself, an OS and documented it in his
> books. I give him credit for my desire to have code be really
> simple and self explanatory.
Agreed, modulo (for argument's sake) "equally". Xinu was the first
book I read on “Unix†internals, and it greatly inspired me.
> I'd kinda like to invite him to join us, what do you think?
Go for it!
Greg
--
Sent from my desktop computer.
Finger grog@lemis.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed. If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 163 bytes --]
next prev parent reply other threads:[~2019-12-05 4:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 23:58 [TUHS] In Memoriam: John Lions Dave Horsfall
2019-12-05 4:16 ` Larry McVoy
2019-12-05 4:31 ` Greg 'groggy' Lehey [this message]
2019-12-08 10:56 ` [TUHS] Xinu (was: In Memoriam: John Lions) Naveen Nathan
2019-12-05 6:26 ` [TUHS] In Memoriam: John Lions Wesley Parish
2019-12-05 6:53 ` Thomas Paulsen
2019-12-05 14:16 ` A. P. Garcia
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=20191205043159.GA42246@eureka.lemis.com \
--to=grog@lemis.com \
--cc=lm@mcvoy.com \
--cc=tuhs@tuhs.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).