Bug#57726: Still present in 2.2.7

[karlheg@bittersweet.inetarena.com (Karl M. Hegbloom)]

>>>>> "Santiago" == Santiago Vila <sanvila@unex.es> writes:

    Santiago> More info about this bug: I've tested the "mv" command from
    Santiago> 2.2.7-2000-02-13 with the following results:

    Santiago> * It seems fixed when using "mv" from a /mnt-mounted root.bin file
    Santiago> on a potato system. I can't no longer reproduce the strange behaviour
    Santiago> as explained in the bug report.

 Good.

    Santiago> * It still does strange things when used within the boot floppies.
    Santiago> To test the boot floppies I usually switch to the second virtual console,
    Santiago> mount under /mnt the partition where I have my normal development system
    Santiago> and do the following:

    Santiago> cd /mnt
    Santiago> mkdir BACKUP
    Santiago> mv * BACKUP

 Uh... you `cd /mnt', then `mv * BACKUP'???  I think it's doing what
 you tell it to do.  Don't you want to instead `mkdir /mnt/BACKUP',
 then `cd /', `cp -a ... /mnt/BACKUP', using a list of directories
 rather than a glob so that you don't try to copy /proc?

    Santiago> Today, "mv" behaved as a cp -a and my disk becomed full. It does not
    Santiago> work properly either when renaming a directory into something else
    Santiago> (it produces a lot of disk activity when doing this).

 This is known and expected with the current version of `cp_mv.c' in
 busybox.  `mv' always does a recursive copy rather than calling
 `rename()' right now.  I have plans to fix this, and also to make
 both `mv' and `cp' preserve hard link structure the way the GNU
 shellutils does.  Give me a week or so.