bootsys.1m (2012 03)

b
bootsys(1M) bootsys(1M)
for more information on configuration 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 operating sys-
tem. 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 configuring a
.rhosts file 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 configuration
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
files copied to the client before it reboots.
-f Causes bootsys to remove all the client’s prior configuration 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 configuration information from being used. This option
causes the files /var/opt/ignite/clients/0x
LLA/config and
/var/opt/ignite/clients/history/0x
LLA/config to be removed or emptied.
-i configuration
Specifies a system configuration to be used for clients. If any clients have a file in the directory
/var/opt/ignite/clients/0x
LLA/ that conflicts with the configuration 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 configuration file
and force it to the given configuration .
The configuration parameter must be a quoted string matching a configuration found in the
/var/opt/ignite/data/INDEX
file. The configurations available may be listed with the
command:
/opt/ignite/bin/manage_index -l
-R target_operating_system_release
Specifies 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 con-
taining the required Ignite-UX kernel and RAM file system must exist under
/opt/ignite/boot, for example /opt/ignite/boot/Rel_B.11.23
. This option can-
not be used with the
-i option. The -f option may be used with this option in order to have
bootsys remove the client’s configuration file and force it to the given target operating system.
-l sw-sel=true|false
One or more -l options may be supplied to modify the default software that is selected for
loading by the set of clients being installed. This is useful when automating installations
where using just the -i option to select the configuration does not give enough control. An
example command line usage of this option is:
bootsys -l golden image1=true \
-l golden image2=false myclient
-V var=value
One or more -V options may be supplied to set a value to a variable. The possible values may
be a number, a number followed by a size suffix, or a string. A size suffix can be K or KB
for kilobytes, or M or MB for megabytes. An example command line usage of this option is:
bootsys -V foo1=fooval -V foo2=200MB myclient
2 Hewlett-Packard Company − 2 − HP-UX 11i Version 3: March 2012