Re: mv command wierdness. (error in VFS?)

Tom Eastep (eastep@loc1.tandem.com)
Thu, 17 Dec 1998 23:48:23 +0000


Chris Wedgwood wrote:
>
> On Thu, Dec 17, 1998 at 09:15:33PM +0000, Tom Eastep wrote:
>
> > Assuming that mv used rename(2), POSIX says that only the parent
> > directory's ctime and mtime should have been updated.
>
> Why ctime -- and why not atime?
>
> -cw

Well, I was just paraphrasing from POSIX.1. The rational is roughly as
follows:

An inode's ctime gets updated any time the inode is modified (think of
it as the modification time for the inode itself; thus ctime gets
updated any time that mtime changes). Unless overridden with a mount
option, the parent directory's atime _would_ have been updated during
pathname resolution (although POSIX doesn't require this, it's done
under Linux).

-Tom

-- 
Tom Eastep
Compaq Computer Corporation
Enterprise Computing Group
Tandem Division
tom.eastep@compaq.com

- 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/