From: segaloco via TUHS <tuhs@tuhs.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] 4.3BSD User Contributed Software Volume?
Date: Sat, 17 Jun 2023 19:37:55 +0000 [thread overview]
Message-ID: <Wi79aNS45NVI3EnXUe-xVqXKIZTg2ELWZZu0aGbraM0SgWgdsm4Tc_inf79VRxwQdNOZU19YTD0hhrPmnDZF__HMDC2ffcpYsLpv9KUbgkk=@protonmail.com> (raw)
Hello, I've come across something in a bookshelf up at the local university that I have thus far been unsuccessful at locating online.
It's a binder amongst other 4.3BSD binders like the reference manuals and supplementary documents but this one is labeled "User Contributed Software (UCS)". I can't find any of these in the doc folder of the 4.3BSD copies in the archive nor can I find a scan of the originals. There is an overview at the start listing the following packages: B, X, ansi (VAX tape tools), apl, bib, courier, cpm, dipress, dsh, emacs, enet, help, hyper, icon, jove, kermit, mh, mkmf, mmdf, news, notes, npl00, patch, path alias, rcs, rn, spms, sumacc, sunrpc, tac, tools, umodem, and xns.
There are a preponderance of man pages as well as some focused papers for B, SPMS, the Icon programming language, and MMDFII. I didn't scribble down more notes before heading home because I figured this was something I'd find on page one of an internet search, but thus far have had no luck. If I don't turn up a digital copy soon I might just have to make another trip up there soon with my flatbed scanner. In any case I left a note too hoping whoever the curator of that bookshelf is (it was in some club room) might have the scoop on those binders, if they're left over from some long gone 4.3BSD installation in the EE/CS department and if they might have some siblings in other bookshelves nearby.
- Matt G.
next reply other threads:[~2023-06-17 19:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-17 19:37 segaloco via TUHS [this message]
2023-06-17 20:23 ` [TUHS] " Jeremy C. Reed
2023-06-17 20:37 ` Jeremy C. Reed
2023-06-17 20:48 ` segaloco via TUHS
2023-06-18 1:07 ` Jonathan Gray
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='Wi79aNS45NVI3EnXUe-xVqXKIZTg2ELWZZu0aGbraM0SgWgdsm4Tc_inf79VRxwQdNOZU19YTD0hhrPmnDZF__HMDC2ffcpYsLpv9KUbgkk=@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).