PROBLEM:  (60651, 77772, 60651, 66106, 64050) (PATCH ID: OSF440-371)
********


This patch fixes the following problems with the mv command:
    - an  invalid error message when attempting to move files in which
      the source name is the same as the destination name. The message
      would look something like the following:
            mv: rename foo to foo/fooo: Invalid argument

      The error message, with this patch, will now look something
      like the following:
            mv:  foo and foo are identical


   - when using "mv -i" to rename a symlink pointing to a file on a
     different filesystem owned by a different user results in the prompt:
               Ownership of y will change. Continue?

   - when moving a file from one filesystem to another, the "mv" command
     will copy the file rather than using the rename() system call. If
     there are any errors writing to the destination filesystem, the
     destination file is unlink()'d, and "mv" returns an error to the
     shell.  This can also result in the loss of a file.
PROBLEM: (BCSM40LZ1, 79464) (PATCH ID: OSF440-474)
********
This patch corrects the problem with the mv(1) command deleting files in
the directory when the user moves a directory to itself.


PROBLEM: (BCSM40LZ1, 79464) (PATCH ID: OSF440-466)
********
This patch corrects the problem with the mv(1) command deleting files in 
the directory when the user moves a directory to itself.


PROBLEM: (HPAQB1F1V) (PATCH ID: OSF440-588)
********
This patch fixes a problem in which the "mv" command will not perform
a move if the inode of the file is the same as the inode of the 
destination directory, even though said file and directory reside on different
file systems.