Pádraig Brady 9654b67a54 cp: with --link always use linkat() if available ...

* src/copy.c (copy_reg): If linkat() is available it doesn't
matter about the gnulib emulation provided, and thus the
LINK_FOLLOWS_SYMLINKS should not have significance here.
This was noticed on FreeBSD and the consequence is that
cp --link will create hardlinks to symlinks there, rather
than emulating with symlinks to symlinks.
* tests/cp/link-deref.sh: Adjust the checks to cater
for all cases where hardlinks to symlinks are supported.

2014-02-10 10:02:34 +00:00

..

abuse.sh

…

acl.sh

…

attr-existing.sh

…

backup-1.sh

…

backup-dir.sh

…

backup-is-src.sh

…

capability.sh

…

cp-a-selinux.sh

…

cp-deref.sh

…

cp-HL.sh

…

cp-i.sh

…

cp-mv-backup.sh

…

cp-mv-enotsup-xattr.sh

…

cp-parents.sh

…

deref-slink.sh

…

dir-rm-dest.sh

…

dir-slash.sh

…

dir-vs-file.sh

…

existing-perm-dir.sh

…

existing-perm-race.sh

…

fail-perm.sh

…

fiemap-2.sh

…

fiemap-empty.sh

…

fiemap-FMR.sh

…

fiemap-perf.sh

…

file-perm-race.sh

…

into-self.sh

…

link-deref.sh

…

link-heap.sh

…

link-no-deref.sh

…

link-preserve.sh

…

link-symlink.sh

…

link.sh

…

nfs-removal-race.sh

…

no-ctx.sh

…

no-deref-link1.sh

…

no-deref-link2.sh

…

no-deref-link3.sh

…

parent-perm-race.sh

…

parent-perm.sh

…

perm.sh

…

preserve-2.sh

…

preserve-gid.sh

…

preserve-link.sh

…

preserve-mode.sh

…

preserve-slink-time.sh

…

proc-short-read.sh

…

proc-zero-len.sh

…

r-vs-symlink.sh

…

reflink-auto.sh

…

reflink-perm.sh

…

same-file.sh

…

slink-2-slink.sh

…

sparse-fiemap.sh

…

sparse-to-pipe.sh

…

sparse.sh

…

special-bits.sh

…

special-f.sh

…

src-base-dot.sh

…

symlink-slash.sh

…

thru-dangling.sh

…

trailing-slash

…