XF86Config

NAME

XF86Config - Configuration File for XFree86  

DESCRIPTION

XFree86 uses a configuration file called XF86Config for its initial setup. This configuration file is searched for in the following places when the server is started as a normal user:

/etc/X11/<cmdline> /usr/X11R6/etc/X11/<cmdline> /etc/X11/$XF86CONFIG /usr/X11R6/etc/X11/$XF86CONFIG /etc/X11/XF86Config-4 /etc/X11/XF86Config /etc/XF86Config /usr/X11R6/etc/X11/XF86Config.<hostname> /usr/X11R6/etc/X11/XF86Config-4 /usr/X11R6/etc/X11/XF86Config /usr/X11R6/lib/X11/XF86Config.<hostname> /usr/X11R6/lib/X11/XF86Config-4 /usr/X11R6/lib/X11/XF86Config

where <cmdline> is a relative path (with no ".." components) specified with the -xf86config command line option, $XF86CONFIG is the relative path (with no ".." components) specified by that environment variable, and <hostname> is the machine`s hostname as reported by gethostname(3).

When the X server is started by the "root" user, the config file search locations are as follows:

<cmdline> /etc/X11/<cmdline> /usr/X11R6/etc/X11/<cmdline> $XF86CONFIG /etc/X11/$XF86CONFIG /usr/X11R6/etc/X11/$XF86CONFIG $HOME/XF86Config /etc/X11/XF86Config-4 /etc/X11/XF86Config /etc/XF86Config /usr/X11R6/etc/X11/XF86Config.<hostname> /usr/X11R6/etc/X11/XF86Config-4 /usr/X11R6/etc/X11/XF86Config /usr/X11R6/lib/X11/XF86Config.<hostname> /usr/X11R6/lib/X11/XF86Config-4 /usr/X11R6/lib/X11/XF86Config

where <cmdline> is the path specified with the -xf86config command line option (which may be absolute or relative), $XF86CONFIG is the path specified by that environment variable (absolute or relative), $HOME is the path specified by that environment variable (usually the home directory), and <hostname> is the machine`s hostname as reported by gethostname(3).

The XF86Config file is composed of a number of sections which may be present in any order. Each section has the form:

Section N`34`SectionNameN`34` SectionEntry ... EndSection

The section names are:

Files File pathnames ServerFlags Server flags Module Dynamic module loading InputDevice Input device description Device Graphics device description VideoAdaptor Xv video adaptor description Monitor Monitor description Modes Video modes descriptions Screen Screen configuration ServerLayout Overall layout DRI DRI-specific configuration Vendor Vendor-specific configuration

The following obsolete section names are still recognised for compatibility purposes. In new config files, the InputDevice section should be used instead.

Keyboard Keyboard configuration Pointer Pointer/mouse configuration

The old XInput section is no longer recognised.

The ServerLayout sections are at the highest level. They bind together the input and output devices that will be used in a session. The input devices are described in the InputDevice sections. Output devices usually consist of multiple independent components (e.g., and graphics board and a monitor). These multiple components are bound together in the Screen sections, and it is these that are referenced by the ServerLayout section. Each Screen section binds together a graphics board and a monitor. The graphics boards are described in the Device sections, and the monitors are described in the Monitor sections.

Config file keywords are case-insensitive, and "_" characters are ignored. Most strings (including Option names) are also case-insensitive, and insensitive to white space and "_" characters.

Each config file entry usually takes up a single line in the file. They consist of a keyword, which is possibly followed by one or more arguments, with the number and types of the arguments depending on the keyword. The argument types are:

Integer an integer number in decimal, hex or octal Real a floating point number String a string enclosed in double quote marks (N`34`)

Note: hex integer values must be prefixed with "0x", and octal values with "0".

A special keyword called Option may be used to provide free-form data to various components of the server. The Option keyword takes either one or two string arguments. The first is the option name, and the optional second argument is the option value. Some commonly used option value types include:

Integer an integer number in decimal, hex or octal Real a floating point number String a sequence of characters Boolean a boolean value (see below) Frequency a frequency value (see below)

Note that all Option values, not just strings, must be enclosed in quotes.

Boolean options may optionally have a value specified. When no value is specified, the option`s value is TRUE. The following boolean option values are recognised as TRUE:

1, on, true, yes

and the following boolean option values are recognised as FALSE:

0, off, false, no

If an option name is prefixed with N`34`NoN`34`, then the option value is negated.

Example: the following option entries are equivalent:

Option N`34`AccelN`34` N`34`OffN`34` Option N`34`NoAccelN`34` Option N`34`NoAccelN`34` N`34`OnN`34` Option N`34`AccelN`34` N`34`falseN`34` Option N`34`AccelN`34` N`34`noN`34`

Frequency option values consist of a real number that is optionally followed by one of the following frequency units:

Hz, k, kHz, M, MHz

When the unit name is omitted, the correct units will be determined from the value and the expectations of the appropriate range of the value. It is recommended that the units always be specified when using frequency option values to avoid any errors in determining the value.  

FILES SECTION

The Files section is used to specify some path names required by the server. Some of these paths can also be set from the command line (see Xserver(1) and XFree86(1)). The command line settings override the values specified in the config file. The entries that can appear in this section are:

FontPath N`34`pathN`34`

sets the search path for fonts. This path is a comma separated list of font path elements which the X server searches for font databases. Multiple FontPath entries may be specified, and they will be concatenated to build up the fontpath used by the server. Font path elements may be either absolute directory paths, or a font server identifier. Font server identifiers have the form:

<trans>/<hostname>:<port-number>

where <trans> is the transport type to use to connect to the font server (e.g., unix for UNIX-domain sockets or tcp for a TCP/IP connection), <hostname> is the hostname of the machine running the font server, and <port-number> is the port number that the font server is listening on (usually 7100).

When this entry is not specified in the config file, the server falls back to the compiled-in default font path, which contains the following font path elements:

/usr/X11R6/lib/X11/fonts/misc/ /usr/X11R6/lib/X11/fonts/Speedo/ /usr/X11R6/lib/X11/fonts/Type1/ /usr/X11R6/lib/X11/fonts/CID/ /usr/X11R6/lib/X11/fonts/75dpi/ /usr/X11R6/lib/X11/fonts/100dpi/

The recommended font path contains the following font path elements:

/usr/X11R6/lib/X11/fonts/local/ /usr/X11R6/lib/X11/fonts/misc/ /usr/X11R6/lib/X11/fonts/75dpi/:unscaled /usr/X11R6/lib/X11/fonts/100dpi/:unscaled /usr/X11R6/lib/X11/fonts/Type1/ /usr/X11R6/lib/X11/fonts/CID/ /usr/X11R6/lib/X11/fonts/Speedo/ /usr/X11R6/lib/X11/fonts/75dpi/ /usr/X11R6/lib/X11/fonts/100dpi/

Font path elements that are found to be invalid are removed from the font path when the server starts up.

RGBPath N`34`pathN`34`

sets the path name for the RGB color database. When this entry is not specified in the config file, the server falls back to the compiled-in default RGB path, which is:

/usr/X11R6/lib/X11/rgb

Note that an implicit .txt is added to this path if the server was compiled to use text rather than binary format RGB color databases.

ModulePath N`34`pathN`34`

sets the search path for loadable X server modules. This path is a comma separated list of directories which the X server searches for loadable modules loading in the order specified. Multiple ModulePath entries may be specified, and they will be concatenated to build the module search path used by the server.

 

SERVERFLAGS SECTION

The ServerFlags section is used to specify some global X server options. All of the entries in this section are Options, although for compatibility purposes some of the old style entries are still recognised. Those old style entries are not documented here, and using them is discouraged.

Options specified in this section (with the exception of the N`34`DefaultServerLayoutN`34` Option) may be overridden by Options specified in the active ServerLayout section. Options with command line equivalents are overridden when their command line equivalent is used. The options recognised by this section are:

Option N`34`DefaultServerLayoutN`34` N`34`layout-idN`34`

This specifies the default ServerLayout section to use in the absence of the -layout command line option.

Option N`34`NoTrapSignalsN`34` N`34`booleanN`34`

This prevents the X server from trapping a range of unexpected fatal signals and exiting cleanly. Instead, the X server will die and drop core where the fault occurred. The default behaviour is for the X server to exit cleanly, but still drop a core file. In general you never want to use this option unless you are debugging an X server problem and know how to deal with the consequences.

Option N`34`DontVTSwitchN`34` N`34`booleanN`34`

This disallows the use of the Ctrl+Alt+Fn sequence (where Fn refers to one of the numbered function keys). That sequence is normally used to switch to another oqvirtual terminal)cq on operating systems that have this feature. When this option is enabled, that key sequence has no special meaning and is passed to clients. Default: off.

Option N`34`DontZapN`34` N`34`booleanN`34`

This disallows the use of the Ctrl+Alt+Backspace sequence. That sequence is normally used to terminate the X server. When this option is enabled, that key sequence has no special meaning and is passed to clients. Default: off.

Option N`34`DontZoomN`34` N`34`booleanN`34`

This disallows the use of the Ctrl+Alt+Keypad-Plus and Ctrl+Alt+Keypad-Minus sequences. These sequences allows you to switch between video modes. When this option is enabled, those key sequences have no special meaning and are passed to clients. Default: off.

Option N`34`DisableVidModeExtensionN`34` N`34`booleanN`34`

This disables the parts of the VidMode extension used by the xvidtune client that can be used to change the video modes. Default: the VidMode extension is enabled.

Option N`34`AllowNonLocalXvidtuneN`34` N`34`booleanN`34`

This allows the xvidtune client (and other clients that use the VidMode extension) to connect from another host. Default: off.

Option N`34`DisableModInDevN`34` N`34`booleanN`34`

This disables the parts of the XFree86-Misc extension that can be used to modify the input device settings dynamically. Default: that functionality is enabled.

Option N`34`AllowNonLocalModInDevN`34` N`34`booleanN`34`

This allows a client to connect from another host and change keyboard and mouse settings in the running server. Default: off.

Option N`34`AllowMouseOpenFailN`34` N`34`booleanN`34`

This allows the server to start up even if the mouse device can`t be opened/initialised. Default: false.

Option N`34`VTInitN`34` N`34`commandN`34`

Runs command after the VT used by the server has been opened. The command string is passed to "/bin/sh -c", and is run with the real user`s id with stdin and stdout set to the VT. The purpose of this option is to allow system dependent VT initialisation commands to be run. This option should rarely be needed. Default: not set.

Option N`34`VTSysReqN`34` N`34`booleanN`34`

enables the SYSV-style VT switch sequence for non-SYSV systems which support VT switching. This sequence is Alt-SysRq followed by a function key (Fn). This prevents the X server trapping the keys used for the default VT switch sequence, which means that clients can access them. Default: off.

Option N`34`XkbDisableN`34` N`34`booleanN`34`

disable/enable the XKEYBOARD extension. The -kb command line option overrides this config file option. Default: XKB is enabled.

Option N`34`BlankTimeN`34` N`34`timeN`34`

sets the inactivity timeout for the blanking phase of the screensaver. time is in minutes. This is equivalent to the Xserver`s `-s` flag, and the value can be changed at run-time with xset(1). Default: 10 minutes.

Option N`34`StandbyTimeN`34` N`34`timeN`34`

sets the inactivity timeout for the "standby" phase of DPMS mode. time is in minutes, and the value can be changed at run-time with xset(1). Default: 20 minutes. This is only suitable for VESA DPMS compatible monitors, and may not be supported by all video drivers. It is only enabled for screens that have the N`34`DPMSN`34` option set (see the MONITOR section below).

Option N`34`SuspendTimeN`34` N`34`timeN`34`

sets the inactivity timeout for the "suspend" phase of DPMS mode. time is in minutes, and the value can be changed at run-time with xset(1). Default: 30 minutes. This is only suitable for VESA DPMS compatible monitors, and may not be supported by all video drivers. It is only enabled for screens that have the N`34`DPMSN`34` option set (see the MONITOR section below).

Option N`34`OffTimeN`34` N`34`timeN`34`

sets the inactivity timeout for the "off" phase of DPMS mode. time is in minutes, and the value can be changed at run-time with xset(1). Default: 40 minutes. This is only suitable for VESA DPMS compatible monitors, and may not be supported by all video drivers. It is only enabled for screens that have the N`34`DPMSN`34` option set (see the MONITOR section below).

Option N`34`PixmapN`34` N`34`bppN`34`

This sets the pixmap format to use for depth 24. Allowed values for bpp are 24 and 32. Default: 32 unless driver constraints don`t allow this (which is rare). Note: some clients don`t behave well when this value is set to 24.

Option N`34`PC98N`34` N`34`booleanN`34`

Specify that the machine is a Japanese PC-98 machine. This should not be enabled for anything other than the Japanese-specific PC-98 architecture. Default: auto-detected.

Option N`34`NoPMN`34` N`34`booleanN`34`

Disables something to do with power management events. Default: PM enabled on platforms that support it.

Option N`34`XineramaN`34` N`34`booleanN`34`

enable or disable XINERAMA extension. Default is disabled.

Option N`34`AllowDeactivateGrabsN`34` N`34`booleanN`34`

This option enables the use of the Ctrl+Alt+Keypad-Divide key sequence to deactivate any active keyboard and mouse grabs. Default: off.

Option N`34`AllowClosedownGrabsN`34` N`34`booleanN`34`

This option enables the use of the Ctrl+Alt+Keypad-Multiply key sequence to kill clients with an active keyboard or mouse grab as well as killing any application that may have locked the server, normally using the XGrabServer(3x) Xlib function. Default: off.
Note that the options AllowDeactivateGrabs and AllowClosedownGrabs will allow users to remove the grab used by screen saver/locker programs. An API was written to such cases. If you enable this option, make sure your screen saver/locker is updated.

Option N`34`HandleSpecialKeysN`34` N`34`whenN`34`

This option controls when the server uses the builtin handler to process special key combinations (such as Ctrl+Alt+Backspace). Normally the XKEYBOARD extension keymaps will provide mappings for each of the special key combinations, so the builtin handler is not needed unless the XKEYBOARD extension is disabled. The value of when can be Always, Never, or WhenNeeded. Default: Use the builtin handler only if needed. The server will scan the keymap for a mapping to the Terminate action and, if found, use XKEYBOARD for processing actions, otherwise the builtin handler will be used.

 

MODULE SECTION

The Module section is used to specify which X server modules should be loaded. This section is ignored when the X server is built in static form. The types of modules normally loaded in this section are X server extension modules, and font rasteriser modules. Most other module types are loaded automatically when they are needed via other mechanisms.

Entries in this section may be in two forms. The first and most commonly used form is an entry that uses the Load keyword, as described here:

Load N`34`modulenameN`34`

This instructs the server to load the module called modulename. The module name given should be the module`s standard name, not the module file name. The standard name is case-sensitive, and does not include the "lib" prefix, or the ".a", ".o", or ".so" suffixes.

Example: the Type 1 font rasteriser can be loaded with the following entry:

Load N`34`type1N`34`

The second form of entry is a SubSection, with the subsection name being the module name, and the contents of the SubSection being Options that are passed to the module when it is loaded.

Example: the extmod module (which contains a miscellaneous group of server extensions) can be loaded, with the XFree86-DGA extension disabled by using the following entry:

SubSection N`34`extmodN`34` Option N`34`omit XFree86-DGAN`34` EndSubSection

Modules are searched for in each directory specified in the ModulePath search path, and in the drivers, input, extensions, fonts, and internal subdirectories of each of those directories. In addition to this, operating system specific subdirectories of all the above are searched first if they exist.

To see what font and extension modules are available, check the contents of the following directories:

/usr/X11R6/lib/modules/fonts /usr/X11R6/lib/modules/extensions

The "bitmap" font modules is loaded automatically. It is recommended that at very least the "extmod" extension module be loaded. If it isn`t some commonly used server extensions (like the SHAPE extension) will not be available.  

INPUTDEVICE SECTION

The config file may have multiple InputDevice sections. There will normally be at least two: one for the core (primary) keyboard, and one of the core pointer.

InputDevice sections have the following format:

Section N`34`InputDeviceN`34` Identifier N`34`nameN`34` Driver N`34`inputdriverN`34` options ... EndSection

The Identifier entry specifies the unique name for this input device. The Driver entry specifies the name of the driver to use for this input device. When using the loadable server, the input driver module N`34`inputdriverN`34` will be loaded for each active InputDevice section. An InputDevice section is considered active if it is referenced by an active ServerLayout section, or if it is referenced by the -keyboard or -pointer command line options. The most commonly used input drivers are "keyboard" and "mouse".

InputDevice sections recognise some driver-independent Options, which are described here. See the individual input driver manual pages for a description of the device-specific options.

Option N`34`CorePointerN`34`

When this is set, the input device is installed as the core (primary) pointer device. There must be exactly 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. This option is implicitly set when the obsolete Pointer section is used.

Option N`34`CoreKeyboardN`34`

When this is set, the input device is to be installed as the core (primary) keyboard device. There must be exactly one core keyboard. If this option is not set here, in the ServerLayout section, or from the -keyboard command line option, then the first input device that is capable of being used as a core keyboard will be selected as the core keyboard. This option is implicitly set when the obsolete Keyboard section is used.

Option N`34`AlwaysCoreN`34` N`34`booleanN`34`

Option N`34`SendCoreEventsN`34` N`34`booleanN`34`

Both of these options are equivalent, and when enabled cause the input device to always report core events. This can be used, for example, to allow an additional pointer device to generate core pointer events (like moving the cursor, etc).

Option N`34`HistorySizeN`34` N`34`numberN`34`

Sets the motion history size. Default: 0.

Option N`34`SendDragEventsN`34` N`34`booleanN`34`

???

 

DEVICE SECTION

The config file may have multiple Device sections. There must be at least one, for the video card being used.

Device sections have the following format:

Section N`34`DeviceN`34` Identifier N`34`nameN`34` Driver N`34`driverN`34` entries ... EndSection

The Identifier entry specifies the unique name for this graphics device. The Driver entry specifies the name of the driver to use for this graphics device. When using the loadable server, the driver module N`34`driverN`34` will be loaded for each active Device section. A Device section is considered active if it is referenced by an active Screen section.

Device sections recognise some driver-independent entries and Options, which are described here. Not all drivers make use of these driver-independent entries, and many of those that do don`t require them to be specified because the information is auto-detected. See the individual graphics driver manual pages for further information about this, and for a description of the device-specific options. Note that most of the Options listed here (but not the other entries) may be specified in the Screen section instead of here in the Device section.

BusID N`34`bus-idN`34`

This specifies the bus location of the graphics card. For PCI/AGP cards, the bus-id string has the form PCI:bus:device:function (e.g., "PCI:1:0:0" might be appropriate for an AGP card). This field is usually optional in single-head configurations when using the primary graphics card. In multi-head configurations, or when using a secondary graphics card in a single-head configuration, this entry is mandatory. Its main purpose is to make an unambiguous connection between the device section and the hardware it is representing. This information can usually be found by running the X server with the -scanpci command line option.

Screen number

This option is mandatory for cards where a single PCI entity can drive more than one display (i.e., multiple CRTCs sharing a single graphics accelerator and video memory). One Device section is required for each head, and this parameter determines which head each of the Device sections applies to. The legal values of number range from 0 to one less than the total number of heads per entity. Most drivers require that the primary screen (0) be present.

Chipset N`34`chipsetN`34`

This usually optional entry specifies the chipset used on the graphics board. In most cases this entry is not required because the drivers will probe the hardware to determine the chipset type. Don`t specify it unless the driver-specific documentation recommends that you do.

Ramdac N`34`ramdac-typeN`34`

This optional entry specifies the type of RAMDAC used on the graphics board. This is only used by a few of the drivers, and in most cases it is not required because the drivers will probe the hardware to determine the RAMDAC type where possible. Don`t specify it unless the driver-specific documentation recommends that you do.

DacSpeed speed

DacSpeed speed-8 speed-16 speed-24 speed-32

This optional entry specifies the RAMDAC speed rating (which is usually printed on the RAMDAC chip). The speed is in MHz. When one value is given, it applies to all framebuffer pixel sizes. When multiple values are give, they apply to the framebuffer pixel sizes 8, 16, 24 and 32 respectively. This is not used by many drivers, and only needs to be specified when the speed rating of the RAMDAC is different from the defaults built in to driver, or when the driver can`t auto-detect the correct defaults. Don`t specify it unless the driver-specific documentation recommends that you do.

Clocks clock ...

specifies the pixel that are on your graphics board. The clocks are in MHz, and may be specified as a floating point number. The value is stored internally to the nearest kHz. The ordering of the clocks is important. It must match the order in which they are selected on the graphics board. Multiple Clocks lines may be specified, and each is concatenated to form the list. Most drivers do not use this entry, and it is only required for some older boards with non-programmable clocks. Don`t specify this entry unless the driver-specific documentation explicitly recommends that you do.

ClockChip N`34`clockchip-typeN`34`

This optional entry is used to specify the clock chip type on graphics boards which have a programmable clock generator. Only a few X servers support programmable clock chips. For details, see the appropriate X server manual page.

VideoRam mem

This optional entry specifies the amount of video ram that is installed on the graphics board. This is measured in kBytes. In most cases this is not required because the X server probes the graphics board to determine this quantity. The driver-specific documentation should indicate when it might be needed.

BiosBase baseaddress

This optional entry specifies the base address of the video BIOS for the VGA board. This address is normally auto-detected, and should only be specified if the driver-specific documentation recommends it.

MemBase baseaddress

