| 1 |
Apparently, though unproven, at 11:24 on Sunday 31 October 2010, Mick did |
| 2 |
opine thusly: |
| 3 |
|
| 4 |
> I dual boot with MSWindows and therefore have set up my /etc/conf.d/clock |
| 5 |
> to: |
| 6 |
> |
| 7 |
> CLOCK="local" |
| 8 |
> TIMEZONE="Europe/London" |
| 9 |
> CLOCK_OPTS="" |
| 10 |
> CLOCK_SYSTOHC="no" |
| 11 |
> SRM="no" |
| 12 |
> ARC="no" |
| 13 |
> |
| 14 |
> I noticed this morning that the clock was still showing summer time (I |
| 15 |
> rarely boot into MSWindows). |
| 16 |
> |
| 17 |
> I had to boot into MSWindows to check what happens there and the clock was |
| 18 |
> showing the new winter time. After that the Linux clock was also showing |
| 19 |
> the updated winter time. |
| 20 |
> |
| 21 |
> Does this mean that twice a year when the clock changes I need to boot into |
| 22 |
> MSWindows first to allow the time change to take place, or is there a Linux |
| 23 |
> side fix for my dual boot set up? |
| 24 |
|
| 25 |
gut feel tells me windows is broken. |
| 26 |
|
| 27 |
All my calendars (electronic and dead-tree) tell me that daylight savings |
| 28 |
switches at the END of today not at the beginning |
| 29 |
|
| 30 |
|
| 31 |
-- |
| 32 |
alan dot mckinnon at gmail dot com |
Archives