From: pechter at gmail.com (William Pechter)
Subject: [COFF] some PDP11 stuff
Date: Sun, 1 Mar 2020 22:19:43 -0500 [thread overview]
Message-ID: <ce38f33b-ae33-4d90-b57a-6fad5135eadd.maildroid@localhost> (raw)
In-Reply-To: <20200301164256.mqi5km4xes3lx5oo@solfire>
Reachable and download able through Android Chrome.
Raspberry Pi Gopher space. Amazing.
Like HECnet... Some folks appreciate Retro computing.
Bill
Sent from pechter at gmail.com
-----Original Message-----
From: mylists at posteo.de
To: coff at minnie.tuhs.org
Sent: Sun, 01 Mar 2020 18:44
Subject: [COFF] some PDP11 stuff
Hi,
while exploring the gopherspace (YES! Still existing,
growing community) I found this gopher page:
gopher://pdp11.tk/1
which can be reached with Lynx for example.
Unfortunately I cannot evaluate the items there, but
may be it is worth a look by someone knowledgeable.
Cheers!
mcc
_______________________________________________
COFF mailing list
COFF at minnie.tuhs.org
https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20200301/dfd75682/attachment.html>
prev parent reply other threads:[~2020-03-02 3:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-01 16:42 mylists
2020-03-02 3:19 ` pechter [this message]
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=ce38f33b-ae33-4d90-b57a-6fad5135eadd.maildroid@localhost \
--to=coff@minnie.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).