From: Clem Cole <clemc@ccc.com>
To: KenUnix <ken.unix.guy@gmail.com>
Cc: UNIX TUHS Group <tuhs@tuhs.org>
Subject: [TUHS] Re: Unix V7 Questions booting and date/time
Date: Sun, 19 Feb 2023 19:36:59 -0500 [thread overview]
Message-ID: <CAC20D2PqdYQ9S5+FzGfDyfExL8K7TEMnywSPoOb-Rx=bDNnA-w@mail.gmail.com> (raw)
In-Reply-To: <CAJXSPs8Zv3Zgm_6dj53C3RpXyJqtGpTvWM0GbuYVZ=3wHKAY3A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1305 bytes --]
On Sun, Feb 19, 2023 at 7:01 PM KenUnix <ken.unix.guy@gmail.com> wrote:
> Was an upgrade for ethernet TCP/IP for Unix V7 ever
> done when running under SIMH?
>
Yes, the BSD 2.9/10/11 stream include the UCB Networking stack - it runs
just fine on SIMH. In fact one Oscar's PiDP-11 [which used simh for the
simulator] its one of the systems that is automatically loaded.
>
> Was an upgrade ever done for Unix V7 when running
> under SIMH to read and set the date/time?
>
Where would you read the clock? SIMH emulates real HW - V7 was distributed
for DEC HW through 1979 on the 11 and DEC had nothing.
That said, could you create something sure - I bet you could. Maybe the
easiest way would be to use a virtual DL/DC/DZ/DH serial port and have V7
read the clock from a 'serial line.' when it boots. Then set up a process
on the SIMH Host system to source the data that V7 read.
That said, you probably could rewrite what you are starting in your example
to SIMH's expect/send command system to do something for you - but I'd have
to think about it.
FWIW: all those deposit commands should be unnecessary. Just make sure you
have a proper boot block on the disk, as dmr tells you in the 'setting up
Unix' document in /usr/doc and SIMH can boot from the controllers.
ᐧ
[-- Attachment #2: Type: text/html, Size: 2894 bytes --]
prev parent reply other threads:[~2023-02-20 0:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 0:01 [TUHS] " KenUnix
2023-02-20 0:36 ` Clem Cole [this message]
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='CAC20D2PqdYQ9S5+FzGfDyfExL8K7TEMnywSPoOb-Rx=bDNnA-w@mail.gmail.com' \
--to=clemc@ccc.com \
--cc=ken.unix.guy@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).