<html><head><meta name="color-scheme" content="light dark"></head><body><pre style="word-wrap: break-word; white-space: pre-wrap;">Patch-ID# 101594-09
Keywords: spam sx sxow sxlib sxxgl sxxil
Synopsis: SunOS 5.3  (SPARCstation 10SX) sxlib/sxow/sxxgl/sxxil jumbo patch
Date: Sep/26/94

Solaris Release: 2.3

SunOS Release: 5.3

Unbundled Product:

Unbundled Release:

Relevant Architectures: sun4m

BugId's fixed with this patch: 1151283 1154350 1154354 1154358 1148227 1149845 1154332 1154343 1154344 1154002 1155861 1155862 1154376 1154338 1154339 1154341 1154338 1154355 1154357 1154359 1154360 1157480 1154346 1157428 1157430 1157766 1157096 1155932 1155782 1155098 1154363 1154361 1154352 1154329 1154279 1154071 1154835 1155290 1155658 1141254 1142930 1148240 1157413 1157414 1157411 1157473 1143031 1154156 1154159 1154353 1155630 1156321 1156324 1156617 1156202 1156193 1156195 1154531 1142933 1159618 1159624 1159685 1158709 1158946 1158789 1159605 1160787 1162155 1159605 1162153 1163914 1165665 1165670 1162672 1163842 1162086 1165877 1165987 1163663 1157322 1168721 1168685 1168072 1169231 1169267 1160617 1161997 1162003 1171622 1171993 1171846 1170509 1169104 1134521 1176000 1174793

Changes incorporated in this version: 1134521 1176000 1174793 1174793

Patches accumulated and obsoleted by this patch: 

Patches which conflict with this patch:

Patches required with this patch:

Obsoleted by: Solaris 2.4

Files included with this patch: 

  /usr/lib/libsx.so.1
  /usr/openwin/server/modules/ddxSUNWcg14.so.1
  /opt/SUNWits/Graphics-sw/xgl-3.0/lib/pipelines/xglSUNWsx.so.3
  /opt/SUNWits/Graphics-sw/xil/lib/pipelines/xilcomputeJpeg_SUNWcg14.so.1
  /opt/SUNWits/Graphics-sw/xil/lib/pipelines/xilcomputeSUNWcg14.so.1
  /opt/SUNWits/Graphics-sw/xil/lib/pipelines/xilcomputesx.so.1
  /opt/SUNWits/Graphics-sw/xil/lib/pipelines/xilcsx.so.1
  /opt/SUNWits/Graphics-sw/xil/lib/pipelines/xilioSUNWcg14.so.1
  /opt/SUNWits/Graphics-sw/xil/lib/pipelines/xilsx.so.1

Problem Description: 

from (101594-09):
  1174793 XGL app dumps core on cg14 when refreshed partially off-screen

from (101594-08):
  1134521 small bytes memory leak with xil_transpose and xil_convolve usage
  1176000 minor memory leak in transpose16SX.cc and transpose8SX.cc

from (101594-07): 
  1169104: Hilighting doesn't work correctly when window is resized or obscured
  1170509: Lit, color-per-vertex polygon (using MSP) is not shaded
  1171846: double buffered window problems on the SX/cgfourteen

from (101594-06):
  1160617: Xsun doesn't free memory on SX(depth=24) when using XFreePixmap().
  1161997: Xsun screen saver on SX or GS leaks memory
  1162003: running Xsun screen saver on SX will cause Xsun to core dump
  1171622: cannot copy to child images of an image that is an SX window
  1171993: kernel dynamic range is incorrectly checked in Convolve8SX.cc

from (101594-05):
  1165877: In SDRC's Master Series, XOR highlight leaves dots behind on SX
  1168721: Same as 1165877
  1165987: SS20 with SX crashes with "Could not find a free SX_hmentblk"
  1163663: repeat xil_create_from_window/xil_destroy &gt; 253 causes di-215 error
  1157322: Xsun Server crashes, 100% repeatable
  1168685: xil_convolve on SX has unacceptable precision
  1168072: xil_cast needs to be ported to SX for 1-banded 16 bit images
  1169231: core dumped in bandCombine16
  1169267: sl_ctx_unspamify sometimes unmaps incorrect number of bytes

from (101594-04):
  1165665: UG crashes when doing rotations with gourand shading
  1165670: UG crashes when doing a context new frame before software shading
  1162672: When the graphics window is resized, UG crashes on SX
  1163842: error message from xil_scale molecule
  1162086: memory leak with xil_export and xil_scale

