Conversation
Lynne
lynne@mk.pars.ee
https://github.com/torvalds/linux/commit/f076ef44a44d02ed91543f820c14c2c7dff53716
I think about this ever so often, and I wonder, how did they fuck this up so hard?
How? The company shouldn't even exist after such a fuck-up.
3
9
1
Paul Barker
pbarker@social.afront.org@lynne I've seen many broken RTCs over the years but this is still my favourite.
0
0
0
@lynne I oftentimes think October has no business having 31 days and November only 30 (December is a blur, cause holidays fuck up any perception of time I managed to scrape up)... but I don't go into the business of implementing calendars, probably to great benefit for humanity.
0
0
0
In general, I do not understand the legacy to keep time in RTC in minutes, hours, days, months and years. Every sane system wants to run in monotonic binary time in its kernel, same for time comparison and adjustments. So ideal chip would provide some ROM field to specify its timebase frequency and then provide single binary number long enough to rollover in some reasonable time, decades, centuries. Some field to store base and some service information would worth to be added. I understand that division by 60 has been heavy deal for some 8-bit chips and even PC BIOS programmers has problems to understand how to convert monotonic time to Gregorian calendar, then the nightmare has been conservation by graphic library called Windows. This library has been replaced by real OS model obtained with DEC employee acquisition, but it keeps by default RTC in local time, adjusts its time during daylight saving period. What should do Windows laptop, when you move between time-zones??? And again there is already option in registry to keep RTC in UTC... But keeping it in some epoch based seconds or milliseconds would be much easier for everybody. All these conversion done during virtualization, RTC loads, stores....
1
0
0