![]() ![]() It has a new inode location, and it is subject to your active umask. The cp command, unlike mv, creates a brand new data object in your filesystem. The philosophical intent of this design is to ensure that, should a move fail, a file is not left in pieces. Move actions are now either attribute reassignments (an inode now points to a different location in your file organization) or amalgamations of a copy action followed by a remove action. ![]() This behavior has largely fallen out of favor. On some systems, the move action is a true move action: Bits are removed from one point in the file system and reassigned to another. That’s the way the mv tool is programmed to move a file: Leave the inode unchanged (unless the file is being moved to a different filesystem), and preserve its ownership and permissions.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |