Add my own report on the Leap Seconds article.

This commit is contained in:
Warren Block 2015-07-14 06:45:55 +00:00
parent 021d93160c
commit a55862be98
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=46963

View file

@ -781,4 +781,56 @@
</task>
</help>
</project>
<project cat='doc'>
<title>Leap Seconds Article</title>
<contact>
<person>
<name>
<given>Warren</given>
<common>Block</common>
</name>
<email>wblock@@FreeBSD.org</email>
</person>
</contact>
<links>
<url href="https://www.freebsd.org/doc/en_US.ISO8859-1/articles/leap-seconds/article.html" />
</links>
<body>
<p>As the leap second scheduled for the end of June approached,
Bartek Rutkowski and others raised questions about how &os;
handled leap seconds. Leap seconds have caused serious
problems for other operating systems in the last few years,
and there was understandable concern.</p>
<p>It was reasonably pointed out that &os; had encountered leap
seconds before, and would be fine this time also. Still, the
absence of reported problems is not really a substitute for a
description of what to expect and how to know if a system is
prepared.</p>
<p>To address concerns and also provide a resource for future
leap seconds, several experts were harrassed relentlessly,
with the results compiled into a short article. Beyond merely
allaying fears about what might happen, this article received
positive responses on the web for how it demonstrated &os;'s
maturity and preparedness.</p>
<p>Great thanks for their patience and expertise are owed to
Peter Jeremy, Poul-Henning Kamp, Ian Lepore, Xin LI, Warner
Losh, and George Neville-Neil.</p>
</body>
<help>
<task>
<p>Compile other short articles on things that &os; does
really well. Of particular interest are features that make
life easier for sysadmins, or how problems on other systems
are dealt with or even made non-problems on &os;.</p>
</task>
</help>
</project>
</report>