Thanks for the bug report. So, 'cp -p' should only fail if the target filesystem is not a POSIX filesystem. Is that the case for you? I see /home/cro/home_root/mnt/hgfs/cro/Documents/TanagerProjects/Signage/flock_installer/ics-ubuntu-image.img as a destination, I'm not sure if 'hgfs' refers to a particular filesystem with non-POSIX semantics?
This is certainly a legitimate bug. We may be able to drop the '-p' with the reasoning that a file copy will create the new file with the same umask and owner as the original file creation, but we need to check this assumption.
Hi David,
Thanks for the bug report. So, 'cp -p' should only fail if the target filesystem is not a POSIX filesystem. Is that the case for you? I see /home/cro/ home_root/ mnt/hgfs/ cro/Documents/ TanagerProjects /Signage/ flock_installer /ics-ubuntu- image.img as a destination, I'm not sure if 'hgfs' refers to a particular filesystem with non-POSIX semantics?
This is certainly a legitimate bug. We may be able to drop the '-p' with the reasoning that a file copy will create the new file with the same umask and owner as the original file creation, but we need to check this assumption.