From: Will Senn <will.senn@gmail.com>
To: segaloco <segaloco@protonmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: history of community help for unix users everywhere
Date: Wed, 8 Feb 2023 13:56:17 -0600 [thread overview]
Message-ID: <2d89bce4-4ac2-df63-ab79-4558899a825e@gmail.com> (raw)
In-Reply-To: <1MaFvhLAILpLyAwHtHDIbStw0NbhQMzAT5VPAEEK0OO8DorBQinSCTKb9Efh4RHxt69dgbyl8l7xgvwlVguSGG34F-AvUIq3HaJ3jH187gg=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 1480 bytes --]
On 2/8/23 1:39 PM, segaloco wrote:
> At least as far as I can glean from manuals, there is the "trouble"
> command circa UNIX/TS 4.0 which was "a front end for the Piscataway
> Change Management Tracking System (CMTS)".
>
> This was used to report issues over uucp to Piscataway where they
> would then be transformed into Modification Requests, examples of
> which in the form of the request form *and* a list of 1980-1983
> changes are in Sys V literature I've scanned.
>
> The utility would request:
> - The user name
> - Their location
> - Phone number
> - Type of request: Hardware, software, documentation, enhancement, and
> unknown
> - System: Product in need of support (usually unix)
> - Release (can be N/A)
> - Severity: 1 - highest 4 - lowest
> - Date
> - Abstract/Summary
> - Detailed Description
>
> There is a note here too that unless stated otherwise, reports may be
> selected for publication in the "Mini-System Newsletter".
Fascinating. Thanks for the details. I did a quick search in the source
archive and all I could find were these:
NetBSD-5.0.2/external/bsd/openldap/dist/doc/guide/admin/troubleshooting.sdf
OpenBSD-4.6/gnu/usr.bin/gcc/gcc/doc/trouble.texi
OpenBSD-4.6/usr.bin/sudo/TROUBLESHOOTING
V10/cmd/icon/docs/trouble.roff
pdp11v/usr/man/a_man/man8/trouble.8
pdp11v/usr/man/u_man/man1/trouble.1
Anybody know what pdp11v is? or where the source code for the utility
is? Did it send email, or what?
Thanks,
Will
[-- Attachment #2: Type: text/html, Size: 3777 bytes --]
next prev parent reply other threads:[~2023-02-08 19:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 18:58 [TUHS] " Will Senn
2023-02-08 19:39 ` [TUHS] " segaloco via TUHS
2023-02-08 19:56 ` Will Senn [this message]
2023-02-08 20:01 ` Henry Bent
2023-02-08 20:02 ` Clem Cole
2023-02-08 19:57 ` Clem Cole
2023-02-08 20:00 ` Clem Cole
2023-02-08 20:17 ` Henry Bent
2023-02-08 20:48 ` Warner Losh
2023-02-08 21:28 ` Dan Cross
2023-02-08 21:34 ` Heinz Lycklama
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=2d89bce4-4ac2-df63-ab79-4558899a825e@gmail.com \
--to=will.senn@gmail.com \
--cc=segaloco@protonmail.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).