Re: [LEAPSECS] Leap seconds ain't broken, but most implementations are broken

2017-01-08 Thread Brooks Harris
On 2017-01-08 10:15 AM, Martin Burnicki wrote: Brooks Harris wrote: On 2017-01-06 11:52 AM, Martin Burnicki wrote: - OS kernels with different features (Windows doesn't even know leap seconds, AFAIK) It is often repeated on LEAPSECS that "Windows doesn't even know leap seconds". That's just

Re: [LEAPSECS] Leap seconds ain't broken, but most implementations are broken

2017-01-08 Thread Martin Burnicki
Zefram wrote: > To be clear: obviously knowledge of the upcoming leap second must come > from some external source. A system with such advance knowledge is then > able to apply that knowledge at the proper time, maintaining a correct > clock through the leap second, without any further external

Re: [LEAPSECS] Leap seconds ain't broken, but most implementations are broken

2017-01-08 Thread Martin Burnicki
Brooks Harris wrote: > On 2017-01-06 11:52 AM, Martin Burnicki wrote: >> >>> >>> - OS kernels with different features (Windows doesn't even know leap >>> seconds, AFAIK) >>> >>> > > It is often repeated on LEAPSECS that "Windows doesn't even know leap > seconds". That's just not true. It knows