[26324] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Silly season

daemon@ATHENA.MIT.EDU (Andrew Brown)
Thu Dec 23 16:50:12 1999

Date: Thu, 23 Dec 1999 16:41:09 -0500
From: Andrew Brown <twofsonet@graffiti.com>
To: "Greg A. Woods" <woods@most.weird.com>
Cc: nanog@merit.edu
Message-ID: <19991223164109.A27653@noc.untraceable.net>
Reply-To: Andrew Brown <atatat@atatdot.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <m121DuS-000g5eC@most.weird.com>; from woods@most.weird.com on Thu, Dec 23, 1999 at 02:28:24PM -0500
Errors-To: owner-nanog-outgoing@merit.edu


>> it would be better, imho, to go to a 64 bit signed time_t, but that
>> would be a major flag day.
>
>"would be"!?!?!  :-)

okay...will be.  when it happens.  i wasn't trying to imply that it
might not...i'm sure it will.

>No, it *WILL* be an important day, but it will happen on a per-system
>basis (and perhaps per-protocol basis if indeed there are any network
>protocols carrying time_t or similar values).

um...like ntp?  or the time protocol as per rfc868, a slightly
adjusted (by 25567 days...gee has this expired already? :) time_t
(well...okay, "a 32 bit binary number") protocol.

fwiw - even if you're on a 64 bit system, any time_t you *expose* to
the outside world is going to be converted to the 32 bit flavor.  so
you might be able to continue after 2038, but you'd probably be rather
alone in it.

and then there's tar, pax, cpio...

-- 
|-----< "CODE WARRIOR" >-----|
codewarrior@daemon.org             * "ah!  i see you have the internet
twofsonet@graffiti.com (Andrew Brown)                that goes *ping*!"
andrew@crossbar.com       * "information is power -- share the wealth."


home help back first fref pref prev next nref lref last post