Been using UNIX since the late 80s; Linux since the mid-90s; virtualization since the early 2000s and spent the past few years working in the cloud space.
Location
Alexandria, VA, USA
Education
B.S. Psychology from Pennsylvania State University
zmodem came in soon after, and I always preferred it! Restarting failed transfers was amazing. I did try Kermit a couple of times (oh, and ymodem), but zmodem was the way to go.
Been using UNIX since the late 80s; Linux since the mid-90s; virtualization since the early 2000s and spent the past few years working in the cloud space.
Location
Alexandria, VA, USA
Education
B.S. Psychology from Pennsylvania State University
Yeah. Ymodem was just a very short way-station between the frustrations of xmodem and zmodem.
Given how flaky NSFnet was at the time, zmodem was a sanity-saver (and screen was so nice, given how slow transfers were: nothing like firing up screen, starting up a auto-retrying transfer, detach and log out ...come back a day or so later to the finished transfer).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Xmodem sucked. Zmodem (or Kermit, even) were the shiznit!
zmodem came in soon after, and I always preferred it! Restarting failed transfers was amazing. I did try Kermit a couple of times (oh, and ymodem), but zmodem was the way to go.
Yeah. Ymodem was just a very short way-station between the frustrations of xmodem and zmodem.
Given how flaky NSFnet was at the time, zmodem was a sanity-saver (and
screenwas so nice, given how slow transfers were: nothing like firing upscreen, starting up a auto-retrying transfer, detach and log out ...come back a day or so later to the finished transfer).