from (101594-03):
  1159605: sx xil_affine is different than memory_based xil_affine
  1160787: rect_convert_8_16_3 incorrectly converts 3-banded BYTEs to 3-banded
  1162155: zoom error with negative fractional offsets
  1159605: sx xil_affine is different than memory_based xil_affine
  1162153: insert and extract 16-bit bands do not work for certain channels
  1163914: clear of Z buffer can sometimes core dump if no cmem
   
from (101594-02):
  1154531: XCopyArea not X11 compliant
  1142933: Xsun core dumps while zoom-out of postscript doc using imagetool
  1159618: fp precision bug in pgon clipper
  1159624: screen-door transparency uses blend attr
  1159685: fix for core dumps and incorrect clipping
  1158709: xil crashes in zoom with certain src &amp; dst origin combinations
  1158946: xil crashes in zoom with negative image origins
  1158789: newframe ignores DC viewport
  1154156: Bilinear interpolation returns wrong result distination data by
  1154159: Bicubic interpolation does not compute correct pixel value over 9
  1154353: ROI's handled incorrectly in Scale16bicubic
  1155630: On SX, xil_scale (NN, sf&gt;2) to a display with an attached roi
  1156321: Any part of 2 scale facotr "nearest" destination XilImage appear
  1156324: Scale factor never work correctly on xil_scale as compared with
  1156617: xil_scale doesn't make proper image which ROI is set without
  1156202: sx-xil scale with bilinear interpolation causes ugly artifacts
  1156193: sx-xil does not interpolate pixels around boundaries during
  1156195: sx-xil does not interpolate pixels around boundaries during

from (101594-01):
  1151283: xil_scale with bilinear, .1., .1 never returns
  1154350: bad error chekcing in OrConst16
  1154354: perrormance problem in Scale16nearest
  1154358: linebytes problem in Threshold16
  1148227: xil_scale of a byte image with an integral scale factor
  1149845: xil_set_pixel() doesn't work (or maybe rescale)
  1154332: memory leak in Convolve8
  1154343: dangerous spamification in Lookup8_8
  1154344: performance problem copy'ing LUT in Lookup8_8
  1154002: JPEG decompression color brightness off by 1.164
  1155861: spamification problem in XilDeviceStorageTypeSX.cc
  1155862: Affine8nearest is broken
  1154376: Memory leak in CG14 driver
  1154338: memory leak in DivideConst8
  1154339: memory leak in Extrema16 
  1154341: memory leak in Extrema8
  1154338: memory leak in DivideConst8
  1154355: memory leak in SubtractConst8 
  1154357: memory leak in SubtractFromConst8
  1154359: memory leak in Translate16nearest
  1154360: memory leak in Translate8nearest
  1157480: memory leak in TranslateBL8SX.cc
  1154346: memory leak in MultiplyConst8.cc
  1157428: Transpose on SX core dumps and does not match memory code
  1157430: Transpose on CG14 core dumps and does not match memory code
  1157766: lookup16_16 outofbounds reg access  under xilch if called after
  1157096: SetValue8 cg14 molecule for 1 band does not replicate all four
  1155932: performance problem in Rescale16 
  1155782: performance problem in rgblinear to other color spaces; uncaced
  1155098: roi and roi_list not destroyed in Convolve16SX.cc for unsupported
  1154363: performance problem in xils_rgb7092rgblinear_8 
  1154361: performance problem in xils_photoycc2rgb709_8 
  1154352: planemasks handled incorrectly in Rotate8nearest 
  1154329: wrong planemask used on 3 band child images in Affine8nearest 
  1154279: 9x9 separable convolution needs to be integrated in sx/xil
  1154071: UniGraphics shows artifacts on SX
  1154835: SX driver crashes when rendering clipped triangle
  1155290: Pro/Engineer application crashes running short_test diagnostic
  1155658: Face distinguishing for msp incorrect if projection is parallel
  1141254: XGL/SX driver generates FPEs
  1142930: z-buffered lines have dropouts if no cmem
  1148240: AVS bounding box not erased through hardware renderer
  1157413: 2d line renderer does not punt if no contig-mem
  1157414: No win-lock is performed if double buffers are switched manually
  1157411: Transparency attrs used when transparency value = 0.0
  1157473: AA lines still drawn when rop != copy
  1143031: Colormap double buffering broken on Sx


