From: Thorsten O. <ad...@th...> - 2017-11-11 14:00:26
|
On Samstag, 11. November 2017 14:11:21 CET Peter Slegg wrote: > I've just joined this new list and was going to post about a timestamp > issue that I had reaised a few years ago. I see there is a discussion > about it all ready. You can view the archive at https://sourceforge.net/p/freemint/mailman/ freemint-discuss/ if you didn't get the whole thread. > On /f there is a file with a timestamp of 19:26 and on /l it is > 20:26. It looks like GMT and BST timeszones. If the drives were attached to different hardware, and you had different timezone settings there, that's possible. > I rsync /f to /l and when rsync checks them it looks like it is > updating the file. However, afterwards the updated file on /l is still > showing 20:26 > > Shouldn't they be identical after rsync ? Hm, don't know. Wouldn't rsync skip the file, if it determines that the contents are the same? At least, the problem we discussed should not occur when copying from FAT to FAT on the same machine. Things might be different if you actually do that over network. > The second issue is that during summer time (BST) the clock (shown in > Multistrip) only shows GMT (BST -1) so I think that the timezone isn't > working. You have to run tzinit during boot time to set up the timezone. And you have to tell it wether your hardware clock is running in local time, or utc. After that, you should run date in a shell to check it, if that does not produce the correct result, you should check wether it is using the correct timezone database. tzinit is part of the mintlib. I'm not sure wether the compiled database is downloadable somewhere, the problem is that you can't create it when cross-compiling, the tools are not prepared for that. There should be some instructions in the tz directory of the mintlib source. Thorsten |