On May 21, 2015, at 7:49 AM, Poul-Henning Kamp p...@phk.freebsd.dk wrote:
In message 20150521134322.gg10...@ucolick.org, Steve Allen writes:
POSIX does not want to know geophysics, nor astrometry, nor politics.
POSIX does not care what is meant by day.
POSIX wants someone else
On 19/05/15 08:30 PM, Joseph M Gwinn wrote:
From: Eric R. Smith ersm...@hfx.eastlink.ca
To: Leap Second Discussion List leapsecs@leapsecond.com
True UTC (with leap seconds) didn't cure a problem the committee cared
about, and managed to cause problems they did care about. In short,
POSIX
LEAPSECS leapsecs-boun...@leapsecond.com wrote on 05/21/2015 08:02:09
AM:
From: Eric R. Smith ersm...@hfx.eastlink.ca
To: Leap Second Discussion List leapsecs@leapsecond.com
Date: 05/21/2015 08:01 AM
Subject: Re: [LEAPSECS] Look Before You Leap ? The Coming Leap
Second and AWS | Hacker
On Thu 2015-05-21T09:02:09 -0300, Eric R. Smith hath writ:
and that each and every day shall be accounted for by exactly 86400
seconds. Is this correct? Since the length of the day is not in fact
exactly 86400 SI seconds, it would follow that a POSIX compliant system
has to know how many days
Eric R. Smith ersm...@hfx.eastlink.ca wrote:
it would follow that a POSIX compliant system has to know how many days
have elapsed since the epoch, i.e. it needs to have some kind of access
to the sky.
Only to the extent that its owners want it to know the correct time.
Tony.
--
In message 20150521134322.gg10...@ucolick.org, Steve Allen writes:
POSIX does not want to know geophysics, nor astrometry, nor politics.
POSIX does not care what is meant by day.
POSIX wants someone else to decide what day means, and for all those
other details to be handled outside the
I stand by my original statement. The label on the box is a mass specification,
not a force specification. See the reference provided.
If you want to pick at the statement you would have to resort to relativity, in
which case I would correct to rest mass.
Sent from my iPad
On May 20, 2015,
On Wed, May 20, 2015 at 3:02 AM, Richard Clark rcl...@noao.edu wrote:
One of its examples of how the metric system is
bad was its confusing use of two units, the newton and the kilogram, to
measure weight. The US system is so much simpler and sensible with just
one unit, the pound.
I am not
In message 05704fac-8087-42ca-bb03-51c4b21c6...@tcs.wap.org, Jonathan E. Har
dis writes:
I stand by my original statement. The label on the box is a mass specificati=
on, not a force specification. See the reference provided.
I didn't say the label didn't describe a mass, I said that
In message dce2e991-a54d-42af-98f8-2d5087fbf...@leapsecond.com, Tom Van Baak
writes:
https://aws.amazon.com/blogs/aws/look-before-you-leap-the-coming-leap-second-and-aws/
So already here the trouble starts: Google uses a smooth curve for their
clock-smearing
and Amazon uses a
In message 32c69001-db69-46c4-905f-d994b017b...@tcs.wap.org, Jonathan E.
Hardis writes:
That box of Wheaties that is labelled 'Net Weight 10 oz' would
correctly weigh 10 oz everywhere on Earth, on the Moon, and on the ISS.
It does not.
For several reasons, but mainly because the
LEAPSECS leapsecs-boun...@leapsecond.com wrote on 05/19/2015 05:49:23
PM:
From: Eric R. Smith ersm...@hfx.eastlink.ca
To: Leap Second Discussion List leapsecs@leapsecond.com
Date: 05/19/2015 06:19 PM
Subject: Re: [LEAPSECS] Look Before You Leap ? The Coming Leap
Second and AWS | Hacker
On May 19, 2015, at 3:02 PM, Richard Clark rcl...@noao.edu wrote:
It was around the late 1600's that it started becomming possible (and
necessary) to decouple weight and mass.
The sound you hear is the sound of chalk screeching on the blackboard.
“Weight” is an ambiguous term that can
On 2015-05-19 08:10, Stephen Colebourne wrote:
A key point I've been making all along is that there needs to be an
internationally agreed standard for how to do the smoothing. In Java I
recommended UTC-SLS simply because it was at least a written up
approach. (My preference is for a linear
In message 20150519181135.cacbe406...@ip-64-139-1-69.sjc.megapath.net, Hal
Murray writes:
I think the problem is conflicting standards. POSIX doesn't agree with UTC.
Not so much doesn't agree as ignores.
Are there any examples of buggy standards with a huge installed base getting
Standards are funny things. Sometimes they get adopted and sometimes
they don't. Sometimes more than one standard becomes the standard.
The leap seconds debate exists because there are two entirely
reasonable ways to talk about time, one based on the sun and one based
on atomic clocks. The solar
On 05/19/2015 12:05 PM, Warner Losh wrote:
One has to wonder, though. UTC is the standard. Why do we need another
standard to subvert the original standard if the original standard were easy
to implement correctly?
Because POSIX requires you to pretend leap seconds don't exit.
? The Coming Leap
Second and AWS | Hacker News
Sent by: LEAPSECS leapsecs-boun...@leapsecond.com
In message
20150519181135.cacbe406...@ip-64-139-1-69.sjc.megapath.net, Hal
Murray writes:
I think the problem is conflicting standards. POSIX doesn't agree with
UTC.
Not so much doesn't
On 19/05/15 05:39 PM, Joseph M Gwinn wrote:
From: Poul-Henning Kamp p...@phk.freebsd.dk
To: Leap Second Discussion List leapsecs@leapsecond.com, Hal
Murray hmur...@megapathdsl.net
Date: 05/19/2015 02:22 PM
Subject: Re: [LEAPSECS] Look Before You Leap ? The Coming Leap
Second and AWS | Hacker
In message 0e448a0c-f75a-43a0-9fb6-7d715ef92...@bsdimp.com, Warner Losh
writes:
Surely the existence of these 'smeared' timescales
points to a fundamental flaw in the method we've chosen to keep atomic
and solar time in sync?
Speaking of flawed...
Reported to me from the
One has to wonder, though. UTC is the standard. Why do we need another
standard to subvert the original standard if the original standard were easy
to implement correctly? Surely the existence of these ‘smeared’ timescales
points to a fundamental flaw in the method we’ve chosen to keep atomic
and
Warner Losh said:
One has to wonder, though. UTC is the standard. Why do we need another
standard to subvert the original standard if the original standard were easy
to implement correctly? Surely the existence of these ?smeared? timescales
points to a fundamental flaw in the method we?ve
Several years ago (2000ish) I came across a website arguing why the US
is right to not adopt the metric system. (I suspect the author had never
heard the term SI) One of its examples of how the metric system is
bad was its confusing use of two units, the newton and the kilogram, to
measure
https://aws.amazon.com/blogs/aws/look-before-you-leap-the-coming-leap-second-and-aws/
https://news.ycombinator.com/item?id=9567761
/tvb
___
LEAPSECS mailing list
LEAPSECS@leapsecond.com
https://pairlist6.pair.net/mailman/listinfo/leapsecs
...@leapsecond.com on behalf of Tom Van Baak
t...@leapsecond.com
Sent: Monday, May 18, 2015 11:59 PM
To: leapsecs@leapsecond.com
Subject: [LEAPSECS] Look Before You Leap – The Coming Leap Second and AWS |
Hacker News
https://aws.amazon.com/blogs/aws/look-before-you-leap-the-coming-leap-second-and-aws
25 matches
Mail list logo
