From: nunojsilva@ist.utl.pt (Nuno J. Silva)
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Winter clock change did not happen
Date: Sun, 31 Oct 2010 13:27:11 +0000 [thread overview]
Message-ID: <878w1eijbk.fsf@ist.utl.pt> (raw)
In-Reply-To: 201010310924.11434.michaelkintzios@gmail.com
Mick <michaelkintzios@gmail.com> writes:
> I dual boot with MSWindows and therefore have set up my /etc/conf.d/clock to:
>
> CLOCK="local"
> TIMEZONE="Europe/London"
> CLOCK_OPTS=""
> CLOCK_SYSTOHC="no"
> SRM="no"
> ARC="no"
>
> I noticed this morning that the clock was still showing summer time (I rarely
> boot into MSWindows).
Was Linux running since before the time change? I suppose it would at
least show the right time if that was the case. If it works, you still
need CLOCK_SYSTOHC="yes" if you want Linux to change the clock.
Linux has no way to know if the time change was done (nor windows),
unless the systems are syncing with other clock (NTP), so both of them
will boot up and think this "local" time is the winter time.
The systems may still register if they already did the timezone change,
so that they know what to do (that was the case with windows 98).
> I had to boot into MSWindows to check what happens there and the clock was
> showing the new winter time. After that the Linux clock was also showing the
> updated winter time.
>
> Does this mean that twice a year when the clock changes I need to boot into
> MSWindows first to allow the time change to take place, or is there a Linux
> side fix for my dual boot set up?
You can write something so that Linux changes the clock, but then be
sure Windows is not set to change it.
A better (read "more complicated") solution would involve some sync
mechanism between both operating systems so that one can tell if the
other already changed the clock.
Unless windows now supports UTC clocks, you have to live either with
this or with an always on winter clock on windows.
--
Nuno J. Silva
gopher://sdf-eu.org/1/users/njsg
next prev parent reply other threads:[~2010-10-31 13:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-31 9:24 [gentoo-user] Winter clock change did not happen Mick
2010-10-31 9:34 ` Alan McKinnon
2010-10-31 10:05 ` Peter Humphrey
2010-10-31 11:32 ` Mick
2010-10-31 12:01 ` Peter Humphrey
2010-10-31 12:56 ` Stéphane Guedon
2010-10-31 13:29 ` [gentoo-user] " Nuno J. Silva
2010-10-31 13:43 ` Mick
2010-10-31 16:02 ` Nuno J. Silva
2010-10-31 16:21 ` Mick
[not found] ` <87wroymh0b.fsf@newton.gmurray.org.uk>
2010-10-31 17:24 ` Mick
2010-10-31 20:08 ` Kevin O'Gorman
2010-10-31 22:24 ` Willie Wong
2010-11-01 6:38 ` Mick
2010-11-01 13:22 ` Grant Edwards
2010-10-31 16:18 ` Nuno J. Silva
2010-10-31 17:09 ` Mick
2010-10-31 22:08 ` [gentoo-user] " Alan McKinnon
2010-10-31 13:27 ` Nuno J. Silva [this message]
2010-10-31 13:50 ` [gentoo-user] " Mick
2010-10-31 16:12 ` Nuno J. Silva
2010-10-31 16:35 ` [gentoo-user] " Jacob Todd
2010-10-31 17:55 ` Stéphane Guedon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878w1eijbk.fsf@ist.utl.pt \
--to=nunojsilva@ist.utl.pt \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox