Hi!
> Storing this as a file attribute is not a simple problem, for
>instance if you move to a bigger disk and rsync everything over you
>almost certainly don't want the creation time to now be "creation
>time, or when I moved stuff to my new HD".
> But in the same vein if it's arbitrary data ... you might as well
>store it somewhere else, like inside the file itself (or an extended
>attribute).
Understood, but not agreed. I guess I need to take this up with the
filesystem developers.
> For instance with digital photos there is probably creation time in
>the photo itself:
>
>% exiftime -t ~/pics/Public/Cats/Catzilla/catzilla\ brave.jpg
>Image Created: 2002:06:19 21:54:03
>% stat --printf 'mtime: %y\nctime: %z\n'
>~/pics/Public/Cats/Catzilla/catzilla.jpg
>mtime: 2002-07-29 19:33:24.000000000 -0400
>ctime: 2006-06-09 17:08:15.000000000 -0400
Now, wouldn't that be something! I just wonder how to do this via
PHP....mhhhh, googling....
> > Using PHP, filectime gives me the changed time whereas filemtime
> > gives the file modified time. So, what is the difference between
> > changed and modified? Is that a difference that applies only to *n*x
> > systems?
>
>http://www.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap04.html#tag_04_07
>
> The simple rule of thumb is that if you are altering the data, mtime
>is updated but if you are altering the metadata ctime is updated
>(note that making the file bigger does both, as it's size changes).
Thanks for the info. I guess it is just the way it is and probably will
stay like that. So I better adjust.
David K.
More information about the ECLUG mailing list