Thus said Andy Goth on Wed, 05 Aug 2015 10:35:56 -0500: > Unix mv would have renamed the directory from dir to dir2, i.e. made > the new directory, moved all files and subdirectories into it, then > removed the old directory.
Slight pedantry (with loose definitions) here... Only under certain circumstances does Unix actually move the files. If the directory rename happens on a single filesystem, then the directory name in the directory entry is simply updated; even in the case where the directory is moved into a different tree, it still retains the same inode and removes the old name from the directory entry and places it into a new directory entry, and no files are actually moved. To the user it might appear that things have ``moved'' but really, just a few inode changes here and there have happened. No data was moved, just metadata (except when the move crosses filesystems). I don't routinely use fossil mv so I don't know how similar its behavior is. Andy -- TAI64 timestamp: 4000000055c2c0e9 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
