d look at the terrain.
Also: When celestial navigation is possible, most vessels
travel a lot further than 50 meters during the time it takes to make
a measurement of the necessary precision.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
F
nds, taking into account the constraints of the
> technological systems
> expected to be used to disseminate this value, "
You're right, I misread that.
They /really/ dont want to ever see a leapsecond or leapminute, do they ?
--
Poul-Henning Kamp | UNIX sin
://www.bipm.org/en/-/2023-12-12-wrc-dubai
Which I read as death notice for the leap-second, with further
details of the funeral to announced after CPGM's meeting in 2026.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since
tion math on
major forrest fires ?
They convert a lot of trees from rigidly rotating surface mass to gasses,
but I have no idea what the total incinerated mass might be...
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer
ded data, fig 7), as when
Newcomb made the astronomical observations in the 1890'ies on which
IAU based their definition of the second, and so, presumably, all
the contemporary LOD observations, moon camera and all that, gave
results close to Newcombs.
--
Poul-Henning Kamp | UNIX since Zi
ct we would end up repeating the "Oops too little - Oops too much"
steering we saw back in the rubber-second years.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
, because public hearings, legislatie action, appropriations
or a referendum might be required, to settle how the country should
vote.
You will see similar slow-motion in organizations of maritime and air
traffic for instance.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@fr
ldlife-strikes.
Transpires that wildlife adapts to our rythm of life, but do not get the
memo that tomorrow rush-hour will be one hour different.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
15 minute and 30 minute deltas, there is a clear tendency to make
changes with far too short notice.
The good news is that stupid timezone decisions can only hurt the
geographical area controlled by the politicians, so there is a
feedback-mechanism in place.
--
Poul-Henning Kamp | UNIX si
Steve Allen writes:
> On Mon 2022-11-14T21:22:27+0000 Poul-Henning Kamp hath writ:
> > I doubt the will manage to convince the other 99+% to do something
> > as deranged as a leap-minute.
>
> > Thanks to timezones and DST, less than 1% of the worlds population
&
s correct to a minute.
I doubt the will manage to convince the other 99+% to do something
as deranged as a leap-minute.
Full hour shifts, on the other hand, can be done merely by changing
the time-zone, and they can be done through the normal political
process, aligned to recognized borders.
--
Pou
get a lot of mileage out of the
KISS principle when it comes to designing standards and APIs.
And
"86400 seconds per day"
is a lot more KISS than
"86400±1 seconds per day"
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org |
that more software will be created
in the next 30 years than were created in the previous 30 years,
so if you want to optimize for more code being correct, you need
to concentrate on getting it right for the future, not for the past.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.2
years ago.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
LEAPSECS m
Joseph Gwinn writes:
> On Sun, 30 Oct 2022 07:08:25 +0000, Poul-Henning Kamp wrote:
> The other ting to keep in mind is the immense existing codebase of
> unix kernels et al, not to mention application code depending on
> those kernels.
This is the mistake we IT-peopl
n
dwarfs" didnt have the in-house UNIX-skill to implement the change.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
__
Steve Allen writes:
> On Tue 2022-07-26T23:33:15+0000 Poul-Henning Kamp hath writ:
> > So looking at the IERS LOD plot going all the way back it seems to
> > me that we have been missing the big signal for about five decades:
> >
> >
> > https://d
So looking at the IERS LOD plot going all the way back it seems to
me that we have been missing the big signal for about five decades:
https://datacenter.iers.org/singlePlot.php?plotname=EOPC04_14_62-NOW_IAU2000A-LOD=224
How did we not notice that earlier ?
--
Poul-Henning Kamp
Steve Allen writes:
> On Mon 2022-03-07T06:33:31+0000 Poul-Henning Kamp hath writ:
> > I looked at the Bulletin A plots this morning to see how DUT1 is
> > developing, but then I noticed the 'dX' term plot:
> >
> >
> > https://datacenter
I looked at the Bulletin A plots this morning to see how DUT1 is
developing, but then I noticed the 'dX' term plot:
https://datacenter.iers.org/singlePlot.php?plotname=BulletinA_All-DX=6
What happened in late 2019 ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p
ed in 2019 by this paper:
https://www.researchgate.net/publication/332757282_Concepts_and_Terminology_for_Sea_Level_Mean_Variability_and_Change_Both_Local_and_Global
I guess that's where the geophycics of "missing" or even negative
leap-seconds live now.
--
Poul-Henning Kamp
Polar Drift in the 1990s Explained by Terrestrial Water Storage Changes:
https://agupubs.onlinelibrary.wiley.com/doi/10.1029/2020GL092114
They dont actually mention leap-seconds though...
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC
close enough to a negative one, that people
are *really* going to freak out.
Hands in the air: Who here besides Warner and me has ever tried to
test handling of negative leap-seconds ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer
nd
> then the first one will be the kind we haven't tried before?
That would be fun, wouldn't it ? :-)
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what
rve, I'd give it 50/50 before 2038.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
__
(ie: a 50/50
probability) on at least one (and probably only one) negative
leap-second before the 2K38 time_t roll over.
This is an unscientific hunch, but based on scientific data: I see
far more co-trending in DUT1 and climate model result than I am
comfortable with.
--
Poul-Henning Kamp
A=9
Is it time for a LEAPSECS betting pool on when the first negative leap second
is deleted ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequate
nd of Sat, 2021-11-27
That is similar to what my old Oncore UT reports:
Leap second info: 2021-11-28 00:00:00 NONE
77714184 seconds (899 days) from now
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD com
In message <20190116085619.ga23...@ucolick.org>, Steve Allen writes:
>On Wed 2019-01-16T08:31:19+0000 Poul-Henning Kamp hath writ:
>> In message <20190115205243.gb25...@ucolick.org>, Steve Allen writes:
>> >That evokes a challenge for all time nuts that I
difftime".
>
>That evokes a challenge for all time nuts that I can make based on
>reading Bulletin Horaire.
>
>What is the epoch that was used for TAI?
Isn't that the same one Loran-C used ? 1958-01-01 00:00:00 GMT ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p
st paragraph of
RFC958 from 1985.
When leap seconds finally appear on the radar, a freak geophysical
happenstance means there are no leap seconds for the precise six
years where most stuff is connected the internet.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org
In message , "Tom Van Baak" writes:
So is it possible to divine if this targets the HF or VLF or both ?
I would imagine that shutting VLF would leave a lot of consumer
electronics stranded.
On the other hand, I'm not sure I see much point in the HF service...
--
Poul-He
In message <20171121152434.gd...@ucolick.org>, Steve Allen writes:
>On Tue 2017-11-21T11:40:22+0000 Poul-Henning Kamp hath writ:
>> Uhm, yes ? Hasn't that been the situation for more than ten years now ?
>
>Yes, but seeing a wikipedia talk page that describe
n the situation for more than ten years now ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained
ther
>prevented it, somebody else should have made a record of that eclipse.
And they probably did, but it didn't survive or we havnt torn down
the city built on top of it later.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer
In message <20171025054835.ga18...@ucolick.org>, Steve Allen writes:
>On Tue 2017-10-24T19:32:31+0000 Poul-Henning Kamp hath writ:
>> The parallel is not as convincing as you may think. Back then, the people
>> who worked with stuff where it made a difference knew
In message <alpine.deb.2.11.1710241530180.22...@grey.csi.cam.ac.uk>, Tony Finch
writes:
>Poul-Henning Kamp <p...@phk.freebsd.dk> wrote:
>>
>> If you magically got all the paperwork changed, you would see a
>> repeat of the GMT fiasco, where UTC is sti
ke it a limited-audience scientific timescale,
for instance for astronomers to point their telescopes with.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice wha
ys happen, and UTC doesn't have DST.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by inc
case most importantly pthread_cond_timedwait().
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be expl
on the current definition
>of Coordinated Universal Time as exactly that,
In the venacular of today, this claim is an "alternative fact".
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
tes and contain no
>licensed code.
Yeah, it's called "FreeBSD" :-)
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately
In message <20161230204404.ga4...@ucolick.org>, Steve Allen writes:
>On Fri 2016-12-30T20:20:57 +0000, Poul-Henning Kamp hath writ:
>> >It may prove useful to know why the POSIX Working Group (WG) excluded
>> >leap seconds, in their own words.
>>
>
d Zeppelin for details.
[2] I wonder if anybody bothered to actually ask IERS director, or
if this is just the usual navel-gazing and circle-jerking from
militant FOSS license-separatists ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD
hs notice we get.
I don't know what the effective latency is from IERS -> TZdata -> distros ->
releases -> users -> computers, but 6 months is only going to be enough
if everybody pays maximum attention *EVERY* *BLOODY* *TIME*.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...
ch higher frequency might be the way to
beat the median filter.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be
will overshoot
in similar fashion.
>Besides being easier for NTP clients to track, a slow smear has the
>advantage [...]
Ohh, and don't forget:
DCF77 only announces the smear one hour in advance.
Poul-Henning
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TC
it will "just work".
Let us know when you are done:
http://bgr.com/2015/09/18/size-of-google-source-code-lines/
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Ne
he rug where hopefully nobody will notice them.
It is just about as far from an endorsement of leapseconds as one
can possibly be.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to
In message <57e575f7.1010...@edlmax.com>, Brooks Harris writes:
>So, now there are at least 3 different smears in use by major providers [...]
Clearly leapseconds are such a good idea that everybody wants in on the game :-/
--
Poul-Henning Kamp | UNIX since Zilog Ze
I'm _almost_ willing to pay $40 to read this, but not quite:
http://www.sciencedirect.com/science/article/pii/S0012821X16302370
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never
to which he replied:
"I am not sure about that!"
Which sounds like there could be another article in his data.
If we are _really_ lucky, there is a way to improve prediction of
future leap-seconds in that.
It will be interesting to see if this El Nino also causes a pause.
--
Don't give up you day job.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
study"
and you'll get 62K hits
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
_
Really ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
In message <56645275.3090...@yahoo.com>, "Michael.Deckers. via LEAPSECS" writes:
>On 2015-12-06 12:26, Poul-Henning Kamp wrote about computer science
>organizations:
>
>> There is nothing notable about that: There are no such ITU-compatible
&
hey wanted to, but which have repeatedly
refused to do so, because they no less pompous asses than ITU.
Poul-Henning
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to m
roduced by 2023?
No, you are not reading it correctly.
"For further study" is an ITU term of art for things they have dropped.
Random example:
https://www.itu.int/rec/dologin_pub.asp?lang=e=T-REC-I.241.6-198811-I!!PDF-E=items
(TELEX over ISDN D-channel)
--
Poul-Henning Kamp
: I'm very interested in reports if anybody get something different
than the IPv4 number "244.34.36.97" back when they lookup the FQDN
'leapsecond.utcd.org'
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer
rotation
*) The melt water gets distributed over much bigger surface area than the ice.
*) The change in altitude is very moderate compared to earth radius
*) The mass is very small relative to earth mass.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP
* the core/mantle interface is
that sensitive, melting most of the ice on Greenland is likely
to impact on both earthquake patterns and LOD significantly.
But the important part in my original answer is what comes
before the comma: "We don't know."
--
Poul-Henning Kamp | UNIX since
e period had other pecularities, for instance almost
statistically significant level of vulcanism.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequ
Looks like cisco may actually have started testing leapseconds now:
https://tools.cisco.com/quickview/bug/CSCut43397
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute
will try to sweep any troubles under the rug as usual.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
$20K for running my pro-bono NTP server :-(
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
thing, because the change of frequency
was bad for the NTP clients PLL's.
The linear smear is just a slightly different frequency for a fixed
period of time, that's a lot easier for the PLL to track.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since
default NTP serves without asking the owner/admins of those servers
if that was 1) allowed and 2) a good idea.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can
get my VLF sampler running though.
Previous leapsecond data:
http://phk.freebsd.dk/Leap/20081231/
http://phk.freebsd.dk/Leap/20051231_HBG/
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since
that the universe(1) command would get executed during the
leapsecond...
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
not a problem in my lifetime.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
; }
And that's why the above is bogus, even before we discuss their choice
of epoch or handling of leapseconds...
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP
time later.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
In message 20150602065310.ga11...@ucolick.org, Steve Allen writes:
On Tue 2015-06-02T06:38:46 +, Poul-Henning Kamp hath writ:
UTC is very much a technical standard, written to solve the problem
of what time did it happen in international (and thus political)
relations
programmers weren't
below the skill-median, we wouldn't have the problem.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained
handling and the risk of being up to half a second wrong about time
for most of a day, they picked the second risk.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what
makes that possible:
Stop inserting leap-seconds into UTC.
[1] The not-on-the-table resolution which would also make that possible
is announcing leap seconds with at least 10-20 years advance notice.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since
In message 556b6735.20784.5a32d...@dan.tobias.name, Daniel R. Tobias writes
:
On 31 May 2015 at 19:33, Poul-Henning Kamp wrote:
Most likely, at some random time after the leapsecond, your clock
steps a second.
...which is basically how most computers deal with time
synchronization
of rather crap
programmers how to cope with a infrequent and intractable complexity
on short notice.
It seems like Daniels scheduling on this one may show us which is more
important.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD
on july 1st will be valuable *factual*
input to the ITU decicion making process.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained
sorts of low-level
activities.
Recent versions of Windows have grown various hack-ish API's, mostly
because there was no to play video without it. Most of these API's
are not good for anything else.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since
servers).
This is *NOT* how your private/work Windows machine will behave,
for that no new information is available and the most recent
guidance was that somewhere between a second and an hour later
the clock will step a second.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p
run some oddball M$ time-sync protocol where they ask
their domain-controllers -- if they have one.
Where domain-controllers get their time is anyones guess.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since
?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
LEAPSECS mailing list
time-zone ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
LEAPSECS
the kernel in the libraries and
applications.
POSIX is not just a kernel API, it *also* defines the functions for
deciding what day means and all that.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
I'm absolutely certain that POSIX will survive much longer than the
current definition of UTC.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can
that your blanket
statement:
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.
...is not correct, because the mass is only applicable in the local
environment at the shipping factory.
--
Poul-Henning
a piecewise linear curve.
I can see reasons for both choices, but I'd probably go with Googles
to avoid the sharp corners.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice
day has
nothing at all to do with the mean solar day. So always ?
not even close...
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained
the enclosed air changes
means that the bouyancy depends on air-pressure and thus altitude.
That goes for anything which isn't enclosed by a rigid container
with neglible elasticity in the range of relevant air-pressures.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org
fixed?
Yes, plenty.
Building codes. Electrical codes. Traffic codes.
The deciding factor is always number of people killed and maimed.
... Or the rich loosing money, that always gets political action.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP
-track at the last WP7A meeting:
The main drive to ditch leap-seconds comes from the only
country ever to flunk Metric-101
rimshot/
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
http://iopscience.iop.org/0295-5075/110/1/10002/article
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
name instead.
I'm pretty damn sure that the brits will remove leaps from GMT as well,
so there still won't be any difference, and people will in all likelyhood
still confuse them.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD
, in particular it defines the
measurement unit on this scale to be 2^-32 SI second and the handling
of epoch roll-overs (every 2^32 SI seconds).
But more importantly, when we get to the point were we are arguing
over the meaning of common well known words we might as well stop it.
--
Poul-Henning Kamp
, interfaces badly with reality.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
notion that unelected
and unrepresentative scientists should not get to decide where and
when the Sun is supposed to be in the sky above.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never
on any day of the week, ie: during the busiest hour of traffic,
on roads, rails and in the air ?
That's what a similar dialog would warn about, if it were conducted
in China or Japan.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD
http://xkcd.com/1481/
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
In message bdf1dd12-9e80-4516-91ba-76127dcb9...@noao.edu, Rob Seaman writes:
On Jan 28, 2015, at 1:34 PM, Poul-Henning Kamp p...@phk.freebsd.dk wrote:
Derives from is not a physical reality, it's merely a social custom.
So many replies to choose from [...]
... all of them unresponsive
1 - 100 of 548 matches
Mail list logo
