public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Drake Donahue" <donahue95@comcast.net>
To: <gentoo-amd64@lists.gentoo.org>
Subject: Re: [gentoo-amd64] Problem with latest timezone update?
Date: Wed, 16 Jan 2008 19:56:38 -0500	[thread overview]
Message-ID: <000601c858a3$d1dcef50$0200a8c0@iwillxp333> (raw)
In-Reply-To: 1200524500.25783.0.camel@kilik.ubersekret.info


----- Original Message ----- 
From: "Steev Klimaszewski" <steev@gentoo.org>
To: <gentoo-amd64@lists.gentoo.org>
Sent: Wednesday, January 16, 2008 6:01 PM
Subject: Re: [gentoo-amd64] Problem with latest timezone update?


<snip>

> Except that neither etc-update nor dispatch-conf touch
> the /etc/localtime file...
>

True, but...
The files that are (maybe) affected directly by etc-update and/or 
dispatch-conf  are /etc/conf.d/clock and /etc/init.d/clock. ('maybe' is used 
because: an emerge update must have affected one or both files; etc-update 
and/or dispatch-conf  must have been invoked by the user; the user must have 
chosen action that resulted in a change to one or both files.
 /etc/conf.d/clock is the configuration file for /etc/init.d/clock.
When /etc/init.d/clock runs (normally at boot), /etc/conf.d/clock is read.
If CLOCK="UTC" is not set in /etc/conf.d/clock, the option --localtime is 
used and TBLURB="Local Time" is set.
The /etc/localtime file is a copy of one of the binary files in 
/usr/share/zoneinfo made by the system installer initially; it is subject to 
update by repeating the manual copy process anytime after system install.
Thus etc-update and/or dispatch-conf can't change localtime; but can change 
whether localtime runs or not.

 -- 
> gentoo-amd64@lists.gentoo.org mailing list
> 

-- 
gentoo-amd64@lists.gentoo.org mailing list



  reply	other threads:[~2008-01-17  0:59 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 [this message]
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
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='000601c858a3$d1dcef50$0200a8c0@iwillxp333' \
    --to=donahue95@comcast.net \
    --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