This optional entry specifies the memory base address of a graphics board`s linear frame buffer. This entry is not used by many drivers, and it should only be specified if the driver-specific documentation recommends it.

IOBase baseaddress

This optional entry specifies the IO base address. This entry is not used by many drivers, and it should only be specified if the driver-specific documentation recommends it.

ChipID id

This optional entry specifies a numerical ID representing the chip type. For PCI cards, it is usually the device ID. This can be used to override the auto-detection, but that should only be done when the driver-specific documentation recommends it.

ChipRev rev

This optional entry specifies the chip revision number. This can be used to override the auto-detection, but that should only be done when the driver-specific documentation recommends it.

TextClockFreq freq

This optional entry specifies the pixel clock frequency that is used for the regular text mode. The frequency is specified in MHz. This is rarely used.

Options

Option flags may be specified in the Device sections. These include driver-specific options and driver-independent options. The former are described in the driver-specific documentation. Some of the latter are described below in the section about the Screen section, and they may also be included here.

 

VIDEOADAPTOR SECTION

Nobody wants to say how this works. Maybe nobody knows ...

 

MONITOR SECTION

The config file may have multiple Monitor sections. There must be at least one, for the monitor being used.

Monitor sections have the following format:

Section N`34`MonitorN`34` Identifier N`34`nameN`34` entries ... EndSection

The Identifier entry specifies the unique name for this monitor. The Monitor section provides information about the specifications of the monitor, monitor-specific Options, and information about the video modes to use with the monitor. Specifying video modes is optional because the server now has a built-in list of VESA standard modes. When modes are specified explicitly in the Monitor section (with the Modes, ModeLine, or UseModes keywords), built-in modes with the same names are not included. Built-in modes with different names are, however, still implicitly included.

The entries that may be used in Monitor sections are described below.

VendorName N`34`vendorN`34`

This optional entry specifies the monitor`s manufacturer.

ModelName N`34`modelN`34`

This optional entry specifies the monitor`s model.

HorizSync horizsync-range

gives the range(s) of horizontal sync frequencies supported by the monitor. horizsync-range may be a comma separated list of either discrete values or ranges of values. A range of values is two values separated by a dash. By default the values are in units of kHz. They may be specified in MHz or Hz if MHz or Hz is added to the end of the line. The data given here is used by the X server to determine if video modes are within the specifications of the monitor. This information should be available in the monitor`s handbook. If this entry is omitted, a default range of 28-33kHz is used.

VertRefresh vertrefresh-range

gives the range(s) of vertical refresh frequencies supported by the monitor. vertrefresh-range may be a comma separated list of either discrete values or ranges of values. A range of values is two values separated by a dash. By default the values are in units of Hz. They may be specified in MHz or kHz if MHz or kHz is added to the end of the line. The data given here is used by the X server to determine if video modes are within the specifications of the monitor. This information should be available in the monitor`s handbook. If this entry is omitted, a default range of 43-72Hz is used.

DisplaySize width height

This optional entry gives the width and height, in millimetres, of the picture area of the monitor. If given this is used to calculate the horizontal and vertical pitch (DPI) of the screen.

Gamma gamma-value

Gamma red-gamma green-gamma blue-gamma

This is an optional entry that can be used to specify the gamma correction for the monitor. It may be specified as either a single value or as three separate RGB values. The values should be in the range 0.1 to 10.0, and the default is 1.0. Not all drivers are capable of using this information.

UseModes N`34`modesection-idN`34`

Include the set of modes listed in the Modes section called modesection-id. This make all of the modes defined in that section available for use by this monitor.

Mode name

This is an optional multi-line entry that can be used to provide definitions for video modes for the monitor. In most cases this isn`t necessary because the built-in set of VESA standard modes will be sufficient. The Mode keyword indicates the start of a multi-line video mode description. The mode description is terminated with the EndMode keyword. The mode description consists of the following entries:

DotClock clock

is the dot (pixel) clock rate to be used for the mode.

HTimings hdisp hsyncstart hsyncend htotal

specifies the horizontal timings for the mode.

VTimings vdisp vsyncstart vsyncend vtotal

specifies the vertical timings for the mode.

Flags N`34`flagN`34` ...

specifies an optional set of mode flags, each of which is a separate string in double quotes. N`34`InterlaceN`34` indicates that the mode is interlaced. N`34`DoubleScanN`34` indicates a mode where each scanline is doubled. N`34`+HSyncN`34` and N`34`-HSyncN`34` can be used to select the polarity of the HSync signal. N`34`+VSyncN`34` and N`34`-VSyncN`34` can be used to select the polarity of the VSync signal. N`34`CompositeN`34` can be used to specify composite sync on hardware where this is supported. Additionally, on some hardware, N`34`+CSyncN`34` and N`34`-CSyncN`34` may be used to select the composite sync polarity.

HSkew hskew

specifies the number of pixels (towards the right edge of the screen) by which the display enable signal is to be skewed. Not all drivers use this information. This option might become necessary to override the default value supplied by the server (if any). "Roving" horizontal lines indicate this value needs to be increased. If the last few pixels on a scan line appear on the left of the screen, this value should be decreased.

VScan vscan

specifies the number of times each scanline is painted on the screen. Not all drivers use this information. Values less than 1 are treated as 1, which is the default. Generally, the N`34`DoubleScanN`34` Flag mentioned above doubles this value.

ModeLine N`34`nameN`34` mode-description

This entry is a more compact version of the Mode entry, and it also can be used to specify video modes for the monitor. is a single line format for specifying video modes. In most cases this isn`t necessary because the built-in set of VESA standard modes will be sufficient.

The mode-description is in four sections, the first three of which are mandatory. The first is the dot (pixel) clock. This is a single number specifying the pixel clock rate for the mode in MHz. The second section is a list of four numbers specifying the horizontal timings. These numbers are the hdisp, hsyncstart, hsyncend, and htotal values. The third section is a list of four numbers specifying the vertical timings. These numbers are the vdisp, vsyncstart, vsyncend, and vtotal values. The final section is a list of flags specifying other characteristics of the mode. Interlace indicates that the mode is interlaced. DoubleScan indicates a mode where each scanline is doubled. +HSync and -HSync can be used to select the polarity of the HSync signal. +VSync and -VSync can be used to select the polarity of the VSync signal. Composite can be used to specify composite sync on hardware where this is supported. Additionally, on some hardware, +CSync and -CSync may be used to select the composite sync polarity. The HSkew and VScan options mentioned above in the Modes entry description can also be used here.

Options

Some Option flags that may be useful to include in Monitor sections (when needed) include N`34`DPMSN`34`, and N`34`SyncOnGreenN`34`.

 

MODES SECTION

The config file may have multiple Modes sections, or none. These sections provide a way of defining sets of video modes independently of the Monitor sections. Monitor sections may include the definitions provided in these sections by using the UseModes keyword. In most cases the Modes sections are not necessary because the built-in set of VESA standard modes will be sufficient.

Modes sections have the following format:

Section N`34`ModesN`34` Identifier N`34`nameN`34` entries ... EndSection

The Identifier entry specifies the unique name for this set of mode descriptions. The other entries permitted in Modes sections are the Mode and ModeLine entries that are described above in the Monitor section.  

SCREEN SECTION

The config file may have multiple Screen sections. There must be at least one, for the "screen" being used. A "screen" represents the binding of a graphics device (Device section) and a monitor (Monitor section). A Screen section is considered "active" if it is referenced by an active ServerLayout section or by the -screen command line option. If neither of those is present, the first Screen section found in the config file is considered the active one.

Screen sections have the following format:

Section N`34`ScreenN`34` Identifier N`34`nameN`34` Device N`34`devidN`34` Monitor N`34`monidN`34` entries ... SubSection N`34`DisplayN`34` entries ... EndSubSection ... EndSection

The Identifier entry specifies the unique name for this screen. The Screen section provides information specific to the whole screen, including screen-specific Options. In multi-head configurations, there will be multiple active Screen sections, one for each head. The entries available for this section are:

Device N`34`device-idN`34`

This specifies the Device section to be used for this screen. This is what ties a specific graphics card to a screen. The device-id must match the Identifier of a Device section in the config file.

Monitor N`34`monitor-idN`34`

specifies which monitor description is to be used for this screen.

VideoAdaptor N`34`xv-idN`34`

specifies an optional Xv video adaptor description to be used with this screen.

DefaultDepth depth

specifies which color depth the server should use by default. The -depth command line option can be used to override this. If neither is specified, the default depth is driver-specific, but in most cases is 8.

DefaultFbBpp bpp

specifies which framebuffer layout to use by default. The -fbbpp command line option can be used to override this. In most cases the driver will chose the best default value for this. The only case where there is even a choice in this value is for depth 24, where some hardware supports both a packed 24 bit framebuffer layout and a sparse 32 bit framebuffer layout.

Options

Various Option flags may be specified in the Screen section. Some are driver-specific and are described in the driver documentation. Others are driver-independent, and will eventually be described here.

Option N`34`AccelN`34`

Enables XAA (X Acceleration Architecture), a mechanism that makes video cards` 2D hardware acceleration available to the X server. This option is on by default, but it may be necessary to turn it off if there are bugs in the driver. There are many options to disable specific acclerated operations, listed below. Note that disabling an operation will have no effect if the operation is not accelerated (whether due to lack of support in the hardware or in the driver).

Option N`34`NoMTRRN`34`

Disables MTRR (Memory Type Range Register) support, a feature of modern processors which can improve video performance by a factor of up to 2.5. Some hardware has buggy MTRR support, and some video drivers have been known to exhibit problems when MTRR`s are used.

Option N`34`XaaNoCPUToScreenColorExpandFillN`34`

Disables accelerated rectangular expansion blits from source patterns stored in system memory (using a memory-mapped aperture).

Option N`34`XaaNoColor8x8PatternFillRectN`34`

Disables accelerated fills of a rectangular region with a full-color pattern.

Option N`34`XaaNoColor8x8PatternFillTrapN`34`

Disables accelerated fills of a trapezoidal region with a full-color pattern.

Option N`34`XaaNoDashedBresenhamLineN`34`

Disables accelerated dashed Bresenham line draws.

Option N`34`XaaNoDashedTwoPointLineN`34`

Disables accelerated dashed line draws between two arbitrary points.

Option N`34`XaaNoImageWriteRectN`34`

Disables acclerated transfers of full-color rectangular patterns from system memory to video memory (using a memory-mapped aperture).

Option N`34`XaaNoMono8x8PatternFillRectN`34`

Disables accelerated fills of a rectangular region with a monochrome pattern.

Option N`34`XaaNoMono8x8PatternFillTrapN`34`

Disables accelerated fills of a trapezoidal region with a monochrome pattern.

Option N`34`XaaNoOffscreenPixmapsN`34`

Disables accelerated draws into pixmaps stored in offscreen video memory.

Option N`34`XaaNoPixmapCacheN`34`

Disables caching of patterns in offscreen video memory.

Option N`34`XaaNoScanlineCPUToScreenColorExpandFillN`34`

Disables accelerated rectangular expansion blits from source patterns stored in system memory (one scan line at a time).

Option N`34`XaaNoScanlineImageWriteRectN`34`

Disables acclerated transfers of full-color rectangular patterns from system memory to video memory (one scan line at a time).

Option N`34`XaaNoScreenToScreenColorExpandFillN`34`

Disables accelerated rectangular expansion blits from source patterns stored in offscreen video memory.

Option N`34`XaaNoScreenToScreenCopyN`34`

Disables accelerated copies of rectangular regions from one part of video memory to another part of video memory.

Option N`34`XaaNoSolidBresenhamLineN`34`

Disables accelerated solid Bresenham line draws.

Option N`34`XaaNoSolidFillRectN`34`

Disables accelerated solid-color fills of rectangles.

Option N`34`XaaNoSolidFillTrapN`34`

Disables accelerated solid-color fills of Bresenham trapezoids.

Option N`34`XaaNoSolidHorVertLineN`34`

Disables accelerated solid horizontal and vertical line draws.

Option N`34`XaaNoSolidTwoPointLineN`34`

Disables accelerated solid line draws between two arbitrary points.

Each Screen section must contain one or more Display subsections. Those subsections provide depth/fbbpp specific configuration information, and the one chosen depends on the depth and/or fbbpp that is being used for the screen. The Display subsection format is described in the section below.

 

DISPLAY SUBSECTION

Each Screen section may have multiple Display subsections. There must be at least one, which matches the depth and/or fbbpp values that are being used for the screen. The "active" Display subsection is the first that matches the depth and/or fbbpp values being used.

Display subsections have the following format:

SubSection N`34`DisplayN`34` Depth depth entries ... EndSubSection

Depth depth

This entry specifies what colour depth the Display subsection is to be used for. This entry is usually mandatory, but it may be omitted in some cases providing an FbBpp entry is present. The range of depth values that are allowed depends on the driver. Most driver support 8, 15, 16 and 24. Some also support 1 and/or 4, and some may support other values (like 30). Note: depth means the number of bits in a pixel that are actually used to determine the pixel colour. 32 is not a valid depth value. Most hardware that uses 32 bits per pixel only uses 24 of them to hold the colour information, which means that the colour depth is 24, not 32.

FbBpp bpp

This entry specifies the framebuffer format this Display subsection is to be used for. This entry is only needed when providing depth 24 configurations that allow a choice between a 24 bpp packed framebuffer format and a 32bpp sparse framebuffer format. In most cases this entry should not be used.

Weight red-weight green-weight blue-weight

This optional entry specifies the relative RGB weighting to be used for a screen is being used at depth 16 for drivers that allow multiple formats. This may also be specified from the command line with the -weight option (see XFree86(1)).

Virtual xdim ydim

This optional entry specifies the virtual screen resolution to be used. xdim must be a multiple of either 8 or 16 for most drivers, and a multiple of 32 when running in monochrome mode. The given value will be rounded down if this is not the case. Video modes which are too large for the specified virtual size will be rejected. If this entry is not present, the virtual screen resolution will be set to accommodate all the valid video modes given in the Modes entry. Some drivers/hardware combinations do not support virtual screens. Refer to the appropriate driver-specific documentation for details.

ViewPort x0 y0

This optional entry sets the upper left corner of the initial display. This is only relevant when the virtual screen resolution is different from the resolution of the initial video mode. If this entry is not given, then the initial display will be centered in the virtual display area.

Modes N`34`mode-nameN`34` ...

This entry is highly desirable for most drivers, and it specifies the list of video modes to use. Each mode-name specified must be in double quotes. They must correspond to those specified or referenced in the appropriate Monitor section (including implicitly referenced built-in VESA standard modes). The server will delete modes from this list which don`t satisfy various requirements. The first valid mode in this list will be the default display mode for startup. The list of valid modes is converted internally into a circular list. It is possible to switch to the next mode with Ctrl+Alt+Keypad-Plus and to the previous mode with Ctrl+Alt+Keypad-Minus. When this entry is omitted, the largest valid mode referenced by the appropriate Monitor section will be used.

Visual N`34`visual-nameN`34`

This optional entry sets the default root visual type. This may also be specified from the command line (see the Xserver(1) man page). The visual types available for depth 8 are (default is PseudoColor):

StaticGray GrayScale StaticColor PseudoColor TrueColor DirectColor

The visual type available for the depths 15, 16 and 24 are (default is TrueColor):

TrueColor DirectColor

Not all drivers support DirectColor at these depths.

The visual types available for the depth 4 are (default is StaticColor):

StaticGray GrayScale StaticColor PseudoColor

The visual type available for the depth 1 (monochrome) is StaticGray.

Black red green blue

This optional entry allows the "black" colour to be specified. This is only supported at depth 1. The default is black.

White red green blue

This optional entry allows the "white" colour to be specified. This is only supported at depth 1. The default is white.

Options

Option flags may be specified in the Display subsections. These may include driver-specific options and driver-independent options. The former are described in the driver-specific documentation. Some of the latter are described above in the section about the Screen section, and they may also be included here.

 

SERVERLAYOUT SECTION

The config file may have multiple ServerLayout sections. A "server layout" represents the binding of one or more screens (Screen sections) and one or more input devices (InputDevice sections) to form a complete configuration. In multi-head configurations, it also specifies the relative layout of the heads. A ServerLayout section is considered "active" if it is referenced by the -layout command line option or by an Option N`34`DefaultServerLayoutN`34` entry in the ServerFlags section (the former takes precedence over the latter). If those options are not used, the first ServerLayout section found in the config file is considered the active one. If no ServerLayout sections are present, the single active screen and two active (core) input devices are selected as described in the relevant sections above.

ServerLayout sections have the following format:

Section N`34`ServerLayoutN`34` Identifier N`34`nameN`34` Screen N`34`screen-idN`34` ... InputDevice N`34`idev-idN`34` ... options ... EndSection

The Identifier entry specifies the unique name for this server layout. The ServerLayout section provides information specific to the whole session, including session-specific Options. The ServerFlags options (described above) may be specified here, and ones given here override those given in the ServerFlags section.

The entries that may be used in this section are described here.

Screen screen-num N`34`screen-idN`34` position-information

One of these entries must be given for each screen being used in a session. The screen-id field is mandatory, and specifies the Screen section being referenced. The screen-num field is optional, and may be used to specify the screen number in multi-head configurations. When this field is omitted, the screens will be numbered in the order that they are listed in. The numbering starts from 0, and must be consecutive. The position-information field describes the way multiple screens are positioned. There are a number of different ways that this information can be provided:

x y

Absolute x y

These both specify that the upper left corner`s coordinates are (x,y). The Absolute keyword is optional. Some older versions of XFree86 (4.2 and earlier) don`t recognise the Absolute keyword, so it`s safest to just specificy the coorindates without it.

RightOf N`34`screen-idN`34`

LeftOf N`34`screen-idN`34`

Above N`34`screen-idN`34`

Below N`34`screen-idN`34`

Relative N`34`screen-idN`34` x y

These give the screen`s location relative to another screen. The first four position the screen immediately to the right, left, above or below the other screen. When positioning to the right or left, the top edges are aligned. When positioning above or below, the left edges are aligned. The Relative form specifies the offset of the screen`s origin (upper left corner) relative to the origin of another screen.

InputDevice N`34`idev-idN`34` N`34`optionN`34` ...

One of these entries must be given for each input device being used in a session. Normally at least two are required, one each for the core pointer and keyboard devices. The idev-id field is mandatory, and specifies the name of the InputDevice section being referenced. Multiple option fields may be specified, each in double quotes. The options permitted here are any that may also be given in the InputDevice sections. Normally only session-specific input device options would be used here. The most commonly used options are:

N`34`CorePointerN`34` N`34`CoreKeyboardN`34` N`34`SendCoreEventsN`34`

and the first two should normally be used to indicate the core pointer and core keyboard devices respectively.

Options

Any option permitted in the ServerFlags section may also be specified here. When the same option appears in both places, the value given here overrides the one given in the ServerFlags section.

Here is an example of a ServerLayout section for a dual headed configuration with two mice:

Section N`34`ServerLayoutN`34` Identifier N`34`Layout 1N`34` Screen N`34`MGA 1N`34` Screen N`34`MGA 2N`34` RightOf N`34`MGA 1N`34` InputDevice N`34`Keyboard 1N`34` N`34`CoreKeyboardN`34` InputDevice N`34`Mouse 1N`34` N`34`CorePointerN`34` InputDevice N`34`Mouse 2N`34` N`34`SendCoreEventsN`34` Option N`34`BlankTimeN`34` N`34`5N`34` EndSection

 

DRI SECTION

This optional section is used to provide some information for the Direct Rendering Infrastructure. Details about the format of this section can be found in the README.DRI document, which is also available on-line at <http://www.xfree86.org/current/DRI.html>.  

VENDOR SECTION

The optional Vendor section may be used to provide vendor-specific configuration information. Multiple Vendor sections may be present, and they may contain an Identifier entry and multiple Option flags. The data therein is not used in this release.

 

FILES

For an example of an XF86Config file, see the file installed as /usr/X11R6/lib/X11/XF86Config.eg.  

SEE ALSO

X(7), Xserver(1), XFree86(1), apm(4), chips(4), cirrus(4), cyrix(4), fbdev(4), glide(4), glint(4), i128(4), i740(4), i810(4), imstt(4), mga(4), neomagic(4), nv(4), r128(4), rendition(4), savage(4), s3virge(4), siliconmotion(4), sis(4), sunbw2(4), suncg14(4), suncg3(4), suncg6(4), sunffb(4), sunleo(4), suntcx(4), tdfx(4), tga(4), trident(4), tseng(4), v4l(4), vesa(4), vga(4), vmware(4),
README <http://www.xfree86.org/current/README.html>,
RELNOTES <http://www.xfree86.org/current/RELNOTES.html>,
README.mouse <http://www.xfree86.org/current/mouse.html>,
README.DRI <http://www.xfree86.org/current/DRI.html>,
Status <http://www.xfree86.org/current/Status.html>,
Install <http://www.xfree86.org/current/Install.html>.  

AUTHORS

This manual page was largely rewritten for XFree86 4.0 by David Dawes <dawes@xfree86.org>.

xferlog

NAME

xferlog - ProFTPD server logfile  

DESCRIPTION

The xferlog file contains logging information from the FTP server daemon, proftpd(8). This file usually is found in /var/log but can be located anywhere by using a proftpd(8) configuration directive. Each server entry is composed of a single line of the following form, with all fields being separated by spaces.

current-time   transfer-time   remote-host   file-size   filename   transfer-type   special-action-flag   direction   access-mode   username   service-name   authentication-method   authenticated-user-id  completion-status

current-time

is the current local time in the form "DDD MMM dd hh:mm:ss YYYY". Where DDD is the day of the week, MMM is the month, dd is the day of the month, hh is the hour, mm is the minutes, ss is the seconds, and YYYY is the year.

transfer-time

is the total time in seconds for the transfer.

remote-host

is the remote host name.

file-size

is the size of the transferred file in bytes.

filename

is the name of the transferred file. If the filename contains any spaces or control characters, each such character is replaced by an underscore (`_`) character.

transfer-type

is a single character indicating the type of transfer. Can be one of:

a

for an ascii transfer

b

for a binary transfer

special-action-flag

is one or more single character flags indicating any special action taken. Can be one or more of:

C

file was compressed

U

file was uncompressed

T

file was tar`ed

_

no action was taken

