The world went pretty numb when the year 2000 was closing in. It was not merely the change in all four digits, but it also beckoned major problems for the software and programs developed during the ...

Another date problem, which results from computing dates into the year 2038 and beyond in 32-bit operating systems. Also called the "Y2K38 problem," Unix and other C applications represent time as the ...

A stark warning about the upcoming Epochalypse, also known as the "Year 2038 problem," has come from the past, as National Museum Of Computing system restorers have discovered an unsetting issue while ...

Remember how panicked we all were about the Y2K crisis back in the year 2000? Everyone freaked out because computers only used two digits to represent a year in their internal clocks, so Jan. 1, 2000 ...

Picture this: it’s January 19th, 2038, at exactly 03:14:07 UTC. Somewhere in a data center, a Unix system quietly ticks over its internal clock counter one more time. But instead of moving forward to ...

Venerable Linux distribution Debian is side-stepping the Y2K38 bug – also known as the Unix Epochalypse – by switching to 64-bit time for everything but the ...

Well, this relates to *nix stuff, so I guess it goes here... I'm sure there's been a hundred threads about it, but it goes without saying that my efforts to search for one were wasted.<BR><BR>The ...

Forbes contributors publish independent expert analyses and insights. Barry Collins is a tech journalist writing about PCs, Macs and games. A looming problem with Linux-based computers being unable to ...

Picture this: it’s January 19th, 2038, at exactly 03:14:07 UTC. Somewhere in a data center, a Unix system quietly ticks over its internal clock counter one more time. But instead of moving forward to ...