Mailinglist Archive: opensuse (3139 mails)

["Carlos E. R." <robin.listas@xxxxxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


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?


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.


- -- 
Cheers,
       Carlos E. R.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Made with pgp4pine 1.76

iD8DBQFFRePvtTMYHG2NR9URAhHjAJ4ohWc8v99vsAv6LVpEYSx4aKJSHwCeOX2v
jR+i9JwoCJHRvCZ68wsp8dw=
=J73Z
-----END PGP SIGNATURE-----