Software Distributor (SD-UX) Administration Guide HP-UX 11i v1, 11i v2, and 11i v3 (762797-001, March 2014)

* (If not concerned with the machine type.)
9000/7??:32* (Series 700, 32-bit capable hardware required)
*:*64 (64-bit capable hardware required)
*:32: (32-bit capable hardware required)
9000/7??:*64 (Series 700, 64-bit capable hardware required)
9000/[78]??:32* (Series 800, 32-bit capable hardware required)
9000/[78]??:*64 (Series 800, 64-bit capable hardware required)
The value is matched against a target’s uname -m or getconf
_CS_HW_CPU_SUPP_BITS result.
number The part or order number of the product.
os_name The operating system name on which the product will run. If not specified, the
attribute is assigned a value of *, meaning it will run on all operating systems.
If there are multiple operating systems, use wildcards or the | symbol to
separate them. The value is matched against a target’s uname -s or getconf
_CS_KERNEL_BITS result.
os_release The release number of the product’s operating system. If not specified, the
attribute is assigned a value of *, meaning it will run on all operating systems.
If there are multiple operating systems, use wildcards or the | symbol to
separate them. The value is matched against a target’s uname -r result.
os_version The version number of the operating system(s) on which the product will run.
If not specified, the attribute is assigned a value of *, meaning it runs on any
version. If there are multiple operating systems, use wildcards or the | symbol
to separate them. The value is matched against a target’s uname -v result.
postkernel Defines a kernel build script to be executed when kernel filesets are loaded.
Kernel filesets have the is_kernel attribute set to true. The default kernel
script is /usr/sbin/mk_kernel. (See the manual reference page for
mk_kernel(1M) for more information.) The default script executes when the
postkernel attribute is not specified. Only one kernel build script is allowed
per product, and the script executes only once, even if defined for multiple
filesets.
readme A text file of the README information for the product. The value must be a
pointer to the filename containing the text
revision The revision information (release number, version) for the product or bundle.
title A one-line string that further identifies the product or bundle.
vendor_tag Associates this product or bundle with a vendor object defined separately in
the PSF, if that object has a matching tag attribute.
end Ends the product or bundle specification. No value is required. This keyword
is optional. If you use it and it is incorrectly placed, the specification will fail.
Control Script Specification
SD-UX supports execution of product and fileset control scripts that allow you to perform additional
checks and operations with other HP-UX commands and functions. The swask, swinstall,
swconfig, swverify, and swremove commands each can execute one or more control scripts
on the primary roots. All scripts are optional but many times are needed correctly complete the
task that you want your software package to perform. See Chapter 11: “Using Control Scripts ”
(page 201) for a complete discussion of control scripts.
Creating a Product Specification File (PSF) 179