diff --git a/data/y2kbug.sgml b/data/y2kbug.sgml index 96885d91c6..05f361fe8d 100644 --- a/data/y2kbug.sgml +++ b/data/y2kbug.sgml @@ -1,121 +1,121 @@ - + + %includes; ]> - + &header;
As management understanding of the Year 2000 problem (aka, "The Millennium Bug") increases, more and more companies are demanding official statements from the vendors of their hardware and software as to how their product will handle the year 2000 date rollover.
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.
(This section based on the text from the Linux Y2K compliance page)
As with all Unix and Unixlike operating systems, time and dates in FreeBSD are represented internally as the number of seconds since the 1st of January 1970 (the Unix "epoch"). Currently, that figure is stored as a 32 bit integer, and will run out part way through 2038. By then we should (hopefully) be using a counter of 64 bits (or greater) which should be good until the end of the universe.
Note that the OS being Y2K compliant will not fix errant applications that are not Y2K compliant.
Note also that the OS expects to read the current date and time from the CMOS clock of your computer. Not all of these devices correctly handle the year 2000. You are advised to test each platform individually to ensure that your hardware clock behaves correctly when going from 1999 to 2000, and that it correctly interprets the year 2000 as a leap year.
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.
"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."
Principal Architect, The FreeBSD project
The following Y2K problems have been identified and fixed in FreeBSD.
This section is currently a placeholder. As we become aware of applications that have a Y2K problem we will note them here, and also attempt to indicate which versions (if any) of the software are fixed.
If you have further questions about FreeBSD's year 2000 compliance, or you have discovered an application running under FreeBSD that is not Y2K compliant, please contact the project at freebsd-bugs@FreeBSD.ORG.&footer;