HP j6700 hp workstations - hp-ux 11.x graphics administration guide - Page 45

Module Module, ModuleName, Sub Options, Files

Get HP j6700 - Workstation PDF manuals and user guides View all HP j6700 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 45 highlights

Chapter 3 configuring X Windows on HP-UX (other graphics cards) the XF86Config file "Module" section The Module section is used to specify which X Server modules should be loaded. The types of modules normally loaded in this section are X Server extension modules, and font rasterizer modules. Most other module types are loaded automatically when they are needed via other mechanisms. There may only be one Module section in the config file. The format of the Module section is as follows: Section ìModuleî Load ìModuleNameî . . . [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 ".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 ".1" suffix. The difference is that 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 HP-UX subdirectories of each directory in the ModulePath. 43

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
configuring X Windows on HP-UX (other graphics cards)
the XF86Config file
Chapter 3
43
“Module” section
The
Module
section is used to specify which X Server modules should be
loaded. The types of modules normally loaded in this section are X Server
extension modules, and font rasterizer modules. Most other module types
are loaded automatically when they are needed via other mechanisms.
There may only be one
Module
section in the config file. The format of
the
Module
section is as follows:
Section ìModuleî
Load ìModuleNameî
. . .
[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 “.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 “.1” suffix. The
difference is that 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 HP-UX
subdirectories of each directory in the
ModulePath
.