Installation guide

You will be prompted to enter a file name for the saved file, or choose an
existing file to load. The following shows a sample of part of a saved file:
# File created from tuning app
kds:
kds_print_flag=0
gpc_input:
kbd_scancode=3
Num_Units_Installed=1
gpc_developer_debug=0
pci:
PCI_Developer_Debug=0
ace:
dcd_timer=2
isa:
ISA_Developer_Debug=0
.
.
.
.
As with any kernel configuration tasks, there is a risk that modifying
attributes can leave your system in an unusable state. Take care only to
change attributes with which you are familiar and only change them when
you are certain of the effect. Refer to the
System Configuration and Tuning
guide for more information on attributes.
5.3 Dynamic System Configuration
When you need to load, unload, or modify a dynamic subsystem, you use
the /sbin/sysconfig command. This command has the following syntax:
/sbin/sysconfig
[-h hostname ][-i index [-v| -c | -m | -q |-Q |-r | -s| -u]]
[
subsystem-name][attribute-list]
You must be the superuser to load and unload subsystems.
You must also know the name of the subsystem you want to manage. You
can determine the name of a subsystem by looking in the documentation
that accompanies the subsystem or in the directories into which the
subsystem is installed. Subsystems are installed in either the /subsys
directory or the /var/subsys directory. When a subsystem is installed, a
file named
subsystem-name .mod appears in one of those two directories.
You use that subsystem name as input to the /sbin/sysconfig
command. The sections that follow describe the commands you use to
manage subsystems.
5–6 Configuring the Kernel