1 |
Mick <michaelkintzios@×××××.com> writes: |
2 |
|
3 |
> I dual boot with MSWindows and therefore have set up my /etc/conf.d/clock to: |
4 |
> |
5 |
> CLOCK="local" |
6 |
> TIMEZONE="Europe/London" |
7 |
> CLOCK_OPTS="" |
8 |
> CLOCK_SYSTOHC="no" |
9 |
> SRM="no" |
10 |
> ARC="no" |
11 |
> |
12 |
> I noticed this morning that the clock was still showing summer time (I rarely |
13 |
> boot into MSWindows). |
14 |
|
15 |
Was Linux running since before the time change? I suppose it would at |
16 |
least show the right time if that was the case. If it works, you still |
17 |
need CLOCK_SYSTOHC="yes" if you want Linux to change the clock. |
18 |
|
19 |
Linux has no way to know if the time change was done (nor windows), |
20 |
unless the systems are syncing with other clock (NTP), so both of them |
21 |
will boot up and think this "local" time is the winter time. |
22 |
|
23 |
The systems may still register if they already did the timezone change, |
24 |
so that they know what to do (that was the case with windows 98). |
25 |
|
26 |
> I had to boot into MSWindows to check what happens there and the clock was |
27 |
> showing the new winter time. After that the Linux clock was also showing the |
28 |
> updated winter time. |
29 |
> |
30 |
> Does this mean that twice a year when the clock changes I need to boot into |
31 |
> MSWindows first to allow the time change to take place, or is there a Linux |
32 |
> side fix for my dual boot set up? |
33 |
|
34 |
You can write something so that Linux changes the clock, but then be |
35 |
sure Windows is not set to change it. |
36 |
|
37 |
A better (read "more complicated") solution would involve some sync |
38 |
mechanism between both operating systems so that one can tell if the |
39 |
other already changed the clock. |
40 |
|
41 |
Unless windows now supports UTC clocks, you have to live either with |
42 |
this or with an always on winter clock on windows. |
43 |
|
44 |
-- |
45 |
Nuno J. Silva |
46 |
gopher://sdf-eu.org/1/users/njsg |