(Improved agile device selection and recovery has eliminated the need for this feature and might result in this step being removed in the future.)

5.Configuration content from the install file system is loaded to determine if the Ignite TUI should be started and if special inventory control is needed. (The Ignite TUI is started by default.)

6.A system I/O inventory is performed. This identifies devices where HP-UX may be installed, and identifies devices and networks used to accomplish installation. Install file system configuration and boot loader option content may be used to control inventory. The boot source is also determined.

7.Unless configuration information directs otherwise, the Ignite TUI is launched on the client.

•The operation to be performed is set. (Advanced Install is the default operation.)

•Networking configuration information is determined, if the installation requires the network.

•The complete set of Ignite configuration files is read and parsed. Note that changing the Configuration or Environment will result in rereading and parsing config content, since these changes generally result in changes to the set of config files.

•System, software, file system, and other configuration changes are gathered via the interface.

•When Go! is selected from the user interface, the requested installation or recovery is launched.

•Configuration sanity checking is performed. If there are problems, you are returned to the TUI.

•The modified configuration is saved to control installation or recovery processing.

8.If the TUI was not selected to launch, sanity checking is done on the selected config.

Phase 1

Storage is set up and Ignite relocates to the new disk file system. The result of this phase is the install or recovery functionality running on what appears to be a normal disk-based file system, and if recovery, an I/O configuration that appears to be restored. Some aspects of the configuration cannot be fully restored until reboot. Processing for this phase is done on a RAM file system.

1.During a recovery, the original I/O configuration is restored if I/O instance data is present in the config. Some aspects of the configuration might be instantly changed. Some aspects are temporarily changed and will be finalized during reboot. If the current system is different, some aspects of the I/O configuration will be impossible to restore.

2.Create disk partitions if needed (Integrity systems only).

3.Create volume manager volumes as needed.

4.Create and mount file systems.

5.Determine software sources and selections.

6.Run pre-config control scripts.

7.Set boot path.

8.Set up and enable swap space.

9.Save final volume configuration data to disk file system.

10.Set locale.

11.Move needed content from RAM file system to disk file system. Load the complete set of commands, libraries, and other files required to accomplish installation and recovery from Ignite command archives to the new disk file system (SYSCMDS or SYSCMDSIA).

12.Change the root directory to the disk file system with chroot.

Phase 2

File content is installed or restored. The result of this phase is the final disk file system and content. Some cleanup and processing that must be done after system reboot is still required. For the HP-UX

How Ignite works 21