From: arnold@skeeve.com
To: crossd@gmail.com, arnold@skeeve.com
Cc: tuhs@tuhs.org, rik@rikfarrow.com, bakul@iitbombay.org
Subject: [TUHS] UREP code (was Re: Re: Minimum Array Sizes in 16 bit C (was Maximum))
Date: Sun, 06 Oct 2024 06:29:44 -0600 [thread overview]
Message-ID: <202410061229.496CTird901191@freefriends.org> (raw)
In-Reply-To: <CAEoi9W7EXZmMGcbKrnKVoreUO0OQK3aNpM6=j+dn0+yxaqw60g@mail.gmail.com>
Dan Cross <crossd@gmail.com> wrote:
> I do wonder if a version of it has survived somewhere; I've personally
> never seen it, but there's very little information about it out there
> anymore.
I don't have it. I think it was licensed software from Penn State.
I don't remember a lot of details. It gave a similar experience
to that on IBM systems; as your mail travelled point to point you
got a message printed on your terminal as to what node it was going through.
(Or something like that.)
There was also a facility similar to write(1) that let you chat with
someone on a remote BITNET site.
Overall, it did work.
Arnold
next prev parent reply other threads:[~2024-10-06 12:30 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-28 13:34 [TUHS] Re: Minimum Array Sizes in 16 bit C (was Maximum) Douglas McIlroy
2024-09-28 16:58 ` G. Branden Robinson
2024-09-28 17:47 ` Luther Johnson
2024-09-28 17:52 ` Luther Johnson
2024-09-28 18:46 ` G. Branden Robinson
2024-09-28 22:08 ` Luther Johnson
2024-09-28 22:45 ` Luther Johnson
2024-09-28 22:50 ` Luther Johnson
2024-09-28 17:59 ` Bakul Shah via TUHS
2024-09-28 22:07 ` Douglas McIlroy
2024-09-28 23:05 ` Rob Pike
2024-09-28 23:30 ` Warner Losh
2024-09-29 10:06 ` Ralph Corderoy
2024-09-29 12:25 ` Warner Losh
2024-09-29 15:17 ` Ralph Corderoy
2024-09-30 12:15 ` Dan Cross
2024-09-28 18:01 ` G. Branden Robinson
2024-10-01 13:13 ` arnold
2024-10-01 13:32 ` Larry McVoy
2024-10-01 13:47 ` arnold
2024-10-01 14:01 ` Larry McVoy
2024-10-01 14:18 ` arnold
2024-10-01 14:25 ` Luther Johnson
2024-10-01 14:56 ` Dan Cross
2024-10-01 15:08 ` Stuff Received
2024-10-01 15:20 ` Larry McVoy
2024-10-01 15:38 ` Peter Weinberger (温博格) via TUHS
2024-10-01 15:50 ` ron minnich
2024-10-01 19:04 ` arnold
2024-10-01 16:49 ` Paul Winalski
2024-10-01 15:44 ` Bakul Shah via TUHS
2024-10-01 19:07 ` arnold
2024-10-01 20:34 ` Rik Farrow
2024-10-02 0:55 ` Steffen Nurpmeso
2024-10-02 5:49 ` arnold
2024-10-02 20:42 ` Dan Cross
2024-10-02 21:54 ` Marc Donner
2024-10-05 17:45 ` arnold
2024-10-06 12:20 ` Dan Cross
2024-10-06 12:29 ` arnold [this message]
2024-10-01 16:40 ` Paul Winalski
2024-09-28 18:05 ` Larry McVoy
2024-09-30 15:49 ` Paul Winalski
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=202410061229.496CTird901191@freefriends.org \
--to=arnold@skeeve.com \
--cc=bakul@iitbombay.org \
--cc=crossd@gmail.com \
--cc=rik@rikfarrow.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).