Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!howland.erols.net!ais.net!uunet!in3.uu.net!128.138.240.25!boulder!rintintin.Colorado.EDU!fcrary
From: fcrary@rintintin.Colorado.EDU (Frank Crary)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Year 2000 problem?
Date: 29 Apr 1997 15:02:02 GMT
Organization: University of Colorado, Boulder
Lines: 13
Message-ID: <5k52ha$2nr@lace.colorado.edu>
References: <3365F634.794BDF32@jnet.vi>
NNTP-Posting-Host: rintintin.colorado.edu
NNTP-Posting-User: fcrary
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:40007
In article <3365F634.794BDF32@jnet.vi>, John Lucas <jlucas@jnet.vi> wrote:
>What happens to FreeBSD hosts on Jan 1, 2000? I notice the "date"
>command uses a two-digit year field to set the time, what about internal
>data structures and other time/date utilities? Should we be worried?
FreeBSD and other Unix platforms shouldn't have any serious problems
on 1 JAN 00. Some utilities may display, or even use, a two-digit
number for the year, but the operating system itself does not. The
time used internally by the operating system is seconds since 1 JAN 1970,
00:00 (Universal time, I think.)
Frank Crary
CU Boulder