Graphics Administration Guide (October 2009)

[SubSection “ModuleName”
Option . . .
EndSubSection]
. . .
EndSection.
Load instructs the server to load the module called ModuleName. The module name given should
be the module's extension name, not the module file name. The extension name is case sensitive,
and does not include the “lib” prefix, or the “.so.1” or “.1” suffix.
Example: the Double Buffered Extension (DBE) can be loaded with the following entry:
Load “dbe”
SubSection also instructs the server to load the module called ModuleName. The module name
given should be the module's extension name, not the module file name. The extension name is
case-sensitive, and does not include the “lib” prefix, or the “.so.1” or “.1” suffix. The difference
between Load and SubSection is that in SubSection the listed Options are passed to the module
when it is loaded.
Modules are searched for in each directory specified in the ModulePath search path (or the default
ModulePath if one is not specified in the Files section) and in the drivers, input, extensions, fonts,
and hpux subdirectories of each directory in the ModulePath.
Noload instructs the server to not load the module called ModuleName.
InputDevice section
An InputDevice section is considered active if there is a reference to it in the active ServerLayout
section. There may be multiple InputDevice sections. There will normally be at least two: one
for the core (primary) keyboard, and one for the core pointer. InputDevice sections have the
following format:
Section "InputDevice"
Identifier "InputDeviceID"
Driver "DriverName"
[Option ...]
. . .
EndSection
The Identifier entry specifies the unique name for this input device and must match an
InputDeviceID in the active ServerLayout section in order to be active.
The Driver entry specifies the name of the driver to use for this input device.
InputDevice sections recognize some driver-independent Options, which are described here.
See the individual input driver manual pages for a description of the device-specific options that
can be entered here.
Table 2-2 Options for InputDevice section
DescriptionValueOption
When this is set, the input device is installed as the core (primary)
pointer device. There must be no more than one core pointer. If
this option is not set here, or in the ServerLayout section, or from
the -pointer command line option, then the first input device
that is capable of being used as a core pointer will be selected as
the core pointer. Source: XF86Config man page.
NACorePointer
When this is set, the input device is to be installed as the core
(primary) keyboard device. There must be no more than one core
keyboard. If this option is not set here, or in the ServerLayout
section, then the first input device that is capable of being used
as a core keyboard will be selected as the core keyboard. Source:
XF86Config man page.
NACoreKeyboard
the XF86Config file 15