The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Dan Cross <crossd@gmail.com>
To: Clem Cole <clemc@ccc.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Paper discussing Unix boot process?
Date: Thu, 11 Apr 2019 10:54:57 -0400	[thread overview]
Message-ID: <CAEoi9W54vVH2E1UiUEV=ntydTxk=3D-zT081xPQse7pK-TFPSA@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2OWGLa4hHTKa=zYTDnDLGwKzoGPxQeU8gDDGBysTmBQ0w@mail.gmail.com>

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

On Thu, Apr 11, 2019 at 9:49 AM Clem Cole <clemc@ccc.com> wrote:

> As my very fragile nth edition photocopy shows, the original Western
> Electric copies are not troff'ed and run through a typesetter because John
> (like most of us at the time) did not have access to one (and Tom Ferrin
> had not yet done the vcat(1) hack at UCSF).  Lions used standard nroff
> output - (in this case, originally to 132 column line printer paper I
> believe).
>

Indeed. Even the mid-90's Peer-to-Peer press reprinting appears to be,
roughly, a facsimile of line printer output. I say 'roughly' because there
is some prefatory material at the beginning that is properly typeset:
dedications, acknowledgements, etc, all written at the time of
(re)publication and similarly a set of "appreciations" at the end.

Interestingly, the title page appears to be approximately original and is
typeset. It also includes this little gem of a note: "COPY NO. 050B  NAME
PROPERTY OF BELL LABORATORIES, INC. COPY TO BE RETURNED TO: COMPUTING
INFORMATION SERVICE MH 2F-128 UNIX OPERATING SYSTEM SOURCE CODE VERSION 6"
(line breaks elided).

I don't think I've ever seen a copy of the original; I suspect the title
page was reset for the PP publication, though it is of course possible that
Lions could have prepared that specially: doing a "one-off" for a single
page, perhaps under contract with an actual publishing company or graphic
artist or something, would have been reasonable while the rest of the
booklet contents were taken from listings.


> [snip]
>
>
        - Dan C.

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

  reply	other threads:[~2019-04-11 14:56 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-10 18:02 Pat Barron
2019-04-10 18:14 ` Erik E. Fair
2019-04-10 18:28   ` Clem Cole
2019-04-10 19:05     ` Bakul Shah
2019-04-10 22:24       ` Clem Cole
2019-04-10 22:53         ` Warren Toomey
2019-04-11  1:45           ` Greg 'groggy' Lehey
2019-04-10 23:19         ` Bakul Shah
2019-04-11  4:52           ` Fabio Scotoni
2019-04-11 13:48             ` Clem Cole
2019-04-11 14:54               ` Dan Cross [this message]
2019-04-11 15:36                 ` Clem Cole
2019-06-26  2:28             ` Peter Jeremy
2019-06-26  7:57               ` Bakul Shah
  -- strict thread matches above, loose matches on Subject: below --
2019-04-17  5:35 Paul Ruizendaal
2019-04-17 18:26 ` Warner Losh
2019-04-16 12:52 Noel Chiappa
2019-04-13 18:35 Noel Chiappa
2019-04-11  1:06 Pat Barron
2019-04-11  1:27 ` Charles Anthony
2019-04-11  2:26 ` Erik E. Fair
2019-04-10 16:51 Pat Barron
2019-04-10 17:20 ` Erik E. Fair
2019-04-10 17:57 ` Dan Cross
2019-04-19 22:31 ` Chris Hanson

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='CAEoi9W54vVH2E1UiUEV=ntydTxk=3D-zT081xPQse7pK-TFPSA@mail.gmail.com' \
    --to=crossd@gmail.com \
    --cc=clemc@ccc.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).