LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Desktop
User Name
Password
Linux - Desktop This forum is for the discussion of all Linux Software used in a desktop context.

Notices


Reply
  Search this Thread
Old 05-28-2018, 11:40 PM   #1
joboy
Member
 
Registered: Jul 2009
Distribution: Debian, Ubuntu, Puppy, Mint
Posts: 655

Rep: Reputation: 7
Time clock setting problem


Hi there,


I am running Mint Debian dualboot with win8 and got an annoying problem. I set the correct location during installation, but everytime I boot windows the time will change to UTC, I don't see how I can change the time zone. After searching for answer I found this, a 7yrs. old bug still exist today !



https://community.linuxmint.com/tutorial/view/275
 
Old 05-28-2018, 11:52 PM   #2
273
LQ Addict
 
Registered: Dec 2011
Location: UK
Distribution: Debian Sid AMD64, Raspbian Wheezy, various VMs
Posts: 7,680

Rep: Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373
That's not a Mint bug, it's a Windows bug -- Windows, unless modified, insists that the real time clock be set to local time rather than UTC. The fix is stated on the linked page and is to set a Windows registry value allowing it to use UTC.
I can only speculate that the bug stems from when DOS was written and a naive customer might have been confused by a system clock set to UTC so the writer of DOS decided to set the RTC to local time to avoid this. Seems that there's at least one place where they're asking for this to be changed.
 
Old 05-28-2018, 11:56 PM   #3
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 21,126

Rep: Reputation: 4120Reputation: 4120Reputation: 4120Reputation: 4120Reputation: 4120Reputation: 4120Reputation: 4120Reputation: 4120Reputation: 4120Reputation: 4120Reputation: 4120
The "bug" is called Windows.

UTC/GMT has been used as the basis for common time reference since the concept was invented.
Microsoft chose to ignore the world and use local time.
 
Old 05-29-2018, 01:51 AM   #4
ondoho
LQ Addict
 
Registered: Dec 2013
Posts: 19,872
Blog Entries: 12

Rep: Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053
it's not a Linux bug.
and AFAIK, many Linux distros even accomodate Dual booters, by offering an option to set the hardware clock to local time.
so there's 2 solutions, 1 for each operating system.
 
Old 05-29-2018, 02:26 PM   #5
AwesomeMachine
LQ Guru
 
Registered: Jan 2005
Location: USA and Italy
Distribution: Debian testing/sid; OpenSuSE; Fedora; Mint
Posts: 5,524

Rep: Reputation: 1015Reputation: 1015Reputation: 1015Reputation: 1015Reputation: 1015Reputation: 1015Reputation: 1015Reputation: 1015
You can change linux's interpretation of the system clock with 'timedatectl'.
 
Old 05-29-2018, 11:45 PM   #6
joboy
Member
 
Registered: Jul 2009
Distribution: Debian, Ubuntu, Puppy, Mint
Posts: 655

Original Poster
Rep: Reputation: 7
Thank guys for the input. I mainly run Linux and occasionally dualboot to Windows, I already set local time reference on Debian, but it changed the BIOS to UTC time, windows is not to blame in this case, and windows did not always time sync to correct the error, or until after a long delay, I mainly use Debian so no idea how other distro works.
 
Old 05-30-2018, 11:44 AM   #7
DavidMcCann
LQ Veteran
 
Registered: Jul 2006
Location: London
Distribution: PCLinuxOS, Debian
Posts: 6,142

Rep: Reputation: 2314Reputation: 2314Reputation: 2314Reputation: 2314Reputation: 2314Reputation: 2314Reputation: 2314Reputation: 2314Reputation: 2314Reputation: 2314Reputation: 2314
As you can see, it's possible to change Windows to be like Linux or Linux to be like Windows. The difference is a matter of history.

Linux is intended to work like Unix, which started on 1960s mainframes. Since few companies could afford one, many used a computer bureau — like cloud computing. In the USA, that meant that the mainframe and the users terminal could be in different time zones or switch to daylight saving on different dates. To to avoid chaos, everyone used GMT/UTC.

Windows, of course, was a successor to MS-DOS. In the early 1980s, desktop computers did not come with batteries. When I switched on my computer, the first thing it did was to ask me to enter the date and time. Naturally, it expected the user to consult their watch — and not to convert to UTC!
 
Old 05-30-2018, 12:00 PM   #8
273
LQ Addict
 
Registered: Dec 2011
Location: UK
Distribution: Debian Sid AMD64, Raspbian Wheezy, various VMs
Posts: 7,680

Rep: Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373
Quote:
Originally Posted by joboy View Post
Thank guys for the input. I mainly run Linux and occasionally dualboot to Windows, I already set local time reference on Debian, but it changed the BIOS to UTC time, windows is not to blame in this case, and windows did not always time sync to correct the error, or until after a long delay, I mainly use Debian so no idea how other distro works.
Debian and, by extension, Mint's setting for "system clock is local time" may or may not be buggy but that is just a workaround for the intrinsic Windows bug. I don't know what Apple do about time but they, too, have publicly messed it up also.
The only way to deal with timne correctly is using UTC and converting for user convenience when necessary. I'll link to this again:
https://www.cl.cam.ac.uk/~mgk25/mswish/ut-rtc.html
Time is tough but the Microsoft approach is brain-dead.
Apologies for ranting but it really is pqathetic stuff like this which cause needless problems all over the place and this is one of the obvious examples os where sticking to "user friendly" is hurting everyone.
 
Old 05-31-2018, 03:17 AM   #9
joboy
Member
 
Registered: Jul 2009
Distribution: Debian, Ubuntu, Puppy, Mint
Posts: 655

Original Poster
Rep: Reputation: 7
Understand, time clock difference would not be a problem if I did not dualboot, but more of a problem if I dualboot and access those high security server with time limited access and the auto time sync did not catch up quick enough.
 
Old 06-01-2018, 12:07 AM   #10
ondoho
LQ Addict
 
Registered: Dec 2013
Posts: 19,872
Blog Entries: 12

Rep: Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053
have you tried the windows fix outlined in post #2?
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
TrueOS time clock setting joboy *BSD 6 03-10-2017 09:34 AM
hardware clock time differs from system time after setting maxgsp Linux - Software 2 02-28-2009 07:15 AM
hardware clock time differs from system time after setting maxgsp Linux - Hardware 1 02-27-2009 05:24 AM
Setting the system clock to a time server? orange400 Linux - General 4 06-13-2005 01:59 PM
Setting the computer clock according to a time server on the internet didi86 Linux - Software 11 10-05-2004 08:52 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Desktop

All times are GMT -5. The time now is 12:41 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration