linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: randy_dunlap <rdunlap@xenotime.net>
To: DervishD <lkml@dervishd.net>
Cc: srinivasg@esntechnologies.co.in, linux-kernel@vger.kernel.org
Subject: Re: Y2K-like bug to hit Linux computers! - Info of the day
Date: Fri, 13 May 2005 08:19:47 -0700	[thread overview]
Message-ID: <20050513081947.3d448d61.rdunlap@xenotime.net> (raw)
In-Reply-To: <20050513143736.GA1019@DervishD>

On Fri, 13 May 2005 16:37:36 +0200 DervishD wrote:

|     Hi :)
| 
|  * Srinivas G. <srinivasg@esntechnologies.co.in> dixit:
| > Tuesday, January 19 2038. Time: 03:14:07 GMT. If Linux programmers get
| > nightmares, it's about this date and time. Immediately after that second
| > is crossed, current computer systems running on Linux will grind to a
| > halt or go into a loop. This will trip up a lot of databases. No, this
| > is not another hoax raised by some anti-Linux lobby. It is Linux's own
| > Y2K nightmare, says Businessworld. 
| 
|     Do you mean we have less than 33 years to switch to a longer type
| to store timestamps? I'm *seriously* frightened. I'm only 32, so I
| think I will manage to spend another half of my life switching to 64
| bits timestamps.
| 
|     But we shouldn't worry, anyway, because the end of the world is
| scheduled to be much sooner. I've heard rumours about a hyperspace
| speedway that must pass *just* over this tiny little planet we call
| home. Maybe the answer is 42.

but that begs the question, "to what question is 42 the answer?"   8;)

---
~Randy

  reply	other threads:[~2005-05-13 15:20 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-13 11:43 Y2K-like bug to hit Linux computers! - Info of the day Srinivas G.
2005-05-13 11:48 ` Matthias-Christian Ott
2005-05-13 12:17 ` Richard B. Johnson
2005-05-13 16:07   ` Lee Revell
2005-05-13 12:22 ` Denis Vlasenko
2005-05-13 12:27   ` Richard B. Johnson
2005-05-13 12:43     ` Richard B. Johnson
2005-05-13 20:36       ` Bill Davidsen
2005-05-13 20:47         ` Valdis.Kletnieks
2005-05-13 21:07           ` Chris Friesen
2005-05-13 21:22             ` Valdis.Kletnieks
2005-05-13 23:10               ` David Lang
2005-05-13 21:24           ` Alan Cox
2005-05-14  9:09           ` christos gentsis
2005-05-14  9:46             ` jnf
2005-05-14 10:37               ` christos gentsis
2005-05-14 10:20             ` Willy Tarreau
2005-05-15 20:25           ` Richard B. Johnson
2005-05-13 14:37 ` DervishD
2005-05-13 15:19   ` randy_dunlap [this message]
2005-05-13 15:24     ` DervishD
2005-05-13 16:11 ` Alan Cox
2005-05-15 16:20 ` Helge Hafting
2005-05-16  2:09   ` Paul Jakma
2005-05-14 12:46 Matthew Geier
2005-05-14 20:27 ` christos gentsis
2005-05-14 21:19   ` Valdis.Kletnieks
2005-05-15  1:04     ` Gene Heskett
     [not found] <43GQ7-5qy-5@gated-at.bofh.it>
2005-05-14 13:41 ` Bodo Eggert <harvested.in.lkml@posting.7eggert.dyndns.org>

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050513081947.3d448d61.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@dervishd.net \
    --cc=srinivasg@esntechnologies.co.in \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).