[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
mv --no-preserve-ownership
From: |
sa |
Subject: |
mv --no-preserve-ownership |
Date: |
Thu, 30 Apr 2015 15:02:53 +0300 |
User-agent: |
Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 |
Dear coreutils developers,
it's still common today when you can copy files somewhere but subsequent
chown() on them returns EACCES:
NFS without strict uid/gid mapping,
CIFS with broken Unix Extensions - nowaday NAS devices,
less common filesystems like sshfs.
When you move files to there, intuitively the operation is plain move,
but mv should be avoided because of error messages (as many as file number):
mv: failed to preserve ownership
Sometimes these error messages probably hide really important error
messages and hence force me to double-check: if files were actually
copied to destination and were actually deleted from source.
During years, I'm inventing, improving and distributing lines like "cp
&&rm", having developed fear for using mv.
What do coreutils developers think about this?
Is there hope for accepting --no-preserve-ownership patch to mv?
-- sa
- mv --no-preserve-ownership,
sa <=