From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/4267 Path: news.gmane.org!not-for-mail From: Laurent Bercot Newsgroups: gmane.linux.lib.musl.general Subject: Re: Pending patches/issues before 0.9.15 release? Date: Thu, 21 Nov 2013 23:04:52 +0000 Message-ID: <528E9194.7090209@skarnet.org> References: <20131121013056.GA2128@brightrain.aerifal.cx> <528DD529.4030408@skarnet.org> <20131121163911.GP24286@brightrain.aerifal.cx> <528E5EB9.1080400@skarnet.org> <20131121225440.GI1685@port70.net> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1385075101 22609 80.91.229.3 (21 Nov 2013 23:05:01 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 21 Nov 2013 23:05:01 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-4271-gllmg-musl=m.gmane.org@lists.openwall.com Fri Nov 22 00:05:06 2013 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1VjdJ2-00047r-NC for gllmg-musl@plane.gmane.org; Fri, 22 Nov 2013 00:05:04 +0100 Original-Received: (qmail 26179 invoked by uid 550); 21 Nov 2013 23:05:04 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 26171 invoked from network); 21 Nov 2013 23:05:04 -0000 X-SourceIP: 89.100.252.69 User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 In-Reply-To: <20131121225440.GI1685@port70.net> Xref: news.gmane.org gmane.linux.lib.musl.general:4267 Archived-At: > according to the official tzdata code the "right/" directory > is obsolete and different path is used for this now Oh ? I will definitely investigate this more. > "The advantage of this scheme is that TAI−10 uniquely refers > to an instant in time, and the difference between two such > values determines the interval between these instants" > > is not true, a single time coordinate cannot uniquely refer to > an instant in time (TAI only specifies the frame of reference > since 1977, before that it was largely nonsense and after that > it only measures the time somewhat accurately for observers at > sea level in rest, but eg outside the gravity well of earth it > is off by 22ms/year) Until we can go back to before 1977 or have computers outside the gravity well of Earth, this is not what matters. What matters is that we need a linear measure of time to synchronize our system clocks on, and TAI is exactly this. > knowing that TAI is non-conforming you need to provide a strong > use-case for it I believe that Linux kernels crashing all over the world because of a leap second happening makes a pretty strong case for not having the system clock jump around. There are several solutions for that, but none of them is simpler than just ignoring the drift at a system level and perform conversions in userland when needed. I'll follow Rich's advice and try to provide a musl patch that's minimally invasive, when I've found the right way to proceed with timezones. -- Laurent