Let's start the count down
Move over Global Warming! The next scare ... Y2K38. We all better start building our bunkers now. ;) http://en.wikipedia.org/wiki/Year_2038_problem
About all this is good for now is getting our bosses to buy 64-bit machines instead of 32-bit stuff. Although I know a couple of morons that moved to western Pennsylvania to live in a Quaker community because of the Y2K bug! They quietly moved back to town 3 or 4 years ago. James Sissel wrote:
Move over Global Warming! The next scare ... Y2K38. We all better start building our bunkers now. ;)
http://en.wikipedia.org/wiki/Year_2038_problem
------------------------------------------------------------------------
_______________________________________________ Kclug mailing list Kclug@kclug.org http://kclug.org/mailman/listinfo/kclug
On Wednesday 16 January 2008, James Sissel wrote:
Move over Global Warming! The next scare ... Y2K38. We all better start building our bunkers now. ;)
You realize this isn't really a problem, right?
Ugh, did this show up on Digg or something? This has been known for years, but this is the second time in as many days I've seen someone get panicked about it. On Jan 16, 2008 2:24 PM, Luke -Jr <luke@dashjr.org> wrote:
On Wednesday 16 January 2008, James Sissel wrote:
Move over Global Warming! The next scare ... Y2K38. We all better start building our bunkers now. ;)
You realize this isn't really a problem, right?
_______________________________________________ Kclug mailing list Kclug@kclug.org http://kclug.org/mailman/listinfo/kclug
And by then, we won't have 32bit clocks, they'll be at least 1024bit, hopefully more, and it won't be an issue. Thanks, Ron Geoffrion 913.488.7664 -----Original Message----- From: kclug-bounces@kclug.org [mailto:kclug-bounces@kclug.org] On Behalf Of feba thatl Sent: Wednesday, January 16, 2008 5:13 PM To: kclug@kclug.org Subject: Re: Let's start the count down Ugh, did this show up on Digg or something? This has been known for years, but this is the second time in as many days I've seen someone get panicked about it. On Jan 16, 2008 2:24 PM, Luke -Jr <luke@dashjr.org> wrote:
On Wednesday 16 January 2008, James Sissel wrote:
Move over Global Warming! The next scare ... Y2K38. We all better start building our bunkers now. ;)
You realize this isn't really a problem, right?
_______________________________________________ Kclug mailing list Kclug@kclug.org http://kclug.org/mailman/listinfo/kclug
_______________________________________________ Kclug mailing list Kclug@kclug.org http://kclug.org/mailman/listinfo/kclug
feba thatl wrote:
Ugh, did this show up on Digg or something? This has been known for years, but this is the second time in as many days I've seen someone get panicked about it.
It showed up because it's now because January 19, 2008 is Saturday and things like 30 year mortgage calculation may start to fail next week.
On Wednesday 16 January 2008, Michael Schultheiss wrote:
feba thatl wrote:
Ugh, did this show up on Digg or something? This has been known for years, but this is the second time in as many days I've seen someone get panicked about it.
It showed up because it's now because January 19, 2008 is Saturday and things like 30 year mortgage calculation may start to fail next week.
Interesting. I, at least, didn't even consider that. Good time to recompile your OS for 64-bit time_t, IMO.
On Jan 17, 2008 4:14 AM, Luke -Jr <luke@dashjr.org> wrote:
It showed up because it's now because January 19, 2008 is Saturday and things like 30 year mortgage calculation may start to fail next week.
Interesting. I, at least, didn't even consider that.
Of course not. It's far easier to over-hype these issues like Y2K was, or over-react the other way, than to think things through completely. Just as 640K was big enough for anybody, and YY was good enough for programs written decades ago, a shell script I wrote one winter to do date math (on Unix systems without GNU date) worked fine until it got to the end of July and tried to add days to get to the month "08", whereupon it triggered a subtle bug; it was being treated as octal due to the leading 0, and of course 8 and 9 are not valid octal digits. If there are programs using 32-bit signed integers to do date math 30 years in the future, they may suddenly find themselves broken horribly, showing a date in December 1901 rather than 2038.
On Jan 17, 2008 12:30 PM, Monty J. Harder <mjharder@gmail.com> wrote:
If there are programs using 32-bit signed integers to do date math 30 years in the future, they may suddenly find themselves broken horribly, showing a date in December 1901 rather than 2038.
"What banking crisis? According to our simulations, thirty years out there's a huge spike in profits!"
participants (8)
-
David Nicol -
feba thatl -
Geoffrion, Ron P [IT] -
James Sissel -
Luke -Jr -
Michael Schultheiss -
Monty J. Harder -
Zscoundrel