Has 'mv' behaviour changed recently

cp -pr .tvtimemnt-dosDrive

Does work without complaint. (Note: The r is necessary as this is a directory)

I decided to compare the output from the 'normal' installed mv with the (more successful) mv copied from RH8. The most notable thing was the difference in return status from what is apparently the "same" call to mkdir; it failed in the new mv and bailed out. Here are some lines from the strace on the 'new' mv:-

stat64("-mnt-dosdrive-.tvtime", 0xfefa8d50) = -1 ENOENT (No such file or directory) lstat64(".tvtime", {stmode=SIFDIR0777, stsize=4096, ...}) = 0 lstat64("-mnt-dosdrive-.tvtime", 0xfefa8c40) = -1 ENOENT (No such file or directory) rename(".tvtime", "-mnt-dosdrive-.tvtime") = -1 EXDEV (Invalid cross-device link) unlink("-mnt-dosdrive-.tvtime") = -1 ENOENT (No such file or directory) lgetxattr(".tvtime", "security.selinux", "root:objectr:userhomet", 255) = 26 open("-proc-self-attr-fscreate", ORDWR) = 3 write(3, "root:objectr:userhomet-0", 26) = 26 close(3) = 0 mkdir("-mnt-dosdrive-.tvtime", 040777) = -1 EACCES (Permission denied)

And here is the corresponding (AFAICT) part from the 'old' mv:-

ioctl(0, SNDCTLTMRTIMEBASE or TCGETS, {B38400 opost isig icanon echo ...}) = 0 stat64("-mnt-dosdrive-.tvtime", 0xfefff8a0) = -1 ENOENT (No such file or directory) lstat64(".tvtime", {stmode=SIFDIR0777, stsize=4096, ...}) = 0 lstat64("-mnt-dosdrive-.tvtime", 0xfefff760) = -1 ENOENT (No such file or directory) rename(".tvtime", "-mnt-dosdrive-.tvtime") = -1 EXDEV (Invalid cross-device link) unlink("-mnt-dosdrive-.tvtime") = -1 ENOENT (No such file or directory) mkdir("-mnt-dosdrive-.tvtime", 040777) = 0

Spot the difference at the end. However, I can't figure out *why* the call fails in one and not the other. The obvious point is that in the new mv, there are some extra calls; something to do with getting extended attributes and secure Linux.

Hmmmmm......

--