list.debian-user@natch.dyndns.org wrote:
|Note that the piped tar trick does you pretty well: | | $ tar cvf . | ( cd newpath; tar xvf - ) | |...too, tar is by default verbose and lets you know what's going on. In |the above instance, on *both* the read and write sides of the equation. | |For synching up two systems, rsync wins over tar. |as you said, rsync keeps also good info on permissions, pipes, sockets....best of all, it permits to "continue" if the first copying has failed. (usefull if there is tons of Gigs to copy) rsync can be used locally : rsync -v -a /boot /target bye
I note that you did not use the "-H" rsync switch, that supposedly preserves "hard" links. Would you use it when simply moving an entire installation to a new drive or system? Would you use it when trying to make a full backup of the installation as an archive, on the same drive? (Hey, it's better than nothing, isn't it?) And in the latter case, how about this for every day (or hour!) use:
sudo rsync -avHu / /backup
Finally, the rsync man page seems to display in a corrupted way in gnome terminal, but not in a plain xterm terminal. I've never seeen any other man page act like that in either terminal. Anyone else notice that? (Try it. Scroll up and down for a little bit, and watch the fun. But don't stand up too fast!)