The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.com>
To: "Greg 'groggy' Lehey" <grog@lemis.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>,
	Doug McIlroy <doug@cs.dartmouth.edu>
Subject: Re: [TUHS] First book on Unix for general readership
Date: Mon, 13 Apr 2020 23:38:00 -0600	[thread overview]
Message-ID: <CANCZdfqZMDyxSf+VJ+ZqtA=t27PqYzF6KkXWXrEU0cmQX0zE4A@mail.gmail.com> (raw)
In-Reply-To: <20200414053024.GA67339@eureka.lemis.com>

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

On Mon, Apr 13, 2020, 11:31 PM Greg 'groggy' Lehey <grog@lemis.com> wrote:

> On Monday, 13 April 2020 at 22:13:17 -0400, Doug McIlroy wrote:
> >
> > Those were the only two that were published as trade books. I still use
> > the 10th Ed regularly. The 7th Ed was a debacle. The publisher didn't
> > bother to send us galleys because they had printed straight from troff.
> > It turned out they did not have the full troff character set, and put
> > an @ sign in place of each missing character. The whole print run was
> > done before we saw a copy. Not knowing whether they ever fixed it, I'd
> > be interested to hear whether or not the botch made it to bookstores.
>
> OK, I've dug out my copies.  Two volumes, published by CBS College
> publishing, aka Holt, Rinehart and Winston in 1982, both titled "UNIX
> Programmer's Manual".  Volume 1 (ISBN 0-03-061742-1) was the man
> pages, and volume 2 (ISBN 0-03-061743-X) was the supplementary docs,
> starting with “7th Edition UNIX — Summary†, dated September 6, 1978.
> They have perforated, 3-hole punched pages, clearly intended to be
> torn out and put into a three-ring binder.
>
> I've skimmed through both of them, and I can't find any obvious
> typesetting errors.  "Typesetting Mathematics" shows some quite
> complicated equations.  And in the quick reference in volume 1, all
> the troff special characters seem right, even up to less common
> characters such as \(bs.  Is there anything specific that I should
> look for?  Scans available if they would help.
>

Mine are like that too. Maybe it was just wrong for the first printing?

Warner

Greg
> --
> Sent from my desktop computer.
> Finger grog@lemis.com for PGP public key.
> See complete headers for address and phone numbers.
> This message is digitally signed.  If your Microsoft mail program
> reports problems, please read http://lemis.com/broken-MUA
>

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

  reply	other threads:[~2020-04-14  5:38 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-14  2:13 Doug McIlroy
2020-04-14  5:30 ` Greg 'groggy' Lehey
2020-04-14  5:38   ` Warner Losh [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-04-14 15:10 Doug McIlroy
2020-04-04 22:41 Doug McIlroy
2020-04-04 15:05 markus schnalke
2020-04-04 15:48 ` Nemo Nusquam
2020-04-14 15:27   ` Steve Mynott
2020-04-14 20:32     ` Warner Losh
2020-04-14 22:03       ` Warner Losh
2020-04-04 16:12 ` Michael Kjörling
2020-04-04 16:45   ` markus schnalke
2020-04-05 23:57     ` Ronald Natalie
2020-04-06  0:08       ` Larry McVoy
2020-04-06  0:27         ` Clem Cole
2020-04-06  0:46           ` Michael Usher via TUHS
2020-04-06  1:41             ` Clem Cole
2020-04-06  1:46               ` Michael Usher via TUHS
2020-04-06 14:51             ` ron
2020-04-08 22:23               ` Greg A. Woods
2020-04-06  0:17       ` Dave Horsfall
2020-04-06 14:54         ` ron
2020-04-06 14:54         ` ron
2020-04-07 10:42       ` Derek Fawcus
2020-04-08 22:16         ` Greg A. Woods
2020-04-04 17:32 ` Warner Losh

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='CANCZdfqZMDyxSf+VJ+ZqtA=t27PqYzF6KkXWXrEU0cmQX0zE4A@mail.gmail.com' \
    --to=imp@bsdimp.com \
    --cc=doug@cs.dartmouth.edu \
    --cc=grog@lemis.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).