The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Chris Hanson <cmhanson@eschatologist.net>
To: Clem Cole <clemc@ccc.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] BSD 4.1, 4.1x, Quasijarus, and 4.3x
Date: Sat, 5 Feb 2022 15:57:41 -0800	[thread overview]
Message-ID: <E664A705-6CD1-478D-890B-897C75C916EB@eschatologist.net> (raw)
In-Reply-To: <CAC20D2OoK1xJXZZUN0jgw42J73kMurYHBDwXXFR_Ux8bjTu-KQ@mail.gmail.com>

On Feb 1, 2022, at 4:22 PM, Clem Cole <clemc@ccc.com> wrote:
> 
> 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].

I don’t know if NetBSD has Ultrix binary compatibility on VAX, but it does on MIPS—so much so that a few years back, someone accidentally pointed their NetBSD boot at the wrong partition on their DECstation and Ultrix booted right up using the NetBSD kernel!

  — Chris


  parent reply	other threads:[~2022-02-06  0:14 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
2022-02-05 23:57     ` Chris Hanson [this message]
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=E664A705-6CD1-478D-890B-897C75C916EB@eschatologist.net \
    --to=cmhanson@eschatologist.net \
    --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).