direction

is the direction of the transfer. Can be one of:

o

outgoing

i

incoming

d

deleted

access-mode

is the method by which the user is logged in. Can be one of:

a

(anonymous) is for an anonymous guest user.

r

(real) is for a local authenticated user.

username

is the local username, or if guest, the ID string given.

service-name

is the name of the service being invoked, usually FTP.

authentication-method

is the method of authentication used. Can be one of:

0

none

1

RFC931 Authentication

authenticated-user-id

is the user id returned by the authentication method. A * is used if an authenticated user id is not available.

completion-status

is a single character indicating the status of the transfer. Can be one of:

c

complete transfer

i

incomplete transfer

 

FILES

/var/log/xferlog

 

AUTHORS

ProFTPD is written and maintained by a number of people, full credits can be found on http://www.proftpd.org/credits.html  

SEE ALSO

proftpd(8)

Full documentation on ProFTPD, including configuration and FAQs, is available at http://www.proftpd.org/

For help/support, try the ProFTPD mailing lists, detailed on http://www.proftpd.org/lists.html

Report bugs at http://bugs.proftpd.org/

xinetd.conf

NAME

xinetd.conf - Extended Internet Services Daemon configuration file  

DESCRIPTION

xinetd.conf is the configuration file that determines the services provided by xinetd. Any line whose first non-white-space character is a `#` is considered a comment line. Empty lines are ignored.

The file contains entries of the form:

service <service_name> {

<attribute> <assign_op> <value> <value> ... ...

}

The assignment operator, assign_op, can be one of `=`, `+=`, `-=`. The majority of attributes support only the simple assignment operator, `=`. Attributes whose value is a set of values support all assignment operators. For such attributes, `+=` means adding a value to the set and `-=` means removing a value from the set. A list of these attributes will be given after all the attributes are described.

Each entry defines a service identified by the service_name. The following is a list of available attributes:

id

This attribute is used to uniquely identify a service. This is useful because there exist services that can use different protocols and need to be described with different entries in the configuration file. By default, the service id is the same as the service name.

type

Any combination of the following values may be used:

RPC

if this is an RPC service

INTERNAL

if this is a service provided by xinetd.

TCPMUX/TCPMUXPLUS

if this is a service that will be started according to the RFC 1078 protocol on the TCPMUX well-known port. See the section describing TCPMUX services below.

UNLISTED

if this is a service not listed in a standard system file (like /etc/rpc for RPC services, or /etc/services for non-RPC services).

flags

Any combination of the following flags may be used:

INTERCEPT

Intercept packets or accepted connections in order to verify that they are coming from acceptable locations (internal or multi-threaded services cannot be intercepted).

NORETRY

Avoid retry attempts in case of fork failure.

IDONLY

Accept connections only when the remote end identifies the remote user (i.e. the remote host must run an identification server). This flag applies only to connection-based services. This flag is ineffective if the USERID log option is not used.

NAMEINARGS

This will cause the first argument in "server_args" to be argv[0] when executing the server, as specified in "server". This allows you to use tcpd by putting tcpd in "server" and the name of the server in "server_args" like in normal inetd.

NODELAY

If the service is a tcp service and the NODELAY flag is set, then the TCP_NODELAY flag will be set on the socket. If the service is not a tcp service, this option has no effect.

KEEPALIVE

If the service is a tcp service and the KEEPALIVE flag is set, then the SO_KEEPALIVE socket flag will be set on the socket. If the service is not a tcp service, this option has no effect.

NOLIBWRAP

This disables internal calling of the tcpwrap library to determine access to the service. This may be needed in order to use libwrap functionality not available to long-running processes such as xinetd; in this case, the tcpd program can be called explicitly (see also the NAMEINARGS flag). For RPC services using TCP transport, this flag is automatically turned on, because xinetd cannot get remote host address information for the rpc port.

SENSOR

This replaces the service with a sensor that detects accesses to the specified port. NOTE: It will NOT detect stealth scans. This flag should be used only on services that you know you don`t need. When an access is made to this service`s port, the IP Address is added to a global no_access list. This causes all subsequent accesses from the originating IP address to be denied access until the deny_time setting expires. The amount of time spent on this list is configurable as the deny_time attribute. The SENSOR flag will also cause xinetd to consider the server attribute to be INTERNAL no matter what is typed on the same line. Another important thing to remember is that if the socket_type is set to stream, then the wait attribute should be set to no.

IPv4

Sets the service to be an IPv4 service (AF_INET).

IPv6

Sets the service to be an IPv6 service (AF_INET6), if IPv6 is available on the system.

REUSE

The REUSE flag is deprecated. All services now implicitly use the REUSE flag.

disable

This is boolean "yes" or "no". This will result in the service being disabled and not starting. See the DISABLE flag description.

socket_type

Possible values for this attribute include:

stream

stream-based service

dgram

datagram-based service

raw

service that requires direct access to IP

seqpacket

service that requires reliable sequential datagram transmission

protocol

determines the protocol that is employed by the service. The protocol must exist in /etc/protocols. If this attribute is not defined, the default protocol employed by the service will be used.

wait

This attribute determines if the service is single-threaded or multi-threaded and whether or not xinetd accepts the connection or the server program accepts the connection. If its value is yes, the service is single-threaded; this means that xinetd will start the server and then it will stop handling requests for the service until the server dies and that the server software will accept the connection. If the attribute value is no, the service is multi-threaded and xinetd will keep handling new service requests and xinetd will accept the connection. It should be noted that udp/dgram services normally expect the value to be yes since udp is not connection oriented, while tcp/stream servers normally expect the value to be no.

user

determines the uid for the server process. The user attribute can either be numeric or a name. If a name is given (recommended), the user name must exist in /etc/passwd. This attribute is ineffective if the effective user ID of xinetd is not super-user.

group

determines the gid for the server process. The group attribute can either be numeric or a name. If a name is given (recommended), the group name must exist in /etc/group. If a group is not specified, the group of user will be used (from /etc/passwd). This attribute is ineffective if the effective user ID of xinetd is not super-user.

instances

determines the number of servers that can be simultaneously active for a service (the default is no limit). The value of this attribute can be either a number or UNLIMITED which means that there is no limit.

nice

determines the server priority. Its value is a (possibly negative) number; check nice(3) for more information.

server

determines the program to execute for this service.

server_args

determines the arguments passed to the server. In contrast to inetd, the server name should not be included in server_args.

libwrap

overrides the service name passed to libwrap (which defaults to the server name, the first server_args component with NAMEINARGS, the id for internal services and the service name for redirected services). This attribute is only valid if xinetd has been configured with the libwrap option.

only_from

determines the remote hosts to which the particular service is available. Its value is a list of IP addresses which can be specified in any combination of the following ways:

a)

a numeric address in the form of %d.%d.%d.%d. If the rightmost components are 0, they are treated as wildcards (for example, 128.138.12.0 matches all hosts on the 128.138.12 subnet). 0.0.0.0 matches all Internet addresses. IPv6 hosts may be specified in the form of abcd:ef01::2345:6789. The rightmost rule for IPv4 addresses does not apply to IPv6 addresses.

b)

a factorized address in the form of %d.%d.%d.{%d,%d,...}. There is no need for all 4 components (i.e. %d.%d.{%d,%d,...%d} is also ok). However, the factorized part must be at the end of the address. This form does not work for IPv6 hosts.

c)

a network name (from /etc/networks). This form does not work for IPv6 hosts.

d)

a host name. When a connection is made to xinetd, a reverse lookup is performed, and the canonical name returned is compared to the specified host name. You may also use domain names in the form of .domain.com. If the reverse lookup of the client`s IP is within .domain.com, a match occurs.

e)

an ip address/netmask range in the form of 1.2.3.4/32. IPv6 address/netmask ranges in the form of 1234::/46 are also valid.

Specifying this attribute without a value makes the service available to nobody.

no_access

determines the remote hosts to which the particular service is unavailable. Its value can be specified in the same way as the value of the only_from attribute. These two attributes determine the location access control enforced by xinetd. If none of the two is specified for a service, the service is available to anyone. If both are specified for a service, the one that is the better match for the address of the remote host determines if the service is available to that host (for example, if the only_from list contains 128.138.209.0 and the no_access list contains 128.138.209.10 then the host with the address 128.138.209.10 can not access the service).

access_times

determines the time intervals when the service is available. An interval has the form hour:min-hour:min (connections will be accepted at the bounds of an interval). Hours can range from 0 to 23 and minutes from 0 to 59.

log_type

determines where the service log output is sent. There are two formats:

SYSLOG syslog_facility [syslog_level]

The log output is sent to syslog at the specified facility. Possible facility names include: daemon, auth, authpriv, user, mail, lpr, news, uucp, ftp local0-7. Possible level names include: emerg, alert, crit, err, warning, notice, info, debug. If a level is not present, the messages will be recorded at the info level.

FILE file [soft_limit [hard_limit]]

The log output is appended to file which will be created if it does not exist. Two limits on the size of the log file can be optionally specified. The first limit is a soft one; xinetd will log a message the first time this limit is exceeded (if xinetd logs to syslog, the message will be sent at the alert priority level). The second limit is a hard limit; xinetd will stop logging for the affected service (if the log file is a common log file, then more than one service may be affected) and will log a message about this (if xinetd logs to syslog, the message will be sent at the alert priority level). If a hard limit is not specified, it defaults to the soft limit increased by 1% but the extra size must be within the parameters <FONT SIZE="-1">LOG_EXTRA_MIN</FONT> and <FONT SIZE="-1">LOG_EXTRA_MAX</FONT> which default to 5K and 20K respectively (these constants are defined in xconfig.h).

log_on_success

determines what information is logged when a server is started and when that server exits (the service id is always included in the log entry). Any combination of the following values may be specified:

PID

logs the server process id (if the service is implemented by xinetd without forking another process the logged process id will be 0)

HOST

logs the remote host address

USERID

logs the user id of the remote user using the RFC 1413 identification protocol. This option is available only for multi-threaded stream services.

EXIT

logs the fact that a server exited along with the exit status or the termination signal (the process id is also logged if the PID option is used)

DURATION

logs the duration of a service session

TRAFFIC

logs the total bytes in and out for a redirected service.

log_on_failure

determines what information is logged when a server cannot be started (either because of a lack of resources or because of access control restrictions). The service id is always included in the log entry along with the reason for failure. Any combination of the following values may be specified:

HOST

logs the remote host address.

USERID

logs the user id of the remote user using the RFC 1413 identification protocol. This option is available only for multi-threaded stream services.

ATTEMPT

logs the fact that a failed attempt was made (this option is implied by all others).

rpc_version

determines the RPC version for a RPC service. The version can be a single number or a range in the form number-number.

rpc_number

determines the number for an UNLISTED RPC service (this attribute is ignored if the service is not unlisted).

env

The value of this attribute is a list of strings of the form `name=value`. These strings will be added to the environment before starting a server (therefore the server`s environment will include xinetd`s environment plus the specified strings).

passenv

The value of this attribute is a list of environment variables from xinetd`s environment that will be passed to the server. An empty list implies passing no variables to the server except for those explicitly defined using the env attribute. (notice that you can use this attribute in conjunction with the env attribute to specify exactly what environment will be passed to the server).

port

determines the service port. If this attribute is specified for a service listed in /etc/services, it must be equal to the port number listed in that file.

redirect

Allows a tcp service to be redirected to another host. When xinetd receives a tcp connection on this port it spawns a process that establishes a connection to the host and port number specified, and forwards all data between the two hosts. This option is useful when your internal machines are not visible to the outside world. Syntax is: redirect = (ip address) (port). You can also use a hostname instead of the IP address in this field. The hostname lookup is performed only once, when xinetd is started, and the first IP address returned is the one that is used until xinetd is restarted. The "server" attribute is not required when this option is specified. If the "server" attribute is specified, this attribute takes priority.

bind

Allows a service to be bound to a specific interface on the machine. This means you can have a telnet server listening on a local, secured interface, and not on the external interface. Or one port on one interface can do something, while the same port on a different interface can do something completely different. Syntax: bind = (ip address of interface).

interface

Synonym for bind.

banner

Takes the name of a file to be splatted at the remote host when a connection to that service is established. This banner is printed regardless of access control. It should *always* be printed when a connection has been made. xinetd outputs the file as-is, so you must ensure the file is correctly formatted for the service`s protocol. In paticular, if the protocol requires CR-LF pairs for line termination, you must supply them.

banner_success

Takes the name of a file to be splatted at the remote host when a connection to that service is granted. This banner is printed as soon as access is granted for the service. xinetd outputs the file as-is, so you must ensure the file is correctly formatted for the service`s protocol. In paticular, if the protocol requires CR-LF pairs for line termination, you must supply them.

banner_fail

Takes the name of a file to be splatted at the remote host when a connection to that service is denied. This banner is printed immediately upon denial of access. This is useful for informing your users that they are doing something bad and they shouldn`t be doing it anymore. xinetd outputs the file as-is, so you must ensure the file is correctly formatted for the service`s protocol. In paticular, if the protocol requires CR-LF pairs for line termination, you must supply them.

per_source

Takes an integer or "UNLIMITED" as an argument. This specifies the maximum instances of this service per source IP address. This can also be specified in the defaults section.

cps

Limits the rate of incoming connections. Takes two arguments. The first argument is the number of connections per second to handle. If the rate of incoming connections is higher than this, the service will be temporarily disabled. The second argument is the number of seconds to wait before re-enabling the service after it has been disabled. The default for this setting is 50 incoming connections and the interval is 10 seconds.

max_load

Takes a floating point value as the load at which the service will stop accepting connections. For example: 2 or 2.5. The service will stop accepting connections at this load. This is the one minute load average. This is an OS dependent feature, and currently only Linux, Solaris, and FreeBSD are supported for this. This feature is only avaliable if xinetd was configured with the -with-loadavg option.

groups

Takes either "yes" or "no". If the groups attribute is set to "yes", then the server is executed with access to the groups that the server`s effective UID has access to. If the groups attribute is set to "no", then the server runs with no supplementary groups. This attribute must be set to "yes" for many BSD systems. This attribute can be set in the defaults section as well.

mdns

Takes either "yes" or "no". On systems that support mdns registration of services (currently only Mac OS X), this will enable or disable registration of the service. This defaults to "yes".

umask

Sets the inherited umask for the service. Expects an octal value. This option may be set in the "defaults" section to set a umask for all services. xinetd sets its own umask to the previous umask OR`d with 022. This is the umask that will be inherited by all child processes if the umask option is not used.

enabled

Takes a list of service ID`s to enable. This will enable only the services listed as arguments to this attribute; the rest will be disabled. If you have 2 ftp services, you will need to list both of their ID`s and not just ftp. (ftp is the service name, not the ID. It might accidentally be the ID, but you better check.) Note that the service "disable" attribute and "DISABLE" flag can prevent a service from being enabled despite being listed in this attribute.

include

Takes a filename in the form of "include /etc/xinetd/service". The file is then parsed as a new configuration file. It is not the same thing as pasting the file into xinetd.conf where the include directive is given. The included file must be in the same form as xinetd.conf. This may not be specified from within a service. It must be specified outside a service declaration.

includedir

Takes a directory name in the form of "includedir /etc/xinetd.d". Every file inside that directory, excluding files with names containing a dot (`.`) or ending with a tilde (`~`), will be parsed as xinetd configuration files. The files will be parsed in alphabetical order according to the C locale. This allows you to specify services one per file within a directory. The includedir directive may not be specified from within a service declaration.

rlimit_as

Sets the Address Space resource limit for the service. One parameter is required, which is either a positive integer representing the number of bytes to set the limit to (K or M may be used to specify kilobytes/megabytes) or "UNLIMITED". Due to the way Linux`s libc malloc is implemented, it is more useful to set this limit than rlimit_data, rlimit_rss and rlimit_stack. This resource limit is only implemented on Linux systems.

rlimit_cpu

Sets the maximum number of CPU seconds that the service may use. One parameter is required, which is either a positive integer representing the number of CPU seconds limit to, or "UNLIMITED".

rlimit_data

Sets the maximum data size resource limit for the service. One parameter is required, which is either a positive integer representing the number of bytes or "UNLIMITED".

rlimit_rss

Sets the maximum resident set size limit for the service. Setting this value low will make the process a likely candidate for swapping out to disk when memory is low. One parameter is required, which is either a positive integer representing the number of bytes or "UNLIMITED".

rlimit_stack

Set the maximum stack size limit for the service. One parameter is required, which is either a positive integer representing the number of bytes or "UNLIMITED".

deny_time

Sets the time span that access to all services on all IP addresses are denied to someone that sets off the SENSOR. The unit of time is in minutes. Valid options are: FOREVER, NEVER, and a numeric value. FOREVER causes the IP address not to be purged until xinetd is restarted. NEVER has the effect of just logging the offending IP address. A typical time value would be 60 minutes. This should stop most DOS attacks while allowing IP addresses that come from a pool to be recycled for legitimate purposes. This option must be used in conjunction with the SENSOR flag.

You don`t need to specify all of the above attributes for each service. The necessary attributes for a service are:

socket_type

user

(non-internal services only)

server

(non-internal services only)

wait

protocol

(RPC and unlisted services only)

rpc_version

(RPC services only)

rpc_number

(unlisted RPC services only)

port

(unlisted non-RPC services only)

The following attributes support all assignment operators:

only_from

no_access

log_on_success

log_on_failure

passenv

env

(does not support the `-=` operator)

These attributes can also appear more than once in a service entry. The remaining attributes support only the `=` operator and can appear at most once in a service entry.

The configuration file may also contain a single defaults entry that has the form

defaults {

<attribute> = <value> <value> ... ...

}

This entry provides default attribute values for service entries that don`t specify those attributes. Possible default attributes:

log_type

(cumulative effect)

bind

per_source

umask

log_on_success

(cumulative effect)

log_on_failure

(cumulative effect)

only_from

(cumulative effect)

no_access

(cumulative effect)

passenv

(cumulative effect)

instances

disabled

(cumulative effect)

enabled

(cumulative effect)

banner

banner_success

banner_fail

per_source

groups

cps

max_load

Attributes with a cumulative effect can be specified multiple times with the values specified each time accumulating (i.e. `=` does the same thing as `+=`). With the exception of disabled they all have the same meaning as if they were specified in a service entry. disabled determines services that are disabled even if they have entries in the configuration file. This allows for quick reconfiguration by specifying disabled services with the disabled attribute instead of commenting them out. The value of this attribute is a list of space separated service ids. enabled has the same properties as disabled. The difference being that enabled is a list of which services are to be enabled. If enabled is specified, only the services specified are available. If enabled is not specified, all services are assumed to be enabled, except those listed in disabled.

 

INTERNAL SERVICES

xinetd provides the following services internally (both stream and datagram based): echo, time, daytime, chargen, and discard. These services are under the same access restrictions as all other services except for the ones that don`t require xinetd to fork another process for them. Those ones (time, daytime, and the datagram-based echo, chargen, and discard) have no limitation in the number of instances.

 

TCPMUX Services

xinetd supports TCPMUX services that conform to RFC 1078. These services may not have a well-known port associated with them, and can be accessed via the TCPMUX well-known port.

For each service that is to be accessed via TCPMUX, a service entry in /etc/xinetd.conf or in a configuration file in an includedir directory must exist.

The service_name field (as defined above for each service in any xinetd configuration file) must be identical to the string that is passed (according to RFC 1078 protocol) to xinetd when the remote service requestor first makes the connection on the TCPMUX well-known port. Private protocols should use a service name that has a high probability of being unique. One way is to prepend the service name with some form of organization ID.

The type field can be either TCPMUX or TCPMUXPLUS. If the type is TCPMUXPLUS, xinetd will handle the initial protocol handshake (as defined in RFC 1078) with the calling process before initiating the service. If the type is TCPMUX, the server that is started is responsible for performing the handshake.

The type field should also include UNLISTED if the service is not listed in a standard system file (like /etc/rpc for RPC services, or /etc/services for non-RPC services).

The socket_type for these services must be stream, and the protocol must be tcp.

Following is a sample TCPMUX service configuration:

service myorg_server {

disable

= no

type

= TCPMUX

socket_type

= stream

protocol

= tcp

wait

= no

user

= root

server

= /usr/etc/my_server_exec

}

Besides a service entry for each service that can be accessed via the TCPMUX well-known port, a service entry for TCPMUX itself must also be included in the xinetd configuration. Consider the following sample:

service tcpmux {

type

= INTERNAL

id

= tcpmux

socket_type

= stream

protocol

= tcp

user

= root

wait

= no

}

 

NOTES

1.

The following service attributes cannot be changed on reconfiguration: socket_type, wait, protocol, type.

2.

When the attributes only_from and no_access are not specified for a service (either directly or via defaults) the address check is considered successful (i.e. access will not be denied).

3.

The address check is based on the IP address of the remote host and not on its domain address. We do this so that we can avoid remote name lookups which may take a long time (since xinetd is single-threaded, a name lookup will prevent the daemon from accepting any other requests until the lookup is resolved). The down side of this scheme is that if the IP address of a remote host changes, then access to that host may be denied until xinetd is reconfigured. Whether access is actually denied or not will depend on whether the new host IP address is among those allowed access. For example, if the IP address of a host changes from 1.2.3.4 to 1.2.3.5 and only_from is specified as 1.2.3.0 then access will not be denied.

4.

If the USERID log option is specified and the remote host either does not run an identification server or the server sends back a bad reply, access will not be denied unless the IDONLY service flag is used.

5.

Interception works by forking a process which acts as a filter between the remote host(s) and the local server. This obviously has a performance impact so it is up to you to make the compromise between security and performance for each service. The following tables show the overhead of interception. The first table shows the time overhead-per-datagram for a UDP-based service using various datagram sizes. For TCP-based services we measured the bandwidth reduction because of interception while sending a certain amount of data from client to server (the time overhead should the same as for UDP-based services but it is "paid" only by the first packet of a continuous data transmission). The amount of data is given in the table as system_callsxdata_sent_per_call, i.e. each send(2) system call transferred so many bytes of data. The bandwidth reduction is given in terms of bytes per second and as a percentage of the bandwidth when interception is not performed. All measurements were done on a SparcStation IPC running SunOS 4.1.

