HPUX Secondary System Loader (hpux)

As mentioned earlier, the hpux utility manages loading the HP-UX kernel and gives control to the kernel. ISL can have hpux run an "autoexecute" file, or commands can be given interactively. In most situations, you would just want to automatically boot the system, however, in our example so far, we have decided to interact with IPL in the interest of looking at some of the functionality in ISL. We proceed with the boot process by simply issuing the HPUX utility name as shown in the following example:

 ISL>  hpux  Boot : disk(0/0/1/1.2.0.0.0.0.0;0)/stand/vmunix 7094272 + 849200 + 724128 start 0x241068 alloc_pdc_pages: Relocating PDC from 0xf0f0000000 to 0x7f9ab000. gate64: sysvec_vaddr = 0xc0002000 for 1 pages NOTICE: nfs3_link(): File system was registered at index 4. NOTICE: autofs_link(): File system was registered at index 6.     System Console is on the Built-In Serial Interface Entering cifs_init... Initialization finished successfully... slot is 8 Logical volume 64, 0x3 configured as ROOT Logical volume 64, 0x2 configured as SWAP Logical volume 64, 0x2 configured as DUMP     Swap device table:  (start & size given in 512-byte blocks)         entry 0 - major is 64, minor is 0x2; start = 0, size = 2097152 Starting the STREAMS daemons-phase 1 Checking root file system. file system is clean - log replay is not required Root check done. Create STCP device files Starting the STREAMS daemons-phase 2     B2352B/9245XB HP-UX (B.11.00) #1: Wed Nov  5 22:38:19 PST 1997 Memory Information:     physical page size = 4096 bytes, logical page size = 4096 bytes     Physical: 2097152 Kbytes, lockable: 1574352 Kbytes, available: 1815496 Kbytes /sbin/ioinitrc: /sbin/bcheckrc: Checking for LVM volume groups and Activating (if any exist) Volume group "/dev/vg00" has been successfully changed. vxfs fsck: sanity check: root file system OK (mounted read/write) Checking hfs file systems /sbin/fsclean: /dev/vg00/lvol1 (mounted) ok HFS file systems are OK, not running fsck Checking vxfs file systems /dev/vg00/lvol8 : vxfs fsck: sanity check: /dev/vg00/lvol8 OK /dev/vg00/lvol3 : vxfs fsck: sanity check: root file system OK (mounted read/write) /dev/vg00/lvol4 : vxfs fsck: sanity check: /dev/vg00/lvol4 OK /dev/vg00/lvol5 : vxfs fsck: sanity check: /dev/vg00/lvol5 OK /dev/vg00/lvol6 : vxfs fsck: sanity check: /dev/vg00/lvol6 OK /dev/vg00/lvol7 : vxfs fsck: sanity check: /dev/vg00/lvol7 OK (c)Copyright 1983-1997 Hewlett-Packard Co.,  All Rights Reserved. (c)Copyright 1979, 1980, 1983, 1985-1993 The Regents of the Univ. of California (c)Copyright 1980, 1984, 1986 Novell, Inc. (c)Copyright 1986-1992 Sun Microsystems, Inc. (c)Copyright 1985, 1986, 1988 Massachusetts Institute of Technology (c)Copyright 1989-1993  The Open Software Foundation, Inc. (c)Copyright 1986 Digital Equipment Corp. (c)Copyright 1990 Motorola, Inc. (c)Copyright 1990, 1991, 1992 Cornell University (c)Copyright 1989-1991 The University of Maryland (c)Copyright 1988 Carnegie Mellon University (c)Copyright 1991-1997 Mentat, Inc. (c)Copyright 1996 Morning Star Technologies, Inc. (c)Copyright 1996 Progressive Systems, Inc. (c)Copyright 1997 Isogon Corporation                            RESTRICTED RIGHTS LEGEND Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in sub-paragraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause in DFARS 252.227-7013.                            Hewlett-Packard Company                            3000 Hanover Street                            Palo Alto, CA 94304 U.S.A. Rights for non-DOD U.S. Government Departments and Agencies are as set forth in FAR 52.227-19(c)(1,2).  .   .   .  Console Login: 

I abbreviated this listing where the three dots appear before the Console Login: prompt.

We have a number of options we can issue with the HPUX utility. Table 1-3 is a list of examples of some common HPUX utility booting options, some of which are from the man page in Appendix A.

Table 1-3. hpux Examples

Command (all at ISL> prompt)	Comments
Automatic Boot	No interaction - autoboot sequence.
hpux -is	Bring up system at run level s for single user mode.
hpux	Default boot sequence from autoexecute normally object file is /stand/vmuinx .
hpux vmunix.test	Boot object file vmunix.test .
hpux (52.5.0.0) /stand/vmunix	Boot from /stand/vmunix on the disk at the path 52.5.0.0.
hpux lan(32) /stand/vmunix	Boot from LAN.
hpux -v	Get HP-UX version numbers ..
hpux ll /stand	List contents of /stand on root disk.

The part of the boot that takes place after the hpux command is issued is in the four following parts :

1. HP-UX initializes the system hardware and devices - The HP-UX kernel locates and initializes system hardware such as memory, I/O busses and devices, and so on. Kernel device drivers are associated with I/O devices at this time. You see many messages fly-by on the system console as this process is taking place.

2. HP-UX kernel data structures are created and initialized - There are many tables for system processes and memory, file systems, and so on that are created. You also see the status of this part of the boot on the system console.

3. HP-UX searches for the root file system - The base file system contains critical system files and is usually found on the disk from which HP-UX boots. Many commands are run as part of this process.

4. HP-UX starts the init process called / sbin/init - The init process, which has an ID of one, starts all other processes on the system. The init process reads /etc/inittab for direction. There is a detailed description of the contents of /etc/inittab in Chapter 7.

I encourage you to issue some of the PDC, ISL, and hpux utility commands covered earlier, especially those that do not modify your system in any way but only provide information about the system.

The next section covers configuring the Secure Web Console.