From: "Bodo Eggert <harvested.in.lkml@posting.7eggert.dyndns.org>" <7eggert@gmx.de>
To: "Srinivas G." <srinivasg@esntechnologies.co.in>,
linux-kernel-Mailing-list <linux-kernel@vger.kernel.org>
Subject: Re: Y2K-like bug to hit Linux computers! - Info of the day
Date: Sat, 14 May 2005 15:41:52 +0200 [thread overview]
Message-ID: <E1DWwtu-0000mS-AY@be1.7eggert.dyndns.org> (raw)
In-Reply-To: 43GQ7-5qy-5@gated-at.bofh.it
Srinivas G. <srinivasg@esntechnologies.co.in> wrote:
> But what about the present? Many applications running on Linux could
> soon be making calculations for dates 30 years away -- say, for mortgage
> and insurance calculations -- and could start giving out error messages
> well before D-day. The problem could be widespread because more and more
> corporates today are migrating to Linux because of the better security
> it offers.
time_t is for systems times only, and it is not to be manipulated directly.
If you'd do that, you'll miss leap seconds and have additional leap years.
Besides that, it's not portable to different EPOCHs.
Therefore, apllications MUST use their own time types.
--
A. Top posters
Q. What's the most annoying thing on Usenet?
next parent reply other threads:[~2005-05-14 13:41 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <43GQ7-5qy-5@gated-at.bofh.it>
2005-05-14 13:41 ` Bodo Eggert <harvested.in.lkml@posting.7eggert.dyndns.org> [this message]
2005-05-14 12:46 Y2K-like bug to hit Linux computers! - Info of the day Matthew Geier
2005-05-14 20:27 ` christos gentsis
2005-05-14 21:19 ` Valdis.Kletnieks
2005-05-15 1:04 ` Gene Heskett
-- strict thread matches above, loose matches on Subject: below --
2005-05-13 11:43 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
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
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=E1DWwtu-0000mS-AY@be1.7eggert.dyndns.org \
--to=7eggert@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--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).