Mailinglist Archive: opensuse (3139 mails)

[James Knott <james.knott@xxxxxxxxxx>]

Carlos E. R. wrote:
> 
> The Sunday 2006-10-29 at 21:35 -0500, James Knott wrote:
> 
>>> Suse 9.1 here and the system internal time is definitely NOT
>>> in UTC. It may have been at install time, but after a little
>>> patience and a lot of beatings I finally got it to work like 
>>> I wanted, which is local time. Since it is all relative anyway,
>>> it makes very little real difference except that I like it better.
>> IIRC, Unix systems generally set the hardware clock to UTC.  However, if
>> you dual boot to Windows, you have to use local time.
> 
> You are confusing terms.
> 
> Which is the "hardware clock" for you?

There is only one hardware clock that I'm aware of and that's the one
built into the mom board.  Yast gives you the option of setting it to
UTC or local time.  What other hardware clock did you have in mind?

> 
> 
> Internal, system, clock is _always_ utc. There is no configuration 
> anywhere to change that, there is no choice at all. This clock is simply a 
> counter maintained by adding a number to it in a program (ie, the kernel).
> 
>    Notice that the time displayed to the user is not the system time.
> 
> The CMOS clock, battery backed, or bios clock, perhaps "hardware clock", 
> can use local or utc, there you have a choice. This clock is read during 
> boot by the operating system to set the system time. If it is utc, then it 
> is straigth away. If the cmos is local, then the utc has to be calculated 
> first, corrected for dls, and the result is used to set system time.
> 
>