path: root/xc/programs/Xserver/hw/xfree86/doc/sgml/RELNOTES.sgml

<!DOCTYPE linuxdoc PUBLIC "-//XFree86//DTD linuxdoc//EN" [
<!ENTITY % defs SYSTEM "defs.ent"> %defs;
]>

<article>

<title>Release Notes for XFree86&trade; &relvers;
<author>The XFree86 Project, Inc
<date>3 July 2000

<ident>
$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/RELNOTES.sgml,v 1.42 2000/07/03 16:27:10 dawes Exp $
</ident>

<abstract>

This document contains some information about the features present
in XFree86 &relvers; and their status.

</abstract>

<toc>

<sect>Introduction to the 4.x Release Series
<p>
XFree86 4.0 was the first official release of the new XFree86 4.  XFree86
4 represents a significant redesign of the XFree86 X server.
Not all of the hardware drivers from 3.3.x have been ported to 4.x yet,
but conversely, 4.x has some hardware support not present in 3.3.x.
We've attempted to provide some information
about the second point in our <htmlurl name="Driver Status document"
url="Status.html">.  Please check there first before downloading  &relvers;.

The 4.0.1 has a new configuration tool, "<tt>xf86cfg</tt>".  It is work
in progress, but definitely worth trying out.  We have also updated the
basic text-based tool "<tt>xf86config</tt>" to generate config files in
the format required by &relvers; (3.3.x config files won't really work
with &relvers;).  We're also on a configuration tool that is built-in
to the X server.  An early version of this is included in the release,
and it works well for some hardware.  To try it out, just run (as root)
"<tt>XFree86 -configure</tt>".  Each of these configuration options will
give you a reasonable starting point for a suitable configuration file.
We've put some effort into documenting the &relvers; config file format,
and you can find that information in the XF86Config manual page. Check
that,  the driver manual pages and the related documentation for further
information.

Oh, another thing you might notice is that our documentation is rather
patchy.  Most of what is present should be in reasonable shape, but
there are gaps.  We thought it better to leave out docs that were very
out of date rather than providing inaccurate and misleading information.
We are looking for people to also help fill those gaps in &lt;hint hint
:-&gt;.

Finally, before you download and install the binary distributions for
this release, please have a quick read through the <htmlurl
name="Installation Document" url="Install.html">.  It may save you some
time.

The next section describes what is new in the latest version (&relvers;).
The other sections below describe some of the new features and changes
between 3.3.x and 4.0.  There is a lot of new features, and we definitely
don't have enough space to cover it all here.

</sect>

<sect>Summary of new features in &relvers;.
<p>
<sect1>X server
<p>
<itemize>
  <item>New DRI drivers for Intel i810, Matrox G400 and G200 (AGP only) and 
	the ATI Rage 128, and updates to the 3Dfx DRI driver, including
	Voodoo5 support.

  <item>The X server now runs on Linux/Sparc including drivers for many
	video cards used on SUN hardware.

  <item>DRI support for the Linux/Sparc implementation that allows 3D direct
	rendering with Creator3D cards.

  <item>Fixed recently publicized security issues.

  <item>Update Mesa to the latest version.

  <item>Xinerama updates and fixes.

  <item>Xv updates and fixes.

  <item>Mouse support in DGA 1.0 compatibility mode should now work correctly
	for most games that make use of it.

  <item>Some bugs with 8+24 overlay support have been fixed.

  <item>Some XKEYBOARD extension problems have been fixed, including
	improvements to the MouseKeys support.

  <item>Add generic DGA support to the sis, neomagic and i810 drivers.

  <item><tt>xf86cfg</tt>, a new graphical configuration tool for XFree86 4.0,
	and can be used to either write the initial configuration or make
	customizations to the current configuration.  <tt>xf86cfg</tt> is
	a work in progress, and allows configuration of:

	<itemize>
	  <item>Specific setup of monitors, cards, keyboards and mice, as
		well as adding or removing them.
	  <item>Server layout setup, allowing complex configuration of
		physical monitor positions, default color depth and/or
		rotated monitors.
	  <item>Mode line editor that can be used to configure multiple
		monitors, and allows adding a modeline specific to a
		monitor directly to the configuration file.
	  <item>AccessX configuration interface, that provides an interface
		to easy setup of most AccessX options, including:

		<itemize>
		  <item>Timeout to reset controls.
		  <item>StickyKeys, for people with disabilities that cannot
			press two keys at the same time.
		  <item>MouseKeys, mouse control only with the keyboard.
		  <item>RepeatKeys, repeat rate and repeat delay.
		  <item>SlowKeys, to avoid pressing keys accidentally, they're
			only accepted if pressed for some specific amount
			of time.
		  <item>BounceKeys, helps avoiding multiple key presses by
			only accepting a key if it is pressed only once and
			not pressed again in a specific amount of time.
		</itemize>
	</itemize>
	
	New configuration options are being worked on, as well as correcting
	some of the bugs in the current options.  A protocol for plugging
	in external modules is also planned.

</itemize>
</sect1>

