Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 21 Nov 2013 23:54:41 +0100
From: Szabolcs Nagy <>
Subject: Re: Pending patches/issues before 0.9.15 release?

* Laurent Bercot <> [2013-11-21 19:27:53 +0000]:
>  The short version of what right/ timezones are is explained here:

according to the official tzdata code the "right/" directory
is obsolete and different path is used for this now

"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)

even in classical physics, a clock source with precise ticks is
not usable for representing dates because the rotation of the
earth is not exactly periodic (by which dates are defined)

so using the absolute time coordinate of an observational frame
of reference for date keeping seems to be rather futile

>  The difference between glibc and musl is 25 seconds, not 35 as I wrote,
> which seems to indicate that musl's gmtime()/localtime() does not take leap
> second tables, which are defined in right/ timezones, into account.
>  I would really love that to be fixed - maybe not for 0.9.15, but for 0.9.16
> if possible, because I'm a hardcore TAI-10 user.

knowing that TAI is non-conforming you need to provide a strong
use-case for it

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.