From: Ben Huntsman <ben@huntsmans.net>
To: Seth Morabito <web@loomcom.com>
Cc: UNIX Heritage Society <tuhs@tuhs.org>
Subject: [TUHS] Re: SVR3 or SVR4 kernel sources for 3B2/700
Date: Sat, 30 Sep 2023 05:38:15 +0000 [thread overview]
Message-ID: <9DB73B8C-CCE2-4321-B875-240CCCAC0271@huntsmans.net> (raw)
In-Reply-To: <337d1f26-81a4-4c8e-9c30-030188ace3e2@app.fastmail.com>
Speaking of the 3B2, has anyone ever seen DMERT out there or had a chance to run it on their 3B2?
Sent from my iPhone
> On Sep 29, 2023, at 4:58 PM, Seth Morabito <web@loomcom.com> wrote:
>
> It's been a while since I asked, and I would be extraordinarily surprised if the situation had changed, but I thought I might try my luck one more time...
>
> The 3B2 is a dreadful computer, but nevertheless I find myself compelled to try to make the SIMH 3B2 emulation more accurate. The emulation for the 3B2/400 is probably as accurate as it's ever going to be, but the 3B2/700 has very clear and known bugs. One of the things holding back fixing those bugs is documentation in the form of source code. I have the leaked kernel source code for the 3B2/400 ("Version 2") architecture, but I have never seen any kernel source code that targets the 3B2/700 or /1000 ("Version 3") architecture. All I have are the system header files from /usr/include/sys, nothing more.
>
> If by some chance you have a /usr/src/uts tree for the 3B2/600, /700, or /1000, I would love to see it. It would refer to the system board using the code name "FALCON", probably with a lot of #ifdef's (at least the system headers do)
>
> -Seth
> --
> Seth Morabito * Poulsbo, WA * https://loomcom.com/
next prev parent reply other threads:[~2023-09-30 5:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 23:57 [TUHS] " Seth Morabito
2023-09-30 5:38 ` Ben Huntsman [this message]
2023-09-30 6:35 ` [TUHS] " Marc Donner
2023-09-30 13:41 ` Seth Morabito
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=9DB73B8C-CCE2-4321-B875-240CCCAC0271@huntsmans.net \
--to=ben@huntsmans.net \
--cc=tuhs@tuhs.org \
--cc=web@loomcom.com \
/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).