ssoPatch -- map new version or component into an SSO member file


ssoPatch [-q] [-l] [-c vendorCode:componentCode] [-v version]
filename [filename...]


The ssoPatch utility patches a new version or component into a Software Storage Object (SSO) member file. ssoPatch works in conjunction with the SSO Path Mapping API for executables, shell scripts, and Tcl scripts.

ssoPatch recognizes the following options:

List the patches found, but do not modify the file.

Perform the operation quietly.

-c vendorCode:componentCode
Specify the vendor and component codes on which to set the version. This updates all matching patch areas found.

-C vendorCode:componentCode
Specify the new vendor and component codes. This changes all components matching the values specified with -c.

-v version
Specify the version number to set in the patch areas.
The start and end patterns are defined as simple strings SSO_COMPID_START_STRING and SSO_COMPID_END_STRING in the /usr/include/sso/pathMap.h file. Everything between the end of the start string and the beginning of the end string is interpreted as the patch area. No checksum or other size information is defined.

NOTE: If the end pattern is not accurate and another end pattern accidentally occurs later in the same file, it is possible for the patch to corrupt the file. To avoid this, check the file beforehand using -l to verify that reasonable sizes and offsets for patch areas are located.

Exit values

If execution was successful, ssoPatch exits with a value of 0. If execution failed, ssoPatch exits with 1.



See also


``About the SSO Path Mapping API'' in Developer's Topics

Standards conformance

ssoPatch is not part of any currently supported standard; it is an extension of AT&T System V provided by The Santa Cruz Operation, Inc.
© 2003 Caldera International, Inc. All rights reserved.
SCO OpenServer Release 5.0.7 -- 11 February 2003