Patch-ID# 101323-01 Keywords: zh_TW scalable fonts Synopsis: OpenWindows 3.1: Patch for Chinese/Taiwan OW Scalable Fonts Date: Nov/24/93 Solaris Release: 2.1 SunOS release: 5.1 Unbundled Product: OpenWindows, Chinese/Taiwan OW Unbundled Release: 3.1 BugId's fixed with this patch: 1146118 Changes incorporated in this version: Originally, SUNWhsft package that contains all the Chinese/Taiwan scalable fonts was required to run Chinese/Taiwan OpenWindows. This patch delivers a new set of X/NeWS fb format font files that will allow users to remove SUNWhsft (Chinese/ Taiwan OpenWindows Scalable Fonts Package) and still be able to run Chinese/Taiwan OpenWindows. Architectures this patch is available for: sparc Other patches which conflict with this patch: This patch obsoleted by: Solaris 2.3 Files included with this patch: reloc/openwin/lib/locale/zh_TW/fonts: Ming-Light12.fb Ming-Light14.fb Ming-Light16.fb Ming-Light20.fb Ming-Light24.fb MingRare-Light12.fb MingRare-Light14.fb MingRare-Light16.fb MingRare-Light20.fb MingRare-Light24.fb MingUnusual-Light12.fb MingUnusual-Light14.fb MingUnusual-Light16.fb MingUnusual-Light20.fb MingUnusual-Light24.fb Problem Description: To run Chinese/Taiwan OpenWindows in Chinese/Taiwan Solaris 2.1, SUNWhsft package had to be installed. This package took up a lot of disk space (~200 MB). It became necessary for us to provide a patch that will enable users to run Chinese/Taiwan OpenWindows without requiring users to keep the scalable fonts after system installation. Note about this patch: ---------------------- We've found a problem with the postremove script that came with the original SUNWhsft package. To workaround this problem, please follow these steps before installing the patch. machinename# cd /var/sadm/pkg/SUNWhsft/install machinename# rm postremove Then, pkgrm SUNWhsft first before running the install_patch. machinename# pkgrm SUNWhsft Follow the procedure on how to install the patch as outlined in the next section. Ignore the message about "sort: can't open ./Synonyms.list: No such file or directory" when installing and backing out the patch. Instructions for applying the patch: ------------------------------------ 1. Become super-user. 2. Apply the patch by typing: //installpatch / where is the directory containing the patch and is the patch number. must be a full path name. Example: # /tmp/101323-01/installpatch /tmp/101323-01 3. If any errors are reported, see the section on "Patch Installation Errors" below. Rebooting the system or restarting the application after a successful patch installation is usually necessary to utilize patch. Instructions for backing out the patch: --------------------------------------- 1. Become super-user. 2. Change directory to /var/sadm/patch: cd /var/sadm/patch 3. Backout patch by typing: /backoutpatch where is the patch number. Example: # 101323-01/backoutpatch 101323-01 4. If any errors are reported, see the section on "Patch Backout Errors" below. Instructions for indentifying patches installed on system: ---------------------------------------------------------- Patch packets that have been installed can be identified by using the pkginfo(1) command: Example: # grep SUNW_PATCHID /var/sadm/pkg/*/pkginfo |cut -d: -f2 |sort -u Command Descriptions -------------------- NAME installpatch - apply patch package to Solaris 2.x system backoutpatch - remove patch package from Solaris 2.x system SYNOPSIS installpatch [-u] [-d] backoutpatch DESCRIPTION These installation and backout utilities apply only to Solaris 2.x associated patches. They do not apply to Solaris 1.x associated patches. These utilities are currently only provided with each patch package and are not included with the standard Solaris 2.x release software. OPTIONS installpatch -u unconditional install, do not verify file attributes -d do not save original files being replaced DIAGNOSTICS Patch Installation Errors: -------------------------- Error message: Patch has already been applied. Explanation and recommended action: This patch has already been applied to the system. If the patch has to be reapplied for some reason, backout the patch and then reapply it. Error message: This patch is obsoleted by a patch which has already been applied to this system. Application of this patch would leave the system in an inconsistent state. Patch installation is aborted. Explanation and recommended action: Occasionally, a patch is replaced by a new patch which incorporates the bug fixes in the old patch and supplies additional fixes also. At this time, the earlier patch is no longer made available to users. The second patch is said to "obsolete" the first patch. However, it is possible that some users may still have the earlier patch and try to apply it to a system on which the later patch is already applied. If the obsoleted patch were allowed to be applied, the additional fixes supplied by the later patch would no longer be available, and the system would be left in an inconsistent state. This error message indicates that the user attempted to install an obsoleted patch. There is no need to apply this patch because the later patch has already supplied the fix. Error message: The packages to be patched are not installed on this system. Explanation and recommended action: None of the packages to be updated by this patch are installed on the system. Therefore, this patch cannot be applied to the system. Error message: This patch is not applicable to client systems. Explanation and recommended action: The patch is only applicable to servers and standalone machines. Attempting to apply this patch to a client system will have no effect on the system. Error message: The /usr/sbin/pkgadd command is not executable. Explanation and recommended action: The /usr/sbin/pkgadd command cannot be executed. The most likely cause of this is that installpatch is being run on a diskless or dataless client and the /usr file system was not exported with root access to the client. See the section above on "Instructions for installing a patch on a diskless or dataless client". Error message: Patch directory is not of expected format. Explanation and recommended action: The patch directory supplied as an argument to installpatch did not contain any patch packages. Verify that the argument supplied to installpatch is correct. Error message: The following validation errors were found: Explanation and recommended action: Before applying the patch, the patch application script verifies that the current versions of the files to be patched have the expected fcs checksums and attributes. If a file to be patched has been modified by the user, the user is notified of this fact. The user then has the opportunity to save the file and make a similar change to the patched version. For example, if the user has modified /etc/inet/inetd.conf and /etc/inet/inetd.conf is to be replaced by the patch, the user can save the locally modified /etc/inet/inetd.conf file and make the same modification to the new file after the patch is applied. After the user has noted all validation errors and taken the appropriate action for each one, the user should re-run installpatch using the "-u" (for "unconditional") option. This time, the patch installation will ignore validation errors and install the patch anyway. Error message: Insufficient space in /var/sadm to save old files. Explanation and recommended action: There is insufficient space in the /var/sadm directory to save old files. The user has two options for handling this problem: (1) generate additional disk space by deleting unneeded files, or (2) override the saving of the old files by using the "-d" (do not save) option when running installpatch. However if the user elects not to save the old versions of the files to be patched, backoutpatch CANNOT be used. One way to regain space on a system is to remove the save area for previously applied patches. Once the user has decided that it is unlikely that a patch will be backed out, the user can remove the files that were saved by installpatch. The following commands should be executed to remove the saved files for patch xxxxxx-yy: cd /var/sadm/patch/xxxxxx-yy rm -r save/* rm .oldfilessaved After these commands have been executed, patch xxxxxx-yy can no longer be backed out. Error message: Save of old files failed. Explanation and recommended action: Before applying the patch, the patch installation script uses cpio to save the old versions of the files to be patched. This error message means that the cpio failed. The output of the cpio would have been preceded this message. The user should take the appropriate action to correct the cpio failure. A common reason for failure will be insufficient disk space to save the old versions of the files. The user has two options for handling insufficient disk space: (1) generate additional disk space by deleting unneeded files, or (2) override the saving of the old files by using the "-d" option when running installpatch. However if the user elects not to save the old versions of the files to be patched, the patch CANNOT be backed out. Error message: Pkgadd of package failed. See /tmp/log. for reason for failure. Explanation and recommended action: The installation of one of patch packages failed. Any previously installed packages in the patch should have been removed. See the log file for the reason for failure. Correct the problem and re-apply the patch. Error message: error while adding patch to root template Explanation and recommended action: The install script determined this system to be a client server. The attempt to apply the patch package to the appropriate root template space located under /export/root/templates failed unexpectedly. Check the log file for any failure messages. Correct the problem and re-apply the patch. Patch Backout Errors: --------------------- Error message: Patch has not been applied to this system. Explanation and recommended action: The user has attempted to back out a patch that was never applied to this system. It is possible that the patch was applied, but that the patch directory /var/sadm/patch/ was deleted somehow. If this is the case, the patch cannot be backed out. The user may have to restore the original files from the initial installation CD. Error message: Patch was installed without backing up the original files. It cannot be backed out. Explanation and recommended action: Either the -d option of installpatch was set when the patch was applied, or the save area of the patch was deleted to regain space. As a result, the original files are not saved and backoutpatch cannot be used. The original files can only be recovered from the original installation CD. Error message: Pkgrm of package failed. See /var/sadm/patch//log for reason for failure. Explanation and recommended action: The removal of one of patch packages failed. See the log file for the reason for failure. Correct the problem and run the backout script again. Error message: Restore of old files failed. Explanation and recommended action: The backout script uses the cpio command to restore the previous versions of the files that were patched. The output of the cpio command should have preceded this message. The user should take the appropriate action to correct the cpio failure. KNOWN PROBLEMS: On client server machines the patch package is NOT applied to existing clients or to the client root template space. Therefore, when appropriate, ALL CLIENT MACHINES WILL NEED THE PATCH APPLIED DIRECTLY USING THIS SAME INSTALLPATCH METHOD ON THE CLIENT. See instructions above for applying patches to a client. After a patch package has been installed pkginfo(1) will not recognize the SUNW_PATCHID macro in the patch package pkginfo file. Instead, to identify patches installed on the system use the grep command method described in the patch README. SEE ALSO pkgadd(1), pkgchk(1), pkgrm(1), pkginfo(1)