The bootsys command must update the AUTO file in the LIF area of the remote client. The command stored in the AUTO file will be similar to " hpux /stand/WINSTALL ", the /stand/WINSTALL file being the Ignite -UX kernel. Once this has been updated, the bootsys command will reboot the remote client in order to start the Ignite-UX kernel/interface.
A2:
The /etc/opt/ignite/instl_boottab file contains temporary IP addresses assigned to network installation clients when they boot across the network. The IP addresses are temporary addresses used simply to give the client an IP configuration in order for it to communicate with the installation server during the installation process. As such, the information in this file is not unique to every install client (although the IP addresses can be reserved for specific clients ). The real IP address for the client will be supplied during the installation process itself. The IP process that uses the instl_boottab file is the instl_bootd server spawned by inetd .
A3:
The first 8KB of INSTALLFS is important because it contains default Ignite-UX parameters that control the installation of software. We can add to or modify the parameters in this 8KB header. In this way, we can perform additional tasks once the installation is complete.
A4:
We may have to use the make_bundles command, because software stored in a Software Distributor depot may not have a bundle specification describing the software in the depot. This is not a problem for Software Distributor itself, because it can understand software when described at the product level. Ignite-UX, however, needs software to be described in bundles . Consequently, make_bundles can understand products and will produce a suitable Product Specification File, from which it can produce a suitable bundle specification for the intended software.
A5:
Impact statements describe the amount of space required in a given filesystem when loading software. Ignite-UX will normally calculate the impact statements when creating a configuration file based on a software depot. When managing a Golden Image, this step needs to be performed manually. The command archive_impact is used to calculate the impact statements for a Golden Image.
