From: Mary Ann Horton <mah@mhorton.net>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Origins and life of the pg pager
Date: Mon, 15 Jun 2020 13:50:17 -0700 [thread overview]
Message-ID: <cd6a1bc9-0379-38d5-77b0-9ec041d12870@mhorton.net> (raw)
In-Reply-To: <m1jkva8-0036tPC@more.local>
[-- Attachment #1: Type: text/plain, Size: 1337 bytes --]
Fascinating.
My UNIX/32V manual, from Berkeley, bears the date "December, 1978" on
the cover. I've hand-written "Unix/32V" on it.
The 32V archive on minnie.tuhs.org bears the date "February, 1979" in
/usr/man/man0/title.
The text of the cover sheets is somewhat different. My copy is "UNIX
PROGRAMMER'S MANUAL / Seventh Edition / VAX-11 Version" compared to TUHS
"UNIX/32V PROGRAMMER'S MANUAL / Version 1.0".
I also note there is no pg.c in the 3BSD distribution.
It seems likely that what Berkeley based 3BSD on was a prerelease of
UNIX/32V, prior to the "official" 1.0 version, and what while pg.c was
written in November, it didn't make it onto the tape we got at Berkeley.
Imagine if pg.c had been on that tape! more might never have been
written. (Of course, we all read TFM, so we might have missed the source
code all by its lonesome.)
Mary Ann
On 6/15/20 1:19 PM, Greg A. Woods wrote:
>> My 32V manual does not include pg.
>>
>> We got UNIX/32V at Berkeley shortly after we got our Vax and decided
>> we didn't like VMS. Early 1979, I think. If it had had pg, Eric
>> probably wouldn't have written more.
>>
>> So if there was a pg in 32V, it must have been added later.
> There is a /usr/src/cmd/pg.c and /usr/bin/pg binary in Unix-32V, but no
> manual page. The pg.c I've seen has the date Nov. 5, 1978.
[-- Attachment #2: Type: text/html, Size: 1906 bytes --]
next prev parent reply other threads:[~2020-06-15 20:50 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-14 22:52 [TUHS] Fwd: " Warren Toomey
2020-06-14 23:37 ` Mary Ann Horton
2020-06-14 23:52 ` [TUHS] " David Barto
2020-06-15 0:06 ` George Michaelson
2020-06-15 0:31 ` Alan D. Salewski
2020-06-15 0:35 ` Alan D. Salewski
2020-06-15 1:38 ` Warner Losh
2020-06-15 1:47 ` Larry McVoy
2020-06-15 2:38 ` Alec Muffett
2020-06-15 2:46 ` Alec Muffett
2020-06-15 2:26 ` Charles H. Sauer
2020-06-15 14:03 ` Mary Ann Horton
2020-06-15 20:19 ` Greg A. Woods
2020-06-15 20:50 ` Mary Ann Horton [this message]
2020-06-15 0:32 ` [TUHS] Fwd: " Nemo Nusquam
2020-06-15 5:41 ` Lars Brinkhoff
2020-06-15 13:56 ` Clem Cole
2020-06-15 14:15 ` Mary Ann Horton
2020-06-15 14:56 ` Clem Cole
2020-06-15 15:04 ` Richard Salz
2020-06-15 16:14 ` Clem Cole
2020-06-15 15:45 ` Lars Brinkhoff
2020-06-15 19:08 ` Lars Brinkhoff
2020-06-21 18:49 ` Michael Siegel
2020-06-22 0:35 ` Greg A. Woods
2020-06-22 16:24 ` Derek Fawcus
2020-06-22 21:33 ` Rob Pike
2020-06-22 21:58 ` Kurt H Maier
2020-06-22 21:59 ` [TUHS] " Bakul Shah
2020-06-22 22:43 ` Steffen Nurpmeso
2020-06-25 1:50 ` Theodore Y. Ts'o
2020-06-25 21:31 ` Steffen Nurpmeso
2020-07-05 1:34 ` Dave Horsfall
2020-06-18 12:49 ` [TUHS] Fwd: " Michael Siegel
2020-06-15 2:26 [TUHS] " Doug McIlroy
2020-06-15 2:41 ` Bakul Shah
2020-06-15 2:55 ` Larry McVoy
2020-06-15 4:26 ` Rob Pike
2020-06-15 4:27 ` Bakul Shah
2020-06-15 4:38 ` George Michaelson
2020-06-15 7:40 ` Ed Carp
2020-06-15 8:17 ` Rob Pike
2020-06-15 7:12 ` Thomas Paulsen
2020-06-15 20:25 Norman Wilson
2020-06-15 21:36 ` Rob Pike
2020-06-15 22:55 ` Henry Bent
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=cd6a1bc9-0379-38d5-77b0-9ec041d12870@mhorton.net \
--to=mah@mhorton.net \
--cc=tuhs@minnie.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).