From: Lars Brinkhoff <lars@nocrew.org>
To: Dan Cross <crossd@gmail.com>
Cc: TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: Fwd: [multicians] Dennis Ritchie's 1993 Usenet posting "BTL Leaves Multics"
Date: Mon, 24 Jun 2024 15:10:07 +0000 [thread overview]
Message-ID: <7wfrt2cr74.fsf@junk.nocrew.org> (raw)
In-Reply-To: <CAEoi9W5RNVvGTPeHQFNHPO+dYZzqfmv31AGmyxigxEy=0HPMCA@mail.gmail.com> (Dan Cross's message of "Mon, 24 Jun 2024 10:46:14 -0400")
Dan Cross wrote:
> I can't resist asking about the nugget buried in here about Ken
> writing a small kernel for the 645. Is that in the archives anywhere?
As far as I understand, the code that is available is for the DPS-8M.
I have asked around for older code. I don't remember exactly, but
possibly 6180 era code might be around, but but unfortunately not 645.
next prev parent reply other threads:[~2024-06-24 15:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Fk0R.1719239897507789113.nLxU@groups.io>
2024-06-24 14:46 ` [TUHS] " Dan Cross
2024-06-24 15:10 ` Lars Brinkhoff [this message]
2024-06-24 18:17 ` [TUHS] " Dan Cross
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=7wfrt2cr74.fsf@junk.nocrew.org \
--to=lars@nocrew.org \
--cc=crossd@gmail.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).