Datagram size (bytes)

Latency (msec)

---------------------

--------------

64

1.19

256

1.51

1024

1.51

4096

3.58

Bytes sent

Bandwidth reduction

----------

-------------------

10000x64

941 (1.2%)

10000x256

4,231 (1.8%)

10000x1024

319,300 (39.5%)

10000x4096

824,461 (62.1%)

 

EXAMPLE

# # Sample configuration file for xinetd # defaults {

log_type

= FILE /var/log/servicelog

log_on_success

= PID

log_on_failure

= HOST

only_from

= 128.138.193.0 128.138.204.0

only_from

= 128.138.252.1

instances

= 10

disabled

= rstatd

} # # Note 1: the protocol attribute is not required # Note 2: the instances attribute overrides the default # service login {

socket_type

= stream

protocol

= tcp

wait

= no

user

= root

server

= /usr/etc/in.rlogind

instances

= UNLIMITED

} # # Note 1: the instances attribute overrides the default # Note 2: the log_on_success flags are augmented # service shell {

socket_type

= stream

wait

= no

user

= root

instances

= UNLIMITED

server

= /usr/etc/in.rshd

log_on_success

+= HOST

} service ftp {

socket_type

= stream

wait

= no

nice

= 10

user

= root

server

= /usr/etc/in.ftpd

server_args

= -l

instances

= 4

log_on_success

+= DURATION HOST USERID

access_times

= 2:00-9:00 12:00-24:00

} # Limit telnet sessions to 8 Mbytes of memory and a total # 20 CPU seconds for child processes. service telnet {

socket_type

= stream

wait

= no

nice

= 10

user

= root

server

= /usr/etc/in.telnetd

rlimit_as

= 8M

rlimit_cpu

= 20

} # # This entry and the next one specify internal services. Since # this is the same service using a different socket type, the # id attribute is used to uniquely identify each entry # service echo {

id

= echo-stream

type

= INTERNAL

socket_type

= stream

user

= root

wait

= no

} service echo {

id

= echo-dgram

type

= INTERNAL

socket_type

= dgram

user

= root

wait

= no

} # # Sample RPC service # service rstatd {

type

= RPC

socket_type

= dgram

protocol

= udp

server

= /usr/etc/rpc.rstatd

wait

= yes

user

= root

rpc_version

= 2-4

env

= LD_LIBRARY_PATH=/etc/securelib

} # # Sample unlisted service # service unlisted {

type

= UNLISTED

socket_type

= stream

protocol

= tcp

wait

= no

server

= /home/user/some_server

port

= 20020

}

 

SEE ALSO

xinetd(1L),

xinetd.log(5)

Postel J., Echo Protocol, RFC 862, May 1983

Postel J., Discard Protocol, RFC 863, May 1983

Postel J., Character Generator Protocol, RFC 864, May 1983

Postel J., Daytime Protocol, RFC 867, May 1983

Postel J., Harrenstien K., Time Protocol, RFC 868, May 1983

M. Lottor, TCP Port Service Multiplexer (TCPMUX), RFC 1078 Nov 1988

StJohns M., Identification Protocol, RFC 1413, February 1993  

BUGS

If the INTERCEPT flag is not used, access control on the address of the remote host is not performed when wait is yes and socket_type is stream.

The NOLIBWRAP flag is automatically turned on for RPC services whose socket_type is stream because xinetd cannot determine the address of the remote host.

If the INTERCEPT flag is not used, access control on the address of the remote host for services where wait is yes and socket_type is dgram is performed only on the first packet. The server may then accept packets from hosts not in the access control list. This can happen with RPC services.

There is no way to put a <FONT SIZE="-1">SPACE</FONT> in an environment variable.

When wait is yes and socket_type is stream, the socket passed to the server can only accept connections.

The INTERCEPT flag is not supported for internal services or multi-threaded services.

xpdfrc

NAME

xpdfrc - configuration file for Xpdf tools (version 3.00)  

DESCRIPTION

All of the Xpdf tools read a single configuration file. If you have a .xpdfrc file in your home directory, it will be read. Otherwise, a system-wide configuration file will be read from /etc/xpdfrc, if it exists. (This is its default location; depending on build options, it may be placed elsewhere.) On Win32 systems, the xpdfrc file should be placed in the same directory as the executables.

The xpdfrc file consists of a series of configuration options, one per line. Blank lines and lines starting with a `#` (comments) are ignored.

The following sections list all of the configuration options, sorted into functional groups. There is an examples section at the end.  

INCLUDE FILES

include config-file

Includes the specified config file. The effect of this is equivalent to inserting the contents of config-file directly into the parent config file in place of the include command. Config files can be nested arbitrarily deep.

 

CHARACTER MAPPING

nameToUnicode map-file

Specifies a file with the mapping from character names to Unicode. This is used to handle PDF fonts that have valid encodings but no ToUnicode entry. Each line of a nameToUnicode file looks like this:

hex-string name

The hex-string is the Unicode (UCS-2) character index, and name is the corresponding character name. Multiple nameToUnicode files can be used; if a character name is given more than once, the code in the last specified file is used. There is a built-in default nameToUnicode table with all of Adobe`s standard character names.

cidToUnicode registry-ordering map-file

Specifies the file with the mapping from character collection to Unicode. Each line of a cidToUnicode file represents one character:

hex-string

The hex-string is the Unicode (UCS-2) index for that character. The first line maps CID 0, the second line CID 1, etc. File size is determined by size of the character collection. Only one file is allowed per character collection; the last specified file is used. There are no built-in cidToUnicode mappings.

unicodeToUnicode font-name-substring map-file

This is used to work around PDF fonts which have incorrect Unicode information. It specifies a file which maps from the given (incorrect) Unicode indexes to the correct ones. The mapping will be used for any font whose name contains font-name-substring. Each line of a unicodeToUnicode file represents one Unicode character:

in-hex out-hex1 out-hex2 ...

The in-hex field is an input (incorrect) Unicode index, and the rest of the fields are one or more output (correct) Unicode indexes. Each occurrence of in-hex will be converted to the specified output sequence.

unicodeMap encoding-name map-file

Specifies the file with mapping from Unicode to encoding-name. These encodings are used for X display fonts and text output (see below). Each line of a unicodeMap file represents a range of one or more Unicode characters which maps linearly to a range in the output encoding:

in-start-hex in-end-hex out-start-hex

Entries for single characters can be abbreviated to:

in-hex out-hex

The in-start-hex and in-end-hex fields (or the single in-hex field) specify the Unicode range. The out-start-hex field (or the out-hex field) specifies the start of the output encoding range. The length of the out-start-hex (or out-hex) string determines the length of the output characters (e.g., UTF-8 uses different numbers of bytes to represent characters in different ranges). Entries must be given in increasing Unicode order. Only one file is allowed per encoding; the last specified file is used. The Latin1, ASCII7, Symbol, ZapfDingbats, UTF-8, and UCS-2 encodings are predefined.

cMapDir registry-ordering dir

Specifies a search directory, dir, for CMaps for the registry-ordering character collection. There can be multiple directories for a particular collection. There are no default CMap directories.

toUnicodeDir dir

Specifies a search directory, dir, for ToUnicode CMaps. There can be multiple ToUnicode directories. There are no default ToUnicode directories.

 

DISPLAY FONTS

displayFontT1 PDF-font-name T1-file

Maps a PDF font, PDF-font-name, to a Type 1 font for display. The Type 1 font file, T1-file, should be a standard .pfa or .pfb file.

displayFontTT PDF-font-name TT-file

Maps a PDF font, PDF-font-name, to a TrueType font for display. The TrueType font file, TT-file, should be a standard .ttf file.

displayNamedCIDFontT1 PDF-font-name T1-file

Maps a specific PDF CID (16-bit) font, PDF-font-name, to a CID font (16-bit PostScript font), for display. There are no default CID font mappings.

displayCIDFontT1 registry-ordering T1-file

Maps the registry-ordering character collection to a CID font (16-bit PostScript font), for display. This mapping is used if the font name doesn`t match any of the fonts declared with displayNamedCIDFont* commands. There are no default CID font mappings.

displayNamedCIDFontTT PDF-font-name TT-file

Maps a specific PDF CID (16-bit) font, PDF-font-name, to a (16-bit) TrueType font, for display. There are no default CID font mappings.

displayCIDFontTT registry-ordering TT-file

Maps the registry-ordering character collection to a (16-bit) TrueType font, for display. This mapping is used if the font name doesn`t match any of the fonts declared with displayNamedCIDFont* commands. There are no default CID font mappings.

fontDir dir

Specifies a search directory for external font files. There can be multiple fontDir directories. If a PDF file uses a font but doesn`t embed it, these directories will be searched for a matching font file. These fonts are used by both xpdf (for display) and pdftops (for embedding in the generated PostScript). Type 1 fonts must have a suffix of ".pfa", ".pfb", ".ps", or no suffix at all. TrueType fonts must have a ".ttf" suffix. Other files in these directories will be ignored. There are no default fontDir directories.

 

POSTSCRIPT CONTROL

psPaperSize width(pts) height(pts)

Sets the paper size for PostScript output. The width and height parameters give the paper size in PostScript points.

psPaperSize letter | legal | A4 | A3 | match

Sets the paper size for PostScript output to a standard size. The default paper size is set when xpdf and pdftops are built, typically to "letter" or "A4". This can also be set to "match", which will set the paper size to match the size specified in the PDF file.

psImageableArea llx lly urx ury

Sets the imageable area for PostScript output. The four integers are the coordinates of the lower-left and upper-right corners of the imageable region, specified in points. This defaults to the full paper size; the psPaperSize option will reset the imageable area coordinates.

psCrop yes | no

If set to "yes", PostScript output is cropped to the CropBox specified in the PDF file; otherwise no cropping is done. This defaults to "yes".

psExpandSmaller yes | no

If set to "yes", PDF pages smaller than the PostScript imageable area are expanded to fill the imageable area. Otherwise, no scalling is done on smaller pages. This defaults to "no".

psShrinkLarger yes | no

If set to yes, PDF pages larger than the PostScript imageable area are shrunk to fit the imageable area. Otherwise, no scaling is done on larger pages. This defaults to "yes".

psCenter yes | no

If set to yes, PDF pages smaller than the PostScript imageable area (after any scaling) are centered in the imageable area. Otherwise, they are aligned at the lower-left corner of the imageable area. This defaults to "yes".

psDuplex yes | no

If set to "yes", the generated PostScript will set the "Duplex" pagedevice entry. This tells duplex-capable printers to enable duplexing. This defaults to "no".

psLevel level1 | level1sep | level2 | level2sep | level3 | level3Sep

Sets the PostScript level to generate. This defaults to "level2".

psFont PDF-font-name PS-font-name

When the PDF-font-name font is used in a PDF file, it will be translated to the PostScript font PS-font-name, which is assumed to be resident in the printer. Typically, PDF-font-name and PS-font-name are the same. By default, only the Base-14 fonts are assumed to be resident.

psNamedFont16 PDF-font-name wMode PS-font-name encoding

When the 16-bit font PDF-font-name is used in a PDF file with the wMode writing mode and is not embedded, the PS-font-name font is substituted for it. The writing mode must be either `H` for horizontal or `V` for vertical. The PS-font-name font is assumed to be resident in the printer and to use the specified encoding (which must have been defined with the unicodeMap command).

psFont16 registry-ordering wMode PS-font-name encoding

When a 16-bit font using the registry-ordering character collection and wMode writing mode is not embedded and does not match any of the fonts declared in psNamedFont16 commands, the PS-font-name font is substituted for it. The writing mode must be either `H` for horizontal or `V` for vertical. The PS-font-name font is assumed to be resident in the printer and to use the specified writing mode and encoding (which must have been defined with the unicodeMap command).

psEmbedType1Fonts yes | no

If set to "no", prevents embedding of Type 1 fonts in generated PostScript. This defaults to "yes".

psEmbedTrueTypeFonts yes | no

If set to "no", prevents embedding of TrueType fonts in generated PostScript. This defaults to "yes".

psEmbedCIDTrueTypeFonts yes | no

If set to "no", prevents embedding of CID TrueType fonts in generated PostScript. For Level 3 PostScript, this generates a CID font, for lower levels it generates a non-CID composite font.

psEmbedCIDPostScriptFonts yes | no

If set to "no", prevents embedding of CID PostScript fonts in generated PostScript. For Level 3 PostScript, this generates a CID font, for lower levels it generates a non-CID composite font.

psOPI yes | no

If set to "yes", generates PostScript OPI comments for all images and forms which have OPI information. This option is only available if the Xpdf tools were compiled with OPI support. This defaults to "no".

psASCIIHex yes | no

If set to "yes", the ASCIIHexEncode filter will be used instead of ASCII85Encode for binary data. This defaults to "no".

psFile file-or-command

Sets the default PostScript file or print command for xpdf. Commands start with a `|` character; anything else is a file. If the file name or command contains spaces it must be quoted. This defaults to unset, which tells xpdf to generate a name of the form <file>.ps for a PDF file <file>.pdf.

fontDir dir

See the description above, in the DISPLAY FONTS section.

 

TEXT CONTROL

textEncoding encoding-name

Sets the encoding to use for text output. (This can be overridden with the "-enc" switch on the command line.) The encoding-name must be defined with the unicodeMap command (see above). This defaults to "Latin1".

textEOL unix | dos | mac

Sets the end-of-line convention to use for text output. The options are:

unix = LF dos = CR+LF mac = CR

(This can be overridden with the "-eol" switch on the command line.) The default value is based on the OS where xpdf and pdftotext were built.

textPageBreaks yes | no

If set to "yes", text extraction will insert page breaks (form feed characters) between pages. This defaults to "yes".

textKeepTinyChars yes | no

If set to "yes", text extraction will keep all characters. If set to "no", text extraction will discard tiny (smaller than 3 point) characters after the first 50000 per page, avoiding extremely slow run times for PDF files that use special fonts to do shading or cross-hatching. This defaults to "no".

 

MISCELLANEOUS SETTINGS

initialZoom percentage | page | width

Sets the initial zoom factor. A number specifies a zoom percentage, where 100 means 72 dpi. You may also specify `page`, to fit the page to the window size, or `width`, to fit the page width to the window width.

enableT1lib yes | no

Enables or disables use of t1lib (a Type 1 font rasterizer). This is only relevant if the Xpdf tools were built with t1lib support. ("enableT1lib" replaces the old "t1libControl" option.) This option defaults to "yes".

enableFreeType yes | no

Enables or disables use of FreeType (a TrueType / Type 1 font rasterizer). This is only relevant if the Xpdf tools were built with FreeType support. ("enableFreeType" replaces the old "freetypeControl" option.) This option defaults to "yes".

antialias yes | no

Enables or disables font anti-aliasing in the PDF rasterizer. This option affects all font rasterizers. ("antialias" replaces the anti-aliasing control provided by the old "t1libControl" and "freetypeControl" options.) This default to "yes".

urlCommand command

Sets the command executed when you click on a URL link. The string "%s" will be replaced with the URL. (See the example below.) This has no default value.

movieCommand command

Sets the command executed when you click on a movie annotation. The string "%s" will be replaced with the movie file name. This has no default value.

mapNumericCharNames yes | no

If set to "yes", the Xpdf tools will attempt to map various numeric character names sometimes used in font subsets. In some cases this leads to usable text, and in other cases it leads to gibberish -- there is no way for Xpdf to tell. This defaults to "yes".

printCommands yes | no

If set to "yes", drawing commands are printed as they`re executed (useful for debugging). This defaults to "no".

errQuiet yes | no

If set to "yes", this suppresses all error and warning messages from all of the Xpdf tools. This defaults to "no".

 

EXAMPLES

The following is a sample xpdfrc file.

# from the Thai support package nameToUnicode /usr/local/share/xpdf/Thai.nameToUnicode # from the Japanese support package cidToUnicode Adobe-Japan1 /usr/local/share/xpdf/Adobe-Japan1.cidToUnicode unicodeMap JISX0208 /usr/local/share/xpdf/JISX0208.unicodeMap cMapDir Adobe-Japan1 /usr/local/share/xpdf/cmap/Adobe-Japan1 # use the Base-14 Type 1 fonts from ghostscript # (note that this overrides the displayFontX command above) displayFontT1 Times-Roman /usr/local/share/ghostscript/fonts/n021003l.pfb displayFontT1 Times-Italic /usr/local/share/ghostscript/fonts/n021023l.pfb displayFontT1 Times-Bold /usr/local/share/ghostscript/fonts/n021004l.pfb displayFontT1 Times-BoldItalic /usr/local/share/ghostscript/fonts/n021024l.pfb displayFontT1 Helvetica /usr/local/share/ghostscript/fonts/n019003l.pfb displayFontT1 Helvetica-Oblique /usr/local/share/ghostscript/fonts/n019023l.pfb displayFontT1 Helvetica-Bold /usr/local/share/ghostscript/fonts/n019004l.pfb displayFontT1 Helvetica-BoldOblique /usr/local/share/ghostscript/fonts/n019024l.pfb displayFontT1 Courier /usr/local/share/ghostscript/fonts/n022003l.pfb displayFontT1 Courier-Oblique /usr/local/share/ghostscript/fonts/n022023l.pfb displayFontT1 Courier-Bold /usr/local/share/ghostscript/fonts/n022004l.pfb displayFontT1 Courier-BoldOblique /usr/local/share/ghostscript/fonts/n022024l.pfb displayFontT1 Symbol /usr/local/share/ghostscript/fonts/s050000l.pfb displayFontT1 ZapfDingbats /usr/local/share/ghostscript/fonts/d050000l.pfb # use the Bakoma Type 1 fonts # (this assumes they happen to be installed in /usr/local/fonts/bakoma) fontDir /usr/local/fonts/bakoma # set some PostScript options psPaperSize letter psDuplex no psLevel level2 psEmbedType1Fonts yes psEmbedTrueTypeFonts yes psFile "| lpr -Pprinter5" # assume that the PostScript printer has the Univers and # Univers-Bold fonts psFont Univers Univers psFont Univers-Bold Univers-Bold # set the text output options textEncoding UTF-8 textEOL unix # misc options t1libControl low freetypeControl low urlCommand "netscape -remote `openURL(%s)`"

 

FILES

/etc/xpdfrc

This is the default location for the system-wide configuration file. Depending on build options, it may be placed elsewhere.

$HOME/.xpdfrc

This is the user`s configuration file. If it exists, it will be read in place of the system-wide file.

 

AUTHOR

The Xpdf software and documentation are copyright 1996-2004 Glyph & Cog, LLC.  

SEE ALSO

xpdf(1), pdftops(1), pdftotext(1), pdfinfo(1), pdftoppm(1), pdfimages(1)
http://www.foolabs.com/xpdf/

XF86Config.5x.php

NAME

XF86Config - Configuration File for XFree86  

DESCRIPTION

XFree86 uses a configuration file called XF86Config for its initial setup. This configuration file is searched for in the following places when the server is started as a normal user:

/etc/X11/<cmdline> /usr/X11R6/etc/X11/<cmdline> /etc/X11/$XF86CONFIG /usr/X11R6/etc/X11/$XF86CONFIG /etc/X11/XF86Config-4 /etc/X11/XF86Config /etc/XF86Config /usr/X11R6/etc/X11/XF86Config.<hostname> /usr/X11R6/etc/X11/XF86Config-4 /usr/X11R6/etc/X11/XF86Config /usr/X11R6/lib/X11/XF86Config.<hostname> /usr/X11R6/lib/X11/XF86Config-4 /usr/X11R6/lib/X11/XF86Config

where <cmdline> is a relative path (with no ".." components) specified with the -xf86config command line option, $XF86CONFIG is the relative path (with no ".." components) specified by that environment variable, and <hostname> is the machine`s hostname as reported by gethostname(3).

When the X server is started by the "root" user, the config file search locations are as follows:

<cmdline> /etc/X11/<cmdline> /usr/X11R6/etc/X11/<cmdline> $XF86CONFIG /etc/X11/$XF86CONFIG /usr/X11R6/etc/X11/$XF86CONFIG $HOME/XF86Config /etc/X11/XF86Config-4 /etc/X11/XF86Config /etc/XF86Config /usr/X11R6/etc/X11/XF86Config.<hostname> /usr/X11R6/etc/X11/XF86Config-4 /usr/X11R6/etc/X11/XF86Config /usr/X11R6/lib/X11/XF86Config.<hostname> /usr/X11R6/lib/X11/XF86Config-4 /usr/X11R6/lib/X11/XF86Config

where <cmdline> is the path specified with the -xf86config command line option (which may be absolute or relative), $XF86CONFIG is the path specified by that environment variable (absolute or relative), $HOME is the path specified by that environment variable (usually the home directory), and <hostname> is the machine`s hostname as reported by gethostname(3).

The XF86Config file is composed of a number of sections which may be present in any order. Each section has the form:

Section N`34`SectionNameN`34` SectionEntry ... EndSection

The section names are:

Files File pathnames ServerFlags Server flags Module Dynamic module loading InputDevice Input device description Device Graphics device description VideoAdaptor Xv video adaptor description Monitor Monitor description Modes Video modes descriptions Screen Screen configuration ServerLayout Overall layout DRI DRI-specific configuration Vendor Vendor-specific configuration

The following obsolete section names are still recognised for compatibility purposes. In new config files, the InputDevice section should be used instead.

Keyboard Keyboard configuration Pointer Pointer/mouse configuration

The old XInput section is no longer recognised.