Patch Installation Instructions: 
-------------------------------- 
Generic 'installpatch' and 'backoutpatch' scripts are provided
within each patch package with instructions appended to this section.
Other specific or unique installation instructions may also be
necessary and should be described below.

Special Install Instructions: 
----------------------------- 

After installing this patch, reboot the system to load the newly
installed driver.


Instructions to install patch using "installpatch"
--------------------------------------------------

1.  Become super-user.

2.  Apply the patch by typing:

	&lt;dir&gt;installpatch &lt;patch-dir&gt;

    where &lt;dir&gt; is the directory containing installpatch, and
    &lt;patch-dir&gt; is the directory containing the patch itself.

    Example:

	# cd /tmp/123456-01
	# ./installpatch .

3.  If any errors are reported, see "Patch Installation Errors" in
    the Command Descriptions section below.

    Rebooting the system or restarting the application after a successful
    patch installation is usually necessary to utilize patch.

    NOTE: 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 the next section for instructions
	  for installing a patch on a client.


Instructions for installing a patch on a dataless client
--------------------------------------------------------------------

1.  Before applying the patch, the following command must be executed
    on the server to give the client read-only, root access to the
    exported /usr file system so that the client can execute the
    pkgadd command:

    share -F nfs -o ro,anon=0 /export/exec/&lt;os_version&gt;/usr

    The command:

    share -F nfs -o ro,root=&lt;client_name&gt; \
		/export/exec/&lt;os_version&gt;/usr

    accomplishes the same goal, but only gives root access to the
    client specified in the command.

2.  Login to the client system and become super-user.

3.  Continue with step 2 in the "Instructions to install patch using
    installpatch" section above.


Instructions for installing a patch on a diskless client
--------------------------------------------------------------------

** To install a patch on a diskless client, you may either follow the
   instructions for installing on a dataless client (that is, you may
   logon to the client and install the patch), or you may use the
   following instructions to install the patch while on the server.

1.  Find the complete path for the root directory of the diskless
    client.

2. Install the patch normally, but add the command option -R &lt;path&gt;
   to the command line. &lt;path&gt; should be the completely specified.

   Example:

	# cd /tmp/123456-01
	# ./installpatch -R /export/root/client1 .

Instructions for backing out a patch using "backoutpatch"
-----------------------------------------------------------

1.  Become super-user. 

2.  Change directory to /var/sadm/patch:
 
        cd /var/sadm/patch
 
3.  Backout patch by typing:
 
        &lt;patch-id&gt;/backoutpatch &lt;patch-id&gt;
 
    where &lt;patch-id&gt; is the patch number.

    Example:

	# cd /var/sadm/patch
	# 123456-01/backoutpatch 123456-01

4.  If any errors are reported, see "Patch Backout Errors" in 
    the Command Descriptions section below.


Instructions for backing out a patch on a dataless client
----------------------------------------------------------

1. Give the client root access to /usr as specified in the installpatch
   section.

2. Logon to the client and follow backoutpatch instructions as
   specified above.


Instructions for backing out a patch on a diskless client
-----------------------------------------------------------

** To backout a patch on a diskless client, you may either follow the
   instructions for backout on a dataless client (that is, you may
   logon to the client and backout the patch), or you may use the
   following instructions to backout the patch while on the server.

1.  Find the complete path for the root directory of the diskless
    client.

2. Backout the patch normally, but add the command option -R &lt;path&gt;
   to the command line. &lt;path&gt; should be the completely specified.

   Example:

	# cd /export/root/client1/var/sadm/patch
	# ./123456-01/backoutpatch -R /export/root/client1 123456-01

Instructions for identifying patches installed on system:
----------------------------------------------------------

Patch packets that have been installed can be identified by
using the -p option. To find out which patches are installed on
a diskless client, use both the -R &lt;dir&gt; option and the -p
option, where &lt;dir&gt; is the fully specified path to the client's
root directory.

	#cd /tmp/123456-01
	#./installpatch -p
	#./installpatch -R /export/root/client1 -p

Also note that the command "showrev -p" will show the patches installed
on the local machine, but will not show patches installed on clients.

Command Descriptions
--------------------

NAME

     installpatch - apply patch package to Solaris 2.x system
     backoutpatch - remove patch package, restore previously saved files

