NAME
kmsystem — set, query planned configuration attributes of kernel modules
SYNOPSIS
/usr/sbin/kmsystem
[-S
system_file]
/usr/sbin/kmsystem
[-c
{y|n}]
[-l
{y|n}]
[-b
{1|2|i
|a}]
[-q]
[-S
system_file]
module_name
DESCRIPTION
kmsystem,
without any option or with the
-S
option only,
displays for all modules the current values of configurable attributes to be used at the next kernel or module build.
The
-q
option may be used to limit this information to the specified module only.
The other options are used to set configuration values that will be used at the next kernel or module build.
kmsystem
operates on configurable information associated to both static or
loadable modules. [See
config(1M).]
When module_name is specified on the command line, one or more of the
-b,
-c,
-l,
or
-q
flags must also be specified.
Options
- -b value
Set the planned loading phase of the specified module.
A
value
equal to
1
(BOOT1),
indicates that once the module is configured
and registered with the kernel, the module should
be loaded during phase 1 of the kernel boot sequence.
A
value
equal to
2
(BOOT2),
indicates that once the module is configured
and registered with the kernel, the module should
be loaded during phase 2 of the kernel boot sequence.
A
value
equal to
i
(INIT),
indicates that once the module is configured
and registered with the kernel, the module should
be loaded during the init process.
A
value
equal to
a
(AUTO),
indicates that once the module is configured and registered with the kernel,
the module is not to be loaded
upon system reboot, but should remain ready to load
on demand, or by the DLKM auto loading mechanism (load
on device access).
Once the module is configured and registered with the
kernel, the
configured
loading phase can be changed dynamically using the
kmadmin(1M)
command,
-b
option.
- -c value
Set the planned configuration of the specified module.
Specifying
y
will cause the module to be configured at the next kernel or module
build [ see config(1M) ]; specifying
n
will cause the module not to be configured.
If a modular system file for the specified module does not exist
then the traditional system file (see
-S
option) is used. The system file is modified accordingly
to set the planned configuration of module_name.
- -l value
Set the planned linkage of the specified module. Specifying
y
will cause the module to be configured as dynamically loadable at the next kernel or module build; specifying
n
will cause the module to be statically linked. If the specified module
does not support dynamic loading,
kmsystem -l y
exits with an error.
- -q
Display the currently planned attribute values for the specified module.
A
-
is displayed for any attribute not supported by the module.
Information returned by this option includes:
module version (loadable modules are given default version 0.1.0; traditional modules are given default version 0.0.0)
- -S system_file
Specify the traditional HP-UX system description file name.
This file is used when getting/setting configurable attributes for
traditional static modules. Users can specify the complete path to
the file name; otherwise,
kmsystem
will search the current directory for the specified file.
The default HP-UX system description file if the
-S
option is not specified is
/stand/system.
This option is for backward compatibility.
EXAMPLES
To display the planned values of configurable attributes of the stape module:
/usr/sbin/kmsystem -q stape
To specify that the stape module should be statically linked:
/usr/sbin/kmsystem -l n stape
To specify that the mod1 module should be configured as dynamically
loadable, and loaded during the init process:
/usr/sbin/kmsystem -l y -b i mod1
NOTES
System administrators must use
kmsystem
and
kmtune(1M)
instead of editing system description files manually.
File format of system description files are subject to change, and
kmsystem
provides compatibility in the event of a format change.
RETURN VALUE
Upon successful completion,
kmsystem
returns with a 0; otherwise it returns with a 1.
DIAGNOSTICS
Output for queries is sent to stdout. Error messages are sent to stderr.
Messages from
kmsystem
are self-explanatory.
FILES
- /usr/conf/master.d/*
Traditional and modular master configuration files
- /stand/system
Default HP-UX system description file (traditional system file)
- /stand/system.d/*
Modular system files