From owner-freebsd-bugs Tue Oct 26 1: 0: 3 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 0852C14C1A for ; Tue, 26 Oct 1999 01:00:01 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id BAA71374; Tue, 26 Oct 1999 01:00:01 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Tue, 26 Oct 1999 01:00:01 -0700 (PDT) Message-Id: <199910260800.BAA71374@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Sheldon Hearn Subject: Re: bin/14472: date for Y#K Reply-To: Sheldon Hearn Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/14472; it has been noted by GNATS. From: Sheldon Hearn To: jin@george.lbl.gov Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: bin/14472: date for Y#K Date: Tue, 26 Oct 1999 09:51:34 +0200 On Mon, 25 Oct 1999 09:12:37 MST, jin@george.lbl.gov wrote: > That is, I could not find how the 2037 is set. Any idea how we > can fix this limitation? It's not a small job. :-) You'd need to change the definition of _BSD_TIME_T, which is a long at the moment. I imagine there's an enormous amount of software (including parts of the kernel) that'd choke on this. Ciao, Sheldon. PS: The function you'd wanna look at is settimeofday. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message