From: Matthew Geier <matthew@arts.usyd.edu.au>
To: linux-kernel@vger.kernel.org
Subject: Re: Y2K-like bug to hit Linux computers! - Info of the day
Date: Sat, 14 May 2005 22:46:47 +1000 [thread overview]
Message-ID: <4285F337.7010301@arts.usyd.edu.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1991 bytes --]
On Sat, May 14, 2005 at 10:09:04AM +0100, christos gentsis wrote:
> BTW is there anyone that plan to use his embedded devise until 2038????
> i would happy to see that :P any way embedded devises are there so they
> will have sort life cycle... how long are you going to use them 6
> months???? maximum 1-2 years....
> so there is no any problem....
I assume you are thinking of 'consumer' devices here, ADSL routers,
Satelite 'Set top boxes' and the like that have short lives.
Embeded computing is much bigger than that. I've got a 20 year old
embedded processor controlled microwave oven. (It still knows how to
cook better than I do :-).
All sorts of Industrial machinery have embeded CPUs. I'm a train nut.
In just this field, railways - equipment is expected to have a 30 year
operational life span, and much of it is now driven by embeded
computers, from traffic control signaling systems that have to be
absolutely safe from 'wrong side failures', 'fly by wire' traction power
control to regulate the trains speed, to monitoring the temprature of
the air-conditioning. A train being built right at this very moment,
with a 'train operating system' computer controlling every aspect of
it's operation will probably still be in service in 2038.
With any luck however, the people writing the software for these
things are aware of this issue and are not blindly using signed 32 bit
absolute time values from 1970.
BTW, the machine i'm typing this on WONT have this problem. (Doubt
that it will be still around in 2038 anyway). It's a 64bit platform and
time_t is 64 bit.
It isn't just a linux problem either, it's a generic Unix/C library
problem. Any software system that uses a signed 32bit number from 1970
to represent time. I have a vague recolection that there was another
popular system around that also used signed 32bit time, only it's epoch
is 1980. Those systems will go belly up 10 years after all the ancient
Unix systems. :-)
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3348 bytes --]
next reply other threads:[~2005-05-14 12:49 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-14 12:46 Matthew Geier [this message]
2005-05-14 20:27 ` Y2K-like bug to hit Linux computers! - Info of the day 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>
-- 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=4285F337.7010301@arts.usyd.edu.au \
--to=matthew@arts.usyd.edu.au \
--cc=linux-kernel@vger.kernel.org \
/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