Managing Systems and Workgroups: A Guide for HP-UX System Administrators

Configuring a System
Reconfiguring the Kernel (HP-UX 11i Version 2)
Chapter 3 357
NOTE /stand/system, and any system file created by exporting the running
configuration, always reflects any changes that are being held for next
boot.
Once you have a system file, you can edit it using any text editor, making
the changes you desire. After editing it, you can apply the changes with
the kconfig -i (import) command. This command has three forms:
kconfig –i filename import to running configuration, now
kconfig –h –i filename import and hold for next boot
kconfig –i configname filename import to saved configuration
In the first form, if the changes cannot be applied to the running system,
they will be held for next boot.
For backward compatibility, the mk_kernel command is still available to
apply changes made in a system file. Note, however, that its name is no
longer accurate since it will apply configuration changes without making
a kernel if it can. This command has the form:
mk_kernel [-o target ] [-s filename ]
filename is the name of the system file to read; if not specified,
/stand/system is used. To import to a saved configuration, target
should be the name of the configuration. To import to the currently
running system, taking effect immediately if possible, target should be
/stand/vmunix. (Changes will be held until next boot if they cannot be
applied immediately.) If target is omitted, the changes will be made to a
saved configuration called hpux_test. It is not possible to import to the
currently running system, forcing changes to be held for next boot, using
mk_kernel. Use kconfig -h -i for that purpose.
It is important to note that the system files at /stand/system and
/stand/ configname /system are automatically recreated after every
configuration change. In this process, comments in the system file are
not preserved. Also, the ordering of lines in the file is not preserved.
Therefore, HP recommends against putting comments in the system
files. Instead, use the -C (Comment) option when importing the
configuration, to add your comments directly to the kernel configuration
log file. (See “The Kernel Configuration Log File” on page 362.)