From: Will Senn <will.senn@gmail.com>
To: tuhs@tuhs.org
Subject: [TUHS] Re: Stdin Redirect in Cu History/Alternatives?
Date: Sat, 10 Dec 2022 22:45:23 -0600 [thread overview]
Message-ID: <9f49e6b0-e12a-d4c5-a021-fdc4409c32c8@gmail.com> (raw)
In-Reply-To: <CAEoi9W48jsKCrDEPc=zDhg32VhCC86O_hC75EyFtpATgKZuOwg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2055 bytes --]
On 12/10/22 10:17 PM, Dan Cross wrote:
> On Sat, Dec 10, 2022, 9:40 PM Larry McVoy <lm@mcvoy.com> wrote:
>
> On Sat, Dec 10, 2022 at 07:33:54PM -0700, Warner Losh wrote:
> > On Sat, Dec 10, 2022 at 7:32 PM Larry McVoy <lm@mcvoy.com> wrote:
> >
> > > On Sat, Dec 10, 2022 at 07:26:09PM -0700, Warner Losh wrote:
> > > > On Sat, Dec 10, 2022, 7:16 PM Larry McVoy <lm@mcvoy.com> wrote:
> > > >
> > > > > Wow, Kermit is still around? I think the last time I used
> that was
> > > > > around 1985.
> > > > >
> > > > > Are modems still a thing?
> > > >
> > > > I used it last year... without a modem.
> > >
> > > What problem does it solve that is not solved?
> >
> > Talking to my DEC Rainbow and downloading files to it? It was
> the go-to
> > protocol of choice. Xmodem is available, but messes up file
> sizes. kermit
> > just works with this device that's so slow it drops characters
> at 2400 baud.
>
> 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?
>
>
> Aside from talking to legacy systems, the Kermit protocol probably has
> little to recommend it (xmodem specifically still gets a bit of a
> workout in embedded/firmware spaces because it's dead simple). Kermit
> as a communications swiss army knife of a program is probably more useful.
>
> That said, I could see it for downloading bulk data from scada systems
> over a slow link (RF, serial, or maybe some weird 7 bit thing). I tend
> to doubt that's happening much with Kermit these days, though.
It works, it's not flaky and it will talk to practically anything. I use
it for talking with virtual systems running older OSes (Mac, unix, etc)
where other stuff doesn't or just sorta works, if you can run kermit and
theres a path, it'll prolly work more often than not, and certainly more
than more exotic stuff.
[-- Attachment #2: Type: text/html, Size: 4036 bytes --]
next prev parent reply other threads:[~2022-12-11 4:46 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 [this message]
2022-12-12 17:06 ` Doug McIntyre
-- 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=9f49e6b0-e12a-d4c5-a021-fdc4409c32c8@gmail.com \
--to=will.senn@gmail.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).