Mastodawn

https://github.com/cr1901/nwbackup I remembered that I wrote this while looking for other code.

NetWork BACKUP- Back up your files on DOS using @mbbrutman's mTCP. File-based using the Archive bit :D.

Only FTP support was ever implemented. Who runs an FTP server nowadays, even at home? I guess I could add an HTTP chunked encoding backend or a helper Rust bin.

Maybe NETDRIVE alleviates the need for it nowadays?

I wanted to implement full drive imaging at some point, but couldn't work out the logistics.

GitHub - cr1901/nwbackup: Network Backup program for mTCP (old DOS machines) and possible embedded targets.

Network Backup program for mTCP (old DOS machines) and possible embedded targets. - cr1901/nwbackup

GitHub

Show thread

mbbrutman

@cr1901 I remember when you wrote that.

I still consider FTP to be invaluable, so it is always available on anything that it can be installed on. And all of my Unix/Linux machines have Telnet clients and servers as well.

NetDrive is a quick way to add a network attached disk. I use it for quickly mounting a central repository of DOS software on a machine and for doing backups. It's much nicer to do backups using standard DOS file copy utils than it is to use FTP, which can be clunky.

Show thread

William D. Jones 1d ago

@mbbrutman No argument from me there that FTP is clunky.

At the time I wrote this, I did FTP backup b/c that was what my NAS exposed easily (i.e. without needing a shell). I think with a rewrite, I would still find FTP support valuable. But maybe there's room for something bespoke too that doesn't require two sockets (TLV protocol, or rsync, if the protocol was documented well).