The ServerLayout sections are at the highest level. They bind together the input and output devices that will be used in a session. The input devices are described in the InputDevice sections. Output devices usually consist of multiple independent components (e.g., and graphics board and a monitor). These multiple components are bound together in the Screen sections, and it is these that are referenced by the ServerLayout section. Each Screen section binds together a graphics board and a monitor. The graphics boards are described in the Device sections, and the monitors are described in the Monitor sections.

Config file keywords are case-insensitive, and "_" characters are ignored. Most strings (including Option names) are also case-insensitive, and insensitive to white space and "_" characters.

Each config file entry usually takes up a single line in the file. They consist of a keyword, which is possibly followed by one or more arguments, with the number and types of the arguments depending on the keyword. The argument types are:

Integer an integer number in decimal, hex or octal Real a floating point number String a string enclosed in double quote marks (N`34`)

Note: hex integer values must be prefixed with "0x", and octal values with "0".

A special keyword called Option may be used to provide free-form data to various components of the server. The Option keyword takes either one or two string arguments. The first is the option name, and the optional second argument is the option value. Some commonly used option value types include:

Integer an integer number in decimal, hex or octal Real a floating point number String a sequence of characters Boolean a boolean value (see below) Frequency a frequency value (see below)

Note that all Option values, not just strings, must be enclosed in quotes.

Boolean options may optionally have a value specified. When no value is specified, the option`s value is TRUE. The following boolean option values are recognised as TRUE:

1, on, true, yes

and the following boolean option values are recognised as FALSE:

0, off, false, no

If an option name is prefixed with N`34`NoN`34`, then the option value is negated.

Example: the following option entries are equivalent:

Option N`34`AccelN`34` N`34`OffN`34` Option N`34`NoAccelN`34` Option N`34`NoAccelN`34` N`34`OnN`34` Option N`34`AccelN`34` N`34`falseN`34` Option N`34`AccelN`34` N`34`noN`34`

Frequency option values consist of a real number that is optionally followed by one of the following frequency units:

Hz, k, kHz, M, MHz

When the unit name is omitted, the correct units will be determined from the value and the expectations of the appropriate range of the value. It is recommended that the units always be specified when using frequency option values to avoid any errors in determining the value.  

FILES SECTION

The Files section is used to specify some path names required by the server. Some of these paths can also be set from the command line (see Xserver(1) and XFree86(1)). The command line settings override the values specified in the config file. The entries that can appear in this section are:

FontPath N`34`pathN`34`

sets the search path for fonts. This path is a comma separated list of font path elements which the X server searches for font databases. Multiple FontPath entries may be specified, and they will be concatenated to build up the fontpath used by the server. Font path elements may be either absolute directory paths, or a font server identifier. Font server identifiers have the form:

<trans>/<hostname>:<port-number>

where <trans> is the transport type to use to connect to the font server (e.g., unix for UNIX-domain sockets or tcp for a TCP/IP connection), <hostname> is the hostname of the machine running the font server, and <port-number> is the port number that the font server is listening on (usually 7100).

When this entry is not specified in the config file, the server falls back to the compiled-in default font path, which contains the following font path elements:

/usr/X11R6/lib/X11/fonts/misc/ /usr/X11R6/lib/X11/fonts/Speedo/ /usr/X11R6/lib/X11/fonts/Type1/ /usr/X11R6/lib/X11/fonts/CID/ /usr/X11R6/lib/X11/fonts/75dpi/ /usr/X11R6/lib/X11/fonts/100dpi/

The recommended font path contains the following font path elements:

/usr/X11R6/lib/X11/fonts/local/ /usr/X11R6/lib/X11/fonts/misc/ /usr/X11R6/lib/X11/fonts/75dpi/:unscaled /usr/X11R6/lib/X11/fonts/100dpi/:unscaled /usr/X11R6/lib/X11/fonts/Type1/ /usr/X11R6/lib/X11/fonts/CID/ /usr/X11R6/lib/X11/fonts/Speedo/ /usr/X11R6/lib/X11/fonts/75dpi/ /usr/X11R6/lib/X11/fonts/100dpi/

Font path elements that are found to be invalid are removed from the font path when the server starts up.

RGBPath N`34`pathN`34`

sets the path name for the RGB color database. When this entry is not specified in the config file, the server falls back to the compiled-in default RGB path, which is:

/usr/X11R6/lib/X11/rgb

Note that an implicit .txt is added to this path if the server was compiled to use text rather than binary format RGB color databases.

ModulePath N`34`pathN`34`

sets the search path for loadable X server modules. This path is a comma separated list of directories which the X server searches for loadable modules loading in the order specified. Multiple ModulePath entries may be specified, and they will be concatenated to build the module search path used by the server.

 

SERVERFLAGS SECTION

The ServerFlags section is used to specify some global X server options. All of the entries in this section are Options, although for compatibility purposes some of the old style entries are still recognised. Those old style entries are not documented here, and using them is discouraged.

Options specified in this section (with the exception of the N`34`DefaultServerLayoutN`34` Option) may be overridden by Options specified in the active ServerLayout section. Options with command line equivalents are overridden when their command line equivalent is used. The options recognised by this section are:

Option N`34`DefaultServerLayoutN`34` N`34`layout-idN`34`

This specifies the default ServerLayout section to use in the absence of the -layout command line option.

Option N`34`NoTrapSignalsN`34` N`34`booleanN`34`

This prevents the X server from trapping a range of unexpected fatal signals and exiting cleanly. Instead, the X server will die and drop core where the fault occurred. The default behaviour is for the X server to exit cleanly, but still drop a core file. In general you never want to use this option unless you are debugging an X server problem and know how to deal with the consequences.

Option N`34`DontVTSwitchN`34` N`34`booleanN`34`

This disallows the use of the Ctrl+Alt+Fn sequence (where Fn refers to one of the numbered function keys). That sequence is normally used to switch to another oqvirtual terminal)cq on operating systems that have this feature. When this option is enabled, that key sequence has no special meaning and is passed to clients. Default: off.

Option N`34`DontZapN`34` N`34`booleanN`34`

This disallows the use of the Ctrl+Alt+Backspace sequence. That sequence is normally used to terminate the X server. When this option is enabled, that key sequence has no special meaning and is passed to clients. Default: off.

Option N`34`DontZoomN`34` N`34`booleanN`34`

This disallows the use of the Ctrl+Alt+Keypad-Plus and Ctrl+Alt+Keypad-Minus sequences. These sequences allows you to switch between video modes. When this option is enabled, those key sequences have no special meaning and are passed to clients. Default: off.

Option N`34`DisableVidModeExtensionN`34` N`34`booleanN`34`

This disables the parts of the VidMode extension used by the xvidtune client that can be used to change the video modes. Default: the VidMode extension is enabled.

Option N`34`AllowNonLocalXvidtuneN`34` N`34`booleanN`34`

This allows the xvidtune client (and other clients that use the VidMode extension) to connect from another host. Default: off.

Option N`34`DisableModInDevN`34` N`34`booleanN`34`

This disables the parts of the XFree86-Misc extension that can be used to modify the input device settings dynamically. Default: that functionality is enabled.

Option N`34`AllowNonLocalModInDevN`34` N`34`booleanN`34`

This allows a client to connect from another host and change keyboard and mouse settings in the running server. Default: off.

Option N`34`AllowMouseOpenFailN`34` N`34`booleanN`34`

This allows the server to start up even if the mouse device can`t be opened/initialised. Default: false.

Option N`34`VTInitN`34` N`34`commandN`34`

Runs command after the VT used by the server has been opened. The command string is passed to "/bin/sh -c", and is run with the real user`s id with stdin and stdout set to the VT. The purpose of this option is to allow system dependent VT initialisation commands to be run. This option should rarely be needed. Default: not set.

Option N`34`VTSysReqN`34` N`34`booleanN`34`

enables the SYSV-style VT switch sequence for non-SYSV systems which support VT switching. This sequence is Alt-SysRq followed by a function key (Fn). This prevents the X server trapping the keys used for the default VT switch sequence, which means that clients can access them. Default: off.

Option N`34`XkbDisableN`34` N`34`booleanN`34`

disable/enable the XKEYBOARD extension. The -kb command line option overrides this config file option. Default: XKB is enabled.

Option N`34`BlankTimeN`34` N`34`timeN`34`

sets the inactivity timeout for the blanking phase of the screensaver. time is in minutes. This is equivalent to the Xserver`s `-s` flag, and the value can be changed at run-time with xset(1). Default: 10 minutes.

Option N`34`StandbyTimeN`34` N`34`timeN`34`

sets the inactivity timeout for the "standby" phase of DPMS mode. time is in minutes, and the value can be changed at run-time with xset(1). Default: 20 minutes. This is only suitable for VESA DPMS compatible monitors, and may not be supported by all video drivers. It is only enabled for screens that have the N`34`DPMSN`34` option set (see the MONITOR section below).

Option N`34`SuspendTimeN`34` N`34`timeN`34`

sets the inactivity timeout for the "suspend" phase of DPMS mode. time is in minutes, and the value can be changed at run-time with xset(1). Default: 30 minutes. This is only suitable for VESA DPMS compatible monitors, and may not be supported by all video drivers. It is only enabled for screens that have the N`34`DPMSN`34` option set (see the MONITOR section below).

Option N`34`OffTimeN`34` N`34`timeN`34`

sets the inactivity timeout for the "off" phase of DPMS mode. time is in minutes, and the value can be changed at run-time with xset(1). Default: 40 minutes. This is only suitable for VESA DPMS compatible monitors, and may not be supported by all video drivers. It is only enabled for screens that have the N`34`DPMSN`34` option set (see the MONITOR section below).

Option N`34`PixmapN`34` N`34`bppN`34`

This sets the pixmap format to use for depth 24. Allowed values for bpp are 24 and 32. Default: 32 unless driver constraints don`t allow this (which is rare). Note: some clients don`t behave well when this value is set to 24.

Option N`34`PC98N`34` N`34`booleanN`34`

Specify that the machine is a Japanese PC-98 machine. This should not be enabled for anything other than the Japanese-specific PC-98 architecture. Default: auto-detected.

Option N`34`NoPMN`34` N`34`booleanN`34`

Disables something to do with power management events. Default: PM enabled on platforms that support it.

Option N`34`XineramaN`34` N`34`booleanN`34`

enable or disable XINERAMA extension. Default is disabled.

Option N`34`AllowDeactivateGrabsN`34` N`34`booleanN`34`

This option enables the use of the Ctrl+Alt+Keypad-Divide key sequence to deactivate any active keyboard and mouse grabs. Default: off.

Option N`34`AllowClosedownGrabsN`34` N`34`booleanN`34`

This option enables the use of the Ctrl+Alt+Keypad-Multiply key sequence to kill clients with an active keyboard or mouse grab as well as killing any application that may have locked the server, normally using the XGrabServer(3x) Xlib function. Default: off.
Note that the options AllowDeactivateGrabs and AllowClosedownGrabs will allow users to remove the grab used by screen saver/locker programs. An API was written to such cases. If you enable this option, make sure your screen saver/locker is updated.

Option N`34`HandleSpecialKeysN`34` N`34`whenN`34`

This option controls when the server uses the builtin handler to process special key combinations (such as Ctrl+Alt+Backspace). Normally the XKEYBOARD extension keymaps will provide mappings for each of the special key combinations, so the builtin handler is not needed unless the XKEYBOARD extension is disabled. The value of when can be Always, Never, or WhenNeeded. Default: Use the builtin handler only if needed. The server will scan the keymap for a mapping to the Terminate action and, if found, use XKEYBOARD for processing actions, otherwise the builtin handler will be used.

 

MODULE SECTION

The Module section is used to specify which X server modules should be loaded. This section is ignored when the X server is built in static form. The types of modules normally loaded in this section are X server extension modules, and font rasteriser modules. Most other module types are loaded automatically when they are needed via other mechanisms.

Entries in this section may be in two forms. The first and most commonly used form is an entry that uses the Load keyword, as described here:

Load N`34`modulenameN`34`

This instructs the server to load the module called modulename. The module name given should be the module`s standard name, not the module file name. The standard name is case-sensitive, and does not include the "lib" prefix, or the ".a", ".o", or ".so" suffixes.

Example: the Type 1 font rasteriser can be loaded with the following entry:

Load N`34`type1N`34`

The second form of entry is a SubSection, with the subsection name being the module name, and the contents of the SubSection being Options that are passed to the module when it is loaded.

Example: the extmod module (which contains a miscellaneous group of server extensions) can be loaded, with the XFree86-DGA extension disabled by using the following entry:

SubSection N`34`extmodN`34` Option N`34`omit XFree86-DGAN`34` EndSubSection

Modules are searched for in each directory specified in the ModulePath search path, and in the drivers, input, extensions, fonts, and internal subdirectories of each of those directories. In addition to this, operating system specific subdirectories of all the above are searched first if they exist.

To see what font and extension modules are available, check the contents of the following directories:

/usr/X11R6/lib/modules/fonts /usr/X11R6/lib/modules/extensions

The "bitmap" font modules is loaded automatically. It is recommended that at very least the "extmod" extension module be loaded. If it isn`t some commonly used server extensions (like the SHAPE extension) will not be available.  

INPUTDEVICE SECTION

The config file may have multiple InputDevice sections. There will normally be at least two: one for the core (primary) keyboard, and one of the core pointer.

InputDevice sections have the following format:

Section N`34`InputDeviceN`34` Identifier N`34`nameN`34` Driver N`34`inputdriverN`34` options ... EndSection

The Identifier entry specifies the unique name for this input device. The Driver entry specifies the name of the driver to use for this input device. When using the loadable server, the input driver module N`34`inputdriverN`34` will be loaded for each active InputDevice section. An InputDevice section is considered active if it is referenced by an active ServerLayout section, or if it is referenced by the -keyboard or -pointer command line options. The most commonly used input drivers are "keyboard" and "mouse".

InputDevice sections recognise some driver-independent Options, which are described here. See the individual input driver manual pages for a description of the device-specific options.

Option N`34`CorePointerN`34`

When this is set, the input device is installed as the core (primary) pointer device. There must be exactly 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. This option is implicitly set when the obsolete Pointer section is used.

Option N`34`CoreKeyboardN`34`

When this is set, the input device is to be installed as the core (primary) keyboard device. There must be exactly one core keyboard. If this option is not set here, in the ServerLayout section, or from the -keyboard command line option, then the first input device that is capable of being used as a core keyboard will be selected as the core keyboard. This option is implicitly set when the obsolete Keyboard section is used.

Option N`34`AlwaysCoreN`34` N`34`booleanN`34`

Option N`34`SendCoreEventsN`34` N`34`booleanN`34`

Both of these options are equivalent, and when enabled cause the input device to always report core events. This can be used, for example, to allow an additional pointer device to generate core pointer events (like moving the cursor, etc).

Option N`34`HistorySizeN`34` N`34`numberN`34`

Sets the motion history size. Default: 0.

Option N`34`SendDragEventsN`34` N`34`booleanN`34`

???

 

DEVICE SECTION

The config file may have multiple Device sections. There must be at least one, for the video card being used.

Device sections have the following format:

Section N`34`DeviceN`34` Identifier N`34`nameN`34` Driver N`34`driverN`34` entries ... EndSection

The Identifier entry specifies the unique name for this graphics device. The Driver entry specifies the name of the driver to use for this graphics device. When using the loadable server, the driver module N`34`driverN`34` will be loaded for each active Device section. A Device section is considered active if it is referenced by an active Screen section.

Device sections recognise some driver-independent entries and Options, which are described here. Not all drivers make use of these driver-independent entries, and many of those that do don`t require them to be specified because the information is auto-detected. See the individual graphics driver manual pages for further information about this, and for a description of the device-specific options. Note that most of the Options listed here (but not the other entries) may be specified in the Screen section instead of here in the Device section.

BusID N`34`bus-idN`34`

This specifies the bus location of the graphics card. For PCI/AGP cards, the bus-id string has the form PCI:bus:device:function (e.g., "PCI:1:0:0" might be appropriate for an AGP card). This field is usually optional in single-head configurations when using the primary graphics card. In multi-head configurations, or when using a secondary graphics card in a single-head configuration, this entry is mandatory. Its main purpose is to make an unambiguous connection between the device section and the hardware it is representing. This information can usually be found by running the X server with the -scanpci command line option.

Screen number

This option is mandatory for cards where a single PCI entity can drive more than one display (i.e., multiple CRTCs sharing a single graphics accelerator and video memory). One Device section is required for each head, and this parameter determines which head each of the Device sections applies to. The legal values of number range from 0 to one less than the total number of heads per entity. Most drivers require that the primary screen (0) be present.

Chipset N`34`chipsetN`34`

This usually optional entry specifies the chipset used on the graphics board. In most cases this entry is not required because the drivers will probe the hardware to determine the chipset type. Don`t specify it unless the driver-specific documentation recommends that you do.

Ramdac N`34`ramdac-typeN`34`

This optional entry specifies the type of RAMDAC used on the graphics board. This is only used by a few of the drivers, and in most cases it is not required because the drivers will probe the hardware to determine the RAMDAC type where possible. Don`t specify it unless the driver-specific documentation recommends that you do.

DacSpeed speed

DacSpeed speed-8 speed-16 speed-24 speed-32

This optional entry specifies the RAMDAC speed rating (which is usually printed on the RAMDAC chip). The speed is in MHz. When one value is given, it applies to all framebuffer pixel sizes. When multiple values are give, they apply to the framebuffer pixel sizes 8, 16, 24 and 32 respectively. This is not used by many drivers, and only needs to be specified when the speed rating of the RAMDAC is different from the defaults built in to driver, or when the driver can`t auto-detect the correct defaults. Don`t specify it unless the driver-specific documentation recommends that you do.

Clocks clock ...

specifies the pixel that are on your graphics board. The clocks are in MHz, and may be specified as a floating point number. The value is stored internally to the nearest kHz. The ordering of the clocks is important. It must match the order in which they are selected on the graphics board. Multiple Clocks lines may be specified, and each is concatenated to form the list. Most drivers do not use this entry, and it is only required for some older boards with non-programmable clocks. Don`t specify this entry unless the driver-specific documentation explicitly recommends that you do.

ClockChip N`34`clockchip-typeN`34`

This optional entry is used to specify the clock chip type on graphics boards which have a programmable clock generator. Only a few X servers support programmable clock chips. For details, see the appropriate X server manual page.

VideoRam mem

This optional entry specifies the amount of video ram that is installed on the graphics board. This is measured in kBytes. In most cases this is not required because the X server probes the graphics board to determine this quantity. The driver-specific documentation should indicate when it might be needed.

BiosBase baseaddress

This optional entry specifies the base address of the video BIOS for the VGA board. This address is normally auto-detected, and should only be specified if the driver-specific documentation recommends it.

MemBase baseaddress

This optional entry specifies the memory base address of a graphics board`s linear frame buffer. This entry is not used by many drivers, and it should only be specified if the driver-specific documentation recommends it.

IOBase baseaddress

This optional entry specifies the IO base address. This entry is not used by many drivers, and it should only be specified if the driver-specific documentation recommends it.

ChipID id

This optional entry specifies a numerical ID representing the chip type. For PCI cards, it is usually the device ID. This can be used to override the auto-detection, but that should only be done when the driver-specific documentation recommends it.

ChipRev rev

This optional entry specifies the chip revision number. This can be used to override the auto-detection, but that should only be done when the driver-specific documentation recommends it.

TextClockFreq freq

This optional entry specifies the pixel clock frequency that is used for the regular text mode. The frequency is specified in MHz. This is rarely used.

Options

Option flags may be specified in the Device sections. These include driver-specific options and driver-independent options. The former are described in the driver-specific documentation. Some of the latter are described below in the section about the Screen section, and they may also be included here.

 

VIDEOADAPTOR SECTION

Nobody wants to say how this works. Maybe nobody knows ...

 

MONITOR SECTION

The config file may have multiple Monitor sections. There must be at least one, for the monitor being used.

Monitor sections have the following format:

Section N`34`MonitorN`34` Identifier N`34`nameN`34` entries ... EndSection

The Identifier entry specifies the unique name for this monitor. The Monitor section provides information about the specifications of the monitor, monitor-specific Options, and information about the video modes to use with the monitor. Specifying video modes is optional because the server now has a built-in list of VESA standard modes. When modes are specified explicitly in the Monitor section (with the Modes, ModeLine, or UseModes keywords), built-in modes with the same names are not included. Built-in modes with different names are, however, still implicitly included.

The entries that may be used in Monitor sections are described below.

VendorName N`34`vendorN`34`

This optional entry specifies the monitor`s manufacturer.

ModelName N`34`modelN`34`

This optional entry specifies the monitor`s model.

HorizSync horizsync-range

gives the range(s) of horizontal sync frequencies supported by the monitor. horizsync-range may be a comma separated list of either discrete values or ranges of values. A range of values is two values separated by a dash. By default the values are in units of kHz. They may be specified in MHz or Hz if MHz or Hz is added to the end of the line. The data given here is used by the X server to determine if video modes are within the specifications of the monitor. This information should be available in the monitor`s handbook. If this entry is omitted, a default range of 28-33kHz is used.

VertRefresh vertrefresh-range

gives the range(s) of vertical refresh frequencies supported by the monitor. vertrefresh-range may be a comma separated list of either discrete values or ranges of values. A range of values is two values separated by a dash. By default the values are in units of Hz. They may be specified in MHz or kHz if MHz or kHz is added to the end of the line. The data given here is used by the X server to determine if video modes are within the specifications of the monitor. This information should be available in the monitor`s handbook. If this entry is omitted, a default range of 43-72Hz is used.

DisplaySize width height

This optional entry gives the width and height, in millimetres, of the picture area of the monitor. If given this is used to calculate the horizontal and vertical pitch (DPI) of the screen.

Gamma gamma-value

Gamma red-gamma green-gamma blue-gamma

This is an optional entry that can be used to specify the gamma correction for the monitor. It may be specified as either a single value or as three separate RGB values. The values should be in the range 0.1 to 10.0, and the default is 1.0. Not all drivers are capable of using this information.

UseModes N`34`modesection-idN`34`

Include the set of modes listed in the Modes section called modesection-id. This make all of the modes defined in that section available for use by this monitor.

Mode name

This is an optional multi-line entry that can be used to provide definitions for video modes for the monitor. In most cases this isn`t necessary because the built-in set of VESA standard modes will be sufficient. The Mode keyword indicates the start of a multi-line video mode description. The mode description is terminated with the EndMode keyword. The mode description consists of the following entries:

