From owner-freebsd-arch@FreeBSD.ORG Sun Oct 30 16:20:39 2011 Return-Path: Delivered-To: arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 792A5106564A; Sun, 30 Oct 2011 16:20:39 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 356508FC12; Sun, 30 Oct 2011 16:20:39 +0000 (UTC) Received: from 63.imp.bsdimp.com (63.imp.bsdimp.com [10.0.0.63]) (authenticated bits=0) by harmony.bsdimp.com (8.14.4/8.14.3) with ESMTP id p9UGIVCM058126 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO); Sun, 30 Oct 2011 10:18:31 -0600 (MDT) (envelope-from imp@bsdimp.com) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=koi8-r From: Warner Losh X-Priority: 3 (Normal) In-Reply-To: <501950672.20111030155316@serebryakov.spb.ru> Date: Sun, 30 Oct 2011 10:18:22 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <9B19F4A4-FBA6-43DD-9FF6-C360AC3A7E59@bsdimp.com> References: <457576448.20111030151023@serebryakov.spb.ru> <20111030113348.GA42759@vniz.net> <501950672.20111030155316@serebryakov.spb.ru> To: lev@freebsd.org X-Mailer: Apple Mail (2.1084) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (harmony.bsdimp.com [10.0.0.6]); Sun, 30 Oct 2011 10:18:31 -0600 (MDT) Cc: arch@freebsd.org Subject: Re: /etc/localtime problems X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2011 16:20:39 -0000 On Oct 30, 2011, at 5:53 AM, Lev Serebryakov wrote: > Hello, Andrey. > You wrote 30 =CF=CB=D4=D1=C2=D2=D1 2011 =C7., 15:33:49: >=20 >>> Now, /etc/localtime is copy of one of files from >>> /usr/share/zoneinfo. It is created at install time or with "tzsetup" >>> utility. >>>=20 >>> IMHO, it is bad practice. For example, Russia changed rules >>> (cancelled Winter Time). Ok, our database was updated properly >>> (r223629 and MFCes), but "make buildworld installworld && = mergemaster" >>> doesn't touch /etc/localtime! So, every administrator of every = FreeBSD >>> server in Russia needs not to forget to update this file manually. >>>=20 >>> It looks not good. >>>=20 >>> IMHO, /etc/localtime should be symlink (in such case "installworld" >>> or "freebsd-update" will fix problem), or "mergemaster" should know >>> about this file and update it too... >=20 >> I generally use symlink too, but the root of problem is that /usr = mount >> can be delayed (NFS, etc.) > Yep, I understand this problem, and thought about it. IMHO, > mergemaster solution will be better, as virtually anybody uses it > after source upgrades. But it will not help in case of binary > upgrades :( After the big USA DST fiasco a few years ago I thought we had a script = to figure out which file was currently installed into /etc/localtime and = copy the right new one over it. Warner=