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: Fri, 17 Mar 2023 16:38:57 +0700 [thread overview]
Message-ID: <CAMYpm877oizjjWWXa7Y6h2m1mbbfoJZRJ69TzxyJCKv3W5Z13g@mail.gmail.com> (raw)
In-Reply-To: <3C251334-5FE0-4F53-8C16-EC3238E31EF8@alchemistowl.org>
[-- Attachment #1: Type: text/plain, Size: 1251 bytes --]
Just a quick check shows
. my archive osf1src10 contains OSC* as tar files, osf1src20 contains
similar filenames but as gzipped tar files.
For osf1src10 untarring all gives a directory ./usr/opt with subdirectories
OSC200 and OSCX200.
A quick check on osf1src10 gives mxr, libmxr.so and mxr.1 but no source of
those.
For osf1src20 same result.
On osf1src10 the OSC* files have date 2003-11-03, on osf1src20 2004-11-06.
Unzipped, untarred the usr directory has size 370Mb. A quick check shows my
osf1src10 and osf1src20 contain the SAME software. Using "ls -lR" most
source files seem from 1994-03-02, but there are groups from 1993-01-26 as
well (e.g. termcap files).
That's all from me.
On Thu, 16 Mar 2023 at 22:59, Arrigo Triulzi <arrigo@alchemistowl.org>
wrote:
> On 16 Mar 2023, at 15:35, Rudi Blom <rudi.j.blom@gmail.com> wrote:
> > 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.
>
> Oh, my apologies. I thought it was a rather more basic question. I can
> have a look at my 4.0D sources and see how those are packaged.
>
> Arrigo
--
The more I learn the better I understand I know nothing.
[-- Attachment #2: Type: text/html, Size: 1869 bytes --]
next prev parent reply other threads:[~2023-03-17 9:39 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
2023-03-16 15:59 ` Arrigo Triulzi via TUHS
2023-03-17 9:38 ` Rudi Blom [this message]
-- 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=CAMYpm877oizjjWWXa7Y6h2m1mbbfoJZRJ69TzxyJCKv3W5Z13g@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).