On Wed, Feb 13, 2013 at 4:06 PM, Andrey Borzenkov <arvidjaar@gmail.com> wrote:
В Wed, 13 Feb 2013 15:00:59 -0500 Greg Freemyer <greg.freemyer@gmail.com> пишет:
On Mon, Feb 11, 2013 at 10:47 PM, Juan R. de Silva <juan.r.d.silva@gmail.com> wrote:
My preferred workaround for the VFAT problem is avoiding use of VFAT.
Unfortunately it may not always depend of a user. E.g. I recently get hit by this bug trying to copy files from my Olympus Voice Recorder to my system.
I still would like to know if there is a bugzilla against this. If there is, I might take a shot at fixing it.
How are you going to fix it? VFAT keeps timestamp in local time. There is no way to know, *which* local time it is. So whatever you do will be wrong for some cases. At the best, you can extend UTC mount option to use timezone offset in case you know from where your USB stick comes from :)
Andrey, Since there was not a opensuse bugzilla entry, I didn't take the time to even check what the issue is. I just kept seeing a reference to a "bug". I took that to mean the linux implementation of something was broken. If the only "bug" is the decision 30 years ago to have FAT based on localtime, then obviously there is nothing that can be done now. fyi: I use FAT analysis software for my day job the allows me to put in the display timezone, and 2 sets of dst settings, and a arbitrary date to control which set of dst settings to use. Thus I can tell it that the filesystem is FAT and that the times were recorded as EST localtime and what the current laws are for DST transition and what they were 10 years ago, and when the law changed. I guess, I was assuming linux offered similar timestamp translation and that there was a bug in translation. Greg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org