009 8:01 AM
To: Mark Andrews
Cc: NANOG list
Subject: Re: Happy 1234567890 everyone!
* Mark Andrews:
> In message ,
> Nathan Malynn writes:
>> Question about 2k38: Aren't most Unixoid systems using 64-bit clocks now?
>
> No. Even if they were you have 32 bit timestam
* Mark Andrews:
> In message ,
> Nathan Malynn writes:
>> Question about 2k38: Aren't most Unixoid systems using 64-bit clocks now?
>
> No. Even if they were you have 32 bit timestamps in lots
> of things that have to be handled even if time/time64 returns
> a 64 bit timestamp.
In message ,
Nathan Malynn writes:
> Question about 2k38: Aren't most Unixoid systems using 64-bit clocks now?
No. Even if they were you have 32 bit timestamps in lots
of things that have to be handled even if time/time64 returns
a 64 bit timestamp.
> On Fri, Feb 13, 2
On Fri, 13 Feb 2009 21:08:12 -0600
Chris Adams wrote:
> Once upon a time, Joe Greco said:
> > FreeBSD used a 64-bit time_t for the AMD64 port pretty much right
> > away. On the flip side, it used a 32-bit time_t for the Alpha
> > port. I guess someone predicted "it wouldn't be a problem."
>
>
Once upon a time, Joe Greco said:
> FreeBSD used a 64-bit time_t for the AMD64 port pretty much right away.
> On the flip side, it used a 32-bit time_t for the Alpha port. I guess
> someone predicted "it wouldn't be a problem."
Tru64 on Alpha uses a 32 bit time_t (they have their own time64_t an
> Once upon a time, Nathan Malynn said:
> > Question about 2k38: Aren't most Unixoid systems using 64-bit clocks now?
>
> Unix/POSIX systems use "time_t" to store the base time counter, which is
> seconds since the epoch (1970-01-01 00:00:00 UTC). Most platforms still
> use a 32 bit time_t for c
On Fri, Feb 13, 2009 at 6:06 PM, Nathan Malynn wrote:
> Question about 2k38: Aren't most Unixoid systems using 64-bit clocks now?
>
Exactly! What are we going to do when we're at the end of the 2^64
epoch?? (after the sun burns out and.. oh wait)
--
Eric
http://nixwizard.net
Once upon a time, Nathan Malynn said:
> Question about 2k38: Aren't most Unixoid systems using 64-bit clocks now?
Unix/POSIX systems use "time_t" to store the base time counter, which is
seconds since the epoch (1970-01-01 00:00:00 UTC). Most platforms still
use a 32 bit time_t for compatibility
Question about 2k38: Aren't most Unixoid systems using 64-bit clocks now?
On Fri, Feb 13, 2009 at 8:03 PM, Chris Adams wrote:
> Once upon a time, Ravi Pina said:
>> Yes... that is more like the y2k38 problem on 03:14:07 UTC
>> 2038-01-19...
>
> Oddly enough, the end of the current Unix epoch is
Once upon a time, Ravi Pina said:
> Yes... that is more like the y2k38 problem on 03:14:07 UTC
> 2038-01-19...
Oddly enough, the end of the current Unix epoch is a prime. Not only
that, it is a Mersenne prime, 2^31 - 1. Even more, it is the largest
known Mersenne prime where its Mersenne number
You haven't lived until you've lived through an epoch.
On Fri, Feb 13, 2009 at 06:54:54PM -0500, Ravi Pina wrote:
> On Fri, Feb 13, 2009 at 06:49:49PM -0500, Steve Church wrote:
> > Just in case you missed it.
> >
> > date -d "Fri Feb 13 23:31:30 UTC 2009" +%s
> >
> > It's like a really geeky y2
On Fri, Feb 13, 2009 at 06:49:49PM -0500, Steve Church wrote:
> Just in case you missed it.
>
> date -d "Fri Feb 13 23:31:30 UTC 2009" +%s
>
> It's like a really geeky y2k without the potential cataclysm. :)
>
> Steve
Yes... that is more like the y2k38 problem on 03:14:07 UTC
2038-01-19...
..
Just in case you missed it.
date -d "Fri Feb 13 23:31:30 UTC 2009" +%s
It's like a really geeky y2k without the potential cataclysm. :)
Steve
13 matches
Mail list logo
