HP-UX Reference (11i v1 05/09) - 1M System Administration Commands A-M (vol 3)

c
config(1M) config(1M)
Options for Loadable Module Configuration
When configuring a loadable module, config
recognizes the following options:
-M module_name
Configure the specified loadable module only. A kernel file is not generated in this case. If successful,
the loadable image of the module is generated.
If the specified module is a stub module (see master(4)),
config prints a message and fails. An
entire kernel build is required to configure stub modules.
-m master
Specify the name of the master kernel configuration information file or directory that
config should
use in creating source files and makefiles. If master is a directory,
config reads all files in that
directory to create its data structures. If master is a file, only that file is read for creating data struc-
tures for
config. By default, config reads the files in the directory
/usr/conf/master.d
.
/usr/conf/master.d
is supplied as part of the HP-UX operating system and should not be
modified by anyone who does not fully understand its structure and purpose.
-u Invoking kmupdate to update the module.
Kernel Module System Description File
Kernel module description files are placed under /stand/system.d
. A system file for a module is
named after the module name and is unique.
Each file consists of three mandatory and one optional sections.
$VERSION:
The line starting with $VERSION indicates the version number for the file format. Version is defined
as a decimal number and starts from one.
Format is:
$VERSION version_number
Example:
$VERSION 1
$CONFIGURE:
The line starting with $CONFIGURE indicates whether the module needs to be configured. If the
second field is either Y or y, the module will be configured on the next build. If the field is either
N or
n, the module will not be configured on the build.
Format is:
$CONFIGURE {Y|y|N|n}
Example:
$CONFIGURE Y
$LOADABLE:
The line starting with $LOADABLE indicates how the module will be configured. If the second field is
either Y or y, the module will be configured as a dynamically loadable module.
If the field is either N or n, the module will be statically linked into the kernel.
If the master file for the module does not have a $LOADABLE section, then the system file should not
have one either.
Format is:
$LOADABLE {Y|y|N|n}
Example:
$LOADABLE Y
$TUNABLE
(Optional system parameter section)
The section between the lines starting with $TUNABLE, and with $$$ indicates tunable parameters of the
module.
HP-UX 11i Version 1: September 2005 6 Hewlett-Packard Company Section 1M143