Manualshelf

system.4 (2010 09)

ManualsBrandsHP ManualsSoftwareHP-UX Manpages
1234
s
system(4) system(4)
NAME
system - system description configuration files
DESCRIPTION
The HP-UX system description file describes kernel configuration information used by the
kconfig and
mk_kernel commands.
The system description file consists of the following information:
• A line specifying the version of the system file.
• The list of packaged and traditional kernel modules to be configured.
• Planned values for system tunable parameters, and other system-wide configuration information.
Lines starting with an asterisk (
*) are comment lines. HP discourages adding comments to the system
description file, since they are not preserved by kernel configuration commands. See kconfig(5) for details.
HP-UX System Description File
System files may contain a line specifying which version of the system file syntax was used when writing
the file. If present, this line must be the first non-comment line of the system description file. This is the
only line in the system description file that must occupy a particular position. All other lines are position
independent. This line has the following format:
version version
where the following values for version are allowed:
1 The system file is formatted as described in this manual page.
0 The system file is formatted in the fashion used in HP-UX 11i Version 1.6 and prior. This value
is the default if no
version line appears in the system file.
New system files should always be created using version 1 of the system file syntax. Support for version 0
will be removed in a future HP-UX release.
System files that are generated by the kernel configuration commands will contain a line indicating which
configuration is being described. This line has the form:
configuration name title timestamp
where:
name is the name of the configuration,
title is the title of the configuration (in quotes), and
timestamp indicates the time at which the system file was generated.
System files may contain lines that list the traditional and packaged kernel modules (including device
drivers and pseudo-drivers) that are to be configured.
Each such line has one of the following two formats:
module where module is either a traditional or packaged kernel module name.
For example,
scsi selects the driver for SCSI disk drives, scsitape selects the driver for
SCSI tape drives, and nfs selects the NFS subsystem. This line format is for backward com-
patibility. It does not allow specification of the state of the module; the module state will be
the default state as given by the module’s developer. To specify the desired state of the
module, use the second format.
module module state [ version ]
where module is either a traditional or packaged kernel module name. state is one of best,
static, auto or loaded; see kcmodule (1M) for definitions of these states.
version is version of the module. The version field is optional. It should generally be omitted
when manually editing or creating system files. It is used by
kconfig -e and
kconfig -i when cloning kernel configurations; see kconfig(1M) for details.
For example,
module scsi static 1.0.[3E0D0C96]
HP-UX 11i Version 3: September 2010 − 1 − Hewlett-Packard Company 1

Summary of content (4 pages)