SYNOPSIS

     installpatch [-udpV] [-S &lt;service&gt;] &lt;patch number&gt;
     backoutpatch [-fV] [-S &lt;service&gt;] &lt;patch number&gt;

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, turns off file validation.  Allows
		the patch to be applied even if some of the files to be
		patched have been modified since original installation.
          -d    Don't back up the files to be patched.  This means
                that the patch CANNOT BE BACKED OUT.
          -p    Print a list of the patches currently applied
          -V    Print script version number
          -S &lt;service&gt;
                Specify an alternate service (e.g. Solaris_2.3) for
                patch package processing references.
	  -R &lt;dir&gt;
		Specify an alternate package installation root. Most
		useful for installing patches on diskless clients
		while logged on to the server.

     backoutpatch:
         -f     force the backout regardless of whether the patch was
                superseded
         -V     print version number only
         -S &lt;service&gt;
                Specify an alternate service (e.g. Solaris_2.3) for
                patch package processing references.
	 -R &lt;dir&gt;
		Specify an alternate package installation root. Most
		useful for removing patches on diskless clients
		while logged on to the server.


DIAGNOSTICS

    Patch Installation Errors:
    --------------------------

    Error message:
	The prepatch script exited with return code &lt;retcode&gt;.
	Installpatch is terminating.

    Explanation and recommended action: The prepatch script supplied
	with the patch exited with a return code other than 0. Run a
	script trace of the installpatch and find out why the prepatch
	had a bad return code. Fix the problem and re-run installpatch.

	To execute a script trace:

	# sh -x ./installpatch . &gt; /tmp/patchout 2&gt;&amp;1

	The file /tmp/patchout will list all commands executed by
	installpatch. You should be able to determine why your prepatch
	script failed by looking through the /tmp/patchout file. If
	you still can't determine the reason for failure, contact
	customer service.

    Error message:
	The postpatch script exited with return code &lt;retcode&gt;.
	Backing out patch.

      Explanation and recommended action: The postpatch script
	provided with the patch exited with an error code other
	than 0, and the patch has not previously been applied.
	Installpatch will execute backoutpatch to return the system
	to its pre-patched state. Create a script trace of the
	installpatch (see above) and find out why the postpatch script
	failed. Correct and re-execute installpatch. If you are
	unable to determine why the postpatch script failed,
	contact customer service.

    Error message:
	The postpatch script exited with return code &lt;retcode&gt;.
	Not backing out patch because this is a re-installation.
	The system may be in an unstable state!
	Installpatch is terminating.

      Explanation and recommended action: The postpatch script
	provided with the patch exited with an error code other
	than 0. Because this is a re-installation of a patch,
	installpatch will not automatically backout the patch. 
	You may backout the patch manually using the backoutpatch 
	command, then generate a script trace of the installpatch 
	as described above. Find out why the postpatch failed, 
	correct the problem, and re-install the patch. If you are 
	unable to determine why the postpatch script failed, contact 
	customer service.

    Error message: 
	Patch &lt;patch-id&gt; has already been applied.

      Explanation and recommended action: This patch has already been
	applied to the system and no additional patch packages would
	be added due to a re-installation.  If the patch has to be 
	reapplied for some reason, backout the patch and then
	reapply it.

   Error message:
	Symbolic link in package &lt;pkg&gt;
	Symbolic links can't be part of a patch.
	Installpatch is terminating.

      Explanation and recommended action: The patch was incorrectly
	built. Contact customer service to get a new patch.

    Error message: 
	This patch is obsoleted by patch &lt;patch-id&gt; which has already
	been applied to this system. 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: 
	None of the packages to patch are installed on this system.

      Explanation and recommended action: The original packages for
	this patch have not been installed and therefore the patch
	cannot be applied.  The original packages need to be installed
	before applying the patch.

    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 -S and -R arguments are mutually exclusive.

      Explanation and recommended action: You have specified both a
	non-native service to patch, and a package installation root.
	These two arguments are mutually exclusive. If patching a
	non-native usr partition, the -S option should be used to patch
	all clients using that service. If patching a client's root 
	partition (either native or non-native), the -R option
	should be used.

    Error message:
	The &lt;service&gt; service cannot be found on this system.

      Explanation and recommended action: You have specified a non-
	native service to patch, but the specified service is not
	installed on your system. Correctly specify the service
	when applying the patch.

    Error message:
	The Package Install Root directory &lt;dir&gt; cannot be found on this system.
      Explanation and recommended action: You have specified a
	directory that is either not mounted, or does not exist on
	your system. Specify the directory correctly when applying
	the patch.

    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: 
	&lt;patch-id&gt; packages are not proper patch packages.

      Explanation and recommended action: The patch directory
	supplied as an argument to installpatch did not contain the
	expected package format.  Verify that the argument supplied
	to installpatch is correct. 

    Error message: 
	The following validation error was found:
	           &lt;validation error(s)&gt;

      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/patch to save old files.

      Explanation and recommended action:  There is insufficient
        space in the /var/sadm/patch 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 &lt;pkgname&gt; package failed with error code &lt;code&gt;.
	See /tmp/log.&lt;patch-id&gt; for reason for failure.

      Explanation and recommended action:  The installation of one of
	patch packages failed. Installpatch will backout the patch
	to leave the system in its pre-patched state.  See the log file
	for the reason for failure.  Correct the problem and
	re-apply the patch.

   Error message:
	Pkgadd of &lt;pkgname&gt; package failed with error code &lt;code&gt;.
	Will not backout patch...patch re-installation.
	Warning: The system may be in an unstable state!
	See /tmp/log.&lt;patch-id&gt; for reason for failure.

      Explanation and recommended action:  The installation of one of
	the patch packages failed. Installpatch will NOT backout the 
	patch.  You may manually backout the patch using backoutpatch,
	then re-apply the entire patch. Look in the log file for the 
	reason pkgadd failed.  Correct the problem and re-apply the 
	patch.

    Patch Installation Messages:
    ---------------------------

    Note: the messages listed below are not necessarily considered errors
    as indicated in the explanations given.  These messages are, however,
    recorded in the patch installation log for diagnostic reference.
    
    Message:
        Package not patched:
        PKG=SUNxxxx
        Original package not installed

      Explanation: One of the components of the patch would have patched a
        package that is not installed on your system. This is not
        necessarily an error. A Patch may fix a related bug for several
        packages. Example: suppose a patch fixes a bug in both the
        online-backup and fddi packages. If you had online-backup installed
	but didn't have fddi installed, you would get the message

        Package not patched:
        PKG=SUNWbf
        Original package not installed

        This message only indicates an error if you thought the package
        was installed on your system. If this is the case, take the
        necessary action to install the package, backout the patch (if
        it installed other packages) and re-install the patch.
 
    Message:
        Package not patched:
        PKG=SUNxxx
        ARCH=xxxxxxx
        VERSION=xxxxxxx
        Architecture mismatch
 
      Explanation: One of the components of the patch would have patched a
        package for an architecture different from your system. This is not
        necessarily an error. Any patch to one of the architecture specific
        packages may contain one element for each of the possible
        architectures. For example, Assume you are running on a sun4m. If
        you were to install a patch to package SUNWcar, you would see the
        following (or similar) messages:
 
        Package not patched:
        PKG=SUNWcar
        ARCH=sparc.sun4c
        VERSION=11.5.0,REV=2.0.18
        Architecture mismatch
 
        Package not patched:
        PKG=SUNWcar
        ARCH=sparc.sun4d
        VERSION=11.5.0,REV=2.0.18
        Architecture mismatch
 
        Package not patched:
        PKG=SUNWcar
        ARCH=sparc.sun4e
        VERSION=11.5.0,REV=2.0.18
        Architecture mismatch
 
        Package not patched:
        PKG=SUNWcar
        ARCH=sparc.sun4
        VERSION=11.5.0,REV=2.0.18
        Architecture mismatch
 
        The only time these messages indicate an error condition
        is if installpatch does not correctly recognize your architecture.
 
    Message:
        Package not patched:
        PKG=SUNxxxx
        ARCH=xxxx
        VERSION=xxxxxxx
        Version mismatch
 
      Explanation: The version of software to which the patch is applied is
        not installed on your system. For example, if you were running Solaris
        5.3, and you tried to install a patch against Solaris 5.2, you would
        see the following (or similar) message:
 
        Package not patched:
        PKG=SUNWcsu
        ARCH=sparc
        VERSION=10.0.2
        Version mismatch
 
        This message does not necessarily indicate an error. If
        the version mismatch was for a package you needed patched, either
        get the correct patch version or install the correct package version.
        Then backout the patch (if necessary) and re-apply.
 
    Message:
	Re-installing Patch.

      Explanation: The patch has already been applied, but there is
	at least one package in the patch that could be added. For
	example, if you applied a patch that had both Openwindows and
	Answerbook components, but your system did not have Answerbook
	installed, the Answerbook parts of the patch would not have
	been applied. If, at a later time, you pkgadd Answerbook, you
	could re-apply the patch, and the Answerbook components of the
	patch would be applied to the system.
 
     Message:
	Installpatch Interrupted.
	Installpatch is terminating.

      Explanation: Installpatch was interrupted during execution
	(usually through pressing ^C). Installpatch will clean up
	its working files and exit.

     Message:
	Installpatch Interrupted.
	Backing out Patch...

      Explanation: Installpatch was interrupted during execution
	(usually through pressing ^C). Installpatch will clean up
	its working files, backout the patch, and exit.

    Patch Backout Errors:
    ---------------------

    Error message:
	prebackout patch exited with return code &lt;retcode&gt;.
	Backoutpatch exiting.

    Explanation and corrective action: the prebackout script
	supplied with the patch exited with a return code other
	than 0. Generate a script trace of backoutpatch to determine
	why the prebackout script failed. Correct the reason for
	failure, and re-execute backoutpatch.

    Error message:
	postbackout patch exited with return code &lt;retcode&gt;.
	Backoutpatch exiting."

      Explanation and corrective action: the postbackout script
	supplied with the patch exited with a return code other than
	0. Look at the postbackout script to determine why it failed.
	Correct the failure and, if necessary, RE-EXECUTE THE 
	POSTBACKOUT SCRIPT ONLY.

    Error message:
	Only one service may be defined.

      Explanation and corrective action: You have attempted to specify
	more than one service from which to backout a patch. Different
	services must have their patches backed out with different
	invocations of backoutpatch.

    Error message:
	The -S and -R arguments are mutually exclusive.

      Explanation and recommended action: You have specified both a
	non-native service to backout, and a package installation root.
	These two arguments are mutually exclusive. If backing out a
	patch from a non-native usr partition, the -S option should be 
	used. If backing out a patch from a client's root 
	partition (either native or non-native), the -R option
	should be used.

    Error message:
	The &lt;service&gt; service cannot be found on this system.

      Explanation and recommended action: You have specified a non-
	native service from which to backout a patch, but the 
	specified service is not installed on your system. Correctly
	specify the service when backing out the patch.

    Error message:
	Only one rootdir may be defined.

      Explanation and recommended action: You have specified more than
	one package install root using the -R option. The -R option
	may be used only once per invocation of backoutpatch.

    Error message:
	The &lt;dir&gt;  directory cannot be found on this system.

      Explanation and recommended action: You have specified a
	directory using the -R option which is either not mounted,
	or does not exist on your system. Verify the directory name
	and re-backout the patch.

    Error message:  
	Patch &lt;patch-id&gt; has not been successfully applied to this system.

      Explanation and recommended action: You have attempted to backout
	a patch that is not applied to this system. If you must
	restore previous versions of patched files, you may have to
	restore the original files from the initial installation CD.

    Error message:  
	Patch &lt;patch-id&gt; has not been successfully applied to this system.
	Will remove directory &lt;dir&gt;

      Explanation and recommended action: You have attempted to back
	out a patch that is not applied to this system. While the
	patch has not been applied, a residual 
	/var/sadm/patch/&lt;patch-id&gt; (perhaps from an unsuccessful
	installpatch) directory still exists. The patch cannot be 
	backed out. If you must restore old versions of the patched
	files, you may have to restore them from the initial 
	installation CD.

    Error message:  
	This patch was obsoleted by patch &lt;patch number&gt;.
        Patches must be backed out in the order in
        which they were installed. Patch backout aborted.
 
      Explanation and recommended action: You are attempting to backout
	patches out of order. Patches should never be backed-out out 
	of sequence.  This could undermine the integrity of the more 
	current patch.

    Error message:
	Patch &lt;patch-id&gt; 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 &lt;pkgname&gt; package failed return code &lt;code&gt;.
	See /var/sadm/patch/&lt;patch-id&gt;/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.
 
     A bug affecting a package utility (eg. pkgadd, pkgrm, pkgchk)
     could affect the reliability of installpatch or backoutpatch 
     which uses package utilities to install and backout the patch 
     package.  It is recommended that any patch that fixes package 
     utility problems be reviewed and, if necessary, applied before
     other patches are applied.  Such existing patches are:

	100901	Solaris 2.1
	101122	Solaris 2.2
	101331	Solaris 2.3

SEE ALSO
     pkgadd, pkgchk, pkgrm, pkginfo, showrev, cpio


</pre></body></html>