Ignite-UX Installation Booting

4
The kernel loads the installation file system by executing calls to the secondary loader to load
the file system. Since the kernel has not initialized the input/output (I/O) subsystem, it has no
ability to access a disk device to read from the installation media.
8. The kernel starts init from the installation file system that was just loaded.
9. Lastly, init starts the installation or recovery process.
Booting from a CD or DVD with HP-UX 11i v2 and greater
The Ignite-UX C.6.0.x version, which supports HP-UX 11i v2 (B.11.23) and greater, contains
installation kernels specific to each supported release of the operating system. In order to select the
correct kernel for your client at network installation time, the bootloader was enhanced to
understand additional AUTO file syntax.
This additional syntax causes hpux to prompt you for the target HP-UX release for the client, for
example B.11.23, and then it retrieves the installation kernel appropriate for that release. The
default prompts and other options of the additional AUTO file syntax can be modified using the
auto_adm command introduced in the Ignite-UX C.6.0.x version. For more information, refer to
auto_adm(4).
Booting from a tape
The only difference between booting from media and tape is that the tape is a serial device so it
requires rewinding and forwarding to access different parts of the tape to locate the files the LIF
points to on the tape.
Booting from a LAN
System booting from a LAN is as follows:
1. The command to boot from the LAN is entered at the BCH prompt.
The IP Address of the server to boot from is optional, and if given, only responses from that
server are accepted.
2. The client performs a bootp broadcast in an attempt to find an Ignite-UX server. The bootp
broadcasts do
not go outside of the local LAN segment. If the Ignite-UX server is on a different
LAN segment and there is no local boot helper, the system fails to boot
3. The Ignite-UX server provides a bootp response to the client.
If the install option was given to the BCH to boot from the LAN, the bootp protocol is still
used. However, the User Datagram Protocol (UDP) ports used are 1067/1068 instead of the
standard 67/68. These custom ports for installation allow you to install HP9000 HP-UX systems
without any interference from other systems. Only the Ignite-UX daemon instl_bootd is set to
listen on these ports for bootp traffic, so only instl_bootd responds. All of the necessary
client boot information is provided in the bootp response.
The response from instl_bootd returns /opt/ignite/boot/boot_lif as the boot file.