From: Serge Burjak <email@example.com>
To: Jonathan Gray <firstname.lastname@example.org>
Cc: Paul Ruizendaal <email@example.com>, firstname.lastname@example.org
Subject: [TUHS] Re: x/y/zmodem on Unix
Date: Tue, 19 Sep 2023 16:10:38 +1000 [thread overview]
Message-ID: <CADtgiZCZ_EOo61yCcr5YurBpEu4+nJBZhuzAan9dEDwaUoNx0Q@mail.gmail.com> (raw)
If anyone wants more zmodem/Chuck Forsberg history, a prolific usenet
poster, here are news archives going back to 1994. It gives a good
indication of his personality. I had been dealing with him for about 6
years by then... Still have the licence keys.
Kermit discussion and comparisons,
On Tue, 19 Sept 2023 at 13:42, Serge Burjak <email@example.com> wrote:
> Chuck Forsberg wrote Zmodem as a sliding Window transfer protocol
> alternative to Kermit and superkermit. It was very high performance
> over slow links. He provided source code support for the protocol
> driver on the server and client end, in various versions. His client
> programs were Yam (yet another modem) and ProYam. You could shell out
> of the client, run other programs. Other client platforms supported
> parts of the protocol. Available as binaries and source when licenced.
> It had a scripting language and out of the box had the zmodem protocol
> which has the ability to send commands, resume transfers, traverse non
> 8 bit or unreliable links, remove or rename source file, deal with
> conflicting file names, synchronise folders and lots of other things.
> I have written many scripts to help dial up users into a unix box and
> download financial research data. Scripts still work across the
> internet. He made the code very portable, clean and I believe it is
> open source now. Chuck is no longer with us.
> SecureCRT ssh client from VanDyke.com still has native support. To
> send a file from the unix host, typically sz filename and it just
> arrives. Sz- u and it will remove the source file after successful
> transfer, plus lots of other options. The binary was typically linked
> so if you type sx it would try to do a transfer with xmodem, even
> though it's the same binary.
> Hope this helps.
> On Tue, 19 Sept 2023 at 12:47, Jonathan Gray <firstname.lastname@example.org> wrote:
> > On Tue, Sep 19, 2023 at 12:31:30AM +0200, Paul Ruizendaal wrote:
> > > I had always associated x/y/zmodem with CP/M and MSDOS, not so much with Unix. Last December Clem already pointed out that it was popular for file exchange in the Unix scene as well, along with several other similar tools. Also, the ymodem approach to file metadata is very unix oriented, suggesting it originated on Unix or at least that Unix users were an important user demographic. Yet, I could find little trace of x/y/zmodem in the TUHS Unix Tree. The search tool finds it in 2.11BSD, in Minix 1.5 and 2.0 and in V10. Kermit is in those as well, and in 4.3BSD and 4.4BSD on top.
> > have a look at
> > tuhs/Applications/Shoppa_Tapes/usenix878889.tar.gz
> > usenix87/Comm/
> > usenix89/Comm/
> > also appears in
> > 386bsd/othersrc/public/zmodem-3.03/
> > where the license was changed to prohibit commercial use after
> > the RLE changes in April 1989
> > https://www.ohse.de/uwe/software/lrzsz.html
> > is derived from an earlier version with the license changed to GPLv2
next prev parent reply other threads:[~2023-09-19 6:11 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
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 [this message]
2023-09-19 6:37 ` Dave Horsfall
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).