From: segaloco via TUHS <tuhs@tuhs.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Found and Purchased Unix 4.1 3B20S Manual
Date: Fri, 02 Dec 2022 05:04:24 +0000 [thread overview]
Message-ID: <AUvhAlVb0td6ugkWvO5gb3mvdLajlbR-jCP71fYT_IMajCGn7_wI9DsSizbV-HUKDk7lo5M7V2iE-XXNeFOYSdn6j9HSShrRP8pyxBQiePU=@protonmail.com> (raw)
Exciting development in the process of finding lost documentation, just sealed this one on eBay: https://www.ebay.com/itm/385266550881?mkcid=16&mkevt=1&mkrid=711-127632-2357-0&ssspo=abbj5srltbk&sssrc=2047675&ssuid=&widget_ver=artemis&media=COPY
After the link is a (now closed) auction for a Western Electric 3B20S UNIX User's Manual Release 4.1, something I thought I'd never see and wasn't sure actually exited: print manuals for 4.x.
Once received I'll be curious to see what differences are obvious between this and the 3.0 manual, and this should be easy to scan given the comb binding. What a nice cover too! I always expected if a 4.x manual of some kind popped up it would feature the falling blocks motif of the two starter package sets of technical reports, but the picture of a 3B20S is nice. How auspicious given the recent discussion on the 3B series. I'm particularly curious to see what makes it specifically a 3B20S manual, if that's referring to it only having commands relevant to that one or omitting any commands/info specific to DEC machines.
Either way, exciting times, this is one of those things that I had originally set out to even verify existed when I first started really studying the history of UNIX documentation, so it's vindicating to have found something floating around out there in the wild. Between this and the 4.0 docs we now should have a much clearer picture of that gulf between III and V.
More to come once I receive it!
- Matt G.
next reply other threads:[~2022-12-02 5:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 5:04 segaloco via TUHS [this message]
2022-12-02 9:36 ` [TUHS] " Sergio Pedraja
2022-12-11 0:07 ` Jason T
2022-12-11 2:21 ` segaloco via TUHS
2022-12-11 6:28 ` John Cowan
2022-12-12 6:15 ` segaloco via TUHS
2022-12-12 13:38 ` G. Branden Robinson
2022-12-12 14:05 ` Ralph Corderoy
2022-12-12 14:25 ` G. Branden Robinson
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='AUvhAlVb0td6ugkWvO5gb3mvdLajlbR-jCP71fYT_IMajCGn7_wI9DsSizbV-HUKDk7lo5M7V2iE-XXNeFOYSdn6j9HSShrRP8pyxBQiePU=@protonmail.com' \
--to=tuhs@tuhs.org \
--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).