<sect1>X libraries and clients.
<p>
<itemize>
  <item>Thread safety issues have been resolved in a few places in the
	libraries.  Upgrading to the latest libraries is essential for
	multi-threaded X applications.

  <item>Some fatal bugs in the big font support have been fixed.  Upgrading
	to the latest libraries will fix this too.

  <item>Fixed recently publicized security issues in some of the X libraries.

  <item>Updates and bug fixes for some clients, including xedit, xman,
	xcalc, fstobdf, xdm.

  <item>Fix some xfs problems.

  <item>XTerm updates.  These include:
	<itemize>
	  <item>Improve logfile security.

	  <item>Workaround for fixed fonts which are generated from
		Unicode fonts:  they omit glyphs for some xterm's
		less-used line-drawing characters, which caused xterm
		to set a flag telling it to use only its internal
		line-drawing characters.

	  <item>Limit numeric parameters of control sequences to 65535
		to simplify checks for numeric overflow.

	  <item>Change index into UDK list to unsigned to guard against
		numeric overflow making the index negative.

	  <item>Add limit checks to ClearInLine(), ScrnInsertChar(),
		ScrnDeleteChar() to correct potential out-of-bounds
		indexing.

	  <item>Add a resource (limitResize) limiting resizing via the
		<tt>CSI 4 t</tt> and <tt>CSI 8 t</tt> sequences.

	  <item>Ignore out-of-bounds resize requests, i.e., where
		sign-extension or truncation of the parameters would
		occur.

	  <item>Change Sun function-keys resource name to sunFunctionKeys
		to work around redefinition of the token sun by xrdb on
		Solaris.  Similarly, renamed resource sun keyboard to
		sunKeyboard.  Change similar resource names for HP and
		SCO to avoid potential conflict with xrdb symbols on
		other systems, as well as for consistency.

	  <item>Change line speed from 9600bd to 38400bd to accommodate
		users who mistakenly use $TERM set to vt100, to reduce
		the effect of padding associated with this terminal
		type.

	  <item>Fix a problem that caused the right scrollbar to be
		positioned incorrectly when re-enabling it.

	  <item>Fix a problem with color support that showed up on some
		platforms.

	  <item>Modify logic for deleteIsDEL resource so it has internally
		3 states:  unspecified, true and false.  If unspecified,
		the keyboard type determines whether the Delete key
		transmits <tt>&lt;esc&gt;[3~</tt> or <tt>\177</tt>, and
		the popup menu entry reflects the internal state.
		Otherwise, the popup menu entry overrides the keyboard
		type.
	
	  <item>Portability fixes for os390, AIX 4.2, Digital Unix 4.0
		and IRIX 6.5.

	</itemize>

</itemize>

<sect1>Fonts and Internationalisation
<p>
<itemize>
  <item>Many of the "misc" bdf fonts have been updated and extended, and
	a wider range of ISO-8859 subsets have been added.  Oblique/italic
	versions of some of them have also been added.

  <item>The converters in Xlib have been improved and reworked.  UTF-8
	support has been added.

  <item>Support for ISO-8859-13 has been added to Xlib and to the UTF-8
	converters.

  <item>XKB keyboard definitions have been added and updated for some
	countries.

  <item>Locale support for Celtic languages has been updated, and a Compose
	file for ISO-8859-14 added.

</itemize>
</sect1>

<sect1>Miscellaneous
<p>
<itemize>
  <item>Preliminary support for Linux/mips (no X servers yet).

  <item>Update support for BSD/OS.

  <item>Update Linux/IA64 support.

  <item>Support for LynxOS 3.1.0.

</itemize>
</sect1>

</sect>

<sect>The new X server
<p>
Unlike XFree86 3.3.x where there are multiple X server binaries, each
of which drive different hardware, XFree86 &relvers; has a single X
server binary called <tt>XFree86</tt>.  This binary can either have one
or more video drivers linked in statically, or, more usually, dynamically
load the video drivers and other modules that are needed.

XFree86 &relvers; has X server support for most UNIX(R) and UNIX-like
operating systems on Intel/x86 platforms, plus support for Linux on
Alpha, PowerPC and Sparc platforms.  Work on support for additional
architectures and operating systems is in progress, and is planned for
future releases.

<sect1>Loader and Modules
<p>
The XFree86 X server has a built-in run-time loader, donated by <url
name="Metro Link" url="http://www.metrolink.com">.  This loader can load
normal object files and libraries in most of the commonly used formats.
Since the loader doesn't rely on an operating system's native dynamic
loader support, it works on platforms that don't provide this feature,
and makes it possible for the modules to be operating system independent
(although not, of course, independent of CPU architecture).  This means
that a module compiled on Linux/x86 can be loaded by an
X server running on Solaris/x86, or FreeBSD, or even OS/2.  
<p>
One of the
main benefits of this loader is that when modules are updated, they do not need
to be recompiled for every different operating system.  In the future
we plan to take advantage of this to provide more frequent driver module 
updates in between major releases.

The loader in version &relvers; has support for Intel (x86), Alpha and
PowerPC platforms.  It also has preliminary support for Sparc platforms.

The X server makes use of modules for video drivers, X server extensions,
font rasterisers, input device drivers, framebuffer layers (like mfb,
cfb, etc), and internal components used by some drivers (like XAA),

The module interfaces (API and ABI) used in this release is still subject
to change without notice.  While we will attempt to provide backward
compatibility for the module interfaces as of the 4.0 release (meaning
that 4.0 modules will work with future core X server binaries), we cannot
guarantee this. 

<bf>Note about module security</bf>
<quote><p>
	The XFree86 X server runs with root privileges, i.e. 
	the X server loadable modules also run with these privileges.
	For this reason we recommend that all users be careful to only
	use loadable modules from reliable sources,  otherwise the
        introduction of viruses and contaminated code can occur and wreak
         havoc on your system.  We hope to have a
	mechanism for signing/verifying the modules that we provide
	available in a future release.

</quote>

<sect1>Configuration File <label id="config">
<p>

The X server configuration file format has been extended to handle some
of the new functionality.  The <tt>xf86config</tt> utility can be used
to generate a basic config file, that may require some manual editing.
The X server also has preliminary support for generating a basic config
file.  This is done by running (as root) "<tt>XFree86 -configure</tt>".
Alternatively, the sample config file <tt>XF86Config.eg</tt> that is
installed in <tt>/usr/X11R6/lib/X11</tt> may be used as a starting point.
The <tt>XF86Setup</tt> utility is currently not usable, but work is
continuing in this area.

The main changes are covered here, but please refer to the XF86Config
manual page for more comprehensive information:

<itemize>
  <item>The Module section is used to load server extension modules and
	font modules, but not XInput drivers.  The <tt>.so</tt> suffix
	should no longer be specified with module names.  Options may
	be supplied for modules by loading the module via a SubSection
	instead of the usual Load keyword.  The <tt>bitmap</tt> module
	is the only font module that is loaded by default.  No server
	extensions are loaded by default, but some are built-in to the
	server.  It is strongly recommended that the extension module
	containing a range of small miscellaneous extensions (<tt>extmod</tt>)
	be loaded because some commonly used things won't work correctly
	without it.  The following example shows how to load all the server
	extensions plus the Type1 and TrueType fonts support, and a
	commented example that shows how to pass options to an extension
	(this one is for loading the misc extensions (<tt>extmod</tt>)
	with the XFree86-VidModeExtension disabled):

<quote><verb>
Section "Module"

    Load "dbe"
    Load "record"
    Load "glx"
    Load "pex5"
    Load "xie"
    Load "extmod"

    Load "type1"
    Load "freetype"

  # SubSection "extmod"
  #     Option "Omit XFree86-VidModeExtension"
  # EndSubSection

EndSection
</verb></quote>

  <item>Option flags have been extended and are now used more widely in the
	config file.  Options flags come in two main types.  The first type
	is exactly like the old form:

<quote><verb>
    Option "name"
</verb></quote>

	where the option just has a name specified.  The name is case
	insensitive, and white space and underscore characters are ignored.
	The second type consists of a name and a value:

<quote><verb>
    Option "name" "value"
</verb></quote>

	The value is passed transparently as a string to the code that
	uses the option.  Common value formats are integer, boolean,
	real, string and frequency.  The following boolean option values
	are recognised as meaning TRUE: <tt>"true"</tt>, <tt>"yes"</tt>,
	<tt>"on"</tt>, <tt>"1"</tt>, and no value.  The values recognised
	as FALSE are <tt>"false"</tt>, <tt>"no"</tt>, <tt>"off"</tt>,
	<tt>"0"</tt>.  In addition to this, <tt>"no"</tt> may be prepended
	to the <em>name</em> of a boolean option to indicate that it is
	false.  Frequency options can have the strings <tt>Hz</tt>,
	<tt>kHz</tt>, or <tt>MHz</tt> appended to the numerical value
	specified.

	Note: the value must always be enclosed in double quotes
	(<tt>"</tt>), even when it is numerical.

  <item>The ServerFlags section now accepts its parameters as Options
	instead of as special keywords.  The older keyword format is
	still recognised for compatibility purposes, but is deprecated
	and support for it will likely be dropped in a future release.
	The DPMS and screen save timeout values are now specified in the
	ServerFlags section rather than elsewhere (because they are global
	parameters, not screen-specific).  This example shows the defaults
	for these:

<quote><verb>
    Option "blank time"    "10"
    Option "standby time"  "20"
    Option "suspend time"  "30"
    Option "off time"      "40"
</verb></quote>

  <item>The Keyboard, Pointer and XInput sections have been replaced by a
	more general InputDevice section.  The old Keyboard and Pointer
	sections are still recognised for compatibility purposes, but
	they are discommended and support for them may be dropped in future
	releases.  The old XInput sections are no longer recognised.
	The keywords from the old sections are expressed as Options in
	the InputDevice sections.  The following example shows typical
	InputDevice sections for the core mouse and keyboard.

<quote><verb>
Section "InputDevice"
    Identifier  "Keyboard 1"
    Driver      "keyboard"
    Option      "AutoRepeat" "500 5"
    Option      "XkbModel"   "pc104"
    Option      "XkbLayout"  "us"
EndSection

Section "InputDevice"
    Identifier  "Mouse 1"
    Driver      "mouse"
    Option      "Protocol"   "PS/2"
    Option      "Device"     "/dev/mouse"
    Option	"SampleRate" "80"
EndSection
</verb></quote>

<!-- what is this doing in the middle of information about the config file??
j
     Note: Additional sample rates have been added for some mice.
           Matching the mouse sampling rate with the vertical refresh
           rate can yield very noticeable improvements in smoothness of
           pointer event driven operations such as window moves and
           scrolling.
-->

  <item>The Monitor section is mostly unchanged.  The main difference is
	that a set of VESA modes is defined internally in the server,
	and so for most monitors, it isn't necessary to specify any modes
	explicitly in the Monitor section.  There is also a new Modes section
	that can be used to define a set of modes separately from the
	Monitor section, and the Monitor section may "include" them
	with the "<tt>UseModes</tt>" keyword.  The Monitor section may also
	include Options.  Options that are monitor-specific, like the
	<tt>"DPMS"</tt> and <tt>"Sync on Green"</tt> options are best
	specified in the Monitor sections.

  <item>The Device sections are mostly unchanged.  The main difference
	is the new (and mandatory) Driver keyword that specifies which
	video driver should be loaded to drive the video card.  Another
	difference is the BusID keyword that is used to specify which of
	possibly multiple video cards the Device section is for.  The
	following is an example for a Matrox card:

<quote><verb>
Section "Device"
    Identifier "MGA 1"
    Driver     "mga"
    BusID      "PCI:1:0:0"
EndSection
</verb></quote>

  <item>The Screen sections are mostly unchanged.  The old Driver keyword
	is no longer used, and a mandatory Identifier keyword has been
	added.  The DefaultColorDepth keyword has been renamed to
	DefaultDepth.

  <item>A new section called ServerLayout has been added to allow the
	layout of the screens and the selection of input devices to be
	specified.  The ServerLayout sections may also include options
	that are normally found in the ServerFlags section.  Multiple
	ServerLayout sections may be present, and selected from the command
	line.  The following example shows a ServerLayout section for a
	dual-headed configuration with two Matrox cards, and two mice:

<quote><verb>
Section "ServerLayout"
    Identifier  "Layout 1"
    Screen      "MGA 1"
    Screen      "MGA 2" RightOf "MGA 1"
    InputDevice "Keyboard 1" "CoreKeyboard"
    InputDevice "Mouse 1"    "CorePointer"
    InputDevice "Mouse 2"    "SendCoreEvents"
    Option      "BlankTime"  "5"
EndSection
</verb></quote>

See the XF86Config man page for a more detailed explanation of the format
of the new ServerLayout section.


</itemize>

The config file search patch has been extended, with the directories
<tt>/etc/X11</tt> and <tt>/usr/X11R6/etc/X11</tt> being added.  The full
search path details are documented in the XF86Config manual page.


<sect1>Command Line Options
<p>

The following new X server command line options have been added:

<quote><p>

<tt>-depth</tt> <it>n</it>
<quote><p>
	This specifies the colour depth that the server is running at.
	The default is 8 for most drivers.  Most drivers support the
	values 8, 15, 16 and 24.  Some drivers also support the values
	1 and 4.  Some drivers may also support other depths.  Note that
	the depth is different from the ``bpp'' that was specified with
	previous versions.  The depth is the number of bits in each
	pixel that are significant in determining the pixel's value.
	The bpp is the total size occupied by each pixel, including bits
	that are not used.  The old <tt>-bpp</tt> option is no longer
	recognised because it isn't a good way of specifying the server
	behaviour.

</quote>

<tt>-fbbpp</tt> <it>n</it>
<quote><p>
	This specifies the bpp format to use for the framebuffer.  This
	may be used in 24-bit mode to force a framebuffer format that is
	different from what the driver chooses by default.  In most cases
	there should be no need to use this option.

</quote>

<tt>-pixmap24</tt>
<quote><p>
	This specifies that the client-side pixmap format should be the
	packed 24-bit format that was often used by the 3.3.x servers.
	The default is the more common 32-bit format.  There should normally
	be no need to use this option.

</quote>

<tt>-pixmap32</tt>
<quote><p>
	This specifies that the client-side pixmap format should be the
	sparse 32-bit format.  This is the default, so there should
	normally be no need to use this option.

</quote>

<tt>-layout</tt> <it>name</it>
<quote><p>
	This specifies which ServerLayout section in the config file to
	use.  When this option is not specified, the first ServerLayout
	section is used.  When there is no ServerLayout section, the
	first Screen section is used.

</quote>

<tt>-screen</tt> <it>name</it>
<quote><p>
	This specifies which Screen section in the config file to
	use.  When this option is not specified, the first ServerLayout
	section is used.  When there is no ServerLayout section, the
	first Screen section is used.

</quote>

<tt>-keyboard</tt> <it>name</it>
<quote><p>
	This specifies which InputDevice section in the config file to
	use for the core keyboard.  This option may be used in conjunction
	with the <tt>-screen</tt> option.

</quote>

<tt>-pointer</tt> <it>name</it>
<quote><p>
	This specifies which InputDevice section in the config file to
	use for the core pointer.  This option may be used in conjunction
	with the <tt>-screen</tt> option.

</quote>

<tt>-modulepath</tt> <it>path</it>
<quote><p>
	This specifies the module search path.  The path should be a
	comma-separated list of absolute directory paths to search for
	server modules.  When specified here, it overrides the value
	specified in the config file.  This option is only available
	when the server is started by the <tt>root</tt> user.

</quote>

<tt>-logfile</tt> <it>file</it>
<quote><p>
	This specifies the log file name.  When specified here, it
	overrides the default value.  This option is only available when
	the server is started by the <tt>root</tt> user.

</quote>

<tt>-scanpci</tt>
<quote><p>
	This specifies that the <tt>scanpci</tt> module should be loaded and
	executed.  This does a scan of the PCI bus.

</quote>

<tt>-logverbose</tt> [<it>n</it>]
<quote><p>
	This options specifies the verbosity level to use for the log file.
	The default is 3.

</quote>

</quote>

The following X server command line options have been changed since 3.3.x:

<quote><p>

<tt>-verbose</tt> [<it>n</it>]
<quote><p>
	This option specifies the verbosity level to use for the server
	messages that get written to stderr.  It may be specified multiple
	times to increase the verbosity level (as with 3.3.x), or the
	verbosity level may be specified explicitly as a number.  The
	default verbosity level is 1.

</quote>

<tt>-xf86config</tt> <it>filename</it>
<quote><p>
	This option has been extended to allow non-root users to specify
	a relative config file name.  The config file search path will be
	used to locate the file in this case.  This makes it possible for
	users to choose from multiple config files that the the sysadmin
	has provided.

</quote>


</quote>


<sect1>XAA
<p>

The XFree86 Acceleration Architecture (XAA) has been completely rewritten
from scratch.  Most drivers implement acceleration by making use of the
XAA module.

<sect1>Multi-head
<p>
Some multi-head configurations are supported in this release, primarily
with multiple PCI/AGP cards.  However, this is an area that is still
being worked on, and we expect that the range of configurations for which
it works well will increase in future releases.  A configuration that
is known to work well in most cases is multiple (supported) Matrox cards.

One of the main problems is with drivers not sufficiently initialising
cards that were not initialised at boot time.  This has been improved
somewhat with the INT10 support that is used by most drivers (which
allows secondary card to be "soft-booted", but in some cases there are
other issues that still need to be resolved.  Some combinations can be
made to work better by changing which card is the primary card (either
by using a different PCI slot, or by changing the system BIOS's preference
for the primary card).

<sect1>Xinerama
<p>
Xinerama is an X server extension that allows multiple physical screens
to behave as a single screen.  With traditional multi-head in X11,
windows cannot span or cross physical screens.  Xinerama removes this
limitation.  Xinerama does, however, require that the physical screens
all have the same root depth, so it isn't possible, for example, to use
an 8-bit screen together with a 16-bit screen in Xinerama mode.

Xinerama is not enabled by default, and can be enabled with the
<tt>+xinerama</tt> command line option for the X server.

Xinerama was included with X11R6.4.  The version included in this release
was completely rewritten for improved performance and correctness.

Known problems:
<itemize>
  <item>Most (all?) window managers are not Xinerama-aware, and so some
	operations like window placement and resizing might not behave
	in an ideal way.  This is an issue that needs to be dealt with
	in the individual window managers, and isn't specifically an
	XFree86 problem.

</itemize>

<sect1>DGA version 2
<p>

DGA 2.0 is included in &relvers;, but is not implemented by all drivers.
Preliminary documentation for the client libraries can be found in the
<tt>README.DGA</tt> document.  A good degree of backwards compatibility
with version 1.0 is provided.


<sect1>DDC
<p>
The VESA(R) Display Data Channel (DDC&trade;) standard allows the monitor
to tell the video card (or on some cases the computer directly) about
itself; particularly the supported screen resolutions and refresh rates.

Partial or complete DDC support is available in most of the video drivers.
DDC is enabled by default, but can be disabled with a "Device" section
entry:  <tt>Option "NoDDC"</tt>.  We have support for DDC versions 1
and 2; these can be disabled independently with <tt>Option "NoDDC1"</tt>
and <tt>Option "NoDDC2"</tt>.

At startup the server prints out DDC information from the display,
but it does not yet use it the determine modelines.  For some drivers,
the X server's new <tt>-configure</tt> option uses the DDC information
when generating the config file.

Changed behavior caused by DDC. Several drivers uses DDC information to
set the screen size and pitch.  This can be overridden by explicitly
resetting it to the and non-DDC default value 75 with the <tt>-dpi
75</tt> command line option for the X server, or by specifying appropriate
screen dimensions with the "DisplaySize" keyword in the "Monitor" section
of the config file.


<sect1>GLX and the Direct Rendering Infrastructure (DRI)
<p>

<url name="Precision Insight" url="http://www.precisioninsight.com">
has been provided with funding and support from <url name="Red Hat"
url="http://www.redhat.com">, <url name="SGI" url="http://www.sgi.com">,
<url name="3Dfx" url="http://www.3dfx.com">, <url name="Intel"
url="http://www.intel.com">, <url name="ATI" url="http://www.ati.com">,
and <url name="Matrox" url="http://www.matrox.com"> to integrate the GLX
extension for 3D rendering in an X11 window.  The 3D core rendering
component is the <url name="Mesa" url="http://www.mesa3d.org"> library.
SGI has released the sources to the GLX extension framework under an
open license, which essentially provides the glue between the 3D
library and this windowing system.  Precision Insight has integrated
these components into the XFree86 X Server and added a Direct Rendering
Infrastructure (DRI).  Direct Rendering provides a highly optimized
path for sending 3D data directly to the graphics hardware.  This
release provides a complete implementation of direct rendering support
for the 3Dfx Banshee and Voodoo3 graphics cards.  Additional direct
rendering drivers will be available for 3Dfx, Intel, ATI and Matrox
boards during the second quarter of 2000.  Updated information on DRI
compatible drivers can be found at the <url name="DRI Project"
url="http://dri.sourceforge.net"> on <url name="SourceForge"
url="http://www.sourceforge.net">.

<sect1>X-Video Extension (Xv)
<p>

An XvQueryPortAttributes function has been added as well as
support for XvImages.  XvImages are XImages in alternate color spaces 
such as YUV and can be passed to the server through shared memory
segments.  This allows clients to display YUV data with high quality
hardware scaling and filtering.   XvImages are only supported
by the Matrox G200/G400 cards at the moment.

<sect1>Other extensions
<p>

The XFree86-Misc extension has not been fully ported to the new server
architecture yet.  This should be completed in a future release.

The XFree86-VidModeExtension extension has been updated, and mostly
ported to the new server architecture.  The area of mode validation
needs further work, and the extension should be used with care.  This
extension has support for changing the gamma setting at run-time, for
modes where this is possible.  The new <tt>xgamma</tt> utility makes
use of this feature.  Compatibility with the 3.3.x version of the
extension is provided.  The missing parts of this extension and some
new features should be completed in a future release.


<sect1>Drivers
<p>

XFree86 &relvers; includes the following drivers:

<table border=1 align="center">
<tabular ca="|l|l|">
   <tabrow>Driver Name<colsep>Description</tabrow>
   <hline>
   <tabrow><tt>apm</tt><colsep>Alliance Pro Motion</tabrow>
   <tabrow><tt>ati</tt><colsep>ATI</tabrow>
   <tabrow><tt>chips</tt><colsep>Chips &amp; Technologies</tabrow>
   <tabrow><tt>cirrus</tt><colsep>Cirrus Logic</tabrow>
   <tabrow><tt>cyrix</tt> (*)<colsep>Cyrix MediaGX</tabrow>
   <tabrow><tt>fbdev</tt><colsep>Linux fbdev</tabrow>
   <tabrow><tt>glide</tt><colsep>Glide2x (3Dfx)</tabrow>
   <tabrow><tt>glint</tt><colsep>3Dlabs, TI</tabrow>
   <tabrow><tt>i740</tt><colsep>Intel i740</tabrow>
   <tabrow><tt>i810</tt><colsep>Intel i810</tabrow>
   <tabrow><tt>mga</tt><colsep>Matrox</tabrow>
   <tabrow><tt>neomagic</tt><colsep>NeoMagic</tabrow>
   <tabrow><tt>nv</tt><colsep>NVIDIA</tabrow>
   <tabrow><tt>r128</tt><colsep>ATI Rage 128</tabrow>
   <tabrow><tt>rendition</tt><colsep>Rendition</tabrow>
   <tabrow><tt>s3virge</tt><colsep>S3 ViRGE</tabrow>
   <tabrow><tt>sis</tt><colsep>SiS</tabrow>
   <tabrow><tt>sunbw2</tt> (+)<colsep>Sun bw2</tabrow>
   <tabrow><tt>suncg14</tt> (+)<colsep>Sun cg14</tabrow>
   <tabrow><tt>suncg3</tt> (+)<colsep>Sun cg3</tabrow>
   <tabrow><tt>suncg6</tt> (+)<colsep>Sun GX and Turbo GX</tabrow>
   <tabrow><tt>sunffb</tt> (+)<colsep>Sun Creator, Creator3D and Elite 3D</tabrow>
   <tabrow><tt>sunleo</tt> (+)<colsep>Sun Leo (ZX)</tabrow>
   <tabrow><tt>suntcx</tt> (+)<colsep>Sun TCX</tabrow>
   <tabrow><tt>tdfx</tt><colsep>3Dfx</tabrow>
   <tabrow><tt>tga</tt><colsep>DEC TGA</tabrow>
   <tabrow><tt>trident</tt><colsep>Trident</tabrow>
   <tabrow><tt>tseng</tt><colsep>Tseng Labs</tabrow>
   <tabrow><tt>vga</tt><colsep>Generic VGA</tabrow>
</tabular>
</table>

Drivers marked with (*) are present in a preliminary form in this release,
but are not complete and/or stable yet.
<p>

Drivers marked with (+) are for Linux/Sparc only.

<sect2>APM <label id="apm">
<p>

This is the driver for Alliance AT3D/AT25 and AT24 chips. There is a rather
complete support for the functions with acceleration at 8,15,16,24 and 32 bits
(limited by the chip at 24bpp). There is preliminary, still buggy, support
for the AP6422 chip, which is still supported in 3.3.x servers. The Xv driver
is almost ok. The Rush extension for glide2x works, with some additions,
including overlay of the result. DGA and DGA2 have been tested ok.
Further information can be found in <htmlurl name="README.apm" url="apm.html">.

<sect2>Chips &amp; Technologies
<p>

Information about the C&amp;T driver can be found in <htmlurl
name="README.chips" url="chips.html">.

<sect2>s3virge
<p>

The s3virge driver is a port of the 3.3.x SVGA S3 ViRGE driver.  As
such it should be as stable and functional as previous XFree86
releases.  There are a couple additional benefits included primarily due
to common enhancements:

<itemize>
  <item>Depth 24 problems resolved with clients using 24/32 bpp pixmaps.
  <item>Our common acceleration architecture (XAA) has been re-written,
	as has the ViRGE acceleration code.  You should find this version
	has better performance than prior releases.

  <item>Multi-head is reported to work.
  <item>The <tt>s3virge</tt> man page lists options and has configuration
	notes for this release of the driver.
  <item>Trio 3D and Trio 3D/2X support has been added, matching the 3.3.6
	driver.
  <item>Supports screen rotation and shadow framebuffer.

</itemize>

Outstanding items not implemented or fully tested:

<itemize>
  <item>DGA support is implemented, but preliminary and untested.
</itemize>

Further information can be found in <htmlurl name="README.s3virge"
url="s3virge.html">.

<sect2>TGA
<p>

The TGA driver is now accelerated and supports both 8 and 32 plane
framebuffers.  It is known to work under Linux/Alpha.  Please see the
<htmlurl name="README.DECtga" url="DECtga.html"> file for further
information.

<sect2>Matrox
<p>

The MGA driver supports the same range or hardware as XFree86 3.3.4,
but has a number of enhancements including multi-head support and
support for (non-destructive) overlays (8-bit + 24-bit).

This release contains performance enhancements for the G400 and particularly
for the G400 MAX.  It also includes XvImage support for G200/G400 chips and
improved memory autodetection support.

Further information can be found in the <tt>mga</tt> <htmlurl name="man page"
url="mga.4.html">.

<sect2>ATI
<p>

Information about the ATI driver can be found in <url name="README.ati"
url="ati.html">.  The current version is not accelerated for all supported
chips.  Some acceleration is included for Mach64 chips.

<sect2>NVIDIA
<p>

The "nv" driver supports all Riva TNT accelerators as well as the GeForce
256 and Quadro accelerators (the GeForce2 and GeForce2 MX are not yet
supported).  DGA 2.0 support is included.

Further information can be found in the nv <htmlurl name="man page"
url="nv.4.html">.   

<sect2>Glide
<p>
This driver is for Voodoo 1 and Voodoo 2 boards. It runs X on top of
the 3DFX Glide API (where this is available, like for Linux). You need
to have Glide 2.x installed before you can run this driver. This
driver uses no hardware acceleration (since there is no 2D
acceleration in these boards) but is rather quick anyway since the CPU
renders to local RAM which is then copied block-wise to the
board. Unfortunately the Voodoo 1/2 boards are rather limited in
resolution. The Voodoo 1 can do 800x600 and the Voodoo 2 can do
1024x768 at best, but still it has some use as a second head in 
Xinerama or multihead mode.

16 and 24 bpp modes are supported (24 bit in 32-bit sparse-packed
mode).

Further information about this driver can be found in the 'glide' driver
man page for XFree86. You will not get this driver running before
reading this man page.

For Voodoo Banshee and Voodoo 3 boards or later: Please use the tdfx
driver which talks directly to the hardware and is much faster.

<sect2>GLINT <label id="glint">
<p>

The "glint" driver supports most 3Dlabs/Texas Instruments GLINT/Permedia
chips. There is a rather complete support (better than in 3.3.x) for
acceleration at 8, 15, 16, and 24 bit depths (limited by some chips at
some depths). 8+24 overlay is supported. The Xv extension is supported
for some boards.

Further information about this driver can be found in the 'glint' driver
man page.

<sect>X libraries and clients
<p>

<sect1>Xaw
<p>

Two versions of the Xaw library are provided in this release. A version with
bug fixes and a few binary compatible improvements and a new version with
several new features.

New features:

<itemize>

  <item>A <tt>displayList</tt> resource is available to all Xaw widgets. It
	basically consists of a list of drawing commands, fully described in
	the <tt>Xaw(3)</tt> manual page, that enables a integration of Xaw
	programs with the new window/desktop managers that allows for
	configurable themes.

  <item>Some new actions were added to all Xaw widgets, to allow more
	configurable control of the widgets, and to allow setting resources
	at run time.

  <item>Since Xpm was integrated into XFree86, programs linked with the
	new Xaw library	will also link with Xpm. This allows for color
	background pixmaps, and also for shaped widgets.

  <item>The text widget is the widget that will present more changes. These
	include:

	<itemize>

	  <item>Block cursor.

	  <item>Compile time limit of 16384 undo/redo levels (that will
		automatically grow if the text is not saved when this mark is
		reached).

	  <item>Overwrite mode.

	  <item>Text killed is inserted in a kill ring list, this text is not
		forgotten, pressing <tt>M-y</tt> allows traversing the kill
		ring list.

	  <item>International support for latin languages is available even
		if the <tt>international</tt> resource is not set. Users will
		need to properly set the <it>locale</it> environment to make
		complete use of this feature.

	  <item>A better <tt>multiply</tt> interface is provided. Pressing
		<tt>C-u,&lt;number&gt;</tt> (where number can be negative)
		allows passing parameters for text actions.

	  <item>Text can be formatted to have left, right, center or full
		justification.

	  <item>Text indentation support is also available.

	</itemize>

<!-- is this still true?
  <item>This release shows the current state of the work to add to the Xaw
	text widget WYSIWYG capabilities. The state is very initial, and
	can be seen as a candidate to a candidate to a very early alpha
	snapshot. There is no public interface for programming yet, because
	the current one is very likely to change before ready to use.
-->

</itemize>

Bug fixes:

<itemize>

  <item>The simple menu widget geometry management code was improved to solve
	problems with menu entries not visible in the screen.

  <item>The form widget geometry code was changed to solve problems with integer
	round problems in the child widgets geometry when resizing the parent
	form widget.

  <item>Several bugs were fixed in the text code, while some code was rewritten
	from scratch.

</itemize>

<p>

<sect1>Xpm
<p>

Version 3.4k of the Xpm (X pixmap) library is now integrated into XFree86.

<sect1>xterm
<p>

New Features:

<itemize>
  <item>Support Unix98 PTY's.

  <item>Support Unicode using UTF-8 input and output.  There are a few
	limitations, this work is still in progress:

	<itemize>
	  <item>You must use the <tt>-u8</tt> command line option to
		use this feature, as well as compile with the
		<tt>OPT_WIDE_CHARS</tt> definition.  (The feature is
		compiled when using imake).

	  <item>Input (from keyboard) and output (select/paste) are in
		UTF-8 form.  There is no support in Xlib for UTF-8;
		xterm uses a lookup table to map keysym codes.
		Select/paste is done either via <tt>STRING</tt> or using
		the new atom <tt>UTF8_STRING</tt>.

	</itemize>

  <item>Add optional feature (resource and command-line options) to make
	xterm use the PTY's sense of erase character on startup, rather
	than requiring it to be <tt>\177</tt>, or set the PTY's erase
	character to match xterm's configuration.  Note that while
	<tt>$TERMCAP</tt> is modified to reflect the actual configuration,
	the terminfo <tt>kdch1</tt> string is not.  (This feature is
	also in XFree86 3.3.4).

  <item>Revised keyboard handling, making two modes (VT220 and Sun/PC) which
	are switched by popup menu.  This makes the numeric keypad work as
	expected.  Codes sent by the backarrow and delete keys also are
	affected.

  <item>Add parameters to function key escape sequences to indicate if
	shift, control or alt are set.  This works for Sun/PC keyboard
	mode.

  <item>Separated command-line and menu settings for reverse video from that
	done under program control.  This is a problem which was introduced
	by X11R6.  Though correct, most users are confused by allowing
	the reset command to undo the effect of the command-line
	<tt>-rv</tt> option.

  <item>Blinking cursor can be specified by resource or popup menu.

  <item>New control sequences for switching between normal and alternate
	screens maintain separate cursor-save locations for the two screens,
	avoiding incorrect cursor placement on exit from vi.

  <item>Support line-drawing characters when the font does not include them
	by drawing them.

  <item>Add support for switching font sizes, by stepping through the font
	menu using shifted keypad plus and minus.

  <item>New resource <tt>trimSelection</tt> allows xterm to trim trailing
	blanks from selected lines.

  <item>Provide user applications a means of determining the version of xterm
	for feature comparison by returning the patch number (e.g., 111) in
	the secondary DA response.

  <item>Modify treatment of <tt>XK_Delete</tt> keysym so it transmits
	parameterized VT220-style "<tt>&lt;esc&gt;[3~</tt>" if modifiers
	(shift, control alt) are given.

  <item>Add ``cacheDoublesize'' resource to limit the caching of font
	information for double-sized characters, to accommodate X terminals
	with limited font memory.

  <item>Add ``metaSendsEscape'' resource, with corresponding control sequence
	and menu entry.  Like ``eightBitInput'', this causes xterm to send ESC
	prefixing the given key, but applies to all keys and is independent
	of the 8-bit/7-bit terminal setting.

  <item>Implement an 88-color model for systems where 256-colors cannot be
	allocated.

  <item>Add support for DEC Locator control sequences for xterm.  This allows
	the xterm mouse to be used with applications that use the DEC Locator
	sequences, such as VAX Tpu, or SMG$ based applications.

  <item>Implement <tt>-hold</tt> option, allowing users to retain the window
	after a shell has exited.

  <item>Add an application resource, ``messages'' (and a corresponding
	<tt>-</tt>/<tt>+mesg</tt> option) which controls the initial
	permission on the terminal.

  <item>Implement UTF-8 translation for Media Copy (print) operations.

  <item>Implement vt320 control sequences for Print Composed Main Display and
	for Print All Pages.  The latter directs xterm to print the current
	screen as well as the scrollback buffer.

</itemize>

Bug fixes/improvements:

<itemize>
  <item>If <tt>colorMode</tt> is enabled by default, compile-in default
	resources to match the colors listed in <tt>XTerm-col.ad</tt>.

  <item>Deprecate DA answerback string, making it settable via a resource
	value for applications which may need this.

  <item>Input characters which are mapped when in vt220 National Replacement
	Character mode.

  <item>Completed support for double size characters.

  <item>Remove <tt>kfnd</tt>/<tt>kll</tt>/<tt>kslt</tt> strings from
	terminfo, because curses applications do not necessarily return
	<tt>khome</tt>/<tt>kend</tt> pairs.

  <item>Corrected ifdef's for menus, which did not allow tek4014 to be
	suppressed properly.

  <item>Improved tests for determining if xterm should use overstriking to
	simulate bold fonts.

  <item>Add test/demo scripts for double size characters, font switching,
	screen resizing and colors.

  <item>Amend treatment of ALT key so that if ALT is used as a modifier in
	key translations, then no parameter will be sent in escape sequences
	for Sun/PC function keys.

  <item>Improved the ptyInitialErase logic to make it work better with
	a terminfo library.

  <item>Modify treatment of line-drawing characters in UTF-8 mode so that
	Unicode values are used rather than characters 1-31 for storing the
	translated characters.

  <item>Modify translation of UTF-8 sequences to reject ``overly long''
	variations.

  <item>Correct a case where colors were not rendered properly.  This
	happened when an application inserted several lines, then changed
	colors.  If this was done all in one write, then there would be no
	intervening refresh, and the new color was applied to the pending
	scrolling operation which was awaiting the next refresh.

  <item>Corrected misspelled resource name in command-line option for HP
	function keys.

  <item>Change label on ``Sun/PC Keyboard'' popup menu entry to ``VT220
	Keyboard'', since the checked state corresponds to VT220 rather than
	Sun/PC.

  <item>Two corrections to simulation of bold font via overstriking:

	<itemize>

	  <item>use clipping to avoid leaving trash at end of the text, and

	  <item>add brackets so wide-character logic does not fall-through
		into the overstriking logic.

	</itemize>

  <item>Modify checks for repeat-character control sequence to test the
	character class against xterm's state table, rather than the
	<tt>isprint()</tt> macro.

  <item>Modify terminfo entry for ``xterm-xfree86'' to reflect modifiers for
	shift and control.

  <item>Add several entries to termcap file to make it have the same set
	of aliases as the terminfo file.

  <item>Scale the color values used for xterm-256color terminfo entry to
	0..1000, as expected by ncurses.

  <item>Change xterm-r6 terminfo definitions for F1-F4 to match program.

  <item>Remove obsolete documentation about modifiers which can be returned
	in mouse tracking mode, and modify logic to ignore modifiers other
	than the existing ones, e.g., NumLock.

  <item>Use free bit from obsolete shift-modifier coding of mouse tracking
	button events to encode buttons 4 and 5, e.g., for a wheel mouse.
	Move the suggested wheel-mouse button translations into charproc.c to
	simplify customization.

  <item>Modify warning if change-ownership of PTY fails; some
	configurations may not happen to have old-style PTY's.

  <item>Add more information, i.e., with strerror for some system calls in
	the main program which may fail due to insufficient permissions.

  <item>Various improvements to configure script, e.g., tests for utmp.

</itemize>

<sect1>xedit
<p>

Xedit have been changed to use most of the new features added to the new
version of the Xaw library, and some xedit only features were added. Emacs
users will find that several of the emacs key bindings work with the new
version of xedit. These include:

<itemize>

  <item>File name tab completion. Including a <it>Emacs dired</it> like window,
	that will be shown when there are more than one match, when
	<tt>C-x,d</tt> is pressed, or when a directory name is specified.

  <item>An unlimited number of files can be edited at the same time. Including
	multiple views of the same or different files.

  <item>The line number of the cursor position is always visible. It can also
	be customized to show the column number, the position offset and the
	current size of the file.

  <item>There is an <tt>autoReplace</tt> resource, that enables automatic text
	replacement at the time text is typed. This feature is useful to create
	simple macros, or to correct common spelling errors.

  <item>A fully featured ispell interface is also available. This interface
	is expected to provide most of the features of the terminal interface
	of the ispell program, with some extra features that include:

	<itemize>

	  <item>A compile time limit of 16 undo levels.

	  <item>Terse mode switch.

	  <item>Dictionary change.

	  <item>The interface also checks for repeated words.

	</itemize>

  <item>A first tentative to add programming modes was done. Currently, there
	is one mode:
	<itemize>

	  <item><bf>C-mode:</bf> this mode is expected to be stable, and fully
		usable.
<!--  This was removed, right?

	  <item><bf>Html-mode:</bf> a lot of work needs to be done yet. It is
		included in this snapshot only to show what the new text widget
		capabilities can do.
-->
	</itemize>

</itemize>

<p>


<sect>Fonts and Internationalisation
<p>

Details about the font support in this version of XFree86 can be found
in the <htmlurl name="README.fonts" url="fonts.html"> document.

<sect1>TrueType support
<p>

This version of XFree86 comes with two TrueType backends, known as
`xfsft' (the <tt>"freetype"</tt> module) and `X-TrueType' (the
<tt>"xtt"</tt> module).  Both of these backends are based on the FreeType
library.

<sect1>CID font support
<p>

Support for CID-keyed fonts is included in this version of XFree86.
The CID-keyed font format was designed by <url name="Adobe Systems"
url="http://www.adobe.com"> for fonts with large character sets.  The
CID-keyed font support in XFree86 was donated by <url name="SGI"
url="http://www.sgi.com">.  See the <htmlurl name="LICENSE"
url="LICENSE.html"> document for a copy of the CID Font Code Public
License.

<sect1>Internationalisation of the scalable font backends
<p>

A new ``fontenc'' layer has been added to allow the scalable font backends
to use a common method of font re-encoding.  This re-encoding makes it
possible to uses fonts in encodings other than their their native
encoding.  This layer is used by the Type1 and Speedo backends and the
`xfsft' version of the TrueType backend.  The `X-TrueType' version of
the TrueType backend uses a different re-encoding method based on loadable
encoding modules.

<sect1>Large font optimisation
<p>

The glyph metrics array, which all the X clients using a particular font
have access to, is now placed in shared memory, so as to reduce redundant
memory consumption.  For non-local clients, the glyph metrics array is
transmitted in a compressed format.

<sect1>Unicode/ISO 10646 support
<p>
What is included:

<itemize>
  <item>All ``-misc-fixed-*'' BDF fonts are now available in the
        ISO10646-1 encoding and cover at least the 614 characters
        found in ISO 8859-{1-5,7-10,14,15}, CP1252, and MES-1. The
        non-bold fonts also cover all Windows Glyph List 4 (WGL4)
        characters, including those found in all 8-bit MS-DOS/Windows
        code pages. The 8-bit variants of the ``-misc-fixed-*'' BDF
        fonts (ISO8859-1, ISO8859-2, KOI8-R, etc.) have all been
        automatically generated from the new ISO10646-1 master fonts.

  <item>Some ``-misc-fixed-*'' BDF ISO10646-1 fonts now cover a
        comprehensive Unicode repertoire of over 3000 characters
        including all Latin, Greek, Cyrillic, Armenian, Gregorian,
        Hebrew, IPA, and APL characters, plus numerous scientific,
	typographic, technical, and backwards-compatibility
        symbols. Some of these fonts also cover Arabic, Ethiopian,
        Thai, Han/Kanji, Hangul, full ISO 8859, and more. For the 6x13
        font there is now a 12x13ja Kanji extension and for the 9x18
        font there is a 18x18ja Kanji/Han/Hangul extension, which
        covers all ISO-2022-JP-2 (RFC 1554) characters. The 9x18 font
        can also be used to implement simple combining characters by
        accent overstriking. For more information, read Markus Kuhn's
        <url name="UTF-8 and Unicode FAQ"
        url="http://www.cl.cam.ac.uk/~mgk25/unicode.html">.

  <item>Mark Leisher's ClearlyU proportional font (similar to Computer
	Modern).

  <item>ISO 10646/Unicode UTF-8 Level 1 support added to xterm
	(enabled with the <tt>-u8</tt> option).

  <item>Both the xfsft (the <tt>"freetype"</tt> module) and the X-TrueType
	(the <tt>"xtt"</tt> module) TrueType font backends support
	Unicode-encoded fonts.

</itemize>

Known problems:

<itemize>
  <item>Xlib does not yet fully support UTF-8 as a locale, which means that
	xterm UTF-8 keyboard support is at the moment a temporary hack.

  <item>Most ISO10646-1 fonts encode no characters above U+31FF. This
        avoids the inefficient allocation and transmission of a
        >700 kB large XFontStruct structure, which would happen if the
        (not very important) ligatures and symbols above U+f000 were
        present.

  <item>ISO 10646 Level 2 combining characters are not yet supported by
	xterm (will be needed for instance for Thai and IPA).

  <item>Switching between a half-width and full-width font pair (such
        as 9x18 and 18x18ja) is not yet supported by xterm (will be
        needed for CJK scripts).

</itemize>

<sect1>Lucidux fonts from Bigelow and Holmes
<p>

XFree86 now includes the ``Lucidux'' family of professionally hinted
Type 1 fonts.  This family consists of the fonts ``Lucidux Serif'',
``Lucidux Sans'' and ``Lucidux Mono'' in Roman and oblique variants,
and includes over 370 glyphs in each font covering among others the
glyphs needed for ISO 8859-1, 2, 3, 4, 9 and 15.  Bold variants will be
included in a future release.  The design and font outlines were donated
by Charles Bigelow and Kris Holmes from Bigelow and Holmes Inc., and
the hinting was donated by Berthold Horn and Blenda Horn from Y&amp;Y, Inc.
For more information, please contact
<email>design@bigelowandholmes.com</email> or
<email>sales@yandy.com</email>, or consult <url name="Y&amp;Y's web site"
url="http://www.yandy.com">.

<sect>Miscellaneous
<p>

<sect1>Directory rearrangements
<p>

Some changes to the installed XFree86 directory structure have been
implemented for 4.0.
One important
change is a modified search path for the X
server's <tt>XF86Config</tt> file.  The details of this can be found
in the XF86Config manual page.  The other main change is moving
most of the run-time configuration files to <tt>/etc/X11</tt>, with
symbolic links in the old <tt>/usr/X11R6/lib/X11</tt> location pointing
to the new location.  Some run-time generated files are now located
under the appropriate subdirectories of <tt>/var</tt>, again with the
relevant symbolic links in the old location.




</article>