From owner-freebsd-stable  Fri Apr 23  4:39:12 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from diamond.ripn.net (unknown [195.19.26.76])
	by hub.freebsd.org (Postfix) with ESMTP id 1045714D80
	for <stable@FreeBSD.ORG>; Fri, 23 Apr 1999 04:39:00 -0700 (PDT)
	(envelope-from ilya@diamond.ripn.net)
Received: (from ilya@localhost)
	by diamond.ripn.net (8.9.2/8.9.2) id PAA44330;
	Fri, 23 Apr 1999 15:36:00 +0400 (MSD)
	(envelope-from ilya)
Message-Id: <199904231136.PAA44330@diamond.ripn.net>
Subject: Re: Year 2000
In-Reply-To: <4.1.19990419154056.00b88920@mail-r> from Ludwig Pummer at "Apr 19, 1999  3:41:31 pm"
To: ludwigp@bigfoot.com (Ludwig Pummer)
Date: Fri, 23 Apr 1999 15:35:59 +0400 (MSD)
Cc: chad@rez.com, stable@FreeBSD.ORG
From: Ilya Varlashkin <ilya@ripn.net>
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

According to Ludwig Pummer:
> At 02:20 PM 4/19/99 , Chad R. Larson wrote:
> >...  But it did make me wonder if the FreeBSD organization,
> >or any of y'all out there have so done (and if so, what the outcome
> >was).  I'd expect sore spots in the locale stuff, perhaps in process
> >accounting.
> 
> http://www.freebsd.org/y2kbug.html
> 

Ok, just look: 

"After extensive analysis and testing, we believe that 
FreeBSD is 100% Y2K compliant...." (from that page)

But what about struct tm from /usr/include/time.h:

        int     tm_year;        /* years since 1900 */

So I suppose asctime(3), localtime(3) and gmtime(3) are not Y2K-compliant, 
are they? Applications that blindly rely on Y2K-compliant OS will 
operate wrong year value. Did I missed something?

-- 
Ilya Varlashkin


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message