The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
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 21:35:29 +0700	[thread overview]
Message-ID: <CAMYpm84Qz=3t6v-TmPJxTMDc_XJQn-K4qzdLyOaaY7aqu1Hc_A@mail.gmail.com> (raw)
In-Reply-To: <B75F5B4B-DA7C-46F6-BCA1-DA63A629E0A4@alchemistowl.org>

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

A misunderstanding, I know all that. It's just that I expected to see a
INSTCTRL file or instctrl directory with such file.That's what I'd consider
normal in DU 4.0 and Tru64 5.0 onwards.

I have that OSF/1 archive on 1.0 and 2.0 a few years already.(found
somewhere) but till now didn't look at it. I've got a DS20E with DU 4.0g.
When I get a change I might install some parts.

Take care,
uncle rubl

On Thu, 16 Mar 2023 at 19:15, Arrigo Triulzi <arrigo@alchemistowl.org>
wrote:

> On 16 Mar 2023, at 10:25, Rudi Blom <rudi.j.blom@gmail.com> wrote:
> > BTW what format do the OSC... 200 archives have so I can 'unpack' them
> easily?
>
> You install them using setld, as in:
>
> setld -l OSC…
>
> (you can have multiple sets in one setld command)
>
> To see what is installed:
>
> setld -i
>
> I assume you don’t need a license for it, otherwise you would have a
> so-called PAK file and you’d load it with:
>
> lmf register < pakfile
> lmf load OSF…
>
> the “pakfile” could be (and was, in academia) a huge list of licenses
> which you’d load in one go.
>
> Arrigo
>
>

-- 
The more I learn the better I understand I know nothing.

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

  reply	other threads:[~2023-03-16 14:35 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
2023-03-16 12:15         ` Arrigo Triulzi via TUHS
2023-03-16 14:35           ` Rudi Blom [this message]
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='CAMYpm84Qz=3t6v-TmPJxTMDc_XJQn-K4qzdLyOaaY7aqu1Hc_A@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).