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

Configuring a System
Reconfiguring the Kernel (HP-UX 11i Version 2)
Chapter 3358
Most changes made in system files can be made using the kernel
configuration commands, and vice versa. Here are the equivalents:
Uses for System Files
System files are primarily useful in four situations. First, they are useful
for system administrators who are familiar with them from previous
releases of HP-UX. If you are used to editing /stand/system and
running mk_kernel to make configuration changes, it will still work.
Second, system files are the only mechanism through which device
bindings can be seen or changed. See “Managing Device Bindings” on
page 359 for more details.
Third, system files are useful if you want to apply multiple configuration
changes simultaneously. You can edit a /stand/system and change three
tunable values and two module states, and have all of those changes take
effect together when you import the system file with kconfig -i or
Table 3-20 Making System File Entries with Kernel Configuration
Commands
System File Line Kernel Configuration Command
modulename
kcmodule
modulename
=best
module
modulename
best kcmodule
modulename
=best
module
modulename state
[
version
]
a
kcmodule
modulename
=
state
(no entry for
modulename
) kcmodule modulename=unused
tunablename tunablevalue
kctune
tunablename
=
tunablevalue
tunable
tunablename tunablevalue
kctune
tunablename
=
tunablevalue
(no entry for
tunablename
) kctune
tunablename
=default
swap
swapdevice
(no equivalent)
dump
dumpdevice
(no equivalent)
driver
devicename drivername
(no equivalent)
a. System files created by the kernel configuration tools always list the version
number for each module. However, it is not required. Administrators adding
module lines to a system file need not give version numbers.