cygwin-x-doc/faq config.xml, 1.6, 1.7 cygwin-x-faq.xml, 1.2,
1.3 errors.xml, 1.7, 1.8 general.xml, 1.3, 1.4 i18n.xml, 1.3,
1.4 install.xml, 1.2, 1.3 licptc.xml, 1.3, 1.4 porting.xml,
1.2, 1.3 remote.xml, 1.3, 1.4
Harold L Hunt II
xserver-commit at pdx.freedesktop.org
Fri Apr 2 23:14:29 PST 2004
Committed by: harold
Update of /cvs/xserver/cygwin-x-doc/faq
In directory pdx:/tmp/cvs-serv28816/faq
Modified Files:
config.xml cygwin-x-faq.xml errors.xml general.xml i18n.xml
install.xml licptc.xml porting.xml remote.xml
Log Message:
Remove old information, add simpler answer to OpenSSH 3.8 question.
Index: config.xml
===================================================================
RCS file: /cvs/xserver/cygwin-x-doc/faq/config.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -d -r1.6 -r1.7
--- a/config.xml 29 Feb 2004 14:20:53 -0000 1.6
+++ b/config.xml 3 Apr 2004 07:14:26 -0000 1.7
@@ -7,12 +7,12 @@
</question>
<answer>
-<para>The configfile support was only limited. Because of this and extra
-dependencies it was removed again. But most of the options which were
-configurable in the configfile are now available as commandline options.
-For more information on configuring other keyboard layout see
-<xref linkend="q-non-U.S.-keyboard-layout"></xref></para>
-</answer>
+<para>The configfile support was only limited. Because of this and
+extra dependencies it was removed again. But most of the options
+which were configurable in the configfile are now available as
+commandline options. For more information on configuring other
+keyboard layout see <xref
+linkend="q-non-U.S.-keyboard-layout"></xref></para> </answer>
</qandaentry>
@@ -61,6 +61,7 @@
</answer>
</qandaentry>
+
<qandaentry>
<question id="window-auto-focus">
<para>Is there a Focus-Follows-Mouse feature (Auto-Focus)?</para>
@@ -75,6 +76,7 @@
</answer>
</qandaentry>
+
<qandaentry>
<question id="disable-terminate-server">
<para>The option -nounixkill has no effect. How can i prevent the server
Index: cygwin-x-faq.xml
===================================================================
RCS file: /cvs/xserver/cygwin-x-doc/faq/cygwin-x-faq.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- a/cygwin-x-faq.xml 16 Mar 2004 03:03:26 -0000 1.2
+++ b/cygwin-x-faq.xml 3 Apr 2004 07:14:26 -0000 1.3
@@ -93,6 +93,14 @@
<revhistory id="revision-history">
<revision>
+<revnumber>1.0.16</revnumber>
+<date>2003-04-03</date>
+<authorinitials>harold at codeweavers.com</authorinitials>
+
+<revremark>Update the ssh instructions. Remove old entries.</revremark>
+</revision>
+
+<revision>
<revnumber>1.0.15</revnumber>
<date>2003-03-09</date>
<authorinitials>huntharo at msu.edu</authorinitials>
Index: errors.xml
===================================================================
RCS file: /cvs/xserver/cygwin-x-doc/faq/errors.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -d -r1.7 -r1.8
--- a/errors.xml 16 Mar 2004 03:03:26 -0000 1.7
+++ b/errors.xml 3 Apr 2004 07:14:26 -0000 1.8
@@ -20,7 +20,7 @@
following to the <quote>Pass 0 rules</quote>section:
<screen>
; X Windows
-*,*,XWin.exe,*,*,cygwin/xfree86,WheelStd,0,9
+*,*,XWin.exe,*,*,&project;,WheelStd,0,9
</screen>
</para>
@@ -30,21 +30,6 @@
<qandaentry>
-<question id="q-cygncurses5.dll-not-found">
-<para>A required DLL file: cygncurses5.dll cannot be found</para>
-</question>
-
-<answer>
-<para>Upgrading from ncurses-5.2-5 to ncurses-5.2-7 requires following
-some <ulink url="&cygwin-url-ncurses-upgrade;">special
-instructions</ulink>; failure to follow those instructions will cause
-the above error message when running various &cygwin; and &project;
-programs.</para>
-</answer>
-</qandaentry>
-
-
-<qandaentry>
<question id="q-owner-tmp-.X11-unix">
<para><errorname>_XSERVTransmkdir: Owner of /tmp/.X11-unix should be
set to root</errorname></para>
@@ -210,27 +195,6 @@
<qandaentry>
-<question id="q-status-integer-divide-by-zero">
-<para><errorname>Exception:
-STATUS_INTEGER_DIVIDE_BY_ZERO</errorname></para>
-</question>
-
-<answer>
-<para>You are most likely running your primary &windows; display at a
-bit depth that requires palettized color, most likely 8 bits per
-pixel, in conjunction with a release of &project; that does not
-support palettized color modes. Palettized color support was added to
-&project; on 2001-06-05. You may either install a newer version of
-&project; that supports palettized color, or you may run your primary
-Windows display at 15, 16, 24, or 32 bits per pixel.</para>
-</answer>
-<answer>
-<para>See <xref linkend="q-status-access-violation"></xref></para>
-</answer>
-</qandaentry>
-
-
-<qandaentry>
<question id="q-status-access-violation">
<para><errorname>Exception: STATUS_ACCESS_VIOLATION</errorname></para>
</question>
Index: general.xml
===================================================================
RCS file: /cvs/xserver/cygwin-x-doc/faq/general.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- a/general.xml 29 Dec 2003 22:21:08 -0000 1.3
+++ b/general.xml 3 Apr 2004 07:14:26 -0000 1.4
@@ -23,7 +23,7 @@
<para>Cygwin tools are, in the words of the <ulink
url="&cygwin-home;">&cygwin; homepage</ulink>, <quote>ports of the
popular GNU development tools and utilities for Windows 95, 98, and
-NT. They function by using the &cygwin; library which provides a
+NT. They function by using the &cygwin; library which provides a
<acronym>UNIX</acronym>-like API on top of the Win32 API.</quote>
&cygwin; provides the compiler (gcc), libraries, headers, and other
utilities which build and support the operation of &project;.</para>
@@ -35,6 +35,7 @@
<question id="q-what-is-x-window-system">
<para>What is the &x-window-system;?</para>
</question>
+
<answer>
<blockquote>
<attribution><citation>ScheiflerGettys92</citation></attribution>
@@ -52,6 +53,7 @@
<question id="q-what-is-x-server">
<para>What is an X Server?</para>
</question>
+
<answer>
<para>An X Server is a program that provides display and user input
services to other programs. In comparison, a file server provides
@@ -70,6 +72,7 @@
<question id="q-what-is-x-client">
<para>What is an X client?</para>
</question>
+
<answer>
<para>An X client is a program that utilizes the display and user
input services provided by an X Server. X clients may run on the same
Index: i18n.xml
===================================================================
RCS file: /cvs/xserver/cygwin-x-doc/faq/i18n.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- a/i18n.xml 8 Mar 2004 14:52:21 -0000 1.3
+++ b/i18n.xml 3 Apr 2004 07:14:26 -0000 1.4
@@ -9,36 +9,36 @@
<para>How do I use a non-U.S. keyboard layout?</para>
</question>
<answer>
-<para>
-Some keyboard layouts are configured according to the Windows keyboard settings.
-For these layouts no special change is needed.
-For all other layouts there is the possibility to configure the layout via
-commandline options.
-</para>
-<para>
-The mainoption for changing the layout is
-<parameter>-xkblayout <replaceable>countrycode</replaceable></parameter>
-where <replaceable>countrycode</replaceable> is in most cases the 2 character
-code which also represents the country in internet adresses (e.g.
-Australia = au, Deutschland = de, France = fr, Japan = jp, United Kingdom = uk).
-</para>
-<para>
-Other options for tweaking the XKB layout are
+<para>Some keyboard layouts are configured according to the Windows
+keyboard settings. For these layouts no special change is needed.
+For all other layouts there is the possibility to configure the layout
+via commandline options.</para>
+
+<para>The mainoption for changing the layout is <parameter>-xkblayout
+<replaceable>countrycode</replaceable></parameter> where
+<replaceable>countrycode</replaceable> is in most cases the 2
+character code which also represents the country in internet adresses
+(e.g. Australia = au, Deutschland = de, France = fr, Japan = jp,
+United Kingdom = uk).</para>
+
+<para>Other options for tweaking the XKB layout are
<parameter>-xkbmodel</parameter>,<parameter>-xkbvariant</parameter>,
-<parameter>-xkboptions</parameter> and <parameter>-xkbrules</parameter>.
-These are the counterparts for the similar named options known from the
-XF86Config file.
-</para>
-<para>If the loading fails, check <xref linkend="q-xkb-not-working"></xref>
-</para>
+<parameter>-xkboptions</parameter> and
+<parameter>-xkbrules</parameter>. These are the counterparts for the
+similar named options known from the XF86Config file.</para>
+
+<para>If the loading fails, check <xref
+linkend="q-xkb-not-working"></xref></para>
</answer>
</qandaentry>
+
<qandaentry>
<question id="q-modmap-obtaining">
<para>Where can I find an xmodmap for my non-U.S. keyboard layout?</para>
</question>
+
<answer>
<para>You can try using an xmodmap file for your keyboard layout from
a GNU/Linux distribution (e.g. RedHat).</para>
@@ -57,6 +57,7 @@
<para>How do I get my non-U.S. keyboard modmap to be installed when
using xdmcp?</para>
</question>
+
<answer>
<para>See <xref linkend="q-non-U.S.-keyboard-layout"></xref></para>
</answer>
@@ -68,6 +69,7 @@
<para>Logging into AIX via XDMCP causes the keyboard to function as if
<keycap>AltGr</keycap> is permanently pressed.</para>
</question>
+
<answer>
<para>[Pavel Rybnicek] The X Keyboard Extension doesn't work with AIX.
The X Keyboard Extension is enabled by default, so you must disable it
@@ -83,41 +85,54 @@
<question id="q-xkb-not-working">
<para>Loading XKB keymaps fails</para>
</question>
+
<answer>
-<para>
-First check if you are able to change the server to another layout via XKB.
-The german layout will be good for testing:
-<screen>setxkbmap de -model pc105
+<para>First check if you are able to change the server to another
+layout via XKB. The german layout will be good for testing:
+
+<screen>
+setxkbmap de -model pc105
</screen>
+
This worked if pressing "Shift" and "8" produces "(" instead of "*".
-If it worked then you can skip the next paragraph.
-</para>
-<para>
-There is currently a problem with the /tmp directory mounted in textmode.
-You can change the setting to binmode with:
-<screen>mount -b "$(cygpath -m /tmp)" /tmp
+If it worked then you can skip the next paragraph.</para>
+
+<para>There is currently a problem with the /tmp directory mounted in
+textmode. You can change the setting to binmode with:
+
+<screen>
+mount -b "$(cygpath -m /tmp)" /tmp
</screen>
+
If this fails with an errormessage stating unsufficient rights, try
-<screen>mount -b -u "$(cygpath -m /tmp)" /tmp
+
+<screen>
+mount -b -u "$(cygpath -m /tmp)" /tmp
</screen>
+
</para>
-<para>
-Not all keyboard layouts are tested very well and some contain errors or do
-not work at all. To test if the compiling of your layout works start
-<screen>xkbcomp -w 3 -xkm -m <replaceable>de</replaceable> /etc/X11/xkb/keymap/xfree86 localhost:0.0
+
+<para>Not all keyboard layouts are tested very well and some contain
+errors or do not work at all. To test if the compiling of your layout
+works start
+
+<screen>
+xkbcomp -w 3 -xkm -m <replaceable>de</replaceable> /etc/X11/xkb/keymap/xfree86 localhost:0.0
</screen>
-(replace the "de" with your layout code).
-This may produce warnings, but must not produce errors. If there are errors
-then please report them to the mailinglist.
-</para>
+
+(replace the "de" with your layout code). This may produce warnings,
+but must not produce errors. If there are errors then please report
+them to the mailinglist.</para>
</answer>
</qandaentry>
+
<qandaentry>
<question id="alt-gr-win-xp-powertoys">
<para>I have Windows XP with Powertoys installed and AltGr does not work.
What can I do?</para>
</question>
+
<answer>
<para>This problem is solved in recent Cygwin/X releases. Use cygwin setup to
upgrade the XFree86-xserv package.
@@ -125,23 +140,31 @@
</answer>
</qandaentry>
+
<qandaentry>
<question id="alt-gr-with-old-x">
<para>AltGr does not work properly when connecting to other unices or to old
XFree86.</para>
</question>
+
<answer>
-<para>The older X11 releases on the various commercial unices define the AltGr
-key as ModeSwitch, MetaR, AltR or similar. Cygwin/X expects it to be
-ISO_Level3_Switch. For reasons unknown to us this is reset when loggin into
-the remote host. As far as we don't have access to such a machine we are unable
-to track this down and find a reason.
-</para>
-<para>
-Sometimes it does help to run <screen>DISPLAY=:0.0 setxkbmap <replaceable>languagecode</replaceable>
+
+<para>The older X11 releases on the various commercial unices define
+the AltGr key as ModeSwitch, MetaR, AltR or similar. Cygwin/X expects
+it to be ISO_Level3_Switch. For reasons unknown to us this is reset
+when loggin into the remote host. As far as we don't have access to
+such a machine we are unable to track this down and find a
+reason.</para>
+
+<para>Sometimes it does help to run
+
+<screen>
+DISPLAY=:0.0 setxkbmap <replaceable>languagecode</replaceable>
</screen>
-from a cygwin shell. For more information see <xref linkend="q-non-U.S.-keyboard-layout"/>.
-</para>
+
+from a cygwin shell. For more information see <xref
+linkend="q-non-U.S.-keyboard-layout"/>.</para>
+
</answer>
</qandaentry>
@@ -188,6 +211,7 @@
<para>How do I put <command>bash</command> into <quote>8 bit</quote>
mode?</para>
</question>
+
<answer>
<para>See <xref linkend="q-bash-extended-chars"></xref></para>
</answer>
Index: install.xml
===================================================================
RCS file: /cvs/xserver/cygwin-x-doc/faq/install.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- a/install.xml 29 Dec 2003 22:21:08 -0000 1.2
+++ b/install.xml 3 Apr 2004 07:14:26 -0000 1.3
@@ -5,6 +5,7 @@
<question id="q-windows-versions-supported">
<para>What versions of Windows does &project; run on?</para>
</question>
+
<answer>
<para>&project; supports Windows 95, Windows 98, Windows Me, Windows
NT 4.0, Windows 2000, Windows XP, and Windows Server 2003 as of
Index: licptc.xml
===================================================================
RCS file: /cvs/xserver/cygwin-x-doc/faq/licptc.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- a/licptc.xml 29 Dec 2003 22:26:16 -0000 1.3
+++ b/licptc.xml 3 Apr 2004 07:14:26 -0000 1.4
@@ -24,9 +24,9 @@
</question>
<answer>
-<para>&xfree; source code is generally licensed under an <ulink
-url="&x-url-license;">X11 style license</ulink>, which is <ulink
-url="&fsf-url-licenses;">certified by the Free Software
+<para>&x-window-system; source code is generally licensed under an
+<ulink url="&x-url-license;">X11 style license</ulink>, which is
+<ulink url="&fsf-url-licenses;">certified by the Free Software
Foundation</ulink> as compatible with the <acronym>GNU</acronym>
<acronym>GPL</acronym>.</para>
</answer>
Index: porting.xml
===================================================================
RCS file: /cvs/xserver/cygwin-x-doc/faq/porting.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- a/porting.xml 9 Nov 2003 23:34:33 -0000 1.2
+++ b/porting.xml 3 Apr 2004 07:14:26 -0000 1.3
@@ -18,6 +18,7 @@
<question id="q-ported-software-list">
<para>Is there a list of software that has been ported to &project;?</para>
</question>
+
<answer>
<para>Yes, see the <ulink
url="&project-url-ported-software;">&project; - Ported
@@ -30,6 +31,7 @@
<question id="q-how-to-port">
<para>How do I start porting software to &project;?</para>
</question>
+
<answer>
<para>&project; provides a software interface that is very similar to
the software interface provided by &linux; and other &unix; systems.
@@ -45,6 +47,7 @@
<para>Are there common problems encountered when porting software to
&project;?</para>
</question>
+
<answer>
<para>One common problem encountered when porting software to
&project; is due to &cygwin;'s inability to distinguish between files
@@ -55,7 +58,7 @@
<title>Include Problems</title>
<para>This example is based off an error that actually occurred in the
-&xfree; source code tree in
+source code tree in
<filename>xc/programs/Xserver/Xext/xvmc.c</filename>.
<filename>xvmc.c</filename> included <filename>XvMC.h</filename>, as
shown below:</para>
@@ -89,6 +92,4 @@
</answer>
</qandaentry>
-
-
</qandadiv>
Index: remote.xml
===================================================================
RCS file: /cvs/xserver/cygwin-x-doc/faq/remote.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- a/remote.xml 8 Mar 2004 13:27:29 -0000 1.3
+++ b/remote.xml 3 Apr 2004 07:14:26 -0000 1.4
@@ -3,75 +3,118 @@
<qandaentry>
<question id="q-ssh-no-x11forwarding">
-<para> X11Forwarding does not work with openssh</para>
+<para>X11Forwarding does not work with OpenSSH under &cygwin;</para>
</question>
+
<answer>
-<para>
-Before establishing the ssh connection the xserver must be started and the
-environment variable <parameter>DISPLAY</parameter> must be set for ssh.
+<label>A1:</label>
+
+<para>OpenSSH 3.8 enables trusted X11 forwarding by default when
+connecting to an ssh server that supports trusted X11 forwarding.
+Most ssh servers for &linux; are versions of OpenSSH that do support
+trusted X11 forwarding, so using OpenSSH 3.8 from Cygwin will result
+in a connection that uses trusted X11 forwarding by default. You will
+quickly notice that this is the case if most of your X applications
+are now killed when you try to copy and paste or if
+<command>xdpyinfo</command> returns only a fraction of the supported
+extensions that it does if run locally.</para>
+
+<para>It is easiest to just override trusted X11 forwarding by passing
+<parameter>-Y</parameter> to <command>ssh</command> in place of
+<parameter>-X</parameter>. The <parameter>-Y</parameter> does the
+same thing as <parameter>-X</parameter>, but it disables trusted X11
+forwarding for the current connection.</para>
+</answer>
+
+
+<answer>
+<label>A2:</label>
+
+<para>Before establishing the ssh connection the xserver must be
+started and the environment variable <parameter>DISPLAY</parameter>
+must be set for ssh.
+
<screen>
$ DISPLAY=<replaceable>localhost:0.0</replaceable>
$ export DISPLAY
$ ssh -X <replaceable>remotehost</replaceable>
</screen>
+
or
+
<screen>
$ DISPLAY=<replaceable>localhost:0.0</replaceable> ssh -X <replaceable>remotehost</replaceable>
</screen>
+
</para>
-</answer>
+</answer>
<answer>
-<para>
-Make sure you're not starting ssh with the parameter <parameter>-x</parameter>.
-This disables <glossterm linkend="gloss-x11forwarding">X11Forwarding</glossterm>.
-The correct parameter is <parameter>-X</parameter> (uppercase).
-</para>
+<label>A3:</label>
+
+<para>Make sure you're not starting ssh with the parameter
+<parameter>-x</parameter>. This disables <glossterm
+linkend="gloss-x11forwarding">X11Forwarding</glossterm>. The correct
+parameter is <parameter>-X</parameter> (uppercase).</para>
</answer>
<answer>
-<para>
-Check that X11Forwarding is not disabled in the openssh client configuration.
+<label>A4:</label>
-The configfiles are by default <filename>~/.ssh/config</filename> and
-<filename>/etc/ssh_config</filename>. The file in the home directory
-overrides settings in the global one.
+<para>Check that X11Forwarding is not disabled in the openssh client
+configuration.</para>
-The configfile is split into various sections starting with
-<quote>Host <replaceable>wildcard</replaceable></quote>.
-The section applies to all hosts where <replaceable>wildcard</replaceable>
-matches the hostname.
+<para>The configfiles are by default
+<filename>~/.ssh/config</filename> and
+<filename>/etc/ssh_config</filename>. The file in the home directory
+overrides settings in the global one.</para>
-If this section contains an entry <quote>ForwardX11 no</quote> then
-X11Forwarding is disabled. To enable it change the entry to
-<screen>ForwardX11 yes</screen>
+<para>The configfile is split into various sections starting with
+<quote>Host <replaceable>wildcard</replaceable></quote>. The section
+applies to all hosts where <replaceable>wildcard</replaceable> matches
+the hostname.</para>
+
+<para>If this section contains an entry <quote>ForwardX11 no</quote>
+then X11Forwarding is disabled. To enable it change the entry to:
</para>
-<para>
-Starting with OpenSSH 3.8 you will need the switch <quote>ForwardX11Trusted
-yes</quote> in the client configuration to allow remote clients full access
-to the xserver. Without it some clients will fail with a similar error:
+
+<screen>
+ForwardX11 yes
+</screen>
+
+<para>Starting with OpenSSH 3.8 you will need the switch
+<quote>ForwardX11Trusted yes</quote> in the client configuration to
+allow remote clients full access to the xserver. Without it some
+clients will fail with a similar error:</para>
+
<screen> X Error of failed request: BadAtom (invalid Atom parameter)
Major opcode of failed request: 18 (X_ChangeProperty)
Atom id in failed request: 0x114
Serial number of failed request: 370
Current serial number in output stream: 372
</screen>
-</para>
</answer>
<answer>
-<para>
-Check that X11Forwarding is not disabled in the ssh server configuration.
+<label>A5:</label>
-The configfile is by default <filename>/etc/ssh/ssh_config</filename>.
-If there is an entry <quote>X11Forwarding no</quote> then X11Forwarding is
-disabled.
+<para>Check that X11Forwarding is not disabled in the ssh server
+configuration.</para>
+
+<para>The configfile is by default
+<filename>/etc/ssh/ssh_config</filename>. If there is an entry
+<quote>X11Forwarding no</quote> then X11Forwarding is
+disabled. </para>
+
+<para>If you have write access to the config file then change it to
+
+<screen>
+X11Forwarding yes
+</screen>
+
+Otherwise ask your you admin to change this for you.</para>
-If you have write access to the config file then change it to
-<screen>X11Forwarding yes</screen>
-Otherwise ask your you admin to change this for you.
-</para>
</answer>
</qandaentry>
@@ -85,6 +128,7 @@
<para><errorname>XDMCP fatal error: Session declined No valid
address</errorname></para>
</question>
+
<answer>
<para>&project; is sometimes unable to determine which local network
interface's address should be reported to the <glossterm
@@ -95,10 +139,12 @@
</answer>
</qandaentry>
+
<qandaentry>
<question id="q-mandrake-8.1-xdmcp">
<para>I get no login screen when using <parameter>-query</parameter></para>
</question>
+
<answer>
<para>[Mika Laitio] For security reasons, XDMCP is not enabled by
default on most Linux/UNIX/*NIX/*BSD distributions (RedHat, Mandrake,
@@ -206,6 +252,7 @@
</answer>
</qandaentry>
+
<qandaentry>
<question id="q-solaris-fonts">
<para>I get no login screen for Solaris</para>
@@ -250,6 +297,7 @@
</answer>
</qandaentry>
+
<qandaentry>
<question id="q-remote-solaris">
<para>XDMCP freezes with remote Solaris machine!</para>
@@ -269,6 +317,7 @@
</answer>
</qandaentry>
+
<qandaentry>
<question id="q-cde-via-xdmcp-hangs">
<para>Login to <acronym>CDE</acronym> on &sun-solaris; via XDMCP hangs
@@ -291,6 +340,7 @@
<question id="q-xdmcp-info">
<para>Where can I find more information about XDMCP.</para>
</question>
+
<answer>
<para>See the <ulink
url="&linuxdoc-url-xdmcp;">&linuxdoc-title-xdmcp;</ulink> for more
@@ -298,4 +348,3 @@
</answer>
</qandaentry>
</qandadiv>
-
More information about the xserver-commit
mailing list