From: Lyndon Nerenberg <lyndon@orthanc.ca>
To: tuhs@minnie.tuhs.org
Subject: [TUHS] UREP
Date: Tue, 09 Jul 2019 13:08:07 -0700 [thread overview]
Message-ID: <40c8dad5e0198e3d@orthanc.ca> (raw)
Back in the day I had the pleasure of firing up what was possibly
the last North American BITNET node (certainly the last one on
NetNorth), on a Sun 3/xxx deskside server running SunOS 3.5(+).
(AUCS, at Athabasca U.)
I'm curious to know if the UREP source code that drove that link
ever escaped. I recall it being licensed code at the time, but
from academia vs. a commercial product. I don't know if that also
applied to the bisync serial driver.
--lyndon
next reply other threads:[~2019-07-09 20:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-09 20:08 Lyndon Nerenberg [this message]
2019-07-10 5:44 ` arnold
2019-07-10 19:31 ` Adam Thornton
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=40c8dad5e0198e3d@orthanc.ca \
--to=lyndon@orthanc.ca \
--cc=tuhs@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).