From: Will Senn <will.senn@gmail.com>
To: Clem Cole <clemc@ccc.com>, Dan Cross <crossd@gmail.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] BSD 4.1, 4.1x, Quasijarus, and 4.3x
Date: Tue, 1 Feb 2022 19:35:27 -0600 [thread overview]
Message-ID: <716d5149-77bf-6149-1d81-b3a89250704a@gmail.com> (raw)
In-Reply-To: <CAC20D2OoK1xJXZZUN0jgw42J73kMurYHBDwXXFR_Ux8bjTu-KQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1614 bytes --]
On 2/1/22 6:22 PM, Clem Cole wrote:
> Dan/Will - I think we need the political way back machine ... below...
>
That's a lot of history. Thanks. Always with the money, I thought it was
strictly altruism that drove the pioneers :).
> Then again, if the idea is running BSD on a Vax, Ultrix 4.5 is even
> better, and has all the DEC languages and layered products.
Wow. I will dig into this. I like the layered stuff. I thought you had
to do RT11/RSTSE/TOPS/etc to have that. I had no idea it was available
on a *nix platform.
>
> 4. Is Quasijarus0c end of the line for VAX 4.xBSD? Why does
> tuhs only have Quasijarus0 and 0a, was there something wrong
> with 0b and 0c?
>
>
> 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].
Sweet. Off to hunt down Ultrix 4.5 :).
Will
[-- Attachment #2: Type: text/html, Size: 4044 bytes --]
next prev parent reply other threads:[~2022-02-02 1:35 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
2022-02-02 1:35 ` Will Senn [this message]
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=716d5149-77bf-6149-1d81-b3a89250704a@gmail.com \
--to=will.senn@gmail.com \
--cc=clemc@ccc.com \
--cc=crossd@gmail.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).