From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1JFJh6-0005lJ-7H for garchives@archives.gentoo.org; Thu, 17 Jan 2008 01:37:24 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 74BE3E0B0E; Thu, 17 Jan 2008 01:37:22 +0000 (UTC) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.232]) by pigeon.gentoo.org (Postfix) with ESMTP id 619ABE0B0E for ; Thu, 17 Jan 2008 01:37:22 +0000 (UTC) Received: by nz-out-0506.google.com with SMTP id s18so404759nze.1 for ; Wed, 16 Jan 2008 17:37:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=5Ul03x5bIMLK7qJgPaRO3tGZ5v8IW+N5C6QFsF3U8i8=; b=uiRSpFnuhElPiNUVXKDgkUIkZjY32LQfWdhvjEFsBGiMNoBybDKO/ZH498JELNT4BhGIPjU/ENPiF3JqyrAmQtjcqLRDZ7dBvnvEd0aILa00iAHV/fZ4w3+o+th/bFwtFdNpSZIqeI7sSEf0b/ENxqt/Q5KtBxc7Do7dovNv+Fw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=NbYX9Ax5H3pPC2Nlt1NyZF1l4jHulvJOt21wBTft5jdFTvSrfyPpWuikn/YMVYH9QPkxx05ChsAbIEs31pJ2TzPmvogxpBMMIVuInIHmiIGlQREsrO8psomJrx/RCWwhqOMmwIL+L1ntKZ6bqSKhBqBVSXgaTlT3ZwgXt66iqX4= Received: by 10.142.187.2 with SMTP id k2mr951304wff.83.1200533841718; Wed, 16 Jan 2008 17:37:21 -0800 (PST) Received: by 10.142.12.9 with HTTP; Wed, 16 Jan 2008 17:37:21 -0800 (PST) Message-ID: <5bdc1c8b0801161737v5d1e71dfi89a3bf4f75e77e0f@mail.gmail.com> Date: Wed, 16 Jan 2008 17:37:21 -0800 From: "Mark Knecht" To: gentoo-amd64@lists.gentoo.org Subject: Re: [gentoo-amd64] Problem with latest timezone update? In-Reply-To: <000601c858a3$d1dcef50$0200a8c0@iwillxp333> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@lists.gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <478CCFC3.8080503@ercbroadband.org> <001701c85798$40c49650$0200a8c0@iwillxp333> <478E0212.8040503@ercbroadband.org> <5bdc1c8b0801160949v77b0bef4yc6ff899c0e7d26cd@mail.gmail.com> <5bdc1c8b0801160957s48a2f651ha452ba2fc04e68aa@mail.gmail.com> <1200524500.25783.0.camel@kilik.ubersekret.info> <000601c858a3$d1dcef50$0200a8c0@iwillxp333> X-Archives-Salt: cd7e9e9f-d5fb-42e6-ba17-5dce2be2f8f9 X-Archives-Hash: 7a37a8407d9071c27ff9205f8275675c On Jan 16, 2008 4:56 PM, Drake Donahue wrote: > > ----- Original Message ----- > From: "Steev Klimaszewski" > To: > Sent: Wednesday, January 16, 2008 6:01 PM > Subject: Re: [gentoo-amd64] Problem with latest timezone update? > > > > > > 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, UTC was set... > 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 installer == Mark, me the guy who built the system, correct? > initially; it is subject to > update by repeating the manual copy process anytime after system install. Which is what I did today to fix this problem. > Thus etc-update and/or dispatch-conf can't change localtime; but can change > whether localtime runs or not. Humm...seems like what you say is true but doesn't explain how emerge -DuN system changed the file. It was clearly changed since I could look inside with vi and compare to the Los_Angeles file and see that they were clearly different... Thanks, Mark -- gentoo-amd64@lists.gentoo.org mailing list