Manualshelf

HP-UX HB v13.00 Ch-05 - SD-UX

ManualsBrandsHP ManualsSoftwareHP-UX 11i v3 Virtual Server Operating Environment (VSE-OE) LTU
12345678910
HP-UX Handbook – Rev 13.00 Page 8 (of 49)
Chapter 05 Software Distributor (SD-UX)
October 29, 2013
IPD directory, each bundle and product gets its own directory.
# ll /var/adm/sw/products
total 6648
dr-x------ 473 root sys 11264 Apr 9 12:24 ./
drwxr-xr-x 13 bin bin 1024 Apr 9 16:08 ../
drwxr-xr-x 7 root sys 1024 Apr 25 2002 Accounting/
drwxr-xr-x 5 root sys 96 Apr 25 2002 ApacheStrong/
drwxr-xr-x 11 root sys 1024 Apr 25 2002 Asian-Core/
...
-rw-r--r-- 1 root sys 1960447 Apr 4 10:34 INDEX
Underneath those directories for all products and bundles one will find the control directories.
Control directories have names like “?files”. For example “ifiles” which is the IPD control
directory, “pfiles” which are bundle and product control directories and “dfiles” which are
depot control directories. Control directories contain control information for the object they refer
to. Here is the type of information that is saved and what file it is contained in:
File
Control Information
INDEX
Bundle, product, subproduct, fileset and IPD attributes (revision, architecture,
is_patch, …). These are the fragment INDEX files from which the master
INDEX file gets created.
INFO
File attributes (path, cksum, mode, …)
file
Files referred to by an attribute. For example, "readme README". The file
README is saved in the control directory.
control scripts
preinstall, postinstall, configure, …
response file
swask response files are saved in the control directory.
_ACL
root ACL file (in IPD control dir only)
_OWNER
root owner file (in IPD control dir only)
Master Index
The master index is a single file – /var/adm/sw/products/INDEX – containing all the attribute-
value pairs from each control directory INDEX file. Frequently, if the master INDEX is
corrupted, it may be rebuilt by concatenating all the good fragment INDEX's, see rebuild the
Master INDEX file..
Session Files
Session files let you save your work from a command session. Each invocation of an SD-UX
command defines a session. The invocation options, source information, software selections, and
target hosts are saved before command execution actually commences. This lets you re- execute
the command even if the session ends before proper completion. Each session is saved to the file