From owner-freebsd-current Sat Jan 2 06:39:04 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA22501 for freebsd-current-outgoing; Sat, 2 Jan 1999 06:39:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from server.noc.demon.net (server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA22496 for ; Sat, 2 Jan 1999 06:39:02 -0800 (PST) (envelope-from fanf@demon.net) Received: by server.noc.demon.net; id OAA10611; Sat, 2 Jan 1999 14:38:38 GMT Received: from fanf.noc.demon.net(195.11.55.83) by inside.noc.demon.net via smap (3.2) id xmaa10608; Sat, 2 Jan 99 14:38:23 GMT Received: from fanf by fanf.noc.demon.net with local (Exim 1.73 #2) id 0zwSC7-0003bb-00; Sat, 2 Jan 1999 14:38:23 +0000 To: current@FreeBSD.ORG From: Tony Finch Subject: Re: Y2K, Y 2038? Newsgroups: chiark.mail.freebsd.current In-Reply-To: Organization: Deliberate Obfuscation To Amuse Tony References: Message-Id: Date: Sat, 2 Jan 1999 14:38:23 +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matt Curtin wrote: > >The wishful thinking about it being "fixed by then" is common, but >doesn't really fly. Fixing the problem in the OS isn't a *huge* deal. >(One could change the time() to return a 64 bit value.) The result, >of course, would be dealing with all of the software that expects >time() to return a 32 bit value. At least the core system has a >finite amount of interfaces that would need to be massaged. The >random stuff floating around the Net will prove more interesting to >bring up to snuff... And there are also those network protocols that represent time as a 32 bit count of seconds (either Unix time or some variant of it). Tony. -- f.a.n.finch fanf@demon.net dot@dotat.at To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message