Installing HP-UX 11.0 and Updating HP-UX 10.x to 11.0 HP 9000 Computers Edition 1

Appendix C 251

Ignite-UX System Administration

Section 4: Customization

This section will focus on ways to customize the default conﬁguration,

either by adding additional info to the default conﬁg (dynamic

parameters) or by adding additional software selections to be loaded

after the archive.

We’ll be adding the following:

• SD Bundles

• Kernel parameters

• Additional install parameters, e.g. swap and networking info

Adding an SD Bundle to the Archive

Environment

Ignite-UX allows you to add patch bundles to your conﬁguration. These

bundles can be forced to load at install time, or can be selectable by the

user. This allows the system admin to install the base Operating System

very quickly with an Ignite-UX archive, and still have the ﬂexibility to

install additional software components selectively, based on machine

type or use (for example: server vs client).

In the following example we’ll explore adding a bundle which consists of

patches, which would be a typical application. You must begin with a

patch bundle, not just a patch depot. You can verify the existence of

bundles with the following command:

# swlist -l bundle -d @ /yourdepot

“Setting Install Parameters Dynamically” lists the procedure used to

create a patch bundle from an existing depot of individual patches.

(You might need to call swreg -l depot /yourdepot to register this depot,

depending on how it originated.)

1. Assuming a S700 patch bundle in the /var/opt/ignite/PB depot, run

the following Ignite-UX command to create a conﬁg ﬁle that Ignite-UX

can use:

# make_config -s /var/opt/ignite/PB -a 700 -c \

/var/opt/ignite/data/Rel_B.11.00/patch_bundle_cfg