The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: segaloco via TUHS <>
To: Phil Budne <>
Subject: [TUHS] Re: Early supported UNIX manual
Date: Sun, 07 Jan 2024 17:21:14 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Sunday, January 7th, 2024 at 7:27 AM, Phil Budne <> wrote:
> Not that I can tell you an easy name for what to call it!

I've just been referring to these as "PGs" for short, so USG PGII.  The MERT manual on the archive is visually similar to this one, as one would expect since it is based on PGIII.  Very very cool to see this finally, thanks Al!  One more down, I believe someone on list has confirmed ownership of a PGIII manual as well, but I'm not sure if the very first issue even had print manuals distributed.  Program Generic is a bit obscure given the earliness of it but my understanding is that it served both as the standard supported UNIX for computer users in the Bell System *and* as the standard base for UNIX-based projects that weren't butted right up against research (e.g. MERT.)  I've seen this "Generic" nomenclature used for other such things in Bell System literature, representing a "stock" version of some technology prior to differentiation into separate products.  It's actually used later in UNIX releases too, a 3B20S document refers to the UNIX Release as the time as "the latest Generic(sic)".  I believe this capitalization points to similar naming influences.

First thing I looked for but couldn't find is a reference to what macro package was used for these documents.  You can see the same style in both the PGII program description document and the MERT 0 manual.  I suspect there's some connection between this and the OSDD package but that's currently just an assumption based on this also looking somewhat BSP-ish in select code, date, etc presentation in the header.  The existence of the program description document leads me to believe there were other such secondary documents distinct from the Volume 2 documents, but this is just a hunch.  Either way, this'll certainly help my manual diffing efforts!

- Matt G.

  reply	other threads:[~2024-01-07 17:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-22 18:52 [TUHS] " Phil Budne
2022-12-22 19:51 ` [TUHS] " segaloco via TUHS
2022-12-22 21:44   ` Phil Budne
2022-12-22 21:55     ` segaloco via TUHS
2022-12-24  3:30     ` Jonathan Gray
2022-12-24  8:58       ` segaloco via TUHS
2022-12-24 10:30         ` Jonathan Gray
2022-12-23  8:47 ` [TUHS] Re: Book Scanning. (Was: Early supported UNIX manual) Ralph Corderoy
2024-01-07  7:03 ` [TUHS] Re: Early supported UNIX manual Jonathan Gray
2024-01-07 10:38   ` Al Kossow
2024-01-07 15:27     ` Phil Budne
2024-01-07 17:21       ` segaloco via TUHS [this message]
2022-12-23  2:26 Noel Chiappa
2022-12-23  4:32 ` Phil Budne
2022-12-23  7:52   ` arnold
2022-12-23  9:09   ` Jonathan Gray
2022-12-23 18:04     ` Phil Budne

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \ \

* 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).