From: "Erik E. Fair" <fair-tuhs@netbsd.org>
To: Pat Barron <patbarron@acm.org>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] Paper discussing Unix boot process?
Date: Wed, 10 Apr 2019 19:26:30 -0700 [thread overview]
Message-ID: <10149.1554949590@cesium.clock.org> (raw)
In-Reply-To: <alpine.LFD.2.21.1904102046190.2402@booboo.lectroid.com>
Pat,
I still know a few people from the 36-bit world so I could put you in touch, but if you really want people to understand primitives, you might want to start with a simpler model, e.g., 16-bit minicomputers like the DEC PDP-11 (smaller models), the DG Nova, perhaps the original mc68000 (no MMU or FPU on-chip in that).
Once you add MMUs to the picture, life gets a lot more complicated, and I'm pretty sure the typical applications programmer doesn't really need to know that class of details, but going for PDP-10 (more "mainframe-ish" system) is going to take them there.
Erik
next prev parent reply other threads:[~2019-04-11 2:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 1:06 Pat Barron
2019-04-11 1:27 ` Charles Anthony
2019-04-11 2:26 ` Erik E. Fair [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-04-17 5:35 Paul Ruizendaal
2019-04-17 18:26 ` Warner Losh
2019-04-16 12:52 Noel Chiappa
2019-04-13 18:35 Noel Chiappa
2019-04-10 18:02 Pat Barron
2019-04-10 18:14 ` Erik E. Fair
2019-04-10 18:28 ` Clem Cole
2019-04-10 19:05 ` Bakul Shah
2019-04-10 22:24 ` Clem Cole
2019-04-10 22:53 ` Warren Toomey
2019-04-11 1:45 ` Greg 'groggy' Lehey
2019-04-10 23:19 ` Bakul Shah
2019-04-11 4:52 ` Fabio Scotoni
2019-04-11 13:48 ` Clem Cole
2019-04-11 14:54 ` Dan Cross
2019-04-11 15:36 ` Clem Cole
2019-06-26 2:28 ` Peter Jeremy
2019-06-26 7:57 ` Bakul Shah
2019-04-10 16:51 Pat Barron
2019-04-10 17:20 ` Erik E. Fair
2019-04-10 17:57 ` Dan Cross
2019-04-19 22:31 ` Chris Hanson
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=10149.1554949590@cesium.clock.org \
--to=fair-tuhs@netbsd.org \
--cc=patbarron@acm.org \
--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).