> At the moment, rename()ing something on an ext2 filesystem will update
> the inode ctimes of the directory or directories it was in or moved
> between, but it doesn't update the inode ctime of the renamed thing
> itself.
>
> On most other systems with a kernel rename(), it appears to update
> the rename()'d object's inode ctime.
[7am uncaffeinated disclaimer applies to the following]
Why should the inode's ctime be changed? Nothing is actually happening to the
inode, it's just directory contents which are being altered. Though by that
logic the directory mtime should be changed, not the ctime. Uhhuh. I'm going
to go back to sleep for a bit ;-)
-- QOTD: "Sure, I turned down a drink once. Didn't understand the question."- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/