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

Configuring a System
Reconfiguring the Kernel (Prior to HP-UX 11i Version 2)
Chapter 3 297
The $TUNABLE section defines the names and default values of the
tunable parameters (variables) for the module. Default (and
optionally minimum) values for tunable parameters are entered
here.
The $DRIVER_INSTALL section defines the module’s name and
associated block and/or character major device number(s).
system File
Definition
Every DLKM module requires a system file. The system file includes the
following three mandatory and one optional section keywords:
• $VERSION—indicates the version number for the file format. Version
1 is the only supported file-format.
NOTE The version number for the master file and system file must be the
same.
• $CONFIGURE—indicates if the module is to be configured into the
system. If $CONFIGURE is Y or y, the module will be configured on the
next build; if $CONFIGURE is N or n, the module will not be configured
on the next build. kmsystem (1M) provides the interface to modify the
flag.
• $LOADABLE—indicates how the module will be configured. If
$LOADABLE is Y or y, the module will be configured as a Dynamically
Configured Loadable Module; if $LOADABLE is N or n, the module will
be statically configured into the kernel, requiring a reboot. kmsystem
provides the interface to modify the flag.
•If$CONFIGURE is N or n, $LOADABLE is ignored.
• $TUNABLE (empty)—place holder for any tunable parameter specified
in the associated master file for which you want to specify a value
other than the default value. Nothing is entered here.
kmtune (1M) is the interface to modify tunable parameters in the
module's system description file and the HP-UX system file
(/stand/system by default).
Modstub.o File
Definition
An optional component, the Modstub.o file is statically configured into
the kernel as a “place holder” for functions implemented in a loadable
module that will be loaded at a later time. Its purpose is to enable the