Move some things around, add a bit.
This commit is contained in:
John Fieber
parent
62f6f846b6
commit
0bb9ee826e
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/www/; revision=2469
2 changed files with 82 additions and 28 deletions
|
|
@ -1,9 +1,9 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
|
||||
<!ENTITY date "$Date: 1998-02-20 17:27:10 $">
|
||||
<!ENTITY date "$Date: 1998-02-23 13:56:02 $">
|
||||
<!ENTITY title 'Year 2000 bug (aka "Millennium bug")'>
|
||||
<!ENTITY % includes SYSTEM "includes.sgml"> %includes;
|
||||
]>
|
||||
<!-- $Id: y2kbug.sgml,v 1.3 1998-02-20 17:27:10 steve Exp $ -->
|
||||
<!-- $Id: y2kbug.sgml,v 1.4 1998-02-23 13:56:02 jfieber Exp $ -->
|
||||
|
||||
<html>
|
||||
&header;
|
||||
|
|
@ -13,18 +13,11 @@
|
|||
official statements from the vendors of their hardware and software
|
||||
as to how their product will handle the year 2000 date rollover.</p>
|
||||
|
||||
<p>The current FreeBSD statement is as follows:</p>
|
||||
<p>Organizations that use unix and unix like operating systems
|
||||
such as FreeBSD are already one step ahead of the problem. FreeBSD
|
||||
will properly maintain time long after year 2000 passes.</p>
|
||||
|
||||
<blockquote><big>"We believe, but cannot guarantee, that FreeBSD is Y2K
|
||||
compliant. We have spent a significant amount of time verifying
|
||||
this to be the case, but it is possible that something may have been
|
||||
overlooked. If a Y2K bug is found in the future, we will attempt to
|
||||
fix it as soon as possible."</big></blockquote>
|
||||
|
||||
<p align="right"><b>David Greenman, Principal Architect, The
|
||||
FreeBSD project</b></p>
|
||||
|
||||
<h2>More information</h2>
|
||||
<h2>Background information</h2>
|
||||
|
||||
<p><i>(This section based on the text from the <a
|
||||
href="http://www.linux.org.uk/mbug.html">Linux Y2K compliance
|
||||
|
|
@ -47,6 +40,40 @@
|
|||
1999 to 2000, and that it correctly interprets the year 2000 as a leap
|
||||
year.</p>
|
||||
|
||||
<h2>What you can do</h2>
|
||||
|
||||
<p>FreeBSD will continue to properly maintain time well into the
|
||||
next century. Third party applications, however, might not.
|
||||
Your best defense against year 2000 issues is a good
|
||||
offense. Listening to stories claiming the coming meltdown of
|
||||
the world as we know it are <strong>not</strong> the way to
|
||||
solve the millenium bug. Nor is waiting until the last
|
||||
minute. The FreeBSD Project recommends that your organization
|
||||
apply sound system administration principles as the millenium
|
||||
approaches.</p>
|
||||
|
||||
<p>There are tests that you can perform to see how your system will
|
||||
respond. Set your clock to a few minutes before midnight on New
|
||||
Year's Eve and watch the system time. Your system should display
|
||||
the year as 2000 and not 1900. If the year is displayed
|
||||
incorrectly, then you will have plenty of time to update your
|
||||
hardware. Operating your organizations information systems under
|
||||
their normal daily load with the clock set forward can provide
|
||||
valuable insight into your vulnerablility to year 2000 issues.</p>
|
||||
|
||||
<h2>FreeBSD Year 2000 Statement</h2>
|
||||
|
||||
<blockquote>
|
||||
<p>"We believe, but cannot guarantee, that FreeBSD is Y2K
|
||||
compliant. We have spent a significant amount of time verifying
|
||||
this to be the case, but it is possible that something may have been
|
||||
overlooked. If a Y2K bug is found in the future, we will attempt to
|
||||
fix it as soon as possible."</p>
|
||||
|
||||
<p align="right">David Greenman<br>Principal Architect, The
|
||||
FreeBSD project</p>
|
||||
</blockquote>
|
||||
|
||||
<h2>Fixed problems</h2>
|
||||
|
||||
<p>The following Y2K problems have been identified and fixed in
|
||||
|
|
@ -82,7 +109,7 @@
|
|||
attempt to indicate which versions (if any) of the software are
|
||||
fixed.</p>
|
||||
|
||||
<h2>More information?</h2>
|
||||
<h2>More information</h2>
|
||||
|
||||
<p>If you have further questions about FreeBSD's year 2000 compliance, or
|
||||
you have discovered an application running under FreeBSD that is not Y2K
|
||||
|
|
|
|||
|
|
@ -1,9 +1,9 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
|
||||
<!ENTITY date "$Date: 1998-02-20 17:27:10 $">
|
||||
<!ENTITY date "$Date: 1998-02-23 13:56:02 $">
|
||||
<!ENTITY title 'Year 2000 bug (aka "Millennium bug")'>
|
||||
<!ENTITY % includes SYSTEM "includes.sgml"> %includes;
|
||||
]>
|
||||
<!-- $Id: y2kbug.sgml,v 1.3 1998-02-20 17:27:10 steve Exp $ -->
|
||||
<!-- $Id: y2kbug.sgml,v 1.4 1998-02-23 13:56:02 jfieber Exp $ -->
|
||||
|
||||
<html>
|
||||
&header;
|
||||
|
|
@ -13,18 +13,11 @@
|
|||
official statements from the vendors of their hardware and software
|
||||
as to how their product will handle the year 2000 date rollover.</p>
|
||||
|
||||
<p>The current FreeBSD statement is as follows:</p>
|
||||
<p>Organizations that use unix and unix like operating systems
|
||||
such as FreeBSD are already one step ahead of the problem. FreeBSD
|
||||
will properly maintain time long after year 2000 passes.</p>
|
||||
|
||||
<blockquote><big>"We believe, but cannot guarantee, that FreeBSD is Y2K
|
||||
compliant. We have spent a significant amount of time verifying
|
||||
this to be the case, but it is possible that something may have been
|
||||
overlooked. If a Y2K bug is found in the future, we will attempt to
|
||||
fix it as soon as possible."</big></blockquote>
|
||||
|
||||
<p align="right"><b>David Greenman, Principal Architect, The
|
||||
FreeBSD project</b></p>
|
||||
|
||||
<h2>More information</h2>
|
||||
<h2>Background information</h2>
|
||||
|
||||
<p><i>(This section based on the text from the <a
|
||||
href="http://www.linux.org.uk/mbug.html">Linux Y2K compliance
|
||||
|
|
@ -47,6 +40,40 @@
|
|||
1999 to 2000, and that it correctly interprets the year 2000 as a leap
|
||||
year.</p>
|
||||
|
||||
<h2>What you can do</h2>
|
||||
|
||||
<p>FreeBSD will continue to properly maintain time well into the
|
||||
next century. Third party applications, however, might not.
|
||||
Your best defense against year 2000 issues is a good
|
||||
offense. Listening to stories claiming the coming meltdown of
|
||||
the world as we know it are <strong>not</strong> the way to
|
||||
solve the millenium bug. Nor is waiting until the last
|
||||
minute. The FreeBSD Project recommends that your organization
|
||||
apply sound system administration principles as the millenium
|
||||
approaches.</p>
|
||||
|
||||
<p>There are tests that you can perform to see how your system will
|
||||
respond. Set your clock to a few minutes before midnight on New
|
||||
Year's Eve and watch the system time. Your system should display
|
||||
the year as 2000 and not 1900. If the year is displayed
|
||||
incorrectly, then you will have plenty of time to update your
|
||||
hardware. Operating your organizations information systems under
|
||||
their normal daily load with the clock set forward can provide
|
||||
valuable insight into your vulnerablility to year 2000 issues.</p>
|
||||
|
||||
<h2>FreeBSD Year 2000 Statement</h2>
|
||||
|
||||
<blockquote>
|
||||
<p>"We believe, but cannot guarantee, that FreeBSD is Y2K
|
||||
compliant. We have spent a significant amount of time verifying
|
||||
this to be the case, but it is possible that something may have been
|
||||
overlooked. If a Y2K bug is found in the future, we will attempt to
|
||||
fix it as soon as possible."</p>
|
||||
|
||||
<p align="right">David Greenman<br>Principal Architect, The
|
||||
FreeBSD project</p>
|
||||
</blockquote>
|
||||
|
||||
<h2>Fixed problems</h2>
|
||||
|
||||
<p>The following Y2K problems have been identified and fixed in
|
||||
|
|
@ -82,7 +109,7 @@
|
|||
attempt to indicate which versions (if any) of the software are
|
||||
fixed.</p>
|
||||
|
||||
<h2>More information?</h2>
|
||||
<h2>More information</h2>
|
||||
|
||||
<p>If you have further questions about FreeBSD's year 2000 compliance, or
|
||||
you have discovered an application running under FreeBSD that is not Y2K
|
||||
|
|
|
|||
Loading…
Reference in a new issue