The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Will Senn <>
To: TUHS main list <>
Subject: [TUHS] v7 software
Date: Thu, 30 Dec 2021 16:10:55 -0600	[thread overview]
Message-ID: <> (raw)

[-- Attachment #1: Type: text/plain, Size: 1533 bytes --]

I'm tooling around doing my annual dive into operating systems ancient 
and not-so-ancient and I've gotten back around to v7 because it has a 
working f77 in baseline. The 3b2 has f77 as an installable package but 
it crashes and burns with read statements like: read *,var - in both 
sysvr2 and sysvr3. After consulting with the fortran expert, I'm gonna 
chalk it up to "man there's a lot of backstory to these seemingly simple 
issues" and just work with v7... in full disclosure f77 also seems to 
work fine on 211bsd, but that's too new for today's dive :).

Anyhow, I ran through my install notes from back in 2017 and did a few 
updates on them to update urls (would everyone just go ahead and move to 
https already?), fix some clunky examples, fix some typos, and update to 
a more recent host environment (although some would argue that Mojave is 
out of date - just give me a drop in replacement for Adobe Acrobat Pro X 
(a 32 bit app) that doesn't phone home every 5 minutes and I'll move to 
Monterey). Version 1.7 of the doc is posted on the blog:

Anyway, now I'm ready to add stuff to my shiny new v7 instance and 
document the additions. So, on to the question of the hour... I did some 
looking around and couldn't easily locate any v7 software archives for 
additional software that will run on v7 (not the distros, which are 
adequately hosted in the Unix Archive). Stuff like pascal, fortran iv, 
fortran 90, basic, lisp and the ilk. Do y'all know of any good caches?



[-- Attachment #2: Type: text/html, Size: 1989 bytes --]

             reply	other threads:[~2021-12-30 22:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-30 22:10 Will Senn [this message]
2021-12-31  1:21 ` Clem Cole
2021-12-31  3:05 Douglas McIlroy

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).