Ignite-UX Reference (March 2010, B3921-90005)

ManualsBrandsHP ManualsSoftwareHP Ignite-UX

bootsys(1M) bootsys(1M)

-w Causes the client system to boot Ignite-UX and then wait for the ignite user interface

running on the Ignite-UX server to instruct the client on how to proceed with the installa-

tion.

If neither the -a nor the -w option is given, the client will boot using the default mode

stored in the /opt/ignite/boot/Rel_release/*INSTALLFS ﬁle. The keywords that

control executing the user interface are control_from_server and run_ui. See

instl_adm(4) for more information on conﬁguration keywords.

-d Causes bootsys to ignore any clients listed that are down, cannot be accessed with

remsh, or are incompatible with the indicated target operating system. bootsys will

continue operating on systems that can be accessed and are compatible with the target oper-

ating system. Without the -d option, bootsys will prompt for the root password of

clients that do not allow remsh access, and will exit if any client appears to be down.

The -d option should be used when executing bootsys from a crontab entry so that

it will prevent bootsys from trying to prompt for passwords.

The user must take appropriate actions, such as conﬁguring a .rhosts ﬁle or setting up

SSH keys before running bootsys to ensure automatic execution can successfully occur

using this option.

-v Causes bootsys to give verbose messages.

-h Prevents bootsys from inserting the client’s host name and IP address into the conﬁgura-

tion information copied to the client. This may be useful if you would rather have the client

obtain this information using the DHCP or BOOTP protocol when it boots. You must have

a DHCP server, or a server with an /etc/bootptab entry for the client, if you use this

option or an interactive menu appears on the client on the console to obtain networking

information.

-r Causes bootsys to prepare each client for install but suppresses rebooting the system.

This may be useful if you want to use a different method to reboot the system, or wish to

check the ﬁles copied to the client before it reboots.

-f Causes bootsys to remove all the client’s prior conﬁguration history before rebooting the

client. This ensures that it uses all the default parameters, and that either the -i or -R

option takes effect preventing past conﬁguration information from being used. This option

causes the ﬁles /var/opt/ignite/clients/0xLLA/config and

/var/opt/ignite/clients/history/0xLLA/config to be removed or emptied.

-i conﬁguration

Speciﬁes a system conﬁguration to be used for clients. If any clients have a ﬁle in the direc-

tory /var/opt/ignite/clients/0xLLA/ that conﬂicts with the conﬁguration given

with the -i option, bootsys returns an error. This option cannot be used with the -R

option. The -f option may be used with this option to have bootsys remove the client’s

conﬁguration ﬁle and force it to the given conﬁguration.

The conﬁguration parameter must be a quoted string matching a conﬁguration found in the

/var/opt/ignite/data/INDEX ﬁle. The conﬁgurations available may be listed

with the command:

/opt/ignite/bin/manage_index -l

-R target_operating_system_release

Speciﬁes the version of the HP-UX operating system that will be installed on the client.

For example, -R B.11.23. A release directory matching the selected target operating

system containing the required Ignite-UX kernel and RAM ﬁle system must exist under

/opt/ignite/boot, for example /opt/ignite/boot/Rel_B.11.23. This

option cannot be used with the -i option. The -f option may be used with this option

in order to have bootsys remove the client’s conﬁguration ﬁle and force it to the given tar-

get operating system.