From: Rudi Blom <rudi.j.blom@gmail.com>
To: Arrigo Triulzi <arrigo@alchemistowl.org>
Cc: segaloco via TUHS <tuhs@tuhs.org>,
Joseph Holsten <joseph@josephholsten.com>
Subject: [TUHS] Re: OSF/1.0 Sources
Date: Thu, 16 Mar 2023 16:25:46 +0700 [thread overview]
Message-ID: <CAMYpm867TSpM71jeuPgi2inT4-aykmxgLhsBCn0s1W-FU_M+vA@mail.gmail.com> (raw)
In-Reply-To: <A9691910-C2F1-48CA-BDF8-90E13143F815@alchemistowl.org>
[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]
on osf1-1.0 I see a OSCBISL200 which seems to include mx and mxr. I don't
know anything about it but found this chapter online with at the very end:
"For more information on the mx translator and the mxr run-time
environment, see the DECmigrate for DEC OSF/1 V1.2: Translating Executables
manual."
http://www2.phys.canterbury.ac.nz/dept/docs/manuals/unix/DEC_4.0e_Docs/HTML/APS3EETE/CHVRVWXX.HTM
BTW what format do the OSC... 200 archives have so I can 'unpack' them
easily?
On Thu, 16 Mar 2023 at 14:35, Arrigo Triulzi <arrigo@alchemistowl.org>
wrote:
> > On 16 Mar 2023, at 07:29, Rudi Blom <rudi.j.blom@gmail.com> wrote:
> >
> > appended osf1-1.lst, osf1-2.lst
>
> Ah, those are the original installation packages - I have them, by pure
> accident, for Tru64 Unix 4.0D but I am definitely not uploading those
> anywhere…
>
> No idea where ‘mx’ would be in them but it must be there as it was shipped
> without any special additional PAKs needed.
>
> Arrigo
>
>
>
--
The more I learn the better I understand I know nothing.
[-- Attachment #2: Type: text/html, Size: 2562 bytes --]
next prev parent reply other threads:[~2023-03-16 9:26 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
2023-03-16 6:29 ` Rudi Blom
2023-03-16 7:35 ` Arrigo Triulzi via TUHS
2023-03-16 9:25 ` Rudi Blom [this message]
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=CAMYpm867TSpM71jeuPgi2inT4-aykmxgLhsBCn0s1W-FU_M+vA@mail.gmail.com \
--to=rudi.j.blom@gmail.com \
--cc=arrigo@alchemistowl.org \
--cc=joseph@josephholsten.com \
--cc=tuhs@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).