From owner-freebsd-bugs Mon Jan 4 04:06:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA06429 for freebsd-bugs-outgoing; Mon, 4 Jan 1999 04:06:28 -0800 (PST) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA06423 for ; Mon, 4 Jan 1999 04:06:23 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id NAA13348; Mon, 4 Jan 1999 13:05:01 +0100 (CET) To: "Daniel O'Callaghan" cc: freebsd-bugs@FreeBSD.ORG Subject: Re: Y2K In-reply-to: Your message of "Mon, 04 Jan 1999 22:46:36 +1100." Date: Mon, 04 Jan 1999 13:04:59 +0100 Message-ID: <13346.915451499@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message , "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