Re: Bug in fat-fs code: file date/time wrong

Peter Samuelson (peter@wire.cadcamlab.org)
Mon, 15 Nov 1999 00:45:58 -0600 (CST)

[Joe Zbiciak]
> Edgar pointed out the real problem that I had missed: You need to
> figure out if DST was active for each file based on its timestamp.
> Duh. I feel pretty stupid now for not having realized that.

Hmmmmmm ... maybe I'm missing something, but it seems to me that (as
others never fail to point out whenever Linux-specific FAT behavior
comes up) the only raison d'être for FAT is compatibility with legacy
systems. In this case you care about seeing the same timestamps as
these systems.

So, what do legacy systems do?

Extremely limited testing with NT4 vs. mtools suggests that the legacy
system I have seems to use the *current* DST setting -- or, more to the
point, reads and writes timestamps in reference to *current* wall clock
time, *not* correcting for whether DST was in effect at the file's
mtime.

So Linux FAT should do the same. It breaks Unix semantics, but FAT
never was about Unix semantics in the first place.

-- 
Peter Samuelson
<sampo.creighton.edu!psamuels>


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