This OPENSTEP 4.2 for MachOS patch fixes several problems relating to date processing including a number of problems with processing dates after 1999. Apple recommends this patch for all users of OPENSTEP 4.2 for MachOS. This patch is available as NeXTanswer #2659, as well as at our Year 2000 web page at http://enterprise.apple.com/y2k/.
Installing the OPENSTEP 4.2 for MachOS Patch 1:
To install this patch, do the following:
1. Log in as root. (If you're not sure how to log in as root, see your system administrator.)
2. Make sure your computer is running OPENSTEP 4.2 for MachOS.
Warning: Installing the OPENSTEP 4.2 for MachOS Patch 1 on a computer that isn't running OPENSTEP 4.2 for MachOS will result in unexpected problems.
3. Double-click on the 4.2MachPatch1.pkg file.
4. Click the Install button in the Installer package window.
An Install Package panel opens. Use this panel to select the same architecture and languages as you did when originally installing OPENSTEP.
5. Click Install in the Install Package panel, and if prompted for confirmation, click OK to proceed.
The Installer window displays information about the progress of the installation, which may take several minutes.
6. After Installer finishes installing the patch package, log out and restart the computer.
Problems solved in this release
Four Digit Year Entry with /bin/date
Problem ID: 2179467
The Unix /bin/date command now correctly handles 2-, 3-, and 4-digit years for dates in the valid Unix range (1 Jan 1970 - 31 Dec 2037).. This patch allows four-digit year entry through /bin/date. In addition, input dates are now checked for validity and out-of-range dates are rejected.
New RCS Package
Problem ID: 2249097
The version of RCS which shipped with OPENSTEP 4.2 did not handle dates after 1999 correctly in some commands. This patch installs RCS version 5.7, a much more recent version which does not experience this date problem. Please see the RCS documentation for a complete list of new and updated features in this release.
Hardware Clock Setting
Problem ID: 2253935, 2258123
Previously, setting a date after 1999 with /bin/date or with the OPENSTEP Preferences application would cause an illegal value to be stored in the hardware clock of Intel and NeXT-branded Motorola hardware systems. As a result, some systems would show an incorrect year after reboot. With this patch, the hardware clock is now set correctly for dates after 1999.
Date handling in ftpd
Problem ID: 2251927
The ftp daemon's MDTM command had been updated to handle dates after 1999 correctly.
tmac Macro Date Handling
Problem ID: 2256331
Previously, default dates generated by the tmac macros used for troff and nroff typesetting were not correct for years after 1999. The various man, me, and ms macros now generate default dates after 1999 correctly.
Date reporting in atq
Problem ID: 2258151
In OPENSTEP 4.2, the atq command displayed the job date incorrectly for jobs created with the at command after 1999. The atq command has been modified to correctly represent jobs scheduled from 1970 through 2037.
Job scheduling and execution with at and atrun
Problem ID: 2263271
Under certain circumstances, atrun did not correctly handle jobs scheduled with at after 1999. The at and atrun commands have been modified to correctly and consistently handle the scheduling and execution of jobs regardless of date.
Date display in /usr/ucb/mail
Problem ID: 2259253
In OPENSTEP 4.2, the Date: header of email messages written by /usr/lib/sendmail used a two-digit year in the creation time. This problem affected email created and read with the /bin/mail and /usr/ucb/mail programs. sendmail has been modified to write four-digit years in the date header.
ntpd Error Messaging
Problem ID: 2260775
Under OPENSTEP 4.2, the error message returned when an excessive offset was encountered did not report the year correctly for years after 1999. This error message now reports the year correctly.
Disclaimer
THE SOFTWARE PATCH PROVIDED FROM APPLE IS PROVIDED "AS IS" AND WITHOUT WARRANTY, EXPRESS OR IMPLIED. APPLE SPECIFICALLY DISCLAIMS ANY IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT WILL APPLE BE LIABLE FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO ANY LOST PROFITS, LOST SAVINGS OR ANY INCIDENTAL OR CONSEQUENTIAL DAMAGES, WHETHER RESULTING FROM IMPAIRED OR LOST DATA, SOFTWARE OR COMPUTER FAILURE OR ANY OTHER CAUSE, EVEN IF APPLE IS ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, OR FOR ANY OTHER CLAIM BY CUSTOMER OR FOR ANY THIRD PARTY CLAIM.
![[Index]](http://enterprise.apple.com/NeXTanswers/images/index.gif)
![[Download]](http://enterprise.apple.com/NeXTanswers/images/Download.gif)
