[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090107105201.054c011f@lxorguk.ukuu.org.uk>
Date: Wed, 7 Jan 2009 10:52:01 +0000
From: Alan Cox <alan@...rguk.ukuu.org.uk>
To: David Newall <davidn@...idnewall.com>
Cc: Nick Andrew <nick@...k-andrew.net>,
Linas Vepstas <linasvepstas@...il.com>, david@...g.hm,
Kyle Moffett <kyle@...fetthome.net>,
Ben Goodger <goodgerster@...il.com>,
Robert Hancock <hancockr@...w.ca>,
linux-kernel@...r.kernel.org,
"Jeffrey J. Kosowsky" <jeff@...owsky.org>,
MentalMooMan <slashdot@...eshallam.info>,
Travis Crump <pretzalz@...hhouse.org>, burdell@...ntheinter.net
Subject: Re: Bug: Status/Summary of slashdot leap-second crash on new years
2008-2009
> True but irrelevant because the RTC returns a timestamp. And it's
> quietly understood that the RTC is only an approximation.
You miss the point.
The RTC stores the CMOS time in MM DD YY HH:MM:SS format. That conversion
is done kernel side when reading/writing the RTC chip. Thus if you are
using leap second timing your BIOS RTC values will not agree with the
expected value.
> However it is now clear that no special kernel support is required for
> leap-seconds, and any such code that's been incorporated needs to be
> removed. Removed I say!
There never has been any. Its all handled (both posix and sane) by glibc.
Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists