3 ms·
Recommending rsync as a more 'modern' replacement for SCP made me smile. Rsync is .. idosyncratic and documented by a single codebase (not withstanding the fine
by ggm 8y ago
Recommending rsync as a more 'modern' replacement for SCP made me smile. Rsync is .. idosyncratic and documented by a single codebase (not withstanding the fine work OpenBSD people have done writing their own rsync)
- johnchristopher 8y agoMy pet peeve grief with rsync is that I have to double check the man page for the trailing slash rule every time I use it. Otherwise I love it.
- ggm 8y agoI get hit by that one. but, tbf Linux and BSD differ on the behaviour of cp -r with ./thing/ and ./thing -I found references to ./thing/. worked on both. I also find the --include --exclude behaviour very confusing. does --include=* outweigh --exclude=thing and vice-versa and does this reset left to right?
- pgeorgi 8y agoThat's why I have cpdup (https://github.com/DragonFlyBSD/cpdup https://github.com/DragonFlyBSD/cpdup) around on all systems I use. No need to worry about rsync's special syntax.
- mcbain 8y agoMy shell history is sure to show every use of ‘rsync <whatever>’ to be preceded by ‘rsync -n <whatever>’ to make sure I have the paths correct.
- adrian_b 8y agoWhile you are right, at least rsync works correctly, i.e. it is able to make perfect copies of files, regardless of the files systems used at source and at destination, while scp and sftp have always lost information (file metadata) in certain cases. Any file copying program which is unable to make identical copies is garbage in my opinion. The Linux tmpfs file system is another bad example. Like scp, which can silently lose information, copying a file to a tmpfs directory, then again to a decent file system can lose file metadata.
- e12e 8y agoSo zmodem for simple file transfer and rsync for everything else?