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

The command line is most effective for:
• Quickly executing simple commands
• Executing tasks that take a long time to accomplish
• Creating commands for later execution by scripts
A typical command line might look like this:
Figure 15 Sample Command
The example shows that you have several ways to specify SD-UX behavior including command-line
options (such as -f and -s), input files (mysoft and /mnt/cd), and target selections.
A complete list of command line components includes:
• Software selections and software selection files ((page 35))
• Target selections and target selection files ((page 37))
• Command-line options ((page 37))
• Session files ((page 39))
Each item on this list is discussed in more detail in the following sections.
Software Selections
Software selections let you specify software in great detail. You can also use an input file to specify
software.
Syntax
The software_selections syntax is identical for all SD-UX commands that require it
(bundle[.product[.subproduct][.fileset]][,version] and
product[.subproduct][.fileset][,version]):
• The = (equals) relational operator lets you specify selections with the following shell wildcard
and pattern-matching notations:
[ ] Square brackets—groups an expression
* Asterisk—wildcard for multiple characters
? Question mark—wildcard for a single character
For example, the following expression installs all bundles and products with tags that end with
man:
swinstall -s sw_server \*man
• Bundles and products are recursive. Bundles can contain other bundles. For example:
swinstall bun1.bun2.prod.sub1.fset,r=1.0
or (using expressions):
swinstall bun[12].bun?.prod.sub*,a=HP-UX
• The \* software specification selects all products.
CAUTION: To avoid data loss, use the \* specification with considerable care (such as
when removing software from the root directory, /).
Working from the Command Line 35