Patch Name: PHSS_7674 Patch Description: s700_800 10.10 HPterm June 96 Point Patch Creation Date: 96/06/10 Post Date: 96/06/14 Repost: 96/10/29 The patch incorrectly referenced the fileset X11.VUE-RUN, instead of X11.X11-RUN-CL. The file /usr/bin/X11/hpterm was delivered in X11.VUE-RUN for HP-UX 10.01, but it is delivered in X11.X11-RUN-CL for HP-UX 10.10. The patch documentation has been corrected and the patch reformatted so that the swinstall 'Match What Target Has' operation will succeed if the fileset X11.X11-RUN-CL is present. Hardware Platforms - OS Releases: s700: 10.10 s800: 10.10 Products: N/A Filesets: X11.X11-RUN-CL Automatic Reboot?: No Status: General Superseded Critical: No Path Name: /hp-ux_patches/s700_800/10.X/PHSS_7674 Symptoms: PHSS_7674: The following symptoms correspond to the descriptions in the defect descriptions field for PHSS_7674: 1. Hpterms from 10.10 to a 9.X system have the wrong value for $LINES and $COLUMNS. Defect Description: PHSS_7674: The following defect descriptions are for PHSS_7674: 1. This was caused by a workaround for a libXm defect on 10.10. The defect has been fixed and the workaround has been removed. SR: 1653170654 Patch Files: /usr/bin/X11/hpterm what(1) Output: /usr/bin/X11/hpterm: X Window System, Version 11 R5+ HP-UX B.10.10.00 May 1996 Release (build date: Wed Jun 12 12:52:12 IST 1996) hpterm: $Revision: 2.126 $ cksum(1) Output: 2992848526 286720 /usr/bin/X11/hpterm Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: None Equivalent Patches: None Patch Package Size: 340 Kbytes Installation Instructions: Please review all instructions and the Hewlett-Packard SupportLine User Guide or your Hewlett-Packard support terms and conditions for precautions, scope of license, restrictions, and, limitation of liability and warranties, before installing this patch. ------------------------------------------------------------ 1. Back up your system before installing a patch. 2. Login as root. 3. Copy the patch to the /tmp directory. 4. Move to the /tmp directory and unshar the patch: cd /tmp sh PHSS_7674 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHSS_7674.depot 5b. For a homogeneous NFS Diskless cluster run swcluster on the server to install the patch on the server and the clients: swcluster -i -b This will invoke swcluster in the interactive mode and force all clients to be shut down. WARNING: All cluster clients must be shut down prior to the patch installation. Installing the patch while the clients are booted is unsupported and can lead to serious problems. The swcluster command will invoke an swinstall session in which you must specify: alternate root path - default is /export/shared_root/OS_700 source depot path - /tmp/PHSS_7674.depot To complete the installation, select the patch by choosing "Actions -> Match What Target Has" and then "Actions -> Install" from the Menubar. 5c. For a heterogeneous NFS Diskless cluster: - run swinstall on the server as in step 5a to install the patch on the cluster server. - run swcluster on the server as in step 5b to install the patch on the cluster clients. The cluster clients must be shut down as described in step 5b. By default swinstall will archive the original software in /var/adm/sw/patch/PHSS_7674. If you do not wish to retain a copy of the original software, you can create an empty file named /var/adm/sw/patch/PATCH_NOSAVE. Warning: If this file exists when a patch is installed, the patch cannot be deinstalled. Please be careful when using this feature. It is recommended that you move the PHSS_7674.text file to /var/adm/sw/patch for future reference. To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHSS_7674.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: Note: before attempting to install this patch, it is necessary to first turn off the Vue environment. The typical way of doing this is to use the 'init' command to set the system's run state to a level which will not run Vue. The following example will set the system's run state to '2', which is a level at which Vue does not typically run: init 2