DotClock clock

is the dot (pixel) clock rate to be used for the mode.

HTimings hdisp hsyncstart hsyncend htotal

specifies the horizontal timings for the mode.

VTimings vdisp vsyncstart vsyncend vtotal

specifies the vertical timings for the mode.

Flags N`34`flagN`34` ...

specifies an optional set of mode flags, each of which is a separate string in double quotes. N`34`InterlaceN`34` indicates that the mode is interlaced. N`34`DoubleScanN`34` indicates a mode where each scanline is doubled. N`34`+HSyncN`34` and N`34`-HSyncN`34` can be used to select the polarity of the HSync signal. N`34`+VSyncN`34` and N`34`-VSyncN`34` can be used to select the polarity of the VSync signal. N`34`CompositeN`34` can be used to specify composite sync on hardware where this is supported. Additionally, on some hardware, N`34`+CSyncN`34` and N`34`-CSyncN`34` may be used to select the composite sync polarity.

HSkew hskew

specifies the number of pixels (towards the right edge of the screen) by which the display enable signal is to be skewed. Not all drivers use this information. This option might become necessary to override the default value supplied by the server (if any). "Roving" horizontal lines indicate this value needs to be increased. If the last few pixels on a scan line appear on the left of the screen, this value should be decreased.

VScan vscan

specifies the number of times each scanline is painted on the screen. Not all drivers use this information. Values less than 1 are treated as 1, which is the default. Generally, the N`34`DoubleScanN`34` Flag mentioned above doubles this value.

ModeLine N`34`nameN`34` mode-description

This entry is a more compact version of the Mode entry, and it also can be used to specify video modes for the monitor. is a single line format for specifying video modes. In most cases this isn`t necessary because the built-in set of VESA standard modes will be sufficient.

The mode-description is in four sections, the first three of which are mandatory. The first is the dot (pixel) clock. This is a single number specifying the pixel clock rate for the mode in MHz. The second section is a list of four numbers specifying the horizontal timings. These numbers are the hdisp, hsyncstart, hsyncend, and htotal values. The third section is a list of four numbers specifying the vertical timings. These numbers are the vdisp, vsyncstart, vsyncend, and vtotal values. The final section is a list of flags specifying other characteristics of the mode. Interlace indicates that the mode is interlaced. DoubleScan indicates a mode where each scanline is doubled. +HSync and -HSync can be used to select the polarity of the HSync signal. +VSync and -VSync can be used to select the polarity of the VSync signal. Composite can be used to specify composite sync on hardware where this is supported. Additionally, on some hardware, +CSync and -CSync may be used to select the composite sync polarity. The HSkew and VScan options mentioned above in the Modes entry description can also be used here.

Options

Some Option flags that may be useful to include in Monitor sections (when needed) include N`34`DPMSN`34`, and N`34`SyncOnGreenN`34`.

 

MODES SECTION

The config file may have multiple Modes sections, or none. These sections provide a way of defining sets of video modes independently of the Monitor sections. Monitor sections may include the definitions provided in these sections by using the UseModes keyword. In most cases the Modes sections are not necessary because the built-in set of VESA standard modes will be sufficient.

Modes sections have the following format:

Section N`34`ModesN`34` Identifier N`34`nameN`34` entries ... EndSection

The Identifier entry specifies the unique name for this set of mode descriptions. The other entries permitted in Modes sections are the Mode and ModeLine entries that are described above in the Monitor section.  

SCREEN SECTION

The config file may have multiple Screen sections. There must be at least one, for the "screen" being used. A "screen" represents the binding of a graphics device (Device section) and a monitor (Monitor section). A Screen section is considered "active" if it is referenced by an active ServerLayout section or by the -screen command line option. If neither of those is present, the first Screen section found in the config file is considered the active one.

Screen sections have the following format:

Section N`34`ScreenN`34` Identifier N`34`nameN`34` Device N`34`devidN`34` Monitor N`34`monidN`34` entries ... SubSection N`34`DisplayN`34` entries ... EndSubSection ... EndSection

The Identifier entry specifies the unique name for this screen. The Screen section provides information specific to the whole screen, including screen-specific Options. In multi-head configurations, there will be multiple active Screen sections, one for each head. The entries available for this section are:

Device N`34`device-idN`34`

This specifies the Device section to be used for this screen. This is what ties a specific graphics card to a screen. The device-id must match the Identifier of a Device section in the config file.

Monitor N`34`monitor-idN`34`

specifies which monitor description is to be used for this screen.

VideoAdaptor N`34`xv-idN`34`

specifies an optional Xv video adaptor description to be used with this screen.

DefaultDepth depth

specifies which color depth the server should use by default. The -depth command line option can be used to override this. If neither is specified, the default depth is driver-specific, but in most cases is 8.

DefaultFbBpp bpp

specifies which framebuffer layout to use by default. The -fbbpp command line option can be used to override this. In most cases the driver will chose the best default value for this. The only case where there is even a choice in this value is for depth 24, where some hardware supports both a packed 24 bit framebuffer layout and a sparse 32 bit framebuffer layout.

Options

Various Option flags may be specified in the Screen section. Some are driver-specific and are described in the driver documentation. Others are driver-independent, and will eventually be described here.

Option N`34`AccelN`34`

Enables XAA (X Acceleration Architecture), a mechanism that makes video cards` 2D hardware acceleration available to the X server. This option is on by default, but it may be necessary to turn it off if there are bugs in the driver. There are many options to disable specific acclerated operations, listed below. Note that disabling an operation will have no effect if the operation is not accelerated (whether due to lack of support in the hardware or in the driver).

Option N`34`NoMTRRN`34`

Disables MTRR (Memory Type Range Register) support, a feature of modern processors which can improve video performance by a factor of up to 2.5. Some hardware has buggy MTRR support, and some video drivers have been known to exhibit problems when MTRR`s are used.

Option N`34`XaaNoCPUToScreenColorExpandFillN`34`

Disables accelerated rectangular expansion blits from source patterns stored in system memory (using a memory-mapped aperture).

Option N`34`XaaNoColor8x8PatternFillRectN`34`

Disables accelerated fills of a rectangular region with a full-color pattern.

Option N`34`XaaNoColor8x8PatternFillTrapN`34`

Disables accelerated fills of a trapezoidal region with a full-color pattern.

Option N`34`XaaNoDashedBresenhamLineN`34`

Disables accelerated dashed Bresenham line draws.

Option N`34`XaaNoDashedTwoPointLineN`34`

Disables accelerated dashed line draws between two arbitrary points.

Option N`34`XaaNoImageWriteRectN`34`

Disables acclerated transfers of full-color rectangular patterns from system memory to video memory (using a memory-mapped aperture).

Option N`34`XaaNoMono8x8PatternFillRectN`34`

Disables accelerated fills of a rectangular region with a monochrome pattern.

Option N`34`XaaNoMono8x8PatternFillTrapN`34`

Disables accelerated fills of a trapezoidal region with a monochrome pattern.

Option N`34`XaaNoOffscreenPixmapsN`34`

Disables accelerated draws into pixmaps stored in offscreen video memory.

Option N`34`XaaNoPixmapCacheN`34`

Disables caching of patterns in offscreen video memory.

Option N`34`XaaNoScanlineCPUToScreenColorExpandFillN`34`

Disables accelerated rectangular expansion blits from source patterns stored in system memory (one scan line at a time).

Option N`34`XaaNoScanlineImageWriteRectN`34`

Disables acclerated transfers of full-color rectangular patterns from system memory to video memory (one scan line at a time).

Option N`34`XaaNoScreenToScreenColorExpandFillN`34`

Disables accelerated rectangular expansion blits from source patterns stored in offscreen video memory.

Option N`34`XaaNoScreenToScreenCopyN`34`

Disables accelerated copies of rectangular regions from one part of video memory to another part of video memory.

Option N`34`XaaNoSolidBresenhamLineN`34`

Disables accelerated solid Bresenham line draws.

Option N`34`XaaNoSolidFillRectN`34`

Disables accelerated solid-color fills of rectangles.

Option N`34`XaaNoSolidFillTrapN`34`

Disables accelerated solid-color fills of Bresenham trapezoids.

Option N`34`XaaNoSolidHorVertLineN`34`

Disables accelerated solid horizontal and vertical line draws.

Option N`34`XaaNoSolidTwoPointLineN`34`

Disables accelerated solid line draws between two arbitrary points.

Each Screen section must contain one or more Display subsections. Those subsections provide depth/fbbpp specific configuration information, and the one chosen depends on the depth and/or fbbpp that is being used for the screen. The Display subsection format is described in the section below.

 

DISPLAY SUBSECTION

Each Screen section may have multiple Display subsections. There must be at least one, which matches the depth and/or fbbpp values that are being used for the screen. The "active" Display subsection is the first that matches the depth and/or fbbpp values being used.

Display subsections have the following format:

SubSection N`34`DisplayN`34` Depth depth entries ... EndSubSection

Depth depth

This entry specifies what colour depth the Display subsection is to be used for. This entry is usually mandatory, but it may be omitted in some cases providing an FbBpp entry is present. The range of depth values that are allowed depends on the driver. Most driver support 8, 15, 16 and 24. Some also support 1 and/or 4, and some may support other values (like 30). Note: depth means the number of bits in a pixel that are actually used to determine the pixel colour. 32 is not a valid depth value. Most hardware that uses 32 bits per pixel only uses 24 of them to hold the colour information, which means that the colour depth is 24, not 32.

FbBpp bpp

This entry specifies the framebuffer format this Display subsection is to be used for. This entry is only needed when providing depth 24 configurations that allow a choice between a 24 bpp packed framebuffer format and a 32bpp sparse framebuffer format. In most cases this entry should not be used.

Weight red-weight green-weight blue-weight

This optional entry specifies the relative RGB weighting to be used for a screen is being used at depth 16 for drivers that allow multiple formats. This may also be specified from the command line with the -weight option (see XFree86(1)).

Virtual xdim ydim

This optional entry specifies the virtual screen resolution to be used. xdim must be a multiple of either 8 or 16 for most drivers, and a multiple of 32 when running in monochrome mode. The given value will be rounded down if this is not the case. Video modes which are too large for the specified virtual size will be rejected. If this entry is not present, the virtual screen resolution will be set to accommodate all the valid video modes given in the Modes entry. Some drivers/hardware combinations do not support virtual screens. Refer to the appropriate driver-specific documentation for details.

ViewPort x0 y0

This optional entry sets the upper left corner of the initial display. This is only relevant when the virtual screen resolution is different from the resolution of the initial video mode. If this entry is not given, then the initial display will be centered in the virtual display area.

Modes N`34`mode-nameN`34` ...

This entry is highly desirable for most drivers, and it specifies the list of video modes to use. Each mode-name specified must be in double quotes. They must correspond to those specified or referenced in the appropriate Monitor section (including implicitly referenced built-in VESA standard modes). The server will delete modes from this list which don`t satisfy various requirements. The first valid mode in this list will be the default display mode for startup. The list of valid modes is converted internally into a circular list. It is possible to switch to the next mode with Ctrl+Alt+Keypad-Plus and to the previous mode with Ctrl+Alt+Keypad-Minus. When this entry is omitted, the largest valid mode referenced by the appropriate Monitor section will be used.

Visual N`34`visual-nameN`34`

This optional entry sets the default root visual type. This may also be specified from the command line (see the Xserver(1) man page). The visual types available for depth 8 are (default is PseudoColor):

StaticGray GrayScale StaticColor PseudoColor TrueColor DirectColor

The visual type available for the depths 15, 16 and 24 are (default is TrueColor):

TrueColor DirectColor

Not all drivers support DirectColor at these depths.

The visual types available for the depth 4 are (default is StaticColor):

StaticGray GrayScale StaticColor PseudoColor

The visual type available for the depth 1 (monochrome) is StaticGray.

Black red green blue

This optional entry allows the "black" colour to be specified. This is only supported at depth 1. The default is black.

White red green blue

This optional entry allows the "white" colour to be specified. This is only supported at depth 1. The default is white.

Options

Option flags may be specified in the Display subsections. These may include driver-specific options and driver-independent options. The former are described in the driver-specific documentation. Some of the latter are described above in the section about the Screen section, and they may also be included here.

 

SERVERLAYOUT SECTION

The config file may have multiple ServerLayout sections. A "server layout" represents the binding of one or more screens (Screen sections) and one or more input devices (InputDevice sections) to form a complete configuration. In multi-head configurations, it also specifies the relative layout of the heads. A ServerLayout section is considered "active" if it is referenced by the -layout command line option or by an Option N`34`DefaultServerLayoutN`34` entry in the ServerFlags section (the former takes precedence over the latter). If those options are not used, the first ServerLayout section found in the config file is considered the active one. If no ServerLayout sections are present, the single active screen and two active (core) input devices are selected as described in the relevant sections above.

ServerLayout sections have the following format:

Section N`34`ServerLayoutN`34` Identifier N`34`nameN`34` Screen N`34`screen-idN`34` ... InputDevice N`34`idev-idN`34` ... options ... EndSection

The Identifier entry specifies the unique name for this server layout. The ServerLayout section provides information specific to the whole session, including session-specific Options. The ServerFlags options (described above) may be specified here, and ones given here override those given in the ServerFlags section.

The entries that may be used in this section are described here.

Screen screen-num N`34`screen-idN`34` position-information

One of these entries must be given for each screen being used in a session. The screen-id field is mandatory, and specifies the Screen section being referenced. The screen-num field is optional, and may be used to specify the screen number in multi-head configurations. When this field is omitted, the screens will be numbered in the order that they are listed in. The numbering starts from 0, and must be consecutive. The position-information field describes the way multiple screens are positioned. There are a number of different ways that this information can be provided:

x y

Absolute x y

These both specify that the upper left corner`s coordinates are (x,y). The Absolute keyword is optional. Some older versions of XFree86 (4.2 and earlier) don`t recognise the Absolute keyword, so it`s safest to just specificy the coorindates without it.

RightOf N`34`screen-idN`34`

LeftOf N`34`screen-idN`34`

Above N`34`screen-idN`34`

Below N`34`screen-idN`34`

Relative N`34`screen-idN`34` x y

These give the screen`s location relative to another screen. The first four position the screen immediately to the right, left, above or below the other screen. When positioning to the right or left, the top edges are aligned. When positioning above or below, the left edges are aligned. The Relative form specifies the offset of the screen`s origin (upper left corner) relative to the origin of another screen.

InputDevice N`34`idev-idN`34` N`34`optionN`34` ...

One of these entries must be given for each input device being used in a session. Normally at least two are required, one each for the core pointer and keyboard devices. The idev-id field is mandatory, and specifies the name of the InputDevice section being referenced. Multiple option fields may be specified, each in double quotes. The options permitted here are any that may also be given in the InputDevice sections. Normally only session-specific input device options would be used here. The most commonly used options are:

N`34`CorePointerN`34` N`34`CoreKeyboardN`34` N`34`SendCoreEventsN`34`

and the first two should normally be used to indicate the core pointer and core keyboard devices respectively.

Options

Any option permitted in the ServerFlags section may also be specified here. When the same option appears in both places, the value given here overrides the one given in the ServerFlags section.

Here is an example of a ServerLayout section for a dual headed configuration with two mice:

Section N`34`ServerLayoutN`34` Identifier N`34`Layout 1N`34` Screen N`34`MGA 1N`34` Screen N`34`MGA 2N`34` RightOf N`34`MGA 1N`34` InputDevice N`34`Keyboard 1N`34` N`34`CoreKeyboardN`34` InputDevice N`34`Mouse 1N`34` N`34`CorePointerN`34` InputDevice N`34`Mouse 2N`34` N`34`SendCoreEventsN`34` Option N`34`BlankTimeN`34` N`34`5N`34` EndSection

 

DRI SECTION

This optional section is used to provide some information for the Direct Rendering Infrastructure. Details about the format of this section can be found in the README.DRI document, which is also available on-line at <http://www.xfree86.org/current/DRI.html>.  

VENDOR SECTION

The optional Vendor section may be used to provide vendor-specific configuration information. Multiple Vendor sections may be present, and they may contain an Identifier entry and multiple Option flags. The data therein is not used in this release.

 

FILES

For an example of an XF86Config file, see the file installed as /usr/X11R6/lib/X11/XF86Config.eg.  

SEE ALSO

X(7), Xserver(1), XFree86(1), apm(4), chips(4), cirrus(4), cyrix(4), fbdev(4), glide(4), glint(4), i128(4), i740(4), i810(4), imstt(4), mga(4), neomagic(4), nv(4), r128(4), rendition(4), savage(4), s3virge(4), siliconmotion(4), sis(4), sunbw2(4), suncg14(4), suncg3(4), suncg6(4), sunffb(4), sunleo(4), suntcx(4), tdfx(4), tga(4), trident(4), tseng(4), v4l(4), vesa(4), vga(4), vmware(4),
README <http://www.xfree86.org/current/README.html>,
RELNOTES <http://www.xfree86.org/current/RELNOTES.html>,
README.mouse <http://www.xfree86.org/current/mouse.html>,
README.DRI <http://www.xfree86.org/current/DRI.html>,
Status <http://www.xfree86.org/current/Status.html>,
Install <http://www.xfree86.org/current/Install.html>.  

AUTHORS

This manual page was largely rewritten for XFree86 4.0 by David Dawes <dawes@xfree86.org>.

xfs

NAME

xfs - layout of the XFS filesystem  

DESCRIPTION

An XFS filesystem can reside on a regular disk partition or on a logical volume. An XFS filesystem has up to three parts: a data section, a log section, and a realtime section. Using the default mkfs.xfs(8) options, the realtime section is absent, and the log area is contained within the data section. The log section can be either separate from the data section or contained within it. The filesystem sections are divided into a certain number of blocks, whose size is specified at mkfs.xfs time with the -b option.

The data section contains all the filesystem metadata (inodes, directories, indirect blocks) as well as the user file data for ordinary (non-realtime) files and the log area if the log is internal to the data section. The data section is divided into a number of allocation groups. The number and size of the allocation groups are chosen by mkfs.xfs so that there is normally a small number of equal-sized groups. The number of allocation groups controls the amount of parallelism available in file and block allocation. It should be increased from the default if there is sufficient memory and a lot of allocation activity. The number of allocation groups should not be set very high, since this can cause large amounts of CPU time to be used by the filesystem, especially when the filesystem is nearly full. More allocation groups are added (of the original size) when xfs_growfs(8) is run.

The log section (or area, if it is internal to the data section) is used to store changes to filesystem metadata while the filesystem is running until those changes are made to the data section. It is written sequentially during normal operation and read only during mount. When mounting a filesystem after a crash, the log is read to complete operations that were in progress at the time of the crash.

The realtime section is used to store the data of realtime files. These files had an attribute bit set through xfsctl(3) after file creation, before any data was written to the file. The realtime section is divided into a number of extents of fixed size (specified at mkfs.xfs time). Each file in the realtime section has an extent size that is a multiple of the realtime section extent size.

Each allocation group contains several data structures. The first sector contains the superblock. For allocation groups after the first, the superblock is just a copy and is not updated after mkfs.xfs. The next three sectors contain information for block and inode allocation within the allocation group. Also contained within each allocation group are data structures to locate free blocks and inodes; these are located through the header structures.

Each XFS filesystem is labeled with a Universal Unique Identifier (UUID). The UUID is stored in every allocation group header and is used to help distinguish one XFS filesystem from another, therefore you should avoid using dd or other block-by-block copying programs to copy XFS filesystems. If two XFS filesystems on the same machine have the same UUID, xfsdump(8) may become confused when doing incremental and resumed dumps. xfsdump and xfsrestore are recommended for making copies of XFS filesystems.

 

OPERATIONS

Some functionality specific to the XFS filesystem is accessible to applications through the xfsctl(3) and by-handle (see open_by_handle(3)) interfaces.

 

MOUNT OPTIONS

Refer to the mount(8) manual entry for descriptions of the individual XFS mount options.

 

SEE ALSO

xfsctl(3), mount(8), mkfs.xfs(8), xfs_info(8), xfs_admin(8), xfsdump(8), xfsrestore(8).

xorg.conf.5x.php

NAME

xorg.conf - Configuration File for Xorg  

INTRODUCTION

Xorg supports several mechanisms for supplying/obtaining configuration and run-time parameters: command line options, environment variables, the xorg.conf configuration file, auto-detection, and fallback defaults. When the same information is supplied in more than one way, the highest precedence mechanism is used. The list of mechanisms is ordered from highest precedence to lowest. Note that not all parameters can be supplied via all methods. The available command line options and environment variables (and some defaults) are described in the Xserver(1x) and Xorg(1x) manual pages. Most configuration file parameters, with their defaults, are described below. Driver and module specific configuration parameters are described in the relevant driver or module manual page.  

DESCRIPTION

Xorg uses a configuration file called xorg.conf for its initial setup. This configuration file is searched for in the following places when the server is started as a normal user:

/etc/X11/<cmdline> /usr/X11R6/etc/X11/<cmdline> /etc/X11/$XORGCONFIG /usr/X11R6/etc/X11/$XORGCONFIG /etc/X11/xorg.conf-4 /etc/X11/xorg.conf /etc/xorg.conf /usr/X11R6/etc/X11/xorg.conf.<hostname> /usr/X11R6/etc/X11/xorg.conf-4 /usr/X11R6/etc/X11/xorg.conf /usr/X11R6/lib/X11/xorg.conf.<hostname> /usr/X11R6/lib/X11/xorg.conf-4 /usr/X11R6/lib/X11/xorg.conf

where <cmdline> is a relative path (with no ".." components) specified with the -config command line option, $XORGCONFIG is the relative path (with no ".." components) specified by that environment variable, and <hostname> is the machine`s hostname as reported by gethostname(3).

