From owner-freebsd-current@FreeBSD.ORG  Mon Jan  2 20:53:46 2006
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: current@freebsd.org
Delivered-To: freebsd-current@FreeBSD.ORG
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 795C516A41F
	for <current@freebsd.org>; Mon,  2 Jan 2006 20:53:46 +0000 (GMT)
	(envelope-from phk@critter.freebsd.dk)
Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1E9C743D55
	for <current@freebsd.org>; Mon,  2 Jan 2006 20:53:45 +0000 (GMT)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (unknown [192.168.48.2])
	by phk.freebsd.dk (Postfix) with ESMTP id 669B2BC50;
	Mon,  2 Jan 2006 20:53:44 +0000 (UTC)
To: Matthias Andree <matthias.andree@gmx.de>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Mon, 02 Jan 2006 21:50:32 +0100."
	<m3psnagxrb.fsf@merlin.emma.line.org> 
Date: Mon, 02 Jan 2006 21:53:43 +0100
Message-ID: <80432.1136235223@critter.freebsd.dk>
Sender: phk@critter.freebsd.dk
Cc: current@freebsd.org
Subject: Re: FreeBSD handles leapsecond correctly 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Jan 2006 20:53:46 -0000

In message <m3psnagxrb.fsf@merlin.emma.line.org>, Matthias Andree writes:

>And tell me one reason why the leap second must be discontinued while
>the leap day (Feb 29th) can be carried on. It's the same story,
>irregular rollover, inserting one particular unit of time.

You are clearly not thinking rationally here.

I know already now that year 2048 will be a leap year, but I still
don't know if there will be a leap second on june 30th 2006.

>> None of them got it right by any strech of the imagination because 
>> it is impossible to get it right and be POSIX compliance.
>
>Wow, and you claim FreeBSD handles it correctly.

Yes, FreeBSD handles it correctly under the impossible constraints
of POSIX.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.