I hope you realize that VFAT file systems don't have a ctime.
Under Unix, ctime is defined as the last change to inode time. It
gets set when ever one does a chown(), chmod(), link(), touch, etc.
Here are the times associated with a file:
Unix:
mtime Last date/time modified
ctime Last date/time of inode change
atime Last date/time accessed
DOS/Win* (gleaned by reading FreeBSD OS sources):
MDate Last date modified
MTime Last time of day modified
CDate Creation date
CTime Creation time of day
ADate Last date accessed
[Note: I can't find any ATime in the code]
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.
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, ?????
Chris Karakas wrote:
>
> Martin Brown wrote:
> > > How do I change the ctime of a vfat file?
> > try moving it
>
> Sorry, I've tried it, but this does not change the *ctime* of a vfat
> file. Check with ls -lc to see yourself. Any other ideas?
>
> --
> Regards
>
> Chris Karakas
> Donīt waste your cpu time - crack rc5: http://www.distributed.net
--
Gary Algier, WB2FWZ [EMAIL PROTECTED] +1 856 787 2758
Ulticom Inc., 1020 Briggs Rd, Mt. Laurel, NJ 08054 Fax:+1 856 866 2033
This space intentionally left blank by the censors.