From: Doug McIntyre <merlyn@geeks.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Stdin Redirect in Cu History/Alternatives?
Date: Mon, 12 Dec 2022 11:06:46 -0600 [thread overview]
Message-ID: <Y5dfpqA3k7tDarI5@geeks.org> (raw)
In-Reply-To: <20221211023955.GP8801@mcvoy.com>
On Sat, Dec 10, 2022 at 06:39:55PM -0800, Larry McVoy wrote:
> OK, that is cool, but my question was what problem does it solve that
> we face today? Other than talking to 30-40 year old hardware. Why is
> Kermit still a thing?
Up until recent, I used kermit on my mac laptop to talk out multiple serial ports
to control different devices configured over serial quite regularly.
(Now I use the Serial.app)
There were other ways to do it, but kermit was familure, and worked flawlessy.
next prev parent reply other threads:[~2022-12-12 17:06 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-12 17:42 Nelson H. F. Beebe
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
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 21:34 ` Dave Horsfall
2022-12-12 21:46 ` Chet Ramey
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=Y5dfpqA3k7tDarI5@geeks.org \
--to=merlyn@geeks.org \
--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).