Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Time errors

Received: by 10.66.88.200 with SMTP id bi8mr3493355pab.27.1352136136000;
        Mon, 05 Nov 2012 09:22:16 -0800 (PST)
Path: s9ni81180pbb.0!nntp.google.com!npeer03.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!post01.iad.highwinds-media.com!newsfe15.iad.POSTED!not-for-mail
Newsgroups: alt.os.linux.suse
From: unruh <un...@invalid.ca>
Subject: Re: Time errors
References: <jcGdnUZ1cfe_3BbNnZ2dnUVZ_u-dnZ2d@giganews.com>
 <chmjs.4836$pn7.60@newsfe18.iad>
 <m6GdnapM0bQU4BPNnZ2dnUVZ_t-dnZ2d@giganews.com>
 <508f22f1$19$fuzhry+tra$mr2ice@news.patriot.net>
 <te6dnSJ0sKrM-BLNnZ2dnUVZ_q2dnZ2d@giganews.com>
 <TTKjs.7609$lD4.3845@newsfe24.iad>
 <arSdnYmmIpk5aRLNnZ2dnUVZ_vednZ2d@giganews.com>
 <znTjs.15058$2Q3.12034@newsfe25.iad>
 <vuedndEPkqPIgQ3NnZ2dnUVZ_sCdnZ2d@giganews.com>
 <EZVjs.12718$Be.9900@newsfe13.iad>
 <69mdne9GyuXe0Q3NnZ2dnUVZ_t6dnZ2d@giganews.com>
 <50919d6f$11$fuzhry+tra$mr2ice@news.patriot.net>
 <mf-dna95U9rMMQzNnZ2dnUVZ_r2dnZ2d@giganews.com>
 <5093b84f$7$fuzhry+tra$mr2ice@news.patriot.net>
 <6LednU6gIpbKqQnNnZ2dnUVZ_vOdnZ2d@giganews.com>
 <50959953$1$fuzhry+tra$mr2ice@news.patriot.net>
 <ysednRUtD_3S4AvNnZ2dnUVZ_omdnZ2d@giganews.com>
 <50972e04$35$fuzhry+tra$mr2ice@news.patriot.net>
 <fc6dnahHR9udRwrNnZ2dnUVZ_jmdnZ2d@giganews.com>
User-Agent: slrn/0.9.9p1 (Linux)
Mime-Version: 1.0
Lines: 24
Message-ID: <bBSls.9847$kP4.9510@newsfe15.iad>
NNTP-Posting-Host: 24.84.110.223
X-Complaints-To: internet.abuse@sjrb.ca
X-Trace: 1352136135 24.84.110.223 (Mon, 05 Nov 2012 17:22:15 UTC)
NNTP-Posting-Date: Mon, 05 Nov 2012 17:22:15 UTC
Date: Mon, 05 Nov 2012 17:22:15 GMT
X-Received-Bytes: 2606
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

On 2012-11-05, bad sector <forgetski@postit_INVALID_.gov> wrote:
> On 11/04/2012 10:09 PM, Shmuel (Seymour J.) Metz wrote:
>
>> If facts and logic won't change your opinion then I doubt that the
>> developers will value it any more than I do.
>
> They can do real polls of real people to discover if there's a demand 
> for what they want to implement instead of listening to voices coming 
> from 'the cloud'.

As you have finally discovered, it was a configuration error. Whether it
was yours or theirs is irrelevant. If it was theirs they obviously felt
that for their clientel, that UTC=no was a more reasonable configuration
than was UTC=yes (eg lots of dual booting with Windows). They may have
been wrong in thier feelings, but that does not alter the fact that it
was a simply configuration error. And you were mistaken in your
impression of how the hardware clock worked. The system uses it to set
the system time at bootup, and sets the rtc from the system time on
shutdown. Whether that is how you would like it is really irrelevant.


>
>
>