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

Configuring a System
Reconfiguring the Kernel (HP-UX 11i Version 2)
Chapter 3 327
Each kernel module in the currently running configuration has a state,
which describes how the module is being used. The possible states are:
When kcmodule is giving information about the currently running
system, and there are configuration changes being held for next boot,
kcmodule will list both the current state and the state at next boot. For
next boot, the same states are used, with complementary meanings:
When kcmodule is giving information about a saved configuration, the
same states are used.
Next to each module state is a “cause”, which tells why the module is (or
will be) in that state. The causes are:
unused The module is installed on the system but not in use.
static The module is statically bound into the kernel
executable. This is the most common state. Moving a
module into or out of this state requires relinking the
kernel executable and rebooting.
loaded The module is dynamically loaded into the kernel. Newer
modules support this state. Such modules may be added
to the kernel configuration or removed from it without
rebooting.
auto The module will be dynamically loaded into the kernel
when it is first needed, but it hasn’t been needed yet.
unused The module will not be used.
static The module will be statically bound into the kernel
executable.
loaded The module will be dynamically loaded into the kernel
during the boot process.
auto The module will be dynamically loaded into the kernel
when it is first needed after each boot.
explicit The system administrator explicitly chose the state.