Simulating the AUTO File on a Partition

On a non-vPars computer, the LIF's AUTO file on the boot disk can contain a boot string that includes boot options, such as -lq for booting without quorum, or a boot kernel path, such as /stand/vmunix.other for booting an alternate kernel. The AUTO file can be changed either through lif shell commands or mkboot.

However, on a vPars computer, the LIF's AUTO file is read only on computer bootup; for example, the AUTO file might contain "hpux /stand/vpmon", which causes the vPars monitor to be booted when the computer is booted. The AUTO file is not read when a virtual partition is booted.

To simulate the AUTO file effect when a partition is booted, you can modify the boot options and boot path entries in the vPars partition database via vparmodify:

Examples

On a non-vPars computer, to change the AUTO file to use the boot options -lq, the command is:
# mkboot -a "hpux -lq"
On a vPars computer, to get the same effect when the partition winona2 is booted, modify the partition database using -o (boot options):
# vparmodify -p winona2 -o "-lq"
On a non-vPars computer, to change the AUTO file to use a different kernel, the command is:
# mkboot -a "hpux /stand/vmunix.other"
On a vPars computer, to get the same effect when the partition winona2 is booted, modify the partition database using -b (boot path):
# vparmodify -p winona2 -b "/stand/vmunix.other"




	NOTE: On a vPars computer, the HP-UX command mkboot does modify the LIF's `AUTO` file. However, on a vPars computer, what is booted initially is the vPars monitor; then the monitor boots the virtual partitions. Therefore, what can be in the LIF `AUTO` file is a boot string that boots the monitor. See “Autobooting the Monitor and All Virtual Partitions”.

Simulating the AUTO File on a Partition

Technical documentation

» Table of Contents

» Glossary

» Index

Examples