Re: [LEAPSECS] leap seconds in POSIX

2020-02-01 Thread Brooks Harris
On 2020-01-30 7:02 AM, Tom Van Baak wrote: Hal, I see some good comments; did you get the answer you wanted? My take: > Does anybody know of a good writeup of how to fix POSIX to know about leap seconds > and/or why POSIX hasn't done anything about it yet? No write-up. No fix. It's not

Re: [LEAPSECS] leap seconds in POSIX

2020-02-01 Thread Warner Losh
On Sat, Feb 1, 2020 at 3:39 PM Brooks Harris wrote: > > (As I understand it time_t is deprecated and replaced by struct timespec > in modern POSIX systems. This does not eliminate the leap-second > difficulty.) > Kinda sorta... the timespec struct has a time_t inside of it. > The leap-second

[LEAPSECS] Leap seconds have a larger context than POSIX

2020-02-01 Thread Seaman, Robert Lewis - (rseaman)
Tried to send this a few days ago, but it never showed up on the list. Steve has provided gritty details since. Since roughly the second world war, the distinction between time-of-day and interval-time has become increasingly clear. But the history of this distinction goes back at least as far

Re: [LEAPSECS] leap seconds in POSIX

2020-02-01 Thread Brooks Harris
On 2020-02-01 3:01 AM, Hal Murray wrote: t...@leapsecond.com said: I see some good comments; did you get the answer you wanted? Nothing off list, so you have seen everything that I saw. I was hoping that there would be a good white paper or blog that discussed all the possibilities that have

Re: [LEAPSECS] leap seconds in POSIX

2020-02-01 Thread Michael Shields
On Sat, Feb 1, 2020 at 12:01 AM Hal Murray wrote: > Has anybody considered having time_t and the kernel keep smeared time? > > The idea is that you can convert from smeared time to TAI or UTC with leaps. > So a few new library routines should be enough for the few people who care > about leap

Re: [LEAPSECS] leap seconds in POSIX

2020-02-01 Thread Steve Summit
Warner Losh wrote: > But the problem with time_t are legend. I should do a talk that > lists them all. Here is, I think, the fundamental one, as I like to describe it. As Clive Feather observed years ago, There are three desirable properties for time: (1) A day is always 86400

Re: [LEAPSECS] leap seconds in POSIX

2020-02-01 Thread Steve Allen
On Sat 2020-02-01T00:01:22-0800 Hal Murray hath writ: > I was hoping that there would be a good white paper or blog that discussed all > the possibilities that have been considered and explained why they were > rejected. That cannot happen because of the other factor that has been in the politics

Re: [LEAPSECS] Leap seconds have a larger context than POSIX

2020-02-01 Thread Warner Losh
On Sat, Feb 1, 2020 at 10:57 PM Seaman, Robert Lewis - (rseaman) < rsea...@email.arizona.edu> wrote: > Tried to send this a few days ago, but it never showed up on the list. > Steve has provided gritty details since. > > > > Since roughly the second world war, the distinction between time-of-day

Re: [LEAPSECS] Leap seconds have a larger context than POSIX

2020-02-01 Thread Steve Allen
On Sun 2020-02-02T00:33:08+0100 Warner Losh hath writ: > It's the fact that things like filesystems > specify an elapsed time since an epoch in a time scale without leap > seconds. Every FAT or NTFS disk around has a time like this. Beginning 2018-06-01 the value of Microsoft Windows FILETIME

Re: [LEAPSECS] leap seconds in POSIX

2020-02-01 Thread Brooks Harris
On 2020-02-01 9:39 AM, Brooks Harris wrote: On 2020-01-30 7:02 AM, Tom Van Baak wrote: Hal, I see some good comments; did you get the answer you wanted? My take: > Does anybody know of a good writeup of how to fix POSIX to know about leap seconds > and/or why POSIX hasn't done anything

Re: [LEAPSECS] leap seconds in POSIX

2020-02-01 Thread Hal Murray
t...@leapsecond.com said: > I see some good comments; did you get the answer you wanted? Nothing off list, so you have seen everything that I saw. I was hoping that there would be a good white paper or blog that discussed all the possibilities that have been considered and explained why they