Conversation
Jarkko Sakkinen
jarkko
it is 2023 and i'm implementing #zmodem just a sub-portion of it: 32-bit binary transfers. So ignoring 16-bit and alternative hex protocol. There's some non lively looking zmodem crate and of course lrzsz but neither of them feel too inspiring to contribute or build on top off.
1
0
1
Tbh, I don't really get why people have done new kermit/minicom style programs and promote X-modem and Y-modem, which nobody used even in 1993 when calling BBS's because they were so terrible. Why not then just use kermit. or minicom instead. I want to sort of well integrated "zmodem experience" :-)
1
0
0
My online life started about then in the BBS world first and I've yet to meet a person who willingly uses xmodem or ymodem for anything. I would be more eager to try out stuff that promotes explicitly to support neither. they were already corpses when i first discovered of their existence.
you *literally* need to visit maybe a rest home to meet a living person who has ever had any profitalble use for them...
on the other hand zmodem is still a thing with SBC's and FPGA's.
you *literally* need to visit maybe a rest home to meet a living person who has ever had any profitalble use for them...
on the other hand zmodem is still a thing with SBC's and FPGA's.
1
0
1
and like additional development from this would be to do something like https://en.wikipedia.org/wiki/SMODEM, which would allow have a TTY session and concurrent file transfer simultaneously from the same serial cable, which would be enormous improvement. but yeah this part requires already diverging from original zmodem so let's get that right first.
1
0
1
so the way to differentiate from other offerings here is for me to just not make generic xyzmodem crate but just focus on fluent zmodem binary transmit. and for further support disregard any other features except binary link level stuff that makes sense to modern SBC's. still makes the interface just generic enough to later on support SMODEM style multiplexing where the bandwidth can be shared with file transfers and an interactive session.
so the scope is anything that helps with the transport layer and not carry any corpse protocols.
just using this as a tool to put some notes as this thing keeps developing :-) i'll try to get zcbin first work in my tior serial tool concept (GPL2) and later on detach the protocol part to a MIT or similar licensed crate.
so the scope is anything that helps with the transport layer and not carry any corpse protocols.
just using this as a tool to put some notes as this thing keeps developing :-) i'll try to get zcbin first work in my tior serial tool concept (GPL2) and later on detach the protocol part to a MIT or similar licensed crate.
0
0
0