Windows is saving time in Local Time, while Ubuntu (and mint) in UTC, so solution is to make one of them use the other one's format.
For ubuntu its a simple solution
Code: Select all
timedatectl set-local-rtc 1
Code: Select all
timedatectl set-local-rtc 1
If the Linux Mint installer does Not give you that option it should... perhaps it is there but not too clear.FrostyRussian wrote: ⤴Tue May 01, 2018 10:24 amSince we already have Windows installed, and we are right now installing Linux, change should happen in Linux and not Windows.
If you prefer it this way this does not mean, that everybody will like it this way. There might be the case, that the user has changed it in Windows already, in this case it would be bad idea.FrostyRussian wrote: ⤴Tue May 01, 2018 10:24 am Since we already have Windows installed, and we are right now installing Linux, change should happen in Linux and not Windows.
I dont prefer it this or that way, its all the same to me, a simple command in linux or reg file in windows (notepad/sublime or any other IDE) - it may take me a few minutes to find exact command or registry content (depending on where im gonna do it) but it wont make any difference for me.Cosmo. wrote: ⤴Tue May 01, 2018 4:19 pmIf you prefer it this way this does not mean, that everybody will like it this way. There might be the case, that the user has changed it in Windows already, in this case it would be bad idea.FrostyRussian wrote: ⤴Tue May 01, 2018 10:24 am Since we already have Windows installed, and we are right now installing Linux, change should happen in Linux and not Windows.
Code: Select all
# dpkg-reconfigure tzdata
Current default time zone: 'America/Tijuana'
Local time is now: Wed May 2 19:07:07 PDT 2018.
Universal Time is now: Thu May 3 02:07:07 UTC 2018.
The question may sound(!) simple, but I bet every amount, that a huge number would not know, what and why to select. We would see numerous question about the criteria for this or that choice. Those questions in the forum are not a real problem. The real problem is, that the user does not get further in the installation process, because the installer would wait for the answer and the user does not know, what to choose.FrostyRussian wrote: ⤴Wed May 02, 2018 8:14 pm Asking a simple question whether user wants to use Local or UCT
There is nothing simple about time. Even Linux gets it wrong.Cosmo. wrote: ⤴Thu May 03, 2018 5:28 amThe question may sound(!) simple, but I bet every amount, that a huge number would not know, what and why to select. We would see numerous question about the criteria for this or that choice. Those questions in the forum are not a real problem. The real problem is, that the user does not get further in the installation process, because the installer would wait for the answer and the user does not know, what to choose.FrostyRussian wrote: ⤴Wed May 02, 2018 8:14 pm Asking a simple question whether user wants to use Local or UCT
Unfortunately not all that simple: keeping the RTC on local time creates a few unsolvable issues specifically/especially in light of DST. RTC on UTC or local time is not a matter of equally valid choices: the Windows choice is the technically worse one. For a generic description of the issue(s) see for example http://www.cl.cam.ac.uk/~mgk25/mswish/ut-rtc.html.
We've seen previous topics on the forums here about for example pictures on a FAT-formatted SD card from a digital camera now showing incorrect timestamps due to this. Initially opinions might be seen to legitimately vary and certainly systemd has a very worrying tendency to dump its issues on everyone else, but once you investigate you do in fact quickly come to the conclusion that RTC on local really is the technically wrong choice and should not be made without the user explicitly telling you that he's fine with technically wrong choices just to appease Windows.systemd will no longer inform the kernel about the current timezone, as this is necessarily incorrect and racy as the kernel has no understanding of DST and similar concepts. This hence means FAT timestamps will be always considered UTC, similar to what Android is already doing. Also, when the RTC is configured to the local time (rather than UTC) systemd will never synchronize back to it, as this might confuse Windows at a later boot.
Windows is a problem because it came from DOS. Back when Microsoft started, computers weren't connected to the internet. So, time was kept as local time. Windows kept the DOS conventions so the file times would be the same. But now, it has become a problem.FrostyRussian wrote: ⤴Thu May 03, 2018 6:37 pmAnd we ALL know that Windows (read microsoft) is a problem, if it wasnt we wouldnt be here discussing these