From: Steve Mynott <steve.mynott@gmail.com>
To: tuhs@tuhs.org
Subject: [TUHS] hal.gnu.ai.mit.edu
Date: Sat, 25 Aug 2018 19:45:51 +0100 [thread overview]
Message-ID: <CANuZA8STu8kX1=-WeJatqN2UhZ7n-49Sn=2sXZq9Fei1SH5hBQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 465 bytes --]
Back in the early 90s before the FSF withdrew the service due to misuse it
was possible to write off to them to get a free shell account on "hal" as I
did. I recall having to telnet through one of three gateway systems so
assume it was on its own little subnet.
But I can't remember what sort of system (hardware or OS) it was now
however and wondered if anyone else did?
--
Steve Mynott <steve.mynott@gmail.com>
cv25519/ECF8B611205B447E091246AF959E3D6197190DD5
[-- Attachment #2: Type: text/html, Size: 723 bytes --]
next reply other threads:[~2018-08-25 18:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-25 18:45 Steve Mynott [this message]
2018-08-25 18:59 ` Steve Mynott
2018-08-26 0:28 ` Jim Carpenter
2018-08-31 3:30 ` Greg 'groggy' Lehey
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='CANuZA8STu8kX1=-WeJatqN2UhZ7n-49Sn=2sXZq9Fei1SH5hBQ@mail.gmail.com' \
--to=steve.mynott@gmail.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).