From: segaloco via TUHS <tuhs@tuhs.org>
To: Douglas McIlroy <douglas.mcilroy@dartmouth.edu>
Cc: TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] Re: UNIX Manual Cover Art Origins?
Date: Thu, 20 Apr 2023 05:24:48 +0000 [thread overview]
Message-ID: <ygzBk_LDCjUa9skXKAzn_-z-m14veoNpeg13mcBduMGt9FYB4_XiPVnWwmNWMLKoNcqo5s-JF-TzjKGPwaqJLpd10xSZ3001JxngFq4Jmyo=@protonmail.com> (raw)
In-Reply-To: <CAKH6PiVtay6jFwRJcNEJDKN6cZ=DQpo8icYcVFxHaFt54zaB3g@mail.gmail.com>
Thanks for the info Doug! That certainly gave me somewhere to start. After stepping through the circa 1983 BTL SVR2 manual, the only Whippany-specific pages I found related to a "DI-3000" printing system from Precision Visuals. The cover of the referenced manual is on Google Books, but I can't seem to find a scanned copy. Whether it would've been related, couldn't say. Much of what I can find on DI-3000 is advertising materials and articles about specific applications, but no general user material.
I'm glad to have the V7 and V10 editions on hand, but I didn't know V8 and V9 also saw print release, although just now searching I did find what appeared to be a comb-bound print of V8, but couldn't find a second source for the image (https://media.licdn.com/dms/image/C5112AQHO14UEpqFPPQ/article-cover_image-shrink_600_2000/0/1520220760198?e=2147483647&v=beta&t=Rt8IyYB6GgD5RIBjBAjwP8hgcxcuKML0BwIxgzhLW0M).
Anywho, I'll add DI-3000 to my list of things to comb for history of every now and then, maybe something cool will pop up.
- Matt G.
------- Original Message -------
On Wednesday, April 19th, 2023 at 1:10 PM, Douglas McIlroy <douglas.mcilroy@dartmouth.edu> wrote:
> > Does anyone know of any of the tools, formats, practices, etc. used in producing the actual graphical covers of various published UNIX manuals?
>
>
> The Bell Labs publication department at Whippany did the physical
> design for the bound versions of the Research Unix manual--from v7 as
> a trade brook through v10, also a trade book.. They did the cover
> designs for v8-v10 in house. I am not sure whether they did the v7
> cover, farmed it out, or left it up to Holt Rinehart. Whippany handled
> the printing of v8 and v9. Saunders College Publishing did it for v10.
>
> Unfortunately, I do not remember whom I dealt with in Whippany, and my
> records of the interactions are long gone.
>
> Doug
next prev parent reply other threads:[~2023-04-20 5:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 20:10 [TUHS] " Douglas McIlroy
2023-04-20 5:24 ` segaloco via TUHS [this message]
2023-04-20 10:38 ` [TUHS] " arnold
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='ygzBk_LDCjUa9skXKAzn_-z-m14veoNpeg13mcBduMGt9FYB4_XiPVnWwmNWMLKoNcqo5s-JF-TzjKGPwaqJLpd10xSZ3001JxngFq4Jmyo=@protonmail.com' \
--to=tuhs@tuhs.org \
--cc=douglas.mcilroy@dartmouth.edu \
--cc=segaloco@protonmail.com \
/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).