When the Xorg server is started by the "root" user, the config file search locations are as follows:

<cmdline> /etc/X11/<cmdline> /usr/X11R6/etc/X11/<cmdline> $XORGCONFIG /etc/X11/$XORGCONFIG /usr/X11R6/etc/X11/$XORGCONFIG $HOME/xorg.conf /etc/X11/xorg.conf-4 /etc/X11/xorg.conf /etc/xorg.conf /usr/X11R6/etc/X11/xorg.conf.<hostname> /usr/X11R6/etc/X11/xorg.conf-4 /usr/X11R6/etc/X11/xorg.conf /usr/X11R6/lib/X11/xorg.conf.<hostname> /usr/X11R6/lib/X11/xorg.conf-4 /usr/X11R6/lib/X11/xorg.conf

where <cmdline> is the path specified with the -config command line option (which may be absolute or relative), $XORGCONFIG is the path specified by that environment variable (absolute or relative), $HOME is the path specified by that environment variable (usually the home directory), and <hostname> is the machine`s hostname as reported by gethostname(3).

The xorg.conf file is composed of a number of sections which may be present in any order. Each section has the form:

Section N`34`SectionNameN`34` SectionEntry ... EndSection

The section names are:

Files File pathnames ServerFlags Server flags Module Dynamic module loading InputDevice Input device description Device Graphics device description VideoAdaptor Xv video adaptor description Monitor Monitor description Modes Video modes descriptions Screen Screen configuration ServerLayout Overall layout DRI DRI-specific configuration Vendor Vendor-specific configuration

The following obsolete section names are still recognised for compatibility purposes. In new config files, the InputDevice section should be used instead.

Keyboard Keyboard configuration Pointer Pointer/mouse configuration

The old XInput section is no longer recognised.

The ServerLayout sections are at the highest level. They bind together the input and output devices that will be used in a session. The input devices are described in the InputDevice sections. Output devices usually consist of multiple independent components (e.g., and graphics board and a monitor). These multiple components are bound together in the Screen sections, and it is these that are referenced by the ServerLayout section. Each Screen section binds together a graphics board and a monitor. The graphics boards are described in the Device sections, and the monitors are described in the Monitor sections.

Config file keywords are case-insensitive, and "_" characters are ignored. Most strings (including Option names) are also case-insensitive, and insensitive to white space and "_" characters.

Each config file entry usually takes up a single line in the file. They consist of a keyword, which is possibly followed by one or more arguments, with the number and types of the arguments depending on the keyword. The argument types are:

Integer an integer number in decimal, hex or octal Real a floating point number String a string enclosed in double quote marks (N`34`)

Note: hex integer values must be prefixed with "0x", and octal values with "0".

A special keyword called Option may be used to provide free-form data to various components of the server. The Option keyword takes either one or two string arguments. The first is the option name, and the optional second argument is the option value. Some commonly used option value types include:

Integer an integer number in decimal, hex or octal Real a floating point number String a sequence of characters Boolean a boolean value (see below) Frequency a frequency value (see below)

Note that all Option values, not just strings, must be enclosed in quotes.

Boolean options may optionally have a value specified. When no value is specified, the option`s value is TRUE. The following boolean option values are recognised as TRUE:

1, on, true, yes

and the following boolean option values are recognised as FALSE:

0, off, false, no

If an option name is prefixed with N`34`NoN`34`, then the option value is negated.

Example: the following option entries are equivalent:

Option N`34`AccelN`34` N`34`OffN`34` Option N`34`NoAccelN`34` Option N`34`NoAccelN`34` N`34`OnN`34` Option N`34`AccelN`34` N`34`falseN`34` Option N`34`AccelN`34` N`34`noN`34`

Frequency option values consist of a real number that is optionally followed by one of the following frequency units:

Hz, k, kHz, M, MHz

When the unit name is omitted, the correct units will be determined from the value and the expectations of the appropriate range of the value. It is recommended that the units always be specified when using frequency option values to avoid any errors in determining the value.  

FILES SECTION

The Files section is used to specify some path names required by the server. Some of these paths can also be set from the command line (see Xserver(1x) and Xorg(1x)). The command line settings override the values specified in the config file. The Files section is optional, as are all of the entries that may appear in it.

The entries that can appear in this section are:

FontPath N`34`pathN`34`

sets the search path for fonts. This path is a comma separated list of font path elements which the Xorg server searches for font databases. Multiple FontPath entries may be specified, and they will be concatenated to build up the fontpath used by the server. Font path elements may be either absolute directory paths, or a font server identifier. Font server identifiers have the form:

<trans>/<hostname>:<port-number>

where <trans> is the transport type to use to connect to the font server (e.g., unix for UNIX-domain sockets or tcp for a TCP/IP connection), <hostname> is the hostname of the machine running the font server, and <port-number> is the port number that the font server is listening on (usually 7100).

When this entry is not specified in the config file, the server falls back to the compiled-in default font path, which contains the following font path elements:

/usr/X11R6/lib/X11/fonts/misc/ /usr/X11R6/lib/X11/fonts/Speedo/ /usr/X11R6/lib/X11/fonts/Type1/ /usr/X11R6/lib/X11/fonts/CID/ /usr/X11R6/lib/X11/fonts/75dpi/ /usr/X11R6/lib/X11/fonts/100dpi/

The recommended font path contains the following font path elements:

/usr/X11R6/lib/X11/fonts/local/ /usr/X11R6/lib/X11/fonts/misc/ /usr/X11R6/lib/X11/fonts/75dpi/:unscaled /usr/X11R6/lib/X11/fonts/100dpi/:unscaled /usr/X11R6/lib/X11/fonts/Type1/ /usr/X11R6/lib/X11/fonts/CID/ /usr/X11R6/lib/X11/fonts/Speedo/ /usr/X11R6/lib/X11/fonts/75dpi/ /usr/X11R6/lib/X11/fonts/100dpi/

Font path elements that are found to be invalid are removed from the font path when the server starts up.

RGBPath N`34`pathN`34`

sets the path name for the RGB color database. When this entry is not specified in the config file, the server falls back to the compiled-in default RGB path, which is:

/usr/X11R6/lib/X11/rgb

Note that an implicit .txt is added to this path if the server was compiled to use text rather than binary format RGB color databases.

ModulePath N`34`pathN`34`

sets the search path for loadable Xorg server modules. This path is a comma separated list of directories which the Xorg server searches for loadable modules loading in the order specified. Multiple ModulePath entries may be specified, and they will be concatenated to build the module search path used by the server.

 

SERVERFLAGS SECTION

The ServerFlags section is used to specify some global Xorg server options. All of the entries in this section are Options, although for compatibility purposes some of the old style entries are still recognised. Those old style entries are not documented here, and using them is discouraged. The ServerFlags section is optional, as are the entries that may be specified in it.

Options specified in this section (with the exception of the N`34`DefaultServerLayoutN`34` Option) may be overridden by Options specified in the active ServerLayout section. Options with command line equivalents are overridden when their command line equivalent is used. The options recognised by this section are:

Option N`34`DefaultServerLayoutN`34` N`34`layout-idN`34`

This specifies the default ServerLayout section to use in the absence of the -layout command line option.

Option N`34`NoTrapSignalsN`34` N`34`booleanN`34`

This prevents the Xorg server from trapping a range of unexpected fatal signals and exiting cleanly. Instead, the Xorg server will die and drop core where the fault occurred. The default behaviour is for the Xorg server to exit cleanly, but still drop a core file. In general you never want to use this option unless you are debugging an Xorg server problem and know how to deal with the consequences.

Option N`34`DontVTSwitchN`34` N`34`booleanN`34`

This disallows the use of the Ctrl+Alt+Fn sequence (where Fn refers to one of the numbered function keys). That sequence is normally used to switch to another N`34`virtual terminalN`34` on operating systems that have this feature. When this option is enabled, that key sequence has no special meaning and is passed to clients. Default: off.

Option N`34`DontZapN`34` N`34`booleanN`34`

This disallows the use of the Ctrl+Alt+Backspace sequence. That sequence is normally used to terminate the Xorg server. When this option is enabled, that key sequence has no special meaning and is passed to clients. Default: off.

Option N`34`DontZoomN`34` N`34`booleanN`34`

This disallows the use of the Ctrl+Alt+Keypad-Plus and Ctrl+Alt+Keypad-Minus sequences. These sequences allows you to switch between video modes. When this option is enabled, those key sequences have no special meaning and are passed to clients. Default: off.

Option N`34`DisableVidModeExtensionN`34` N`34`booleanN`34`

This disables the parts of the VidMode extension used by the xvidtune client that can be used to change the video modes. Default: the VidMode extension is enabled.

Option N`34`AllowNonLocalXvidtuneN`34` N`34`booleanN`34`

This allows the xvidtune client (and other clients that use the VidMode extension) to connect from another host. Default: off.

Option N`34`DisableModInDevN`34` N`34`booleanN`34`

This disables the parts of the Xorg-Misc extension that can be used to modify the input device settings dynamically. Default: that functionality is enabled.

Option N`34`AllowNonLocalModInDevN`34` N`34`booleanN`34`

This allows a client to connect from another host and change keyboard and mouse settings in the running server. Default: off.

Option N`34`AllowMouseOpenFailN`34` N`34`booleanN`34`

This allows the server to start up even if the mouse device can`t be opened/initialised. Default: false.

Option N`34`VTInitN`34` N`34`commandN`34`

Runs command after the VT used by the server has been opened. The command string is passed to "/bin/sh -c", and is run with the real user`s id with stdin and stdout set to the VT. The purpose of this option is to allow system dependent VT initialisation commands to be run. This option should rarely be needed. Default: not set.

Option N`34`VTSysReqN`34` N`34`booleanN`34`

enables the SYSV-style VT switch sequence for non-SYSV systems which support VT switching. This sequence is Alt-SysRq followed by a function key (Fn). This prevents the Xorg server trapping the keys used for the default VT switch sequence, which means that clients can access them. Default: off.

Option N`34`XkbDisableN`34` N`34`booleanN`34`

disable/enable the XKEYBOARD extension. The -kb command line option overrides this config file option. Default: XKB is enabled.

Option N`34`BlankTimeN`34` N`34`timeN`34`

sets the inactivity timeout for the blanking phase of the screensaver. time is in minutes. This is equivalent to the Xorg server`s `-s` flag, and the value can be changed at run-time with xset(1x). Default: 10 minutes.

Option N`34`StandbyTimeN`34` N`34`timeN`34`

sets the inactivity timeout for the "standby" phase of DPMS mode. time is in minutes, and the value can be changed at run-time with xset(1x). Default: 20 minutes. This is only suitable for VESA DPMS compatible monitors, and may not be supported by all video drivers. It is only enabled for screens that have the N`34`DPMSN`34` option set (see the MONITOR section below).

Option N`34`SuspendTimeN`34` N`34`timeN`34`

sets the inactivity timeout for the "suspend" phase of DPMS mode. time is in minutes, and the value can be changed at run-time with xset(1x). Default: 30 minutes. This is only suitable for VESA DPMS compatible monitors, and may not be supported by all video drivers. It is only enabled for screens that have the N`34`DPMSN`34` option set (see the MONITOR section below).

Option N`34`OffTimeN`34` N`34`timeN`34`

sets the inactivity timeout for the "off" phase of DPMS mode. time is in minutes, and the value can be changed at run-time with xset(1x). Default: 40 minutes. This is only suitable for VESA DPMS compatible monitors, and may not be supported by all video drivers. It is only enabled for screens that have the N`34`DPMSN`34` option set (see the MONITOR section below).

Option N`34`PixmapN`34` N`34`bppN`34`

This sets the pixmap format to use for depth 24. Allowed values for bpp are 24 and 32. Default: 32 unless driver constraints don`t allow this (which is rare). Note: some clients don`t behave well when this value is set to 24.

Option N`34`PC98N`34` N`34`booleanN`34`

Specify that the machine is a Japanese PC-98 machine. This should not be enabled for anything other than the Japanese-specific PC-98 architecture. Default: auto-detected.

Option N`34`NoPMN`34` N`34`booleanN`34`

Disables something to do with power management events. Default: PM enabled on platforms that support it.

Option N`34`XineramaN`34` N`34`booleanN`34`

enable or disable XINERAMA extension. Default is disabled.

Option N`34`AllowDeactivateGrabsN`34` N`34`booleanN`34`

This option enables the use of the Ctrl+Alt+Keypad-Divide key sequence to deactivate any active keyboard and mouse grabs. Default: off.

Option N`34`AllowClosedownGrabsN`34` N`34`booleanN`34`

This option enables the use of the Ctrl+Alt+Keypad-Multiply key sequence to kill clients with an active keyboard or mouse grab as well as killing any application that may have locked the server, normally using the XGrabServer(3x) Xlib function. Default: off.
Note that the options AllowDeactivateGrabs and AllowClosedownGrabs will allow users to remove the grab used by screen saver/locker programs. An API was written to such cases. If you enable this option, make sure your screen saver/locker is updated.

Option N`34`HandleSpecialKeysN`34` N`34`whenN`34`

This option controls when the server uses the builtin handler to process special key combinations (such as Ctrl+Alt+Backspace). Normally the XKEYBOARD extension keymaps will provide mappings for each of the special key combinations, so the builtin handler is not needed unless the XKEYBOARD extension is disabled. The value of when can be Always, Never, or WhenNeeded. Default: Use the builtin handler only if needed. The server will scan the keymap for a mapping to the Terminate action and, if found, use XKEYBOARD for processing actions, otherwise the builtin handler will be used.

 

MODULE SECTION

The Module section is used to specify which Xorg server modules should be loaded. This section is ignored when the Xorg server is built in static form. The types of modules normally loaded in this section are Xorg server extension modules, and font rasteriser modules. Most other module types are loaded automatically when they are needed via other mechanisms. The Module section is optional, as are all of the entries that may be specified in it.

Entries in this section may be in two forms. The first and most commonly used form is an entry that uses the Load keyword, as described here:

Load N`34`modulenameN`34`

This instructs the server to load the module called modulename. The module name given should be the module`s standard name, not the module file name. The standard name is case-sensitive, and does not include the "lib" prefix, or the ".a", ".o", or ".so" suffixes.

Example: the Type 1 font rasteriser can be loaded with the following entry:

Load N`34`type1N`34`

The second form of entry is a SubSection, with the subsection name being the module name, and the contents of the SubSection being Options that are passed to the module when it is loaded.

Example: the extmod module (which contains a miscellaneous group of server extensions) can be loaded, with the Xorg-DGA extension disabled by using the following entry:

SubSection N`34`extmodN`34` Option N`34`omit XFree86-DGAN`34` EndSubSection

Modules are searched for in each directory specified in the ModulePath search path, and in the drivers, input, extensions, fonts, and internal subdirectories of each of those directories. In addition to this, operating system specific subdirectories of all the above are searched first if they exist.

To see what font and extension modules are available, check the contents of the following directories:

/usr/X11R6/lib/modules/fonts /usr/X11R6/lib/modules/extensions

The "bitmap" font modules is loaded automatically. It is recommended that at very least the "extmod" extension module be loaded. If it isn`t some commonly used server extensions (like the SHAPE extension) will not be available.  

INPUTDEVICE SECTION

The config file may have multiple InputDevice sections. There will normally be at least two: one for the core (primary) keyboard, and one of the core pointer. If either of these two is missing, a default configuration for the missing ones will be used. Currently the default configuration may not work as expected on all platforms.

InputDevice sections have the following format:

Section N`34`InputDeviceN`34` Identifier N`34`nameN`34` Driver N`34`inputdriverN`34` options ... EndSection

The Identifier and Driver entries are required in all InputDevice sections. All other entries are optional.

The Identifier entry specifies the unique name for this input device. The Driver entry specifies the name of the driver to use for this input device. When using the loadable server, the input driver module N`34`inputdriverN`34` will be loaded for each active InputDevice section. An InputDevice section is considered active if it is referenced by an active ServerLayout section, if it is referenced by the -keyboard or -pointer command line options, or if it is selected implicitly as the core pointer or keyboard device in the absence of such explicit references. The most commonly used input drivers are "keyboard" and "mouse".

In the absence of an explicitly specified core input device, the first InputDevice marked as CorePointer (or CoreKeyboard) is used. If there is no match there, the first InputDevice that uses the "mouse" (or "keyboard" or "kbd") driver is used. The final fallback is to use built-in default configurations.

InputDevice sections recognise some driver-independent Options, which are described here. See the individual input driver manual pages for a description of the device-specific options.

Option N`34`CorePointerN`34`

When this is set, the input device is installed as the core (primary) pointer device. There must be exactly 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. This option is implicitly set when the obsolete Pointer section is used.

Option N`34`CoreKeyboardN`34`

When this is set, the input device is to be installed as the core (primary) keyboard device. There must be exactly one core keyboard. If this option is not set here, in the ServerLayout section, or from the -keyboard command line option, then the first input device that is capable of being used as a core keyboard will be selected as the core keyboard. This option is implicitly set when the obsolete Keyboard section is used.

Option N`34`AlwaysCoreN`34` N`34`booleanN`34`

Option N`34`SendCoreEventsN`34` N`34`booleanN`34`

Both of these options are equivalent, and when enabled cause the input device to always report core events. This can be used, for example, to allow an additional pointer device to generate core pointer events (like moving the cursor, etc).

Option N`34`HistorySizeN`34` N`34`numberN`34`

Sets the motion history size. Default: 0.

Option N`34`SendDragEventsN`34` N`34`booleanN`34`

???

 

DEVICE SECTION

The config file may have multiple Device sections. There must be at least one, for the video card being used.

Device sections have the following format:

Section N`34`DeviceN`34` Identifier N`34`nameN`34` Driver N`34`driverN`34` entries ... EndSection

The Identifier and Driver entries are required in all Device sections. All other entries are optional.

The Identifier entry specifies the unique name for this graphics device. The Driver entry specifies the name of the driver to use for this graphics device. When using the loadable server, the driver module N`34`driverN`34` will be loaded for each active Device section. A Device section is considered active if it is referenced by an active Screen section.

Device sections recognise some driver-independent entries and Options, which are described here. Not all drivers make use of these driver-independent entries, and many of those that do don`t require them to be specified because the information is auto-detected. See the individual graphics driver manual pages for further information about this, and for a description of the device-specific options. Note that most of the Options listed here (but not the other entries) may be specified in the Screen section instead of here in the Device section.

BusID N`34`bus-idN`34`

This specifies the bus location of the graphics card. For PCI/AGP cards, the bus-id string has the form PCI:bus:device:function (e.g., "PCI:1:0:0" might be appropriate for an AGP card). This field is usually optional in single-head configurations when using the primary graphics card. In multi-head configurations, or when using a secondary graphics card in a single-head configuration, this entry is mandatory. Its main purpose is to make an unambiguous connection between the device section and the hardware it is representing. This information can usually be found by running the Xorg server with the -scanpci command line option.

Screen number

This option is mandatory for cards where a single PCI entity can drive more than one display (i.e., multiple CRTCs sharing a single graphics accelerator and video memory). One Device section is required for each head, and this parameter determines which head each of the Device sections applies to. The legal values of number range from 0 to one less than the total number of heads per entity. Most drivers require that the primary screen (0) be present.

Chipset N`34`chipsetN`34`

This usually optional entry specifies the chipset used on the graphics board. In most cases this entry is not required because the drivers will probe the hardware to determine the chipset type. Don`t specify it unless the driver-specific documentation recommends that you do.

Ramdac N`34`ramdac-typeN`34`

This optional entry specifies the type of RAMDAC used on the graphics board. This is only used by a few of the drivers, and in most cases it is not required because the drivers will probe the hardware to determine the RAMDAC type where possible. Don`t specify it unless the driver-specific documentation recommends that you do.

DacSpeed speed

DacSpeed speed-8 speed-16 speed-24 speed-32

This optional entry specifies the RAMDAC speed rating (which is usually printed on the RAMDAC chip). The speed is in MHz. When one value is given, it applies to all framebuffer pixel sizes. When multiple values are give, they apply to the framebuffer pixel sizes 8, 16, 24 and 32 respectively. This is not used by many drivers, and only needs to be specified when the speed rating of the RAMDAC is different from the defaults built in to driver, or when the driver can`t auto-detect the correct defaults. Don`t specify it unless the driver-specific documentation recommends that you do.

Clocks clock ...

specifies the pixel that are on your graphics board. The clocks are in MHz, and may be specified as a floating point number. The value is stored internally to the nearest kHz. The ordering of the clocks is important. It must match the order in which they are selected on the graphics board. Multiple Clocks lines may be specified, and each is concatenated to form the list. Most drivers do not use this entry, and it is only required for some older boards with non-programmable clocks. Don`t specify this entry unless the driver-specific documentation explicitly recommends that you do.

ClockChip N`34`clockchip-typeN`34`

This optional entry is used to specify the clock chip type on graphics boards which have a programmable clock generator. Only a few Xorg drivers support programmable clock chips. For details, see the appropriate driver manual page.

VideoRam mem

This optional entry specifies the amount of video ram that is installed on the graphics board. This is measured in kBytes. In most cases this is not required because the Xorg server probes the graphics board to determine this quantity. The driver-specific documentation should indicate when it might be needed.

BiosBase baseaddress

This optional entry specifies the base address of the video BIOS for the VGA board. This address is normally auto-detected, and should only be specified if the driver-specific documentation recommends it.

MemBase baseaddress

This optional entry specifies the memory base address of a graphics board`s linear frame buffer. This entry is not used by many drivers, and it should only be specified if the driver-specific documentation recommends it.

IOBase baseaddress

