search for: in94

Am 14.11.19 um 10:54 schrieb Paul Slootman via rsync: > You need to specify the source directory as the link-dest directory. Hi, I tried it also because it's an old question which has never worked for me. Instead it creates copies and not hard links: pierre at in94:~/tmp$ ls -li a b a: insgesamt 8 257315 -rw-r--r-- 1 pierre pierre 4 Nov 14 10:53 1 257316 -rw-r--r-- 1 pierre pierre 6 Nov 14 10:53 2 b: insgesamt 0 pierre at in94:~/tmp$ rsync -av --link-dest=a a/ b/ sending incremental file list --link-dest arg does not exist: a ./ 1 2 sent 194 bytes received...

...> Use a full pathname for --link-dest to remove all uncertainty. > E.g.: > > rsync -av --link-dest=$(pwd)/a a/ b/ > > In this case, as the destination is also in same current directory, you > could use: > > rsync -av --link-dest=../a a/ b/ Working: pierre at in94:~/tmp$ ls -li a b a: insgesamt 8 257315 -rw-r--r-- 1 pierre pierre 4 Nov 14 10:53 1 257316 -rw-r--r-- 1 pierre pierre 6 Nov 14 10:53 2 b: insgesamt 0 pierre at in94:~/tmp$ rsync -av --link-dest=$(pwd)/a a/ b/ sending incremental file list ./ sent 98 bytes received 19 bytes 234.00 bytes/sec tota...

Have a directory with a bunch rpms in it, mostly x86_64. Have another directory with a bunch, mostly 'noarch'. Some of the noarch files are already in the x86_64 dir and don't want to overwrite them. They are on the same physical disk, so really, just want the new 'noarch' files hardlinked into the destination. sitting in the noarch dir, I tried: rsync -auv