From: Larry McVoy <lm@mcvoy.com>
To: Dan Cross <crossd@gmail.com>
Cc: Michael Kj??rling <e5655f30a07f@ewoof.net>, tuhs@tuhs.org
Subject: [TUHS] Re: Stdin Redirect in Cu History/Alternatives?
Date: Mon, 12 Dec 2022 17:54:20 -0800 [thread overview]
Message-ID: <20221213015420.GA15726@mcvoy.com> (raw)
In-Reply-To: <CAEoi9W7neRTHkzo7RkOJzuLBgD0x=ZWLObD-FSVCr0dWNxvSBg@mail.gmail.com>
On Sun, Dec 11, 2022 at 10:04:54AM -0500, Dan Cross wrote:
> I think this is in line with Larry's question about non-legacy
> use-cases for these ancient serial transfer protocols in late 2022.
Indeed, this was just what I was looking for. I had no idea that
serial transfer protocols were still useful.
It makes me wish I had kept the source for quicknet, I wrote my
own file transfer and remote terminal for CP/M in the middle
1980s. I did it just because I wanted things to work a certain
way and none of the other options did what I wanted. quicknet was
really pleasant on a 128K Z80 (not really 128K because the screen
was mapped in there, but more than 64K). I spent many a pleasant
hour logged in to uwvax in quicknet, got a lot of work done.
Thanks to you and others who had shown that serial transfer still
matters. Who knew? You did.
--
---
Larry McVoy Retired to fishing http://www.mcvoy.com/lm/boat
next prev parent reply other threads:[~2022-12-13 1:55 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-10 19:38 [TUHS] " segaloco via TUHS
2022-12-11 0:22 ` [TUHS] " Clem Cole
2022-12-11 2:37 ` segaloco via TUHS
2022-12-11 13:59 ` Michael Kjörling
2022-12-11 14:28 ` Steve Nickolas
2022-12-11 15:04 ` Dan Cross
2022-12-13 1:54 ` Larry McVoy [this message]
2022-12-11 17:18 ` Adam Thornton
2022-12-11 18:54 ` Michael Kjörling
2022-12-11 19:55 ` Dave Horsfall
2022-12-11 20:03 ` Larry McVoy
2022-12-11 23:22 ` segaloco via TUHS
2022-12-12 2:15 ` [TUHS] Clever code (was " Bakul Shah
2022-12-12 2:44 ` [TUHS] " Steve Nickolas
2022-12-12 3:09 ` Andrew Warkentin
2022-12-12 3:34 ` Larry McVoy
2022-12-12 5:00 ` Kevin Bowling
2022-12-12 5:26 ` Andrew Warkentin
2022-12-12 15:02 ` Larry McVoy
2022-12-12 15:29 ` Clem Cole
2022-12-12 15:39 ` Dan Cross
2022-12-12 16:04 ` Larry McVoy
2022-12-12 16:26 ` Clem Cole
2022-12-12 22:20 ` Liam Proven
2022-12-12 23:10 ` segaloco via TUHS
2022-12-12 23:24 ` Larry McVoy
2022-12-13 2:00 ` Andrew Warkentin
2022-12-13 13:37 ` Larry McVoy
2022-12-13 23:00 ` Andrew Warkentin
2022-12-14 1:05 ` Larry McVoy
2022-12-14 1:40 ` segaloco via TUHS
2022-12-14 6:32 ` Rich Morin
2022-12-14 2:01 ` Andrew Warkentin
2022-12-14 7:49 ` arnold
2022-12-14 11:54 ` Brad Spencer
2022-12-14 12:08 ` [TUHS] Re: (TUHS -> COFF?) Re: Clever code Michael Kjörling
2022-12-14 15:14 ` [TUHS] Microware's OS-9 (was: Clever code) G. Branden Robinson
2022-12-14 22:41 ` [TUHS] " John Cowan
2022-12-14 9:46 ` [TUHS] Re: Clever code (was Re: Re: Stdin Redirect in Cu History/Alternatives? Harald Arnesen
2022-12-15 18:33 ` Liam Proven
2022-12-16 10:42 ` Harald Arnesen
2022-12-18 14:05 ` Liam Proven
2022-12-18 15:08 ` Stuff Received
2022-12-19 11:47 ` Liam Proven
2022-12-20 8:30 ` Andrew Warkentin
2022-12-20 11:57 ` Liam Proven
2022-12-15 0:29 ` Bakul Shah
2022-12-15 2:54 ` Larry McVoy
2022-12-15 5:36 ` Bakul Shah
2022-12-15 14:02 ` Dan Cross
2022-12-15 14:06 ` Larry McVoy
2022-12-15 14:18 ` Dan Cross
2022-12-15 14:02 ` Larry McVoy
2022-12-15 8:01 ` Andrew Warkentin
2022-12-12 9:48 ` [TUHS] Re: Clever code Michael Kjörling
2022-12-12 21:34 ` [TUHS] Re: Stdin Redirect in Cu History/Alternatives? Dave Horsfall
2022-12-12 21:46 ` Chet Ramey
2022-12-11 0:42 Nelson H. F. Beebe
2022-12-11 2:16 ` Larry McVoy
2022-12-11 2:26 ` Warner Losh
2022-12-11 2:32 ` Larry McVoy
2022-12-11 2:33 ` Warner Losh
2022-12-11 2:39 ` Larry McVoy
2022-12-11 2:49 ` Bakul Shah
2022-12-11 3:10 ` Phil Budne
2022-12-11 4:17 ` Dan Cross
2022-12-11 4:45 ` Will Senn
2022-12-12 17:06 ` Doug McIntyre
2022-12-12 17:42 Nelson H. F. Beebe
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=20221213015420.GA15726@mcvoy.com \
--to=lm@mcvoy.com \
--cc=crossd@gmail.com \
--cc=e5655f30a07f@ewoof.net \
--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).