This optional entry specifies the IO base address. This entry is not used by many drivers, and it should only be specified if the driver-specific documentation recommends it.

ChipID id

This optional entry specifies a numerical ID representing the chip type. For PCI cards, it is usually the device ID. This can be used to override the auto-detection, but that should only be done when the driver-specific documentation recommends it.

ChipRev rev

This optional entry specifies the chip revision number. This can be used to override the auto-detection, but that should only be done when the driver-specific documentation recommends it.

TextClockFreq freq

This optional entry specifies the pixel clock frequency that is used for the regular text mode. The frequency is specified in MHz. This is rarely used.

Options

Option flags may be specified in the Device sections. These include driver-specific options and driver-independent options. The former are described in the driver-specific documentation. Some of the latter are described below in the section about the Screen section, and they may also be included here.

 

VIDEOADAPTOR SECTION

Nobody wants to say how this works. Maybe nobody knows ...

 

MONITOR SECTION

The config file may have multiple Monitor sections. There should normally be at least one, for the monitor being used, but a default configuration will be created when one isn`t specified.

Monitor sections have the following format:

Section N`34`MonitorN`34` Identifier N`34`nameN`34` entries ... EndSection

The only mandatory entry in a Monitor section is the Identifier entry.

The Identifier entry specifies the unique name for this monitor. The Monitor section provides information about the specifications of the monitor, monitor-specific Options, and information about the video modes to use with the monitor. Specifying video modes is optional because the server now has a built-in list of VESA standard modes. When modes are specified explicitly in the Monitor section (with the Modes, ModeLine, or UseModes keywords), built-in modes with the same names are not included. Built-in modes with different names are, however, still implicitly included.

The entries that may be used in Monitor sections are described below.

VendorName N`34`vendorN`34`

This optional entry specifies the monitor`s manufacturer.

ModelName N`34`modelN`34`

This optional entry specifies the monitor`s model.

HorizSync horizsync-range

gives the range(s) of horizontal sync frequencies supported by the monitor. horizsync-range may be a comma separated list of either discrete values or ranges of values. A range of values is two values separated by a dash. By default the values are in units of kHz. They may be specified in MHz or Hz if MHz or Hz is added to the end of the line. The data given here is used by the Xorg server to determine if video modes are within the specifications of the monitor. This information should be available in the monitor`s handbook. If this entry is omitted, a default range of 28-33kHz is used.

VertRefresh vertrefresh-range

gives the range(s) of vertical refresh frequencies supported by the monitor. vertrefresh-range may be a comma separated list of either discrete values or ranges of values. A range of values is two values separated by a dash. By default the values are in units of Hz. They may be specified in MHz or kHz if MHz or kHz is added to the end of the line. The data given here is used by the Xorg server to determine if video modes are within the specifications of the monitor. This information should be available in the monitor`s handbook. If this entry is omitted, a default range of 43-72Hz is used.

DisplaySize width height

This optional entry gives the width and height, in millimetres, of the picture area of the monitor. If given this is used to calculate the horizontal and vertical pitch (DPI) of the screen.

Gamma gamma-value

Gamma red-gamma green-gamma blue-gamma

This is an optional entry that can be used to specify the gamma correction for the monitor. It may be specified as either a single value or as three separate RGB values. The values should be in the range 0.1 to 10.0, and the default is 1.0. Not all drivers are capable of using this information.

UseModes N`34`modesection-idN`34`

Include the set of modes listed in the Modes section called modesection-id. This make all of the modes defined in that section available for use by this monitor.

Mode N`34`nameN`34`

This is an optional multi-line entry that can be used to provide definitions for video modes for the monitor. In most cases this isn`t necessary because the built-in set of VESA standard modes will be sufficient. The Mode keyword indicates the start of a multi-line video mode description. The mode description is terminated with the EndMode keyword. The mode description consists of the following entries:

DotClock clock

is the dot (pixel) clock rate to be used for the mode.

HTimings hdisp hsyncstart hsyncend htotal

specifies the horizontal timings for the mode.

VTimings vdisp vsyncstart vsyncend vtotal

specifies the vertical timings for the mode.

Flags N`34`flagN`34` ...

specifies an optional set of mode flags, each of which is a separate string in double quotes. N`34`InterlaceN`34` indicates that the mode is interlaced. N`34`DoubleScanN`34` indicates a mode where each scanline is doubled. N`34`+HSyncN`34` and N`34`-HSyncN`34` can be used to select the polarity of the HSync signal. N`34`+VSyncN`34` and N`34`-VSyncN`34` can be used to select the polarity of the VSync signal. N`34`CompositeN`34` can be used to specify composite sync on hardware where this is supported. Additionally, on some hardware, N`34`+CSyncN`34` and N`34`-CSyncN`34` may be used to select the composite sync polarity.

HSkew hskew

specifies the number of pixels (towards the right edge of the screen) by which the display enable signal is to be skewed. Not all drivers use this information. This option might become necessary to override the default value supplied by the server (if any). "Roving" horizontal lines indicate this value needs to be increased. If the last few pixels on a scan line appear on the left of the screen, this value should be decreased.

VScan vscan

specifies the number of times each scanline is painted on the screen. Not all drivers use this information. Values less than 1 are treated as 1, which is the default. Generally, the N`34`DoubleScanN`34` Flag mentioned above doubles this value.

ModeLine N`34`nameN`34` mode-description

This entry is a more compact version of the Mode entry, and it also can be used to specify video modes for the monitor. is a single line format for specifying video modes. In most cases this isn`t necessary because the built-in set of VESA standard modes will be sufficient.

The mode-description is in four sections, the first three of which are mandatory. The first is the dot (pixel) clock. This is a single number specifying the pixel clock rate for the mode in MHz. The second section is a list of four numbers specifying the horizontal timings. These numbers are the hdisp, hsyncstart, hsyncend, and htotal values. The third section is a list of four numbers specifying the vertical timings. These numbers are the vdisp, vsyncstart, vsyncend, and vtotal values. The final section is a list of flags specifying other characteristics of the mode. Interlace indicates that the mode is interlaced. DoubleScan indicates a mode where each scanline is doubled. +HSync and -HSync can be used to select the polarity of the HSync signal. +VSync and -VSync can be used to select the polarity of the VSync signal. Composite can be used to specify composite sync on hardware where this is supported. Additionally, on some hardware, +CSync and -CSync may be used to select the composite sync polarity. The HSkew and VScan options mentioned above in the Modes entry description can also be used here.

Options

Some Option flags that may be useful to include in Monitor sections (when needed) include N`34`DPMSN`34`, and N`34`SyncOnGreenN`34`.

 

MODES SECTION

The config file may have multiple Modes sections, or none. These sections provide a way of defining sets of video modes independently of the Monitor sections. Monitor sections may include the definitions provided in these sections by using the UseModes keyword. In most cases the Modes sections are not necessary because the built-in set of VESA standard modes will be sufficient.

Modes sections have the following format:

Section N`34`ModesN`34` Identifier N`34`nameN`34` entries ... EndSection

The Identifier entry specifies the unique name for this set of mode descriptions. The other entries permitted in Modes sections are the Mode and ModeLine entries that are described above in the Monitor section.  

SCREEN SECTION

The config file may have multiple Screen sections. There must be at least one, for the "screen" being used. A "screen" represents the binding of a graphics device (Device section) and a monitor (Monitor section). A Screen section is considered "active" if it is referenced by an active ServerLayout section or by the -screen command line option. If neither of those is present, the first Screen section found in the config file is considered the active one.

Screen sections have the following format:

Section N`34`ScreenN`34` Identifier N`34`nameN`34` Device N`34`devidN`34` Monitor N`34`monidN`34` entries ... SubSection N`34`DisplayN`34` entries ... EndSubSection ... EndSection

The Identifier and Device entries are mandatory. All others are optional.

The Identifier entry specifies the unique name for this screen. The Screen section provides information specific to the whole screen, including screen-specific Options. In multi-head configurations, there will be multiple active Screen sections, one for each head. The entries available for this section are:

Device N`34`device-idN`34`

This mandatory entry specifies the Device section to be used for this screen. This is what ties a specific graphics card to a screen. The device-id must match the Identifier of a Device section in the config file.

Monitor N`34`monitor-idN`34`

specifies which monitor description is to be used for this screen. If a Monitor name is not specified, a default configuration is used. Currently the default configuration may not function as expected on all platforms.

VideoAdaptor N`34`xv-idN`34`

specifies an optional Xv video adaptor description to be used with this screen.

DefaultDepth depth

specifies which color depth the server should use by default. The -depth command line option can be used to override this. If neither is specified, the default depth is driver-specific, but in most cases is 8.

DefaultFbBpp bpp

specifies which framebuffer layout to use by default. The -fbbpp command line option can be used to override this. In most cases the driver will chose the best default value for this. The only case where there is even a choice in this value is for depth 24, where some hardware supports both a packed 24 bit framebuffer layout and a sparse 32 bit framebuffer layout.

Options

Various Option flags may be specified in the Screen section. Some are driver-specific and are described in the driver documentation. Others are driver-independent, and will eventually be described here.

Option N`34`AccelN`34`

Enables XAA (X Acceleration Architecture), a mechanism that makes video cards` 2D hardware acceleration available to the Xorg server. This option is on by default, but it may be necessary to turn it off if there are bugs in the driver. There are many options to disable specific accelerated operations, listed below. Note that disabling an operation will have no effect if the operation is not accelerated (whether due to lack of support in the hardware or in the driver).

Option N`34`BiosLocationN`34` N`34`addressN`34`

Set the location of the BIOS for the Int10 module. One may select a BIOS of another card for posting or the legacy V_BIOS range located at 0xc0000 or an alternative address (BUS_ISA). This is only useful under very special circumstances and should be used with extreme care.

Option N`34`InitPrimaryN`34` N`34`booleanN`34`

Use the Int10 module to initialize the primary graphics card. Normally, only secondary cards are soft-booted using the Int10 module, as the primary card has already been initialized by the BIOS at boot time. Default: false.

Option N`34`NoInt10N`34` N`34`booleanN`34`

Disables the Int10 module, a module that uses the int10 call to the BIOS of the graphics card to initialize it. Default: false.

Option N`34`NoMTRRN`34`

Disables MTRR (Memory Type Range Register) support, a feature of modern processors which can improve video performance by a factor of up to 2.5. Some hardware has buggy MTRR support, and some video drivers have been known to exhibit problems when MTRR`s are used.

Option N`34`XaaNoCPUToScreenColorExpandFillN`34`

Disables accelerated rectangular expansion blits from source patterns stored in system memory (using a memory-mapped aperture).

Option N`34`XaaNoColor8x8PatternFillRectN`34`

Disables accelerated fills of a rectangular region with a full-color pattern.

Option N`34`XaaNoColor8x8PatternFillTrapN`34`

Disables accelerated fills of a trapezoidal region with a full-color pattern.

Option N`34`XaaNoDashedBresenhamLineN`34`

Disables accelerated dashed Bresenham line draws.

Option N`34`XaaNoDashedTwoPointLineN`34`

Disables accelerated dashed line draws between two arbitrary points.

Option N`34`XaaNoImageWriteRectN`34`

Disables accelerated transfers of full-color rectangular patterns from system memory to video memory (using a memory-mapped aperture).

Option N`34`XaaNoMono8x8PatternFillRectN`34`

Disables accelerated fills of a rectangular region with a monochrome pattern.

Option N`34`XaaNoMono8x8PatternFillTrapN`34`

Disables accelerated fills of a trapezoidal region with a monochrome pattern.

Option N`34`XaaNoOffscreenPixmapsN`34`

Disables accelerated draws into pixmaps stored in offscreen video memory.

Option N`34`XaaNoPixmapCacheN`34`

Disables caching of patterns in offscreen video memory.

Option N`34`XaaNoScanlineCPUToScreenColorExpandFillN`34`

Disables accelerated rectangular expansion blits from source patterns stored in system memory (one scan line at a time).

Option N`34`XaaNoScanlineImageWriteRectN`34`

Disables accelerated transfers of full-color rectangular patterns from system memory to video memory (one scan line at a time).

Option N`34`XaaNoScreenToScreenColorExpandFillN`34`

Disables accelerated rectangular expansion blits from source patterns stored in offscreen video memory.

Option N`34`XaaNoScreenToScreenCopyN`34`

Disables accelerated copies of rectangular regions from one part of video memory to another part of video memory.

Option N`34`XaaNoSolidBresenhamLineN`34`

Disables accelerated solid Bresenham line draws.

Option N`34`XaaNoSolidFillRectN`34`

Disables accelerated solid-color fills of rectangles.

Option N`34`XaaNoSolidFillTrapN`34`

Disables accelerated solid-color fills of Bresenham trapezoids.

Option N`34`XaaNoSolidHorVertLineN`34`

Disables accelerated solid horizontal and vertical line draws.

Option N`34`XaaNoSolidTwoPointLineN`34`

Disables accelerated solid line draws between two arbitrary points.

Each Screen section may optionally contain one or more Display subsections. Those subsections provide depth/fbbpp specific configuration information, and the one chosen depends on the depth and/or fbbpp that is being used for the screen. The Display subsection format is described in the section below.

 

DISPLAY SUBSECTION

Each Screen section may have multiple Display subsections. The "active" Display subsection is the first that matches the depth and/or fbbpp values being used, or failing that, the first that has neither a depth or fbbpp value specified. The Display subsections are optional. When there isn`t one that matches the depth and/or fbbpp values being used, all the parameters that can be specified here fall back to their defaults.

Display subsections have the following format:

SubSection N`34`DisplayN`34` Depth depth entries ... EndSubSection

Depth depth

This entry specifies what colour depth the Display subsection is to be used for. This entry is usually specified, but it may be omitted to create a match-all Display subsection or when wishing to match only against the FbBpp parameter. The range of depth values that are allowed depends on the driver. Most driver support 8, 15, 16 and 24. Some also support 1 and/or 4, and some may support other values (like 30). Note: depth means the number of bits in a pixel that are actually used to determine the pixel colour. 32 is not a valid depth value. Most hardware that uses 32 bits per pixel only uses 24 of them to hold the colour information, which means that the colour depth is 24, not 32.

FbBpp bpp

This entry specifies the framebuffer format this Display subsection is to be used for. This entry is only needed when providing depth 24 configurations that allow a choice between a 24 bpp packed framebuffer format and a 32bpp sparse framebuffer format. In most cases this entry should not be used.

Weight red-weight green-weight blue-weight

This optional entry specifies the relative RGB weighting to be used for a screen is being used at depth 16 for drivers that allow multiple formats. This may also be specified from the command line with the -weight option (see Xorg(1x)).

Virtual xdim ydim

This optional entry specifies the virtual screen resolution to be used. xdim must be a multiple of either 8 or 16 for most drivers, and a multiple of 32 when running in monochrome mode. The given value will be rounded down if this is not the case. Video modes which are too large for the specified virtual size will be rejected. If this entry is not present, the virtual screen resolution will be set to accommodate all the valid video modes given in the Modes entry. Some drivers/hardware combinations do not support virtual screens. Refer to the appropriate driver-specific documentation for details.

ViewPort x0 y0

This optional entry sets the upper left corner of the initial display. This is only relevant when the virtual screen resolution is different from the resolution of the initial video mode. If this entry is not given, then the initial display will be centered in the virtual display area.

Modes N`34`mode-nameN`34` ...

This optional entry specifies the list of video modes to use. Each mode-name specified must be in double quotes. They must correspond to those specified or referenced in the appropriate Monitor section (including implicitly referenced built-in VESA standard modes). The server will delete modes from this list which don`t satisfy various requirements. The first valid mode in this list will be the default display mode for startup. The list of valid modes is converted internally into a circular list. It is possible to switch to the next mode with Ctrl+Alt+Keypad-Plus and to the previous mode with Ctrl+Alt+Keypad-Minus. When this entry is omitted, the valid modes referenced by the appropriate Monitor section will be used. If the Monitor section contains no modes, then the selection will be taken from the built-in VESA standard modes.

Visual N`34`visual-nameN`34`

This optional entry sets the default root visual type. This may also be specified from the command line (see the Xserver(1x) man page). The visual types available for depth 8 are (default is PseudoColor):

StaticGray GrayScale StaticColor PseudoColor TrueColor DirectColor

The visual type available for the depths 15, 16 and 24 are (default is TrueColor):

TrueColor DirectColor

Not all drivers support DirectColor at these depths.

The visual types available for the depth 4 are (default is StaticColor):

StaticGray GrayScale StaticColor PseudoColor

The visual type available for the depth 1 (monochrome) is StaticGray.

Black red green blue

This optional entry allows the "black" colour to be specified. This is only supported at depth 1. The default is black.

White red green blue

This optional entry allows the "white" colour to be specified. This is only supported at depth 1. The default is white.

Options

Option flags may be specified in the Display subsections. These may include driver-specific options and driver-independent options. The former are described in the driver-specific documentation. Some of the latter are described above in the section about the Screen section, and they may also be included here.

 

SERVERLAYOUT SECTION

The config file may have multiple ServerLayout sections. A "server layout" represents the binding of one or more screens (Screen sections) and one or more input devices (InputDevice sections) to form a complete configuration. In multi-head configurations, it also specifies the relative layout of the heads. A ServerLayout section is considered "active" if it is referenced by the -layout command line option or by an Option N`34`DefaultServerLayoutN`34` entry in the ServerFlags section (the former takes precedence over the latter). If those options are not used, the first ServerLayout section found in the config file is considered the active one. If no ServerLayout sections are present, the single active screen and two active (core) input devices are selected as described in the relevant sections above.

ServerLayout sections have the following format:

Section N`34`ServerLayoutN`34` Identifier N`34`nameN`34` Screen N`34`screen-idN`34` ... InputDevice N`34`idev-idN`34` ... options ... EndSection

Each ServerLayout section must have an Identifier entry and at least one Screen entry.

The Identifier entry specifies the unique name for this server layout. The ServerLayout section provides information specific to the whole session, including session-specific Options. The ServerFlags options (described above) may be specified here, and ones given here override those given in the ServerFlags section.

The entries that may be used in this section are described here.

Screen screen-num N`34`screen-idN`34` position-information

One of these entries must be given for each screen being used in a session. The screen-id field is mandatory, and specifies the Screen section being referenced. The screen-num field is optional, and may be used to specify the screen number in multi-head configurations. When this field is omitted, the screens will be numbered in the order that they are listed in. The numbering starts from 0, and must be consecutive. The position-information field describes the way multiple screens are positioned. There are a number of different ways that this information can be provided:

x y

Absolute x y

These both specify that the upper left corner`s coordinates are (x,y). The Absolute keyword is optional. Some older versions of Xorg (4.2 and earlier) don`t recognise the Absolute keyword, so it`s safest to just specify the coordinates without it.

RightOf N`34`screen-idN`34`

LeftOf N`34`screen-idN`34`

Above N`34`screen-idN`34`

Below N`34`screen-idN`34`

Relative N`34`screen-idN`34` x y

These give the screen`s location relative to another screen. The first four position the screen immediately to the right, left, above or below the other screen. When positioning to the right or left, the top edges are aligned. When positioning above or below, the left edges are aligned. The Relative form specifies the offset of the screen`s origin (upper left corner) relative to the origin of another screen.

InputDevice N`34`idev-idN`34` N`34`optionN`34` ...

One of these entries should be given for each input device being used in a session. Normally at least two are required, one each for the core pointer and keyboard devices. If either of those is missing, suitable InputDevice entries are searched for using the method described above in the INPUTDEVICE section. The idev-id field is mandatory, and specifies the name of the InputDevice section being referenced. Multiple option fields may be specified, each in double quotes. The options permitted here are any that may also be given in the InputDevice sections. Normally only session-specific input device options would be used here. The most commonly used options are:

N`34`CorePointerN`34` N`34`CoreKeyboardN`34` N`34`SendCoreEventsN`34`

and the first two should normally be used to indicate the core pointer and core keyboard devices respectively.

Options

Any option permitted in the ServerFlags section may also be specified here. When the same option appears in both places, the value given here overrides the one given in the ServerFlags section.

Here is an example of a ServerLayout section for a dual headed configuration with two mice:

Section N`34`ServerLayoutN`34` Identifier N`34`Layout 1N`34` Screen N`34`MGA 1N`34` Screen N`34`MGA 2N`34` RightOf N`34`MGA 1N`34` InputDevice N`34`Keyboard 1N`34` N`34`CoreKeyboardN`34` InputDevice N`34`Mouse 1N`34` N`34`CorePointerN`34` InputDevice N`34`Mouse 2N`34` N`34`SendCoreEventsN`34` Option N`34`BlankTimeN`34` N`34`5N`34` EndSection

 

DRI SECTION

This optional section is used to provide some information for the Direct Rendering Infrastructure. Details about the format of this section can be found in the README.DRI document, which is also available on-line at <http://www.x.org>.  

VENDOR SECTION

The optional Vendor section may be used to provide vendor-specific configuration information. Multiple Vendor sections may be present, and they may contain an Identifier entry and multiple Option flags. The data therein is not used in this release.

 

FILES

For an example of an xorg.conf file, see the file installed as /usr/X11R6/lib/X11/xorg.conf.eg.  

SEE ALSO

X(7x), Xserver(1x), Xorg(1x), apm(4x), chips(4x), cirrus(4x), cyrix(4x), fbdev(4x), glide(4x), glint(4x), i128(4x), i740(4x), i810(4x), imstt(4x), mga(4x), neomagic(4x), nv(4x), r128(4x), rendition(4x), savage(4x), s3virge(4x), siliconmotion(4x), sis(4x), sunbw2(4x), suncg14(4x), suncg3(4x), suncg6(4x), sunffb(4x), sunleo(4x), suntcx(4x), tdfx(4x), tga(4x), trident(4x), tseng(4x), v4l(4x), vesa(4x), vga(4x), vmware(4x),
 

AUTHORS

This manual page was largely rewritten by David Dawes <dawes@xfree86.org>.