Joe Gwinn wrote:
Magnus,
At 5:10 PM +0200 10/10/09, Magnus Danielson wrote:
Joe,
Joe Gwinn wrote:
At 3:28 PM +0200 10/10/09, Magnus Danielson wrote:
M. Warner Losh wrote:
In message: 4acff759.3090...@rubidium.dyndns.org
Magnus Danielson mag...@rubidium.dyndns.org writes:
: M.
At 10:18 PM -0600 10/10/09, M. Warner Losh wrote:
In message: p06240804c6f6cee17...@[192.168.1.212]
Joe Gwinn joegw...@comcast.net writes:
: Another common source of confusion is that the POSIX Epoch is an instant
: defined in UTC terms,
:
: ... and occurring at a time for which
At 9:07 PM +0200 10/11/09, Magnus Danielson wrote:
Joe,
So in many ways UTC and time_t are only superficially similar things.
time_t is a half-assed attempt to do the right thing for time. It
generally works for most people most of the time, but is wrong where
it doesn't match reality.
On 2009 Oct 11, at 12:43, Joe Gwinn wrote:
Here is my posting to the POSIX Committee (and Austin Group) on the
requirements, summarizing debate up till then:
http://www.opengroup.org/austin/mailarchives/austin-group-l/
msg02131.html
One other practical requirement exists as a result of
Are there any folks who can comment on the operation of ensembles
of systems which use GPS time instead of UTC?
What are these systems?
What reasoning went into the choice of GPS time?
How did they reason so as to overcome the implicit mandates
that POSIX and international standards place on
