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

__________________________________________________________________________________________________________________________________________________________________________________________________
__________________________________________________________________________________________________________________________________________________________________________________________________
STANDARD Printed by: Nora Chuang [nchuang] STANDARD
/build/1111/BRICK/man1m/!!!intro.1m
________________________________________________________________
___ ___
c
config(1M) config(1M)
NAME
config - configure and build an HP-UX system
SYNOPSIS
/usr/sbin/config [-c c_file][-l m_file][-m master][-r path][-s|-u][-S][-t] system_file
/usr/sbin/config -M module_name [[-M module_name]...] [-m master][-u]
DESCRIPTION
config is used to configure the following parts of the operating system:
device drivers
swap and dump devices
tunable system parameters
kernel modules
config supports the following configurations:
whole kernel configuration (first form)
Both the static kernel (vmunix) and dynamically loadable modules are generated, and a system
reboot is necessary.
dynamically loadable module configuration (second form)
Specified loadable modules are dynamically generated and registered with the current system. The
newly configured services are available immediately, without requiring a system reboot.
Kernel modules can either be static modules or dynamically loadable modules.
The first form is used to configure the entire kernel; that is, the static kernel and all kernel modules. This
type of configuration is called a whole kernel configuration. The second form is used to configure only the
dynamically loadable modules.
Static modules are maintained in individual object files which are included or excluded from the static ker-
nel (vmunix) based on whether the features they support are required in the system. Such modules are
non-loadable and remain linked into the kernel.
Dynamically loadable modules are also maintained in individual object files but they are not statically
linked into the kernel. Loadable modules can be configured to be included or excluded from the kernel
dynamically, without having to relink the entire kernel or reboot the system. The loadable image gen-
erated during the configuration of such modules may be auto-loaded or unloaded by the kernel or demand-
loaded or unloaded by the system administrator.
See the Managing Systems and Workgroups for information on how to include or remove a subsystem, file
system, or kernel module, and how to boot the system.
Whole Kernel Configuration (First Form)
To configure a whole kernel,
config reads the user-provided description of an HP-UX system
(system_file), the system description files for kernel modules, and the master kernel configuration table
information.
Note that the system file and system description files for kernel modules should only be modified by using
the kmsystem or kmtune system administration commands.
For all kernel modules to be configured, config checks the interface functions or symbols used by the
modules. If modules rely on symbols not covered by the $INTERFACE section of its master file,
configuration fails. Otherwise, config generates the following output files and directories:
C program source files (conf.c and space.h) that define the configuration tables for various
parts of the system. Unless kernel modules are configured, these files will not be generated.
C program header file (tune.h) that defines tunable parameters of the system required by kernel
and kernel modules.
C program source files (mod_conf.c) that are required by kernel modules. If a space.h header
file is provided with a module, it is included by the source file.
a makefile (config.mk) to compile the C program produced and relink the newly configured sys-
tem with statically linked kernel module object file (vmunix_test ), and to generate kernel
HP-UX Release 11i: December 2000 1 Section 1M135
___
___