From: wkt@tuhs.org (Warren Toomey)
Subject: [TUHS] Move the uucp/news stuff off-list?
Date: Sat, 11 Mar 2017 13:08:19 +1000 [thread overview]
Message-ID: <20170311030819.GA30550@minnie.tuhs.org> (raw)
All, there might be a flurry of e-mails as the uucp/news stuff gets
set up. I think we should move the actual setup messages off-list and
keep TUHS for anecdotes & questions about the old systems. Sound OK?
If so, I can set up another list.
I noticed that seismo is not as well connected (historically) as decvax,
so I've turned seismo into decvax, and I now have three systems on three
physically different boxes:
munnari ----------- decvax ---------- inhp4
at home simh.tuhs.org minnie.tuhs.org
behind NAT 5000 5000
I'm happy to pass either decvax or inhp4 onto someone if someone
else really wants one of them.
Cheers, Warren
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170311/e3742f34/attachment.sig>
next reply other threads:[~2017-03-11 3:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-11 3:08 Warren Toomey [this message]
2017-03-11 3:09 ` Cory Smelosky
2017-03-11 17:50 ` SPC
2017-03-11 18:55 ` Arthur Krewat
2017-03-11 21:08 ` Warren Toomey
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=20170311030819.GA30550@minnie.tuhs.org \
--to=wkt@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).