I can confirm the problem in Slacko 5402 when copying to an NTFS-formatted /mnt/home. And I can confirm that putting the old ntfs-3g 2010.1.16 in the init fixes it.SFR wrote:Another workaround:Removing this option in init script (lines 239 & 249) disables these copy/move errors caused by newer ntfs-3g, but the question is - if that option is really needed for something or if it can be thrown away safely..?http://linux.die.net/man/8/ntfs-3g wrote:no_def_opts
By default ntfs-3g acts as if "silent" (ignore errors on chmod and chown), "allow_other" (allow any user to access files) and "nonempty" (allow mounting on non-empty directories) were set, and "no_def_opts" cancels these default options.
However, if you copy to an external NTFS drive, there is no problem. In that scenario, you are now using the new /bin/ntfs-3g. If you check "mount", the NTFS partition has "allow_other". But /mnt/home has "default_permissions".
I'm guessing that the definition of "default_permissions" has changed in the new ntfs-3g,