I don't normally do this. http://motherboard.vice.com/read/32-bit-integers-and-why-old-computers-matter
This does a really good job educating people on integer overflow :) In our non-pacman universe, the ports guys really did a good job mopping up the 32bit time_t issues. Near the end of that writeup, I hope everyone comes to realize that what is holding back proliferation of 64-bit time_t solutions is simply installed-base backwards-compatiblity. A choice customers re-make every day because that is what they are given to them by vendors, and will keep making until the vendors give them a replacement which does not have the problem. Every time a vendor supplies a 32-bit time_t OS to a 32-bit computer user, it creates a potential circumstance someone might be running that close to one of the numerous issues coming close to 2038 (there are a number of them, read the wikipedia page, and pay close attention to NTP as well). The potential is low today, but increases as time_t ticks... (Mailed from a 64-bit machine, though a sequence of machines, not all of which are 64-bit... to you....)
