Non-Interactive Installation Using Bootsys - HP 9000 Manual

Installing from the Ignite-UX Server
Executing the Installation: Go!
• Swap Configuration
• Kernel Configuration.
• System Information.
The manifest file is saved on the server as
/var/opt/ignite/clients/LLA/manifest/manifest. It is on the
target client system as /var/opt/ignite/local/manifest/manifest.
Using the Ignite-UX interface or the command line, the
/opt/ignite/bin/print_manifest utility prints these files in ASCII
to stdout, using the format instructions from the manifest template file
If the client data is moved to history, that data includes both the client's
manifest and config file. Both these files can be recalled at a later time.

Non-Interactive Installation Using bootsys

The bootsys command can be used to start a system installation on one
or more clients without the need to interact on the console of the client
system. The only requirements are that each client must be currently
booted under HP-UX version 9.0 or newer, and each client must be
accessible on the network. Each will also need to have enough disk space
in the /stand directory to hold the two files:
/opt/ignite/boot/INSTALL and /opt/ignite/boot/INSTALLFS.
bootsys copies the Ignite-UX kernel and RAM filesystem to each client
and then sets the system AUTO file in the LIF area of the root disk to
automatically boot from this kernel at the next system reboot.
Examples: The following sample command line will boot the client system from the
server and wait for install instructions from the Ignite-UX GUI:
To automatically install system1 using a different IP address than what
is currently assigned and without waiting for server interaction, you
would type a line similar to the following:
See the man entry for the bootsys(1m) command for more examples and
information.
120
bootsys -w system_name
bootsys -a system1:1.2.3.45
Chapter 5