Managing and Developing Dynamically Loadable Kernel Modules

Managing Dynamically Loadable Kernel Modules

Chapter 12522

boot a newly conﬁgured kernel.

WARNING Manually copying or moving kernel ﬁles is not a supported

practice, and may result in corrupting the running kernel or

other kernels on the system. See kmupdate(1M) for the supported

interfaces to update and remove kernels.

To conﬁgure the HP-UX kernel to include a statically conﬁgured loadable

module and update the system with the new kernel, execute this config

command:

/usr/sbin/config -u /stand/system

config builds a new kernel. The -u option forces config to call the

kmupdate command to schedule the update of the kernel image, a

required step in the process of successfully booting a newly conﬁgured

kernel.

After the system reboots, your DLKM module will be available as

statically conﬁgured in the new running kernel.

Updating the Kernel

For a DLKM module conﬁgured as statically linked, use the kmupdate

command to schedule theupdate of the system with thenewly conﬁgured

kernel.

Each new kernel conﬁgured with the config(1M) command is composed

of several distributed ﬁles, which are all required for a kernel to boot and

run properly. The main kernel ﬁle is associated with its component ﬁles

by way of a Kernel ID String (KIS) in the main kernel image. For any

kernel, all the ﬁles required by the boot loader need to be accessible from

the /stand/boot.

KIS

directory, where

KIS

uniquely identiﬁes the

kernel being booted.

The kmupdate(1M) command does the following:

❏ schedules the move of the main kernel image and its associated

kernel-component-set ﬁles to the default locations

❏ creates and populates the kernel-speciﬁc directory (/stand/

boot.

KIS

) from which the boot loader will be able to obtain all the

kernel components needed at boot time.