Date: Mon, 04 Jan 1999 13:04:59 +0100 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: "Daniel O'Callaghan" <danny@hilink.com.au> Cc: freebsd-bugs@FreeBSD.ORG Subject: Re: Y2K Message-ID: <13346.915451499@critter.freebsd.dk> In-Reply-To: Your message of "Mon, 04 Jan 1999 22:46:36 %2B1100." <Pine.BSF.3.96.990104223002.16026A-100000@enya.clari.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <Pine.BSF.3.96.990104223002.16026A-100000@enya.clari.net.au>, "Danie l O'Callaghan" writes: >However, it did raise the issue of just when the end of the epoch would >come. Everyone talks about 2038, but no matter how many times I ask my >calculator, it says that 2038 is 2^31 seconds after 1970, and 2^32 seconds >takes us to 2106. Why can't struct timeval contain long unsigned members >instead of long ints? Simple: because struct timeval (×pec) needs to be able to handle signed time intervals. Inetd should be fixed to use unsigned. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?13346.915451499>