linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: christos gentsis <christos_gentsis@yahoo.co.uk>
To: Valdis.Kletnieks@vt.edu
Cc: Bill Davidsen <davidsen@tmr.com>,
	linux-os@analogic.com,
	"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 10:09:04 +0100	[thread overview]
Message-ID: <4285C030.1080706@yahoo.co.uk> (raw)
In-Reply-To: <200505132047.j4DKlcgV025923@turing-police.cc.vt.edu>

Valdis.Kletnieks@vt.edu wrote:

>On Fri, 13 May 2005 16:36:23 EDT, Bill Davidsen said:
>  
>
>>>Mon Jan 18 22:14:07 EST 2038
>>>Fri Dec 13 15:46:09 EST 1901
>>>      
>>>
>>                 ^^^^^ are UTC and GMT that far apart? Leap seconds? WTF?
>>    
>>
>
>The heck with leap seconds - why did it warp back to 1901 rather
>than to 1969/1970? ;)
>  
>
because it look like the time is a signed number... but shall i ask how 
counting something that increase can give a negative number?
second... is the counter on the software? until now i thought that the 
counter is a clock on the hardware... so how is this related with Linux? 
then the counter overflow... this will be a hardware issue... not a 
software issue ( the software will have to support the bigger hardware 
counter but to do that the bigger hardware has to exist first...)

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....


  parent reply	other threads:[~2005-05-14  8:47 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 [this message]
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
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=4285C030.1080706@yahoo.co.uk \
    --to=christos_gentsis@yahoo.co.uk \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.com \
    --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).