Michael Reinsch wrote:
> What is in your /etc/sysconfig/clock? UTC should not be set to true.
Nope, it's set to "false". While poor at kernel compiling, I've got my
config files more or less down pat. :)
> > In my opinion, if this is something that's "broken" at kernel config
> > level, no band-aid fixes with scripts (whether it works or not) is the
> > correct solution.
>
> Well, as this stuff can be handled in user space, why handle them in
> kernel space? The kernel apparently doesn't know enough to handle this
> correctly. That at least is my opinion.
Well, it can handle it. The problem is that the kernel -- at *compile*
time -- has things set on or off. That's reflective of server thinking, not
what's needed for desktop users ("laptop" for now, but most systems have
some sort of power savings). I can hardly blame them, but it seems that it
would be better to have it at a module level.
Besides, in essence this is for people who have multiple (mixed) boots. I'm
soon going to be Linux-only on my laptop, so I'll simply move to GMT on the
hardware clock.
> But it doesn't really matter for the user, so let's try and get this
> fixed the easiest way.
I definitely agree. I guess I'm not a fan of a script correcting something
whose cause could be avoided. On the other hand, I'm beginning to think that
it might be the best way available at the moment. Otherwise, the Mandrake
installer/DrakConf would have to keep two copies of the kernel on hand for
the moment the user changes this setting. This is hardly optimal, and
compilation solutions carried to their extreme lead to Gentoo...
> The main question currently imho is: why does this script not set
> correct time. Maybe there is a bug in hwclock? Could you maybe try
> executing hwclock the same way it is executed by the script? Maybe you
> could also add a line logging the way hwclock is executed by the script.
The execution of hwclock is pretty much vanilla. I can manually execute the
installed "hibernate", but the machine doesn't turn off. But on the good
side, the verbose output confirms that the system clock is reset from the
hwclock with non-GMT. If I didn't need for my machine to turn off, that
would be prefect. :)
Using my "suspend" key on the keyboard is how I go into the mode, and waking
up seems to properly execute *something*. I'm beginning to wonder if some
detail(s) is/are missing in the messages sent to the system by the BIOS.
You wrote some time back, but I wanted to take a moment now that I had one
to reply. In the end, I'm beginning to think I'll take the path of least
resistance and just "solve" it by doing what I intended once Linux-only and
set the hwclock to UTC.
- John
