From: Lennart Sorensen via Talk <talk@lists.gtalug.org>
All 32 bit linux distributions. 64 architectures always used 64 bit time and are hence not effected. This is only a concern for 32 bit x86 (which Debian is explicitly NOT changing since they only intend to support it as a legacy compatibility platform running on 64 bit x86 systems) and 32 bit arm. 32 bit powerpc seems essentially dead. Not sure anyone ever really bothered with mips.
I don't care much about running processes. I care about non-volatile copies of time_t (or whatever the type is called). Is it the case that all non-volatile file systems represent times in some way that extends beyond 2038? If not, which are toast? One guess: 7th Edition Unix Filesystem. Do programs that matter represent times in vulnerable ways in non-volatile storage? Think databases, but not just databases. If they use time_t, the stored representation is already not portable between 32- and 64-bit systems. Or between big-endian and little-endian machines. Why don't I care much about running processes? Because we can update them to use 64-bit time_t and just reboot. Surely there is time to reboot such a system in the next 13 years.