Being a person with many preoccupations, I tried to automate the
process this way:
First, I set system time to the NIST standard (presumes I'm
continually on line; if you are not, there's an alternative
command). Then I set the hardware clock to the system time. I do
this by writing a little execu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Jun 19, 2003 at 04:04:35PM -0400, Nori Heikkinen wrote:
> i just reinstalled my system, and now the time is screwed up. it's
> right now 17:02 EDT. set for the US/Eastern time zone, my computer
> thinks it's 9 AM, and that UTC is 13:00. i ca
Nori Heikkinen said on Thu, Jun 19, 2003 at 04:04:35PM -0400:
> i just reinstalled my system, and now the time is screwed up. it's
> right now 17:02 EDT. set for the US/Eastern time zone, my computer
> thinks it's 9 AM, and that UTC is 13:00. i can change the time zone,
> but it's not the zone t
On Thu, 19 Jun 2003 16:04:35 -0400
Nori Heikkinen <[EMAIL PROTECTED]> wrote:
> i just reinstalled my system, and now the time is screwed up. it's
> right now 17:02 EDT. set for the US/Eastern time zone, my computer
> thinks it's 9 AM, and that UTC is 13:00. i can change the time zone,
> but it'
On Thu, 2003-06-19 at 15:04, Nori Heikkinen wrote:
> i just reinstalled my system, and now the time is screwed up. it's
> right now 17:02 EDT. set for the US/Eastern time zone, my computer
> thinks it's 9 AM, and that UTC is 13:00. i can change the time zone,
> but it's not the zone that's wrong
Nori Heikkinen, 2003-Jun-19 16:04 -0400:
> i just reinstalled my system, and now the time is screwed up. it's
> right now 17:02 EDT. set for the US/Eastern time zone, my computer
> thinks it's 9 AM, and that UTC is 13:00. i can change the time zone,
> but it's not the zone that's wrong, it's wha
6 matches
Mail list logo
