Gary Algier wrote:
>
> I hope you realize that VFAT file systems don't have a ctime.
>
That's how they are constructed. But when I mount a vfat filesystem, it
_has_ to get some (even fictitious) ctime, doen't it? And indeed, this
is the case. If you mount a vfat filesystem and check with ls -lc", you
will see the associated ctimes.
> So, the real question is, what does the OS do when someone does
> a touch (obvious chown, link, etc, won't work)? Since the DOS/Win*
> idea of ctime is the creation time, I don't think it should change.
>
> Therefore, there should be no way to change the ctime.
>
But we have just found one (see previous posting):
touch -a <file>
where <file> belongs to a mounted vfat filesystem. I see that with this
the mtime remains unchanged and the ctime is changed to the current
time.
> If one does make CDate/CTime writable, what does DOS/Win* do when
> the creation time is newer than the access or modify time? This
> should never happen, but if Unix can set it, ?????
>
Oops...I don't know. And I was just in the process of setting the ctime
from 2035 (where it was somehow - how? can you explain this? - set) back
to 2000. Maybe I should go for certain and set it back to 1935... :-)
--
Regards
Chris Karakas
Don´t waste your cpu time - crack rc5: http://www.distributed.net
