From: dave@horsfall.org (Dave Horsfall)
Subject: [TUHS] BerkNet
Date: Thu, 27 Nov 2014 05:26:16 +1100 (EST) [thread overview]
Message-ID: <alpine.BSF.2.11.1411270521200.30791@aneurin.horsfall.org> (raw)
In-Reply-To: <14353.1416983329@cesium.clock.org>
On Tue, 25 Nov 2014, Erik E. Fair wrote:
> I suspect that BerkNet's colon separator for host:file was how the rcp
> command got that syntax, and probably how ssh inherited it.
That could also explain why ACSnet's first incarnation also used a colon
separator (you'll see me as "dave:csu40" in some early AUUGN editions;
that's me at the University of NSW Computing Services Unit 11/40).
--
Dave Horsfall DTM (VK2KFU) "Bliss is a MacBook with a FreeBSD server."
http://www.horsfall.org/spam.html (and check the home page whilst you're there)
next prev parent reply other threads:[~2014-11-26 18:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 1:32 [TUHS] 2.10 Jacob Ritorto
2014-11-21 1:56 ` Nick Downing
[not found] ` <CA+oaVqwGKiOPKm8Bz62Z0s9dEYiAbTXR9=WrQyjqGFX-uaYmjQ@mail.gmail.com>
2014-11-21 3:25 ` Jacob Ritorto
2014-11-21 3:36 ` Cory Smelosky
2014-11-21 4:02 ` Cory Smelosky
2014-11-21 4:43 ` Clem Cole
2014-11-21 4:55 ` Cory Smelosky
2014-11-21 5:46 ` Clem Cole
2014-11-21 6:07 ` Cory Smelosky
2014-11-26 6:28 ` [TUHS] BerkNet Erik E. Fair
2014-11-26 6:48 ` Cory Smelosky
2014-11-27 16:42 ` Mary Ann Horton
2014-11-29 16:38 ` Clem Cole
2014-11-26 18:24 ` Clem Cole
2014-11-26 18:35 ` Dan Cross
2014-11-26 20:03 ` Clem Cole
2014-11-26 18:26 ` Dave Horsfall [this message]
2014-11-21 6:13 ` [TUHS] 2.10 Jacob Ritorto
2014-11-21 13:06 ` Clem Cole
2014-11-26 18:49 [TUHS] BerkNet Noel Chiappa
2014-11-26 20:16 ` Clem Cole
2014-11-27 20:40 ` Dave Horsfall
2014-11-29 16:39 ` Clem Cole
2014-11-26 23:33 ` Jesus Cea
2014-11-27 14:38 Noel Chiappa
2014-11-29 16:34 ` Clem Cole
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=alpine.BSF.2.11.1411270521200.30791@aneurin.horsfall.org \
--to=dave@horsfall.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).