From: Beso <givemesugarr@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Problem with latest timezone update?
Date: Thu, 17 Jan 2008 20:02:35 +0000 [thread overview]
Message-ID: <d257c3560801171202t593bb352pc2637ab246884bb0@mail.gmail.com> (raw)
In-Reply-To: <002c01c8592d$506ab530$0200a8c0@iwillxp333>
[-- Attachment #1: Type: text/plain, Size: 897 bytes --]
i personally have the clock set to UTC and have kde clock set to local. this
in my opinion is the best choice and i think that every hw clock should be
set to UTC since it represents the computers' time in my opinion. every date
calculation is made converting to UTC and calculating the difference between
the UTC and the impute date converted. this is the right way to handle dates
and this, in my opinion, is the reason to why set the clock to the UTC.
2008/1/17, Drake Donahue <donahue95@comcast.net>:
>
> OOPS and duh!
> Just reread your original!
> You want to be on universal time!
> Abject apologies and nevermind.
>
> As I read /etc/init.d/clock, setting CLOCK="UTC" should make
> /etc/localtime
> irrelevant and unused.
> If you are still having problems after the Los_Angeles change maybe
> TIMEZONE="UTC" ?
>
> --
> gentoo-amd64@lists.gentoo.org mailing list
>
>
--
dott. ing. beso
[-- Attachment #2: Type: text/html, Size: 1251 bytes --]
next prev parent reply other threads:[~2008-01-17 20:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-15 15:22 [gentoo-amd64] Problem with latest timezone update? Mark Haney
2008-01-15 16:45 ` Beso
2008-01-15 17:01 ` Drake Donahue
2008-01-16 13:09 ` Mark Haney
2008-01-16 17:49 ` Mark Knecht
2008-01-16 17:57 ` Mark Knecht
2008-01-16 19:33 ` Beso
2008-01-16 23:01 ` Steev Klimaszewski
2008-01-17 0:56 ` Drake Donahue
2008-01-17 1:37 ` Mark Knecht
2008-01-17 10:15 ` Nicolas Litchinko
2008-01-17 12:36 ` Peter Humphrey
2008-01-17 15:08 ` Mark Knecht
2008-01-17 15:53 ` Drake Donahue
2008-01-17 17:20 ` Drake Donahue
2008-01-17 20:02 ` Beso [this message]
2008-01-17 15:24 ` Drake Donahue
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d257c3560801171202t593bb352pc2637ab246884bb0@mail.gmail.com \
--to=givemesugarr@gmail.com \
--cc=gentoo-amd64@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox