Ignite-UX Installation Booting

4. The client retrieves the boot file from the Ignite-UX server using firmware implemented tftp,

and then extracts the ISL.

5. The ISL on the client reads the AUTO file from the boot LIF.

6. The secondary loader reads from the boot LIF and is started with the information read from the

AUTO file.

At this point, both ISL and the secondary loader are set to read from the LAN device. Using a /

(forward slash) in the file name when designating a LAN device causes tftp to access a file,

or if a disk is designated to read from a file system.

In a default Ignite-UX installation, the AUTO file read by a system booting via the network should

contain hpux (;0)/boot/INSTALL. Due to the way NFS diskless was originally designed,

the secondary loader translates the kernel path by taking the path of the boot file,

/opt/ignite/boot/boot_lif, and removing the last two path elements, leaving

/opt/ignite, and then by appending the name from the AUTO file, resulting in

/opt/ignite/boot/[W|V|I]INSTALL

7. The secondary loader loads the INSTALL kernel and executes it.

. This design allows the kernels to be in client-

specific directories without needing each LIF volume to have a different AUTO file.

8. The INSTALL kernel loads the RAM file system, INSTALLFS.

The kernel loads the installation file system by making calls back into secondary loader to load

the file system. At this stage, the kernel cannot read anything from the Ignite-UX server. The

kernel does not have any initialized LAN interfaces from which the installation file system can

be read.

The kernel starts init from the installation file system just loaded. The init process then starts

the installation or recovery process.

As of Ignite-UX version C.6.0.x, all installation kernels are located in release-specific directories so the boot kernel for an 11.11 PA-RISC

system is /boot/Rel_B.11.11/INSTALL not /boot/INSTALL.