Date: Sat, 2 Jan 1999 14:38:23 +0000 From: Tony Finch <dot@dotat.at> To: current@FreeBSD.ORG Subject: Re: Y2K, Y 2038? Message-ID: <E0zwSC7-0003bb-00@fanf.noc.demon.net> In-Reply-To: <xlxzp81pzrp.fsf@gold.cis.ohio-state.edu> References: <Pine.BSF.4.05.9901011850130.10809-100000@nyc-ny73-44.ix.netcom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Matt Curtin <cmcurtin@interhack.net> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E0zwSC7-0003bb-00>