NTP is one such example.
This is a much worse and much more fundamental issue than the y2k bug was, I hope people aren't writing off the severity, the time to start dealing with it is now.
> In the same way, the road is paved for the 64-bit time_t transition. Other operating systems can now make this jump
Haven't Linux and FreeBSD been on 64bit time_t for like 10 years now?
All unix 64bit systems have a 64bit time_t, only OpenBSD and NetBSD at this point have 64bit time_t on 32 bit systems.
This cannot be changed on Linux without breaking userland ABI/API compatibility, something which the maintainers refuse to do.
yeah, I know, those silly ARM chips have been bit on the slow side getting on the 64bit train.
64-bit devices are much more complicated (bus size, peripherals, part count) and therefore more expensive. If your entire task fits in a 32-bit space there is little motivation to use a 64-bit core.
I don't see why 64 bit core would imply any additional external complexity? Didn't 68k have 32bit core and work just fine down to 8bit external bus?
Manufacturers will want to use 32bit processors in new system for a long long time, simply because they can save a few cents.