The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Michael Stiller via TUHS <tuhs@tuhs.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Paul Ruizendaal <pnr@planet.nl>, "tuhs@tuhs.org" <tuhs@tuhs.org>
Subject: [TUHS] Re: x/y/zmodem on Unix
Date: Tue, 19 Sep 2023 11:47:42 +0200	[thread overview]
Message-ID: <A5B55C71-0E54-464B-809A-303CE9C7E9BB@me.com> (raw)
In-Reply-To: <ZQkBnAD1AsrJLibN@mit.edu>

I just wanted to mention, that you can also get zmodem support for iTerm2 if you are on mac.

In fact i use it a lot.

See here:

https://github.com/robberphex/iTerm2-zmodem

Best regards,

Michael


> On 19. Sep 2023, at 04:04, Theodore Ts'o <tytso@mit.edu> wrote:
> 
> On Mon, Sep 18, 2023 at 07:07:25PM -0400, Dan Cross wrote:
>> 
>> xmodem lives on in a lot of embedded applications because of its
>> overall simplicity. We used it to bootstrap kernels onto Oxide
>> computers, for example, while we were doing active development.
> 
> Today, KDE's Konsole terminal window has a "ZModem upload" function,
> which I've used for sending a file up to some system where the
> administrator on the remote machine has disabled scp and sftp for
> random security $REASONS.
> 
> I could compress the file and use uuencode/uudecode, but for larger
> files where cut and paste isn't terribly convenient, using zmodem can
> be one of the simpler and more effective.
> 
> 						- Ted


  reply	other threads:[~2023-09-19  9:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-18 22:31 [TUHS] " Paul Ruizendaal
2023-09-18 23:07 ` [TUHS] " Dan Cross
2023-09-19  2:04   ` Theodore Ts'o
2023-09-19  9:47     ` Michael Stiller via TUHS [this message]
2023-09-19  3:58   ` John Cowan
2023-09-19  2:46 ` Jonathan Gray
2023-09-19  3:42   ` Serge Burjak
2023-09-19  6:10     ` Serge Burjak
2023-09-19  6:37       ` Dave Horsfall

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=A5B55C71-0E54-464B-809A-303CE9C7E9BB@me.com \
    --to=tuhs@tuhs.org \
    --cc=mstiller@me.com \
    --cc=pnr@planet.nl \
    --cc=tytso@mit.edu \
    /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).