Re: no-hard-link for a simple mv wrapper

2020-11-04 Thread Eric L. Zolf
Hi, the man page is misleading: without `--no-hard-links`, rdiff-backup does its best to keep hard links (i.e. stores them under same inode), but _with_ this option, it actually treats them as two different files, and stores them under different inodes, actually duplicating the disk space

no-hard-link for a simple mv wrapper

2020-11-03 Thread Dan Y
I saw today the rdiff-backup command... I wanted to know: I see in the man page the --no-hard-links option: "don't replicate hard links". Is the meaning that it creates hard links instead of to "replicate" them as separate inodes? or does it simply exclude new hard links from the mirror? The