On Sat 13 Oct 2018 at 07:27:57 (+0000), Long Wind wrote: > Thank Teemu Likonen! > You are right. My stretch and jessie think differently about hardware clock. > i run "timedatectl set-local-rtc 1", it should be ok for both now. > though there's warning, i think it's ok
Because China doesn't use Daylight Savings Time nowadays, your choice between UTC and local time is less important than for most as your clock doesn't have to be changed twice a year. For everyone else, it makes a lot more sense to use UTC for the real time clock. Also, judging by my experience on this dual-booting system (W10 and Debian), up-to-date Windows systems can handle hardware clocks set to UTC (just as we can cope with your emails being timestamped with UTC!). If you apply the same logic to any devices you have that are unaware of timezones (like many cameras) and set them to UTC, then it will help with keeping all the file timestamps correct as well. This avoids having to work out all the ramifications spelled out by pages like https://msdn.microsoft.com/en-us/library/windows/desktop/ms724290(v=vs.85).aspx https://msdn.microsoft.com/en-us/library/windows/desktop/ms724290\(v=vs.85\).aspx > On Saturday, October 13, 2018 3:10 PM, Teemu Likonen <tliko...@iki.fi> > wrote: > Long Wind [2018-10-12 21:59:40Z] wrote: > > > jessie and stretch are installed on same PCtime of jessie is wrong: > > Fri Oct 12 21:51:05 CST 2018then i reboot and enter stretch time of > > stretch is right: Sat Oct 13 05:55:30 CST 2018 tzdata of both are > > reconfig to same place > > As others have pointed out probably one operating system thinks that the > hardware clock is in UTC time and other thinks the clock is in local > time. > > You can check and configure this with "timedatectl" command. Running the > command without parameters will show the current status. Command > "timedatectl set-local-rtc [...]" (executed as root user) sets the > option in question. Command's man page tells more. Cheers, David.
