3 ms·
Between Unix-based machines on the same network my go-to is netcat. receiver$ nc -l 2000 > file sender$ nc receiver 2000 < file I usually check MD5 sums w
by DavidSJ 6y ago
Between Unix-based machines on the same network my go-to is netcat.
receiver$ nc -l 2000 > file
sender$ nc receiver 2000 < file
I usually check MD5 sums when I’m done.
- mkayokay 6y agoSCP. simply for the encrypted transmission, and most *nix machines have ssh
- tyingq 6y agoSsh with tar is handy for multiple files. Just be careful you're sending and receiving from the right place. Similar for rsync. (cd /right/place && tar -cf - patt*) | ssh remote '(cd /dest && tar -xvf -)' Of course, you can also use the compression flags with tar.
- DavidSJ 6y agoIt does require having an account on both machines though. I've used nc in situations where one machine is owned by someone else.
- AnonHP 6y agoLooks like you've got the receiver and sender commands reversed. The sender should use input redirection (< file) to read the file and the receiver should use output redirection (> file) to save the file.
- DavidSJ 6y agoLook again. :) That's how I have it.
- therein 6y agoCould easily introduce compression too: receiver$ nc -l 2000 | zcat > file sender$ nc receiver 2000 < $(cat file | gzip -f) But probably something like `rsync -azvP` will be much better in every way yet still quite portable and prevalent.