From 0bb9ee826e0ef4e7bee33f5646abe94dffabd800 Mon Sep 17 00:00:00 2001 From: John Fieber Date: Mon, 23 Feb 1998 13:56:02 +0000 Subject: [PATCH] Move some things around, add a bit. --- data/y2kbug.sgml | 55 ++++++++++++++++++++++++++++++++++++------------ en/y2kbug.sgml | 55 ++++++++++++++++++++++++++++++++++++------------ 2 files changed, 82 insertions(+), 28 deletions(-) diff --git a/data/y2kbug.sgml b/data/y2kbug.sgml index b0d1ea7944..96885d91c6 100644 --- a/data/y2kbug.sgml +++ b/data/y2kbug.sgml @@ -1,9 +1,9 @@ + %includes; ]> - + &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.

-

The current FreeBSD statement is as follows:

- -
"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."
- -

David Greenman, Principal Architect, The - FreeBSD project

+

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.

-

More information

+

Background information

(This section based on the text from the Linux Y2K compliance @@ -47,6 +40,40 @@ 1999 to 2000, and that it correctly interprets the year 2000 as a leap year.

+

What you can do

+ +

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 not 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.

+ +

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.

+ +

FreeBSD Year 2000 Statement

+ +
+

"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."

+ +

David Greenman
Principal Architect, The + FreeBSD project

+
+

Fixed problems

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.

-

More information?

+

More information

If you have further questions about FreeBSD's year 2000 compliance, or you have discovered an application running under FreeBSD that is not Y2K diff --git a/en/y2kbug.sgml b/en/y2kbug.sgml index b0d1ea7944..96885d91c6 100644 --- a/en/y2kbug.sgml +++ b/en/y2kbug.sgml @@ -1,9 +1,9 @@ + %includes; ]> - + &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.

-

The current FreeBSD statement is as follows:

- -
"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."
- -

David Greenman, Principal Architect, The - FreeBSD project

+

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.

-

More information

+

Background information

(This section based on the text from the Linux Y2K compliance @@ -47,6 +40,40 @@ 1999 to 2000, and that it correctly interprets the year 2000 as a leap year.

+

What you can do

+ +

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 not 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.

+ +

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.

+ +

FreeBSD Year 2000 Statement

+ +
+

"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."

+ +

David Greenman
Principal Architect, The + FreeBSD project

+
+

Fixed problems

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.

-

More information?

+

More information

If you have further questions about FreeBSD's year 2000 compliance, or you have discovered an application running under FreeBSD that is not Y2K