From: Arrigo Triulzi via TUHS <tuhs@tuhs.org>
To: Rudi Blom <rudi.j.blom@gmail.com>
Cc: tuhs@tuhs.org, Joseph Holsten <joseph@josephholsten.com>
Subject: [TUHS] Re: OSF/1.0 Sources
Date: Thu, 16 Mar 2023 07:15:37 +0100 [thread overview]
Message-ID: <02FF393E-4CF6-4FCF-B067-214D2F774D41@alchemistowl.org> (raw)
In-Reply-To: <CAMYpm86-q1_JQX_TF6_rza3fHO+ttzmb2MJ_oWL_guBD94MW=A@mail.gmail.com>
On 16 Mar 2023, at 04:28, Rudi Blom <rudi.j.blom@gmail.com> wrote:
> >Speaking of, there’s also the OSF/1.0 source from the same uploader:
> > https://archive.org/details/SapphireDensetsu_gmail_OSF1
> >--
> >~j
>
> Being somewhat of a collector I also have a Osf1-2.0-Src Tar.zip :-)
Out of curiosity: are the sources for “mx", the binary translator from Ultrix to OSF/1 binaries, included? I have fond memories of mx’ing ghostscript from Ultrix to OSF/1 to get it to run under OSF/1 T1.0 - not only did it work but it was the only way to get ghostscript running (for TeX to PS, of course) for quite some time.
Arrigo
next prev parent reply other threads:[~2023-03-16 6:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 3:28 Rudi Blom
2023-03-16 6:15 ` Arrigo Triulzi via TUHS [this message]
2023-03-16 6:29 ` Rudi Blom
2023-03-16 7:35 ` Arrigo Triulzi via TUHS
2023-03-16 9:25 ` Rudi Blom
2023-03-16 12:15 ` Arrigo Triulzi via TUHS
2023-03-16 14:35 ` Rudi Blom
2023-03-16 15:59 ` Arrigo Triulzi via TUHS
2023-03-17 9:38 ` Rudi Blom
-- strict thread matches above, loose matches on Subject: below --
2023-03-15 11:59 [TUHS] Re: UNIX System V Release 2.2 gdts Vax-780 Noel Chiappa
2023-03-15 21:03 ` Warren Toomey via TUHS
2023-03-15 23:56 ` [TUHS] Re: OSF/1.0 Sources Joseph Holsten
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=02FF393E-4CF6-4FCF-B067-214D2F774D41@alchemistowl.org \
--to=tuhs@tuhs.org \
--cc=arrigo@alchemistowl.org \
--cc=joseph@josephholsten.com \
--cc=rudi.j.blom@gmail.com \
/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).