From: Will Senn <will.senn@gmail.com>
To: The Unix Heritage Society mailing list <tuhs@tuhs.org>
Subject: Re: [TUHS] manpages in svr2
Date: Tue, 28 Dec 2021 16:19:02 -0600 [thread overview]
Message-ID: <b213d53c-4378-b19d-f0b3-ce1b0254147f@gmail.com> (raw)
In-Reply-To: <m1n2JuQ-003BOrC@more.local>
[-- Attachment #1: Type: text/plain, Size: 2856 bytes --]
Greg,
I got manpages! Thanks. I took the tarball, extracted the files, cpio'd
'em onto a tape cartridge image, pulled 'em off the cartridge onto
/usr2/manpages, installed the Documenter's Workbench and:
nroff -man echo.1
ECHO(1) UNIX System V ECHO(1)
NAME
echo - echo arguments
SYNOPSIS
echo [ arg ] ...
Yeeha.
Now to type in Stephen's version of man in shell script form :).
Thanks,
Will
On 12/28/21 3:21 PM, Greg A. Woods wrote:
> At Mon, 27 Dec 2021 09:11:20 -0800, "Seth Morabito"<web@loomcom.com> wrote:
> Subject: Re: [TUHS] manpages in svr2
>> I don't believe AT&T ever distributed manpages for the 3B2, but if I'm
>> wrong and someone has a link to a set, I would be very happy to
>> archive them! It's quite possible that at some point someone compiled
>> a set of manpages as a third-party package, but unfortunately so many
>> of the old 3B2 archives disappeared in the late 2000s before I (or
>> anyone else I know) had a chance to archive them completely.
> I definitely had man pages on my 3B2/400 with SysVr3 (and r3.2).
>
> They were pre-formatted (catman), not troff source though, IIRC.
>
> This was true for all of UNIX System V, at least from 2.0 on.
>
> There was a separate "source" distribution for the documentation, called
> the "Machine Readable Documentation", aka MRD. It contains source for
> all of the system documentation, not just the manual pages.
>
> The separation was necessary due to the separate licensing of the
> Documenter's Workbench. You couldn't format roff documents without it,
> not even with nroff, so source for the documentation would be useless to
> anyone who didn't also license DWB. (IIRC some Unix licensees kept
> their versions of V7 nroff working on their later SysV releases so that
> they could ship man page sources that would be usable, but using that
> ancient troff with modern printers was painful even with Chris Lewis'
> psroff.)
>
> The archive.org copy of SysVr2.0-NS32k contains source for DWB, MRD, as
> well as the system and commands:
>
> https://archive.org/download/ATTUNIXSystemVRelease4Version2/SysVr2.0_32000.tgz
>
> I don't know if it is legal or not, but it's been there for ages.
>
> IIRC somewhere there on archive.org there's also a SysVr2 for VAX too,
> complete with binaries and sources, and it has catman pages included.
>
> I do happen to have a copy of the MRD for SysVr3.2 for 3B2, but I don't
> think it is legal. I also had a legal binary license for DWB-2.0 for
> 3B2, but I don't think I have a copy of the media any more.
>
> --
> Greg A. Woods<gwoods@acm.org>
>
> Kelowna, BC +1 250 762-7675 RoboHack<woods@robohack.ca>
> Planix, Inc.<woods@planix.com> Avoncote Farms<woods@avoncote.ca>
[-- Attachment #2: Type: text/html, Size: 4102 bytes --]
next prev parent reply other threads:[~2021-12-28 22:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-27 16:05 Will Senn
2021-12-27 16:16 ` Clem Cole
2021-12-27 17:11 ` Seth Morabito
2021-12-28 21:21 ` Greg A. Woods
2021-12-28 22:19 ` Will Senn [this message]
2021-12-28 23:43 ` Seth Morabito
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=b213d53c-4378-b19d-f0b3-ce1b0254147f@gmail.com \
--to=will.senn@gmail.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).