Nihal Singh
Mar 30, 2018, 11:49:26 AM3/30/18
to Web and Coding Club IIT Bombay
Hello,
The system time often gets messed up when switching between different operating systems on a multi-boot machine and since IITB blocks all other NTP servers (except its own- ntp.iitb.ac.in), correcting this automatically becomes difficult.
With a couple of scripts and an alternate Windows Time Service solution to fix this problem, this blog post might be helpful-
https://nihal111.github.io/2018/03/30/ntp-update-time.html
Further, from the Official Ubuntu documentation, this explains well what makes the system time go haywire when dual booting with Windows.
In a gist, Linux/Unix systems store UTC as the time on the hardware clock and with good reason, since this saves unnecessary changes to the hardware clock when moving between timezones.
On the other hand, Windows stores the local time as the time on the hardware clock. This ends up messing with the system time since both OS deal with the hardware clock differently.
The above link also explains a registry solution to solve the issue, which makes Windows write UTC as the time on the hardware clock or alternatively make Linux save local time on the hardware clock.
Hope this helps someone.
--
Regards,
Nihal Singh,
Manager,
WnCC
The system time often gets messed up when switching between different operating systems on a multi-boot machine and since IITB blocks all other NTP servers (except its own- ntp.iitb.ac.in), correcting this automatically becomes difficult.
With a couple of scripts and an alternate Windows Time Service solution to fix this problem, this blog post might be helpful-
https://nihal111.github.io/2018/03/30/ntp-update-time.html
Further, from the Official Ubuntu documentation, this explains well what makes the system time go haywire when dual booting with Windows.
In a gist, Linux/Unix systems store UTC as the time on the hardware clock and with good reason, since this saves unnecessary changes to the hardware clock when moving between timezones.
On the other hand, Windows stores the local time as the time on the hardware clock. This ends up messing with the system time since both OS deal with the hardware clock differently.
The above link also explains a registry solution to solve the issue, which makes Windows write UTC as the time on the hardware clock or alternatively make Linux save local time on the hardware clock.
Hope this helps someone.
--
Regards,
Nihal Singh,
Manager,
WnCC
Reply all
Reply to author
Forward
0 new messages