| 1 |
----- Original Message ----- |
| 2 |
From: "Steev Klimaszewski" <steev@g.o> |
| 3 |
To: <gentoo-amd64@l.g.o> |
| 4 |
Sent: Wednesday, January 16, 2008 6:01 PM |
| 5 |
Subject: Re: [gentoo-amd64] Problem with latest timezone update? |
| 6 |
|
| 7 |
|
| 8 |
<snip> |
| 9 |
|
| 10 |
> Except that neither etc-update nor dispatch-conf touch |
| 11 |
> the /etc/localtime file... |
| 12 |
> |
| 13 |
|
| 14 |
True, but... |
| 15 |
The files that are (maybe) affected directly by etc-update and/or |
| 16 |
dispatch-conf are /etc/conf.d/clock and /etc/init.d/clock. ('maybe' is used |
| 17 |
because: an emerge update must have affected one or both files; etc-update |
| 18 |
and/or dispatch-conf must have been invoked by the user; the user must have |
| 19 |
chosen action that resulted in a change to one or both files. |
| 20 |
/etc/conf.d/clock is the configuration file for /etc/init.d/clock. |
| 21 |
When /etc/init.d/clock runs (normally at boot), /etc/conf.d/clock is read. |
| 22 |
If CLOCK="UTC" is not set in /etc/conf.d/clock, the option --localtime is |
| 23 |
used and TBLURB="Local Time" is set. |
| 24 |
The /etc/localtime file is a copy of one of the binary files in |
| 25 |
/usr/share/zoneinfo made by the system installer initially; it is subject to |
| 26 |
update by repeating the manual copy process anytime after system install. |
| 27 |
Thus etc-update and/or dispatch-conf can't change localtime; but can change |
| 28 |
whether localtime runs or not. |
| 29 |
|
| 30 |
-- |
| 31 |
> gentoo-amd64@l.g.o mailing list |
| 32 |
> |
| 33 |
|
| 34 |
-- |
| 35 |
gentoo-amd64@l.g.o mailing list |
Archives