From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: coff@tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: [COFF] Re: Terminology query - 'system process'?
Date: Wed, 20 Dec 2023 14:31:41 -0500 (EST) [thread overview]
Message-ID: <20231220193141.DC1C918C092@mercury.lcs.mit.edu> (raw)
> From: Derek Fawcus
> How early does that have to be? MP/M-1.0 (1979 spec) mentions this, as
> "Resident System Processes" ... It was a banked switching, multiuser,
> multitasking system for a Z80/8080.
Anything with a microprocessor is, by definition, late! :-)
I'm impressed, in retrospect, with how quickly the world went from proceesors
built with transistors, through proceesors built out discrete ICs, to
microprocessors. To give an example; the first DEC machine with an IC
processor was the -11/20, in 1970 (the KI10 was 1972); starting with the
LSI-11, in 1975, DEC started using microprocessors; the last PDP-11 with a
CPU made out of of discrete ICs was the -11/44, in 1979. All -11's produced
after that used microprocessors.
So just 10 years... Wow.
Noel
next reply other threads:[~2023-12-20 19:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 19:31 Noel Chiappa [this message]
2023-12-20 20:29 ` Paul Winalski
2023-12-31 3:51 ` steve jenkin
-- strict thread matches above, loose matches on Subject: below --
2023-12-20 20:35 Noel Chiappa
2023-12-14 23:29 Noel Chiappa
2023-12-14 23:54 ` Larry McVoy
2023-12-15 1:15 ` Bakul Shah
2023-12-15 17:51 ` Paul Winalski
2023-12-15 18:08 ` Warner Losh
2023-12-16 2:04 ` Greg 'groggy' Lehey
2023-12-16 19:21 ` Paul Winalski
2023-12-16 19:44 ` Paul Winalski
2023-12-15 13:43 ` Dan Cross
2023-12-19 13:54 ` Derek Fawcus via COFF
2023-12-14 21:48 [COFF] " Noel Chiappa
2023-12-14 22:06 ` [COFF] " Bakul Shah
2023-12-14 22:12 ` Warner Losh
2023-12-14 22:09 ` Clem Cole
2023-12-15 14:20 ` Dan Cross
2023-12-15 16:25 ` Warner Losh
2023-12-15 17:13 ` Bakul Shah
2023-12-15 6:24 ` Lars Brinkhoff
2023-12-15 18:30 ` Stuff Received
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=20231220193141.DC1C918C092@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.edu \
--cc=coff@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).