From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 00:57:53 2006 Return-Path: X-Original-To: freebsd-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 1D3B416A41F for ; Wed, 4 Jan 2006 00:57:53 +0000 (GMT) (envelope-from listas@informatica.info) Received: from deneb.informatica.info (lincl214.informatica.info [86.109.161.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0FCC243D45 for ; Wed, 4 Jan 2006 00:57:51 +0000 (GMT) (envelope-from listas@informatica.info) Received: from [192.168.1.33] (115.Red-83-60-90.dynamicIP.rima-tde.net [83.60.90.115]) (authenticated bits=0) by deneb.informatica.info (8.13.1/8.13.1) with ESMTP id k040vmwB011143 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 4 Jan 2006 01:57:50 +0100 Message-ID: <43BB1D8E.1010204@informatica.info> Date: Wed, 04 Jan 2006 01:57:50 +0100 From: Carlos Amengual User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: es-es, en, ca MIME-Version: 1.0 To: John-Mark Gurney References: <20060103120026.EEEC916A41F@hub.freebsd.org> <43BAE883.1090705@informatica.info> <20060103234638.GA69162@funkthat.com> <43BB15BB.2070705@informatica.info> <20060104003637.GB69162@funkthat.com> In-Reply-To: <20060104003637.GB69162@funkthat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.87.1, clamav-milter version 0.87 on deneb.informatica.info X-Virus-Status: Clean Cc: freebsd-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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 00:57:53 -0000 John-Mark Gurney wrote: > Carlos Amengual wrote this message on Wed, Jan 04, 2006 at 01:24 +0100: > >>John-Mark Gurney wrote: >> >>>so, the only fix for a sextant is a new table of numbers... don't >>>forget the tables HAVE to be updated for precisely the reason leap >>>seconds are inserted... >> >>It is not only an update, it is a change in the tables themselves. And >>sidereal time would no longer be sidereal time. > > > I mean how they are currently updated each year, not updated to use a > new time scale.. > Dropping leap seconds would lead to the use of a timescale different to UT in tables. Of course, a point could be reached where leap seconds are frequent enough to become a pain for computers. In that case, computers could use TDT as time scale, but we need to have UT one way or the other. Astronomers regularly use TDT (formerly ET) as a work timescale, and UT only for Earth-orientation matters (Sidereal Time, which in fact defines UT). Computers could use TDT (not TAI, which AFAIK is not in "real" practical use elsewhere), but simply "freezing" UTC with the drop of leap seconds just adds confusion (another TAI-based timescale in addition to TAI itself and TDT). A "frozen" UT in current use is already invented: TDT. Regards, Carlos Amengual