The year 2038 problem (also known as "Unix Millennium bug", "Y2K38," "Y2K+38," or "Y2.038K" by analogy to the Y2K problem) may cause some computer software to fail before or in the ...

A web site devoted to disseminating information about the year-2038 bug

Year 2038 bug and associated date-related issues FAQ ... updated August 15, 2007. Warning: Dates in calendar are closer than they appear!

The Year 2038 Problem by Roger M. Wilcox last updated 23-October-2003

Example showing how the date would reset (at 03:14:08 UTC on 19 January 2038).

I?ll be retired or dead by the year 2038. Why should I care about Y2038? Won?t most computers have ?64-bit? CPUs way before 2038? Will buying all new Y2038-compliant hardware ...

The Year 2038 Bug. You made it through Y2K, but will you make it through Y2038 (also called Y2.038K)? So why did Y2K go so smoothly? And what is the difference with Y2038?

Why 2038? Our 32-bit root servers currently use the FreeBSD 4.7 operating system. As with all Unix and Unix-like operating systems, time and dates in FreeBSD are represented ...

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

The year 2038 computer clock problem.While not as bad as Y2K ... The year-2038 bug is similar to the Y2K bug in that it involves a time-wrap problem not handled by programmers.

The true delight is in the finding out rather than in the knowing.-- Isaac Asimov

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

Welcome to the year 2038! A lot of interesting things are going to happen in the next 30 years. One of them will be a big push to fix the so called "Year 2038 Problem" on Solaris ...

Year 2038 problem Another date problem, which results from computing dates into the year 2038 and beyond in 32-bit operating systems

What is the Year 2038 problem? While not as bad as Y2K, learn how C programming and the standard time library is causing a Year 2038 computer boggle.

Year 2000 (Y2K) and Year 2038 compliance The approach of year 2000, was quite a challenge for the computer industry, as many older software and hardware systems, wasn't ...

OpenVMS and the year 2038 : The year 2038 problem is associated with the Unix time format (which is seconds since January 1, 1970). The Open Group standard defines this value as ...

A collection of cool, intersting & funny forwarded emails ... The Year 2038 Problem. Test it now? steps? 1. login to yahoo messenger. 2. send instant message to anyone - fine ...

I admit, I have a special weakness for the animated graphics. That's why I could not resist the temptation to copy this animated GIF from the Wikipedia that represents the Year ...

When we use openssl to generate the certificate, we add a certain time, i.e. thirty years, to the time when the certificate is created. It is 2008 now and this makes the ...

The Year 2038 Bug - Y2K38 Problem.; Author: Ruchit Surati; Section: Bugs & Workarounds; Chapter: General Programming

Countdown to upcoming disasters and a scientific analysis of how they work and how they will affect you. Year 2038 Bug, End of world predictions, End of Mayan Calendar, Y2K again ...

To those interested in the year 2038 issues.... I've just added some experimental code to HEAD (which will be OpenSSL 0.9.9). This should make sensible things happen when longer ...

From: "David E. Wheeler" To: PostgreSQL-development Hackers Subject: Year 2038 Bug? Date:

What about the year 2038? There has been increasing discussion in the media about the year 2038. In 2038 the date field used in some C code can overflow.

Wednesday April 05, 2006 The year 2038 Problem. I usually never care about post dates, but the time event tonight is too symmetrical to miss:

A website devoted to the bug predicts that although all personal computers are likely to be 64-bit by the year 2038, and unaffected by the problem, many systems buried within ...

time_t size: The year 2038 bug? From: doug@springer.net Date: Wed Jan 05 2000 - 15:00:08 EST Next message: Richard B. Johnson: "Re: Command-line anomoly V2.3.35" Previous message ...

From: "David E. Wheeler" To: Tom Lane Cc: PostgreSQL-development Hackers

Noted previously in the link-blog -- here are more details on the first known instance of the Year 2038 UNIX epoch rollover bug, where AOLServer installs hung