Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
Ignite-UX Administration Guide: HP Computers with HP-UX 10.x, 11.0 or 11i > Chapter 10 Creating Your Own Install Media

System Bootup Sequence

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

This sequence of events occurs when an HP computer system boots up:

  1. The firmware determines from which device to boot via either user input or primary path.

  2. The firmware looks for a LIF header on that device, and if it finds it, it looks in the LIF header for where the ISL starts.

  3. The firmware loads the ISL into memory from the boot device and executes it. It passes a flag to it that indicates whether to run interactively or to autoboot.

  4. If the ISL is interactive then it gives the ISL> prompt and waits for user input before proceeding.

  5. If the ISL is not interactive, then it looks for the AUTO file on the boot device to determine what to run next.

  6. The AUTO file or user input usually supplies the hpux args command. This tells ISL to load the program HPUX from the LIF header on the boot device and to run it with the given arguments.

  7. The hpux program (also known as the secondary loader) figures out what HP-UX kernel to load, and what arguments to pass to it (like init state).

  8. hpux loads the kernel and starts running it.

  9. For the INSTALL kernel, the kernel looks at its name and realizes that it fits the pattern *INSTALL and then loads the matching *INSTALLFS file from the boot device.

In all these cases the firmware (Processor Dependent Code, or PDC) API services are used when accessing the boot device.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© Hewlett-Packard Development Company, L.P.