mv will automatically use rename, but if that fails (e.g. with EXDEV),
it falls back to copying files. i'd like to require that the mv be
atomic when relocating a directory, and if it isn't, fallback to other
logic. to that end, it'd be nice if mv supported --one-file-system and
would return an
On 1/24/23 00:42, Ondrej Valousek wrote:
+"), stdout);
+ fputs (_("\
+\n\
+--preserve=mode also copies ACLs but only if the destination filesystem\n\
+supports ACLs of the same type (i.e. no Posix <> NFSv4 ACLs conversion)\n\
Doesn't the earlier part of the --help output already say
Improve help to clarify ACL handling
---
src/cp.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/src/cp.c b/src/cp.c
index 016ae8988..73ffd34e9 100644
--- a/src/cp.c
+++ b/src/cp.c
@@ -239,6 +239,11 @@ When --reflink[=always] is specified, perform a
lightweight copy, where the\n\
data
> The "at least in Linux" qualification worries me.
> Having a very quick look at the qset_acl() code suggests it clears ACLs on
> some platforms at least, which chmod_or_fchmod() does not.
> Am I reading that wrong?
You are right.
The question is - why do we need to clear ACLs?
The only real
