From: segaloco via TUHS <email@example.com>
To: The Eunuchs Hysterical Society <firstname.lastname@example.org>
Subject: [TUHS] 3B20S UNIX User's Manual Release 4.1 Scans Thread
Date: Fri, 16 Dec 2022 06:09:43 +0000 [thread overview]
Message-ID: <sEWSgDtf_A1ay827zlkTFsZNBcteijPjv9FJCuo5q2ZJXBWPcoeFmWoaCPUGkB6qCcvPng7IIlJwjW_kjWl43eBSKVO8leUQmwA9-Nyub9Yemail@example.com> (raw)
Good evening folks. I'm starting a new thread to pass along info as I scan materials from the 3B20S manual that I picked up. I figured it'd be easier to trickle out the bits folks ask me for first and then continue to scan the rest, that way anyone looking to sink their teeth into something specific can be sated first.
With that, the first scan (and frankly one of my favorite things about this manual) is the cover itself: https://commons.wikimedia.org/wiki/File:UNIX4.1UsersManualCover.png
Someone had mentioned the idea of making this into a poster and I gotta say, I'd gladly put one up. The image definitely would need some cleanup for that, I just scanned it like it came, haven't tried to clean up any of the wear of time yet. Sadly, the back cover isn't emblazoned with a big Bell logo like the 3.0 and 5.0 (Bell variant) manuals, so scanning that would be a boring white piece of cardstock.
Anywho, the next round which may come later this evening or sometime this weekend is going to be various *ROFF-related documents, so documents like troff(1), mm(5), etc.
- Matt G.
next reply other threads:[~2022-12-16 6:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 6:09 segaloco via TUHS [this message]
2022-12-21 22:17 ` [TUHS] Re: General Document Scans Thread (Was 3B20 Manual Scans) segaloco via TUHS
2022-12-22 0:01 ` segaloco via TUHS
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 \
* 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).