swinstall.1m (2011 09)

ManualsBrandsHP ManualsSoftwareHP-UX Manpages

swinstall(1M) swinstall(1M)

To invoke the GUI, enter

swinstall

swcopy

on the command line (without any command-line options).

You can also invoke the GUI by including the

-i option with any other command-line options.

The

sd command provides an interactive interface for monitoring and scheduling software jobs. You can

also use sd to invoke the swinstall,

copy, and swremove GUIs.

If you have enabled SD’s remote operations features,

swinstall, swcopy, and swremove provide

enhanced GUIs to support operations on remote targets. See

Remote Operation above for details

about enabling remote operations and the enhanced GUIs.

The command-line version of

swinstall can also function interactively when the

ask option is set to

true. This option executes an interactive request script . Request scripts can also be executed by

swconfig and swask. See swconﬁg(1M) and swask(1M), and the

ask=false default option for more

information.

Updating the Operating System

To perform an operating system update, HP recommends that you use the

update-ux command. This

command replaces swgettools to update the operating system to HP-UX 11.11 or higher. update-ux

is not available on 11.00 systems. To perform an update from 11.00 to 11.11 or higher, install

update-

ux from the new operating system media. Then use update-ux to update the OS. See update-ux (1M)

on an 11i system for more information.

Reinstalling SD

If your copy of SD becomes unusable or if you want to install a newer version of SD, HP recommends that

you use the

install-sd command. This command reinstalls SD and also installs any SD patches that

exist in the source depot.

Installing Kernel Software

In HP-UX, the kernel installation process requires that the system boots using the kernel at

/stand/vmunix. Make sure that your system is booted to the

/stand/vmunix kernel before you

install any kernel software or perform an operating system update.

Dependencies Between Software

The

swinstall command supports dependencies , which is software that must be present or absent

before or during the installation of another piece of software. Dependencies apply between ﬁlesets and

other ﬁlesets and products. SD supports three types of dependencies: prerequisites that must be

installed and conﬁgured before the dependent ﬁleset is installed and conﬁgured (respectively); core-

quisites that must be installed and conﬁgured before the dependent is usable. exrequisites that prevent a

dependent ﬁleset from being installed or conﬁgured when they are present.

If a software_selection speciﬁes a dependency on other ﬁlesets and/or products,

swinstall automati-

cally select that software.

By default, all dependencies must be resolved before

swinstall can proceed. You can override this

policy using the enforce_dependencies option.

Note that if you specify a dependency for a ﬁleset and the ﬁleset is superseded by another ﬁleset as part

of a patch,

swinstall still recognizes the dependency.

Features and Differences between swinstall and swcopy

The key difference between

swinstall and swcopy is that swinstall performs the software ins-

tallation, while swcopy copies software into a depot, making it available as a source for installation by

swinstall.

NOTE: To copy to a tape, see the swpackage (1M) manpage.

Other features (differences) include:

• The

swinstall command executes several vendor-supplied scripts during the installation and

conﬁguration of the software_selections. The swcopy command does not execute these scripts.

The swinstall command supports the following scripts:

2 Hewlett-Packard Company − 2 − HP-UX 11i Version 3: September 2011