From: Will Senn <will.senn@gmail.com>
To: Brad Spencer <brad@anduin.eldar.org>, Clem Cole <clemc@ccc.com>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] BSD 4.1, 4.1x, Quasijarus, and 4.3x
Date: Tue, 1 Feb 2022 19:19:24 -0600 [thread overview]
Message-ID: <328d0bc1-b4b4-4693-ea2c-f7780410dbeb@gmail.com> (raw)
In-Reply-To: <xonv8xyw10w.fsf@anduin.eldar.org>
On 2/1/22 6:43 PM, Brad Spencer wrote:
> Clem Cole <clemc@ccc.com> writes:
>
> [snip]
>
>>> Well, no. Both OpenBSD and NetBSD ported back to the VAX, but the OpenBSD
>>> effort has ended due to lack of hardware and interest. It appears that
>>> NetBSD is still being actively developed on the VAX, however, so it's
>>> possible to get a "modern" 4.4BSD derived system on that architecture.
>>>
>> Right - either current NetBSD or the Ultrix 4.5 is what I would do. If
>> NetBSD will run the Ultrix layered products, that would be the system with
>> the most; but I'm not sure if that will work. Ultrix for instance
>> supports DEC (VMS) FTN - which I know you (Will) have been messing with.
>> That is the best (most complete) FTN for Vaxen. I believe there is Ada,
>> PL/1 and maybe even Basic2 and Cobol/RPG [I think most of not all of the
>> VMS languages for the VAX were released on Ultrix but frankly, I don't
>> remember].
> [snip]
>
> NetBSD has a compat_ultrix that can be enabled for NetBSD/vax (and pmax
> / mips) that might allow some of those products to work. The man page
> for it does not mention any of that specifically and does say that there
> are a few limits to it.
>
> https://man.netbsd.org/compat_ultrix.8
>
I tried an install of netbsd latest on simh microvax a few weeks back
and it installed without error. It was slow to boot to login, but I'm
sure that's just the network being misconfigured somehow, I haven't had
time to troubleshoot - let's just call it pilot error.
next prev parent reply other threads:[~2022-02-02 1:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 21:34 Will Senn
2022-02-01 21:47 ` Larry McVoy
2022-02-01 22:04 ` Chet Ramey
2022-02-01 22:18 ` Dan Cross
2022-02-02 0:22 ` Clem Cole
2022-02-02 0:43 ` Brad Spencer
2022-02-02 1:19 ` Will Senn [this message]
2022-02-02 1:35 ` Will Senn
2022-02-05 23:57 ` Chris Hanson
2022-02-02 1:30 ` Will Senn
2022-02-01 23:40 ` George Michaelson
2022-02-01 23:54 ` Steve Nickolas
2022-02-02 0:38 ` Greg 'groggy' Lehey
2022-02-02 1:02 ` Seth Morabito
2022-02-02 10:28 ` Hans Rosenfeld
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=328d0bc1-b4b4-4693-ea2c-f7780410dbeb@gmail.com \
--to=will.senn@gmail.com \
--cc=brad@anduin.eldar.org \
--cc=clemc@ccc.com \
--cc=tuhs@minnie.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).