Date: Sun, 30 Oct 2011 10:18:22 -0600 From: Warner Losh <imp@bsdimp.com> To: lev@freebsd.org Cc: arch@freebsd.org Subject: Re: /etc/localtime problems Message-ID: <9B19F4A4-FBA6-43DD-9FF6-C360AC3A7E59@bsdimp.com> In-Reply-To: <501950672.20111030155316@serebryakov.spb.ru> References: <457576448.20111030151023@serebryakov.spb.ru> <20111030113348.GA42759@vniz.net> <501950672.20111030155316@serebryakov.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
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=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9B19F4A4-FBA6-43DD-9FF6-C360AC3A7E59>