From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/4264 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: Pending patches/issues before 0.9.15 release? Date: Thu, 21 Nov 2013 15:34:31 -0500 Message-ID: <20131121203431.GT24286@brightrain.aerifal.cx> References: <20131121013056.GA2128@brightrain.aerifal.cx> <528DD529.4030408@skarnet.org> <20131121163911.GP24286@brightrain.aerifal.cx> <528E5EB9.1080400@skarnet.org> <20131121194459.GS24286@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1385066079 17409 80.91.229.3 (21 Nov 2013 20:34:39 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 21 Nov 2013 20:34:39 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-4268-gllmg-musl=m.gmane.org@lists.openwall.com Thu Nov 21 21:34:46 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 1VjaxZ-0005tS-UO for gllmg-musl@plane.gmane.org; Thu, 21 Nov 2013 21:34:46 +0100 Original-Received: (qmail 11460 invoked by uid 550); 21 Nov 2013 20:34:44 -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 11449 invoked from network); 21 Nov 2013 20:34:44 -0000 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Xref: news.gmane.org gmane.linux.lib.musl.general:4264 Archived-At: On Thu, Nov 21, 2013 at 09:07:08PM +0100, Daniel Cegiełka wrote: > 2013/11/21 Rich Felker : > > > I'm a pretty hardcore anti-leapseconds / pro-POSIX-seconds guy, > > I think the big problem is the lack of proper approach to leapseconds > and unfortunately it ends this way: > > http://www.wired.com/wiredenterprise/2012/07/leap-second-glitch-explained/ A glitch which would never have happened without the abominations which are leap seconds. Really, the core cause was the NTP folks' agenda in forcing leap seconds onto a POSIX time model where they don't work, resulting in discontinuous, non-monotonic clock jumps and time ambiguity. If they'd instead smoothed out the difference between POSIX seconds and SI seconds over the whole interval between leap seconds as a tiny clock drift, reliable conversion back to TAI seconds could be performed as a presentation step without breaking software doing (valid, per POSIX) interval timing with time_t and timeval/timespec. > 25 seconds is a lot :/ 25 seconds is a lot in one day. It's not a lot in 43 years. It's much smaller than the error tolerance for audio and video timing, and unlikely to matter for anything except physics experiments. Rich