2013. február 13. 22:06 napon Andrey Borzenkov
В Wed, 13 Feb 2013 15:00:59 -0500 Greg Freemyer
пишет: On Mon, Feb 11, 2013 at 10:47 PM, Juan R. de Silva
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 :)
I don't understand this. If vfat keeps local time, then that local time should be used as local time. The user knows that it is local time. For example if vfat localtime indicates 2012-07-15 16:31:00 it should be translated and implemented as 2012-07-15 16:31:00 in linux, independently from time zone and daylight saving time. And I, the user know if I look at the file's timestamp, that the given picture was taken in Japan last summer, and the timestamp indicates Japanase summer local time. And that is what I need. The computer does not have to know which local time it is and it doe not not have to change it. The time zone offset you mention does not work. It is used by default, and if you turn it off (tz=UTC option) the timeshift becomes 2 hours. man mount: tz=UTC This option disables the conversion of timestamps between local time (as used by Windows on FAT) and UTC (which Linux uses internally). This is particuluarly useful when mounting devices (like digital cameras) that are set to UTC in order to avoid the pitfalls of local time. Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org