The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Will Senn <will.senn@gmail.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 14:57:29 -0500	[thread overview]
Message-ID: <CAC20D2PN4J_kkBLoAJrJT2Ko2A+c0+-3g_e-n3Had8CqWJ5WPA@mail.gmail.com> (raw)
In-Reply-To: <b935ca0c-4b6e-afec-d266-070e9cc1e742@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1041 bytes --]

Will,

For those of us outside of BTL, i.e. the Academic users, "Unix News" was
created - which became ';login" - We started to meet informally at a few
universities and talk to each other.   Those of us on the ArpaNet that
email/FTP and the like, started to share patches - but mostly things were
shared when we got together via magtape. When they were held in NYC, we
might be lucky and someone from Research might come (and even accidentally
spill a few bits on the floor that mix fix something).  Eventually, USENIX
was formed, and we met twice a year formally. That was so popular, USENIX
started having specialty conferences such as the one for C and C++, LISA,
Networking, Linux and Free Software, etc. Similarly, with V7, UUCP was
given to use a USENET was started by Tom Truscott and his famous
"auto-dialler" that he hacked with a 12v relay, a DR-11C and described at
the Bolder USENIX conference.   Netnews was not far behind - which sadly
became net.noise when the signal-to-noise ratio disappeared.

Clem
ᐧ

[-- Attachment #2: Type: text/html, Size: 1780 bytes --]

  parent reply	other threads:[~2023-02-08 19:59 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
2023-02-08 20:01     ` Henry Bent
2023-02-08 20:02   ` Clem Cole
2023-02-08 19:57 ` Clem Cole [this message]
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=CAC20D2PN4J_kkBLoAJrJT2Ko2A+c0+-3g_e-n3Had8CqWJ5WPA@mail.gmail.com \
    --to=clemc@ccc.com \
    --cc=tuhs@tuhs.org \
    --cc=will.senn@gmail.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).