LDP
/
LDP
mirror of https://github.com/tLDP/LDP
0
1
Fork 0
Code Releases Activity

updated

This commit is contained in:
gferg 2000-11-08 16:56:12 +00:00
parent 588f1df462
commit 8acde57204
2 changed files with 356 additions and 82 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

58
LDP/howto/docbook/Infrared-HOWTO.sgml
View File

@ -1,5 +1,4 @@
<!DOCTYPE book PUBLIC "-//Davenport//DTD DocBook V3.0//EN" [
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook V3.1//EN" [
]>
<book><?dbhtml filename="Infrared-HOWTO.html">
@ -33,14 +32,14 @@ Linux Mobile Edition
</PUBLISHER>
<RELEASEINFO>Version 3.0</RELEASEINFO>
<RELEASEINFO>Version 3.1</RELEASEINFO>
<PUBDATE>$Date$</PUBDATE>
<LEGALNOTICE>
<PARA>
Copyright (c) 2000 Werner Heuser.
For all chapters permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with the Invariant Sections being "Preface" and "Credits", with the Front-Cover Texts being "Linux Infrared HOWTO", and with the Back-Cover Texts being the section "About the Author". A copy of the license is included in the section entitled "GNU Free Documentation License".
For all chapters permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with the Invariant Sections being "Preface" and "Credits", with the Front-Cover Texts being "Linux Infrared HOWTO", and with the Back-Cover Texts being the section "About the Document and the Author". A copy of the license is included in the section entitled "GNU Free Documentation License".
</PARA>
</LEGALNOTICE>
@ -1026,7 +1025,7 @@ Though I never succeeded to compile all utilities without errors, I recommend to
<PARA>
NOKUBI Takatsugu provides an <Emphasis remap="it">unofficial</Emphasis> <ULink
URL="http://www.daionet.gr.jp/&#732;knok/debian"
URL="http://www.daionet.gr.jp/~knok/debian"
>irda-utils Debian package</ULink
> (needs libc2.1). This package is part of the Potato Debian release. Also Mandrake 6.1, Redhat 6.1 and SuSE 6.1 contain RPM packages of irda-utils.
</PARA>
@ -3025,8 +3024,8 @@ d. I sometimes get a TCP configuration problem after disconnect, which can be so
URL="mailto:thiguchi@pluto.dti.ne.jp"
>&#60;thiguchi@pluto.dti.ne.jp&#62;</ULink
> provided <Emphasis remap="it">IrCOMM support</Emphasis>. From his page at <ULink
URL="http://www.pluto.dti.ne.jp/&#732;thiguchi/irda/"
>http://www.pluto.dti.ne.jp/&#732;thiguchi/irda/</ULink
URL="http://www.pluto.dti.ne.jp/~thiguchi/irda/"
>http://www.pluto.dti.ne.jp/~thiguchi/irda/</ULink
> I have taken the following description (I have modified it at little): "With IrCOMM support you can send or receive short messages between a linux box and a terminal program on a win95 laptop! Please add this line to /etc/conf.modules:
<ProgramListing>
@ -3613,8 +3612,8 @@ Read the <Emphasis remap="it">specification</Emphasis> of the machine, though it
<PARA>
Try to find out whether the FIR chip is a <Emphasis remap="it">PCI</Emphasis> device. Do a <command>cat /proc/pci</command> . The according files for 2.2.x kernels are in <filename>/proc/bus/pci</filename> . Though often the PCI information is incomplete. You may find the latest information about PCI devices and vendor numbers in the kernel documentation usually in <filename>/usr/src/linux/Documentation</filename> or at the page of Craig Hart <ULink
URL="http://members.hyperlink.net.au/&#732;chart"
>http://members.hyperlink.net.au/&#732;chart</ULink
URL="http://members.hyperlink.net.au/~chart"
>http://members.hyperlink.net.au/~chart</ULink
> . From kernel 2.1.82 on, you may use <command>lspci</command> from the <command>pci-utils</command> package, too.
</PARA>
@ -3777,8 +3776,8 @@ URL="http://www.jps.net/tadavis/irda/devids.txt"
<PARA>
WARNING: The package is not intended for the end user, and some of the utilities could be harmful. The only documentation in the package is in M$ Word format. Linux users may read this with <command>catdoc</command>, available at <ULink
URL="http://www.fe.msk.ru/&#732;vitus/catdoc/"
>http://www.fe.msk.ru/&#732;vitus/catdoc/</ULink
URL="http://www.fe.msk.ru/~vitus/catdoc/"
>http://www.fe.msk.ru/~vitus/catdoc/</ULink
> .
</PARA>
</ListItem>
@ -3893,8 +3892,8 @@ URL="http://irda.sourceforge.net"
<PARA>
Takahide Higuchi at <ULink
URL="http://www.pluto.dti.ne.jp/&#732;thiguchi/ir/product.html"
>http://www.pluto.dti.ne.jp/&#732;thiguchi/ir/product.html</ULink
URL="http://www.pluto.dti.ne.jp/~thiguchi/ir/product.html"
>http://www.pluto.dti.ne.jp/~thiguchi/ir/product.html</ULink
>.This page is in japanese.
</PARA>
@ -4229,8 +4228,8 @@ Look at the <Emphasis remap="it">mailing list archivs</Emphasis>, whether your p
URL="http://www.pasta.cs.UiT.No/mailman/listinfo/linux-irda"
>Linux-IrDA mailing list archiv</ULink
>. All mails before are archived at <ULink
URL="http://www.ita.chalmers.se/&#732;svinto/hypermail/irda/"
>http://www.ita.chalmers.se/&#732;svinto/hypermail/irda/</ULink
URL="http://www.ita.chalmers.se/~svinto/hypermail/irda/"
>http://www.ita.chalmers.se/~svinto/hypermail/irda/</ULink
> .
</PARA>
@ -4927,15 +4926,15 @@ LInux Remote Control - LIRC
<PARA>
is a package that supports receiving and sending IR signals of the most common IR remote controls. It contains a device driver for hardware connected to the serial port, a daemon that decodes and sends IR signals using this device driver, a mouse daemon that translates IR signals to mouse movements and a couple of user programs that allow to control your computer with a remote control. Takahide Higuchi wrote about LIRC: "It's great, and it seems almost complete solution, but it seems there is almost nothing supporting hardware on the market (or need to solder some special circuit ... it is hard work for many people to do so). I believe that LIRC will be more popular if consumer IR support is implemented in FastIR drivers and some common API (for example, a raw IrSocket and common ioctls) is made!". You may find LIRC at <ULink
URL="http://fsinfo.cs.uni-sb.de/&#732;columbus/lirc/"
>http://fsinfo.cs.uni-sb.de/&#732;columbus/lirc/</ULink
URL="http://fsinfo.cs.uni-sb.de/~columbus/lirc/"
>http://fsinfo.cs.uni-sb.de/~columbus/lirc/</ULink
>
</PARA>
<PARA>
To subscribe to the LIRC mailing list send an email to &lt;lirc-request@xmission.com&gt; with the word "subscribe" in the body of the message. There is also a mailing list archive at <ULink
URL="http://www.wh9.tu-dresden.de/&#732;heinrich/lirc/list-archive/"
>http://www.wh9.tu-dresden.de/&#732;heinrich/lirc/list-archive/</ULink
URL="http://www.wh9.tu-dresden.de/~heinrich/lirc/list-archive/"
>http://www.wh9.tu-dresden.de/~heinrich/lirc/list-archive/</ULink
>
</PARA>
</ListItem>
@ -4945,8 +4944,8 @@ Serial Infrared Remote Controller
</PARA>
<PARA>
This is a simple, cheap device that can be connected to any serial port to control most components that have infrared remote controls. It was designed and built on a solderless breadboard and is finally designed as a PC board. You may find this package at <ULink
URL="http://www.armory.com/&#732;spcecdt/remote/remote.html"
>http://www.armory.com/&#732;spcecdt/remote/remote.html</ULink
URL="http://www.armory.com/~spcecdt/remote/remote.html"
>http://www.armory.com/~spcecdt/remote/remote.html</ULink
>
</PARA>
</ListItem>
@ -4972,8 +4971,8 @@ A very basic Infra Red device driver. This does not support IrDA (only unreliabl
<PARA>
You may find the tools at <ULink
URL="http://www.netwinder.org/&#732;ryansh/"
>http://www.netwinder.org/&#732;ryansh/</ULink
URL="http://www.netwinder.org/~ryansh/"
>http://www.netwinder.org/~ryansh/</ULink
>
</PARA>
</ListItem>
@ -5169,8 +5168,8 @@ I know that Corel is interested in using CIR for controlling the NetWinder (and
URL="http://www.slashdot.org/articles/98/12/05/0916216.shtml"
>http://www.slashdot.org/articles/98/12/05/0916216.shtml</ULink
> or <ULink
URL="http://www.netwinder.org/&#732;ryansh"
>http://www.netwinder.org/&#732;ryansh</ULink
URL="http://www.netwinder.org/~ryansh"
>http://www.netwinder.org/~ryansh</ULink
>
</PARA>
@ -5711,11 +5710,16 @@ v2.11, 9 March 2000, added links to the 'irctl' and 'IRManager' infrared control
</PARA>
</ListItem>
<ListItem>
<ListItem>
<PARA>
v3.0, 5 November 2000, format changed to DocBook , license changed to GNU Free Documentation License - GFDL, title changed from IR-HOWTO to Infrared-HOWTO, new document URL, links to Linux/IrDA updated
</PARA>
</ListItem>
<ListItem>
<PARA>
v3.1, 8 November 2000, links updated, changed to DocBook 3.1
</PARA>
</ListItem>
@ -6574,7 +6578,7 @@ URL="http://www.opensource.org/osd.html"
<TITLE>Copyrights</TITLE>
<PARA>
For all chapters permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with the Invariant Sections being "Preface" and "Credits", with the Front-Cover Texts being "Linux Infrared HOWTO", and with the Back-Cover Texts being the section "About the Author". A copy of the license is included in the section entitled "GNU Free Documentation License".
For all chapters permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with the Invariant Sections being "Preface" and "Credits", with the Front-Cover Texts being "Linux Infrared HOWTO", and with the Back-Cover Texts being the section "About the Document and the Author". A copy of the license is included in the section entitled "GNU Free Documentation License".
</PARA>
<SECT1>

380
LDP/howto/docbook/XDM-Xterm.sgml
View File

@ -18,6 +18,15 @@
</author>
<revhistory>
<revision>
<revnumber>v0.04</revnumber>
<date>6 November 2000</date>
<authorinitials>kt</authorinitials>
<revremark>
Updates after first public draft.
</revremark>
</revision>
<revision>
<revnumber>v0.03</revnumber>
<date>3 July 2000</date>
@ -61,7 +70,8 @@
<para>
For a full discussion about the installation and configuration
of X terminals, please refer to the 'Thin-client' HOWTO, from
the Linux Documentation Project (see <xref linkend="resources">).
the Linux Documentation Project or the Linux Terminal Server Project
(see <xref linkend="resources">).
</para>
</abstract>
@ -161,10 +171,6 @@
<primary>(your index root)!news on</primary>
</indexterm>
<para>
This is the initial release.
</para>
<para>
The latest version number of this document may be
obtained from
@ -198,6 +204,12 @@
The writers of the XDM, Xserver man pages and the default XDM scripts.
</para>
<para>
Everyone who commented on the earlier versions, including Neil Zanella,
Rafael Herrera, Paul Hornshaw, Clive Jones, Robert de Geus, Alex Schenkman,
Richard Kaszeta, Malcolm Herbet
</para>
</sect2>
<!-- Section2: feedback -->
@ -239,7 +251,12 @@
</listitem>
<listitem>
<para>
LBX ?
Integration with other Unix and Windows
</para>
</listitem>
<listitem>
<para>
FAQs and common mistakes
</para>
</listitem>
</itemizedlist>
@ -318,7 +335,7 @@
This document does not attempt to describe how to install and configure
Linux for an X terminal. For this information, please refer to the
'thin-client' HOWTO document, provided as part of the Linux Documentation
Project (see <xref linkend="resources">).
Project, or the Linux Terminal Server Project (see <xref linkend="resources">).
</para>
</sect2>
@ -442,7 +459,8 @@
<listitem>
<para>
These would be a machine with no local disks, which would perform its
boot up via a network connection to a server. This means obtaining the
boot up from an EPROM (or similar) which utilises a network connection to a
server. This means obtaining the
network configuration, operating system, system configuration and all
applications from the server. Once booted however, this
would be the same as a 'dumb X terminal' (see below). Typically this
@ -460,9 +478,9 @@
<listitem>
<para>
This would be a machine that boots from its local disk into an operating
system, and starts an 'X server' and nothing more. Somehow, a login prompt
would be provided on the machine, to enable a user to login to an
application server somewhere on the network.
system, and starts the 'X server' program and nothing more. Somehow, a login
prompt would be provided on the machine, to enable a user to login to an
'application server' somewhere on the network.
</para>
</listitem>
</VarListentry>
@ -473,8 +491,10 @@
<listitem>
<para>
This would be similar to a dumb X terminal, but would provide the option
of loging on to the local machine itself, hence would be quite capable of
of logging on to the local machine itself, hence would be quite capable of
becoming a standalone workstation (ie no network connectivity) if required.
Most distributions can be configured 'out of the box' as a stand-alone
X Workstation, with a graphical login prompt.
</para>
</listitem>
</VarListentry>
@ -485,9 +505,9 @@
<listitem>
<para>
In the context of this document, I use the term 'application server' to
describe a machine that will provide a running X session and applications
(but not necessarily an actual graphical console login prompt and local
screen and keyboard).
describe a machine that will provide the applications (X clients) that our X
terminal will want to run. This can include everything from editors and browsers,
through to the actual 'Window Manager' itself.
</para>
</listitem>
</VarListentry>
@ -497,9 +517,11 @@
</term>
<listitem>
<para>
This is a machine with a physical console (display, keyboard, mouse, etc)
that is able to provided these facilities as a service to X clients.
Please refer to the X User Howto in
This is the program that manages the display of the machine with a physical
console (display, keyboard, mouse, etc). It can be thought of as a combined
graphics card, keyboard and mouse 'driver'.
This will provide these facilities as a service to X clients (hence the term
'server'). Please refer to the X User Howto in
<xref linkend="resources">
for more details.
</para>
@ -511,8 +533,10 @@
</term>
<listitem>
<para>
This is an application that requires the use of the X server to provide
a display and input.
This is an application that requires the use of an X server to provide
input (keyboard and mouse) and output (display). An X client cannot produce
output without the services of the X server. The X server could be
running locally (on the same machine) or elsewhere on the network.
</para>
</listitem>
</VarListentry>
@ -520,15 +544,15 @@
</para>
<para>
Note that from the above descriptions, an X Workstation could be thought of
as consisting of a dumb X terminal and application server running on a single
From the above descriptions, an X Workstation could be thought of
as consisting of a dumb X terminal and application server running on the same
machine.
</para>
<para>
This document will be looking at the architecture of the various options
listed above and will describe the role that xdm can play in configuring
these setups.
them.
</para>
</sect2>
@ -539,31 +563,30 @@
<title>What can XDM do</title>
<para>
XDM is the utility that will be responsible for providing the users login
prompt and initiating their X session. This could be a local session (in
the case of an X workstation) or via a connection to an application server
from a diskless or dumb X terminal.
XDM is responsible for providing the user with a login
prompt and initiating their X session. It can manage local sessions (ie people
logging into an X workstation) or sessions on remote machines, via a connection
to an application server from a diskless or dumb X terminal.
</para>
<para>
There are 2 main methods that can result with the user being presented
with a login prompt :
XDM has 2 main modes of operation :
<itemizedlist>
<listitem>
<para>
X server query
Query from an X server
</para>
</listitem>
<listitem>
<para>
XDM server managed
XDM managed X server
</para>
</listitem>
</itemizedlist>
</para>
<sect3 id="xserv-query">
<title>X Server Query</title>
<title>Query from an X Server</title>
<para>
The communications between XDM and the actual 'X server' (the machines
@ -572,13 +595,14 @@
</para>
<para>
This permits X servers to send out queries to servers running XDM, basically
saying 'I have someone wanting to login - someone please give me a login
prompt'.
This permits X servers to send out queries to servers running XDM.
Effectively, the X server has to say 'I have someone wanting to login -
please give me a login prompt'. In this mode of operation, XDM will
not do anything unless it is asked to by your X server.
</para>
<para>
This facility can take one of 3 forms :
The query from the X server can take one of 3 forms :
<itemizedlist>
<listitem>
<para>
@ -606,14 +630,14 @@
</para>
<para>
There are several other processes, but these will not be described here
There are several other options, but these will not be described here
- refer to the XDM and XDMCP documentation in <xref linkend="resources">
for more details.
</para>
</sect3>
<sect3 id="xdm-server">
<title>XDM Server Managed</title>
<title>XDM Managed X Server</title>
<para>
If you have a set of machines (eg diskless or dumb X terminals) that just
@ -622,9 +646,15 @@
application server to connect back to each X server and present its login
prompt on each display automatically.
</para>
<para>
In this mode of operation, XDM will actively 'push out' a login prompt
to any listed X server that it knows about, without waiting for
a query from the X servers themselves.
</para>
<para>
In this mode of operation, the configuration file 'Xservers' lists each
In this case, the configuration file 'Xservers' lists each
machine (including the local display, if required) to which XDM should
connect, to display its login prompt.
</para>
@ -633,12 +663,14 @@
This configuration, when used with no remote X servers listed in the
configuration, is the typical configuration used for a X workstation,
in order to present a user with a graphical login to the local machine
he is working on.
he is working on. As stated earlier, most distributions will support
this configuration 'out of the box' in order to present the user with
a local graphical login prompt.
</para>
<para>
Note this assumes that the access control on the X server is such that the
application server XDM is able to connect back to the appropriate display.
Note: XDM must be permitted to connect to the X servers in question - so
the access control on the X servers must be configured accordingly.
</para>
</sect3>
@ -728,6 +760,12 @@
not need to change these, as most distributions would appear to
come with this pre-configured for you.
</para>
<para>
Note that XDM managed X sessions have a different set of startup
and configuration scripts to X sessions started via xinit or startx
(ie non-XDM managed X sessions).
</para>
</listitem>
</VarListentry>
@ -736,9 +774,10 @@
</term>
<listitem>
<para>
Determines which machines can connect to XDM on this machine - ie
Determines which machines can connect to XDM - ie
from which other machines on the network we are accepting XDMCP
queries.
queries. If a machine is not listed in this file, then it will not
be able to request a login prompt from XDM.
</para>
</listitem>
</VarListentry>
@ -752,6 +791,17 @@
login prompt, automatically - ie those machines already running an X
server, but would like this machine to provide the login prompt.
</para>
<para>
This is only required for 'XDM Managed X Servers'. You do not need
any entries in this file if you will be relying on remote X servers
to query XDM.
</para>
<para>
When running as a stand-alone 'X Workstation', there is usually a
single entry in this file, listing just the localhost.
</para>
</listitem>
</VarListentry>
@ -772,7 +822,7 @@
<!-- Section2: XDM Managing X Servers -->
<sect2 id="xdm-xserv">
<title>Configuring XDM to manage X servers</title>
<title>Configuring XDM to Manage X Servers</title>
<para>
An entry must be placed in the Xservers file for each X server
@ -809,11 +859,11 @@
<!-- Section2: XDM for queries -->
<sect2 id="xdm-queries">
<title>Configuring XDM for queries</title>
<title>Configuring XDM to Receive Queries</title>
<para>
The file Xaccess determines which hosts may query XDM on this machine,
in order to be presented with a login prompt.
in order to request a login prompt.
</para>
<para>
@ -827,10 +877,14 @@
</para>
<para>
This means that any host may connect to XDM directly (the first '*').
This means that any host may request a login prompt via XDM (the first '*')
using a direct query.
</para>
<para>
The 'CHOOSER' line specifies which hosts can connect to XDM using
indirect queries - in this case, any host may query this machine for
a list of hosts to connect to (the second '*' line).
a list of potential hosts to connect to (the second '*' line).
</para>
<para>
@ -867,6 +921,12 @@
XDM will normally start X automatically for you and XDM will usually
be configured to run as part of the startup process (via the init scripts).
</para>
<para>
The Xservers file would typically contain a single entry - that of the
local host, and the Xaccess file would only need to permit access from
the local host.
</para>
</listitem>
</varlistentry>
@ -882,6 +942,11 @@
/usr/X11R6/bin/X -ac
</screen>
</para>
<para>
When the remote XDM is started, it will 'push out' a login prompt to
all such configured X servers (as listed in its Xservers file).
</para>
</listitem>
</varlistentry>
@ -925,8 +990,9 @@
<para>
In this mode of operation, instead of the normal XDM login prompt,
the user will be given the 'chooser' widget, which will provide a list
of detected hosts on the network.
the user will be presented with a 'chooser' application, which will
provide a list of detected hosts on the network that are currently
accepting XDM connections.
</para>
<para>
@ -940,7 +1006,7 @@
</para>
<para>
The chooser will obtain its lists of host by one of two methods :
The chooser will obtain its lists of hosts by one of two methods :
<itemizedlist>
<listitem>
<para>
@ -958,8 +1024,9 @@
* CHOOSER %hostlist
</screen>
This will mean that the hosts emma, alex and liam will all be
listed as available (presumably even if one of the machines is
down ? Need to check this ...)
listed as candidates - even if one of the machines is down
(there is often a button to 'ping' the host to see if it is
running, before trying to connect to it).
</para>
</listitem>
</itemizedlist>
@ -1048,6 +1115,196 @@
</sect2>
<!-- Section2: X Resources -->
<sect2 id="x-resources">
<title>X Resources</title>
<para>
This document has only briefly touched on the available X resources, but
I should mention that it is possible to fully configure XDM via the Xresources
file.
</para>
<para>
The following may all be changed if required :
<itemizedlist>
<listitem>
<para> Fonts, login prompt sizes
</para>
</listitem>
<listitem>
<para> Background graphics
</para>
</listitem>
<listitem>
<para> Window Titles, etc
</para>
</listitem>
</itemizedlist>
</para>
<para>
There is a more detailed discussion of XDM resources, on Richard Kaszeta's web site
(see <xref linkend="resources">)
</para>
</sect2>
</sect1>
<!-- Section1: Common Configurations -->
<sect1 id="common-configs">
<title>Common Configurations</title>
<indexterm>
<primary>disk!advanced</primary>
</indexterm>
<!-- Section2: Linux to Linux -->
<sect2 id="cfgs-linux">
<title>Linux to Linux</title>
<sect3 id="cfgs-stdalonex">
<title>Stand-alone X Workstation</title>
<para>
This has already been mentioned several times in this document, but
in summary, it is a PC runing XDM, with a single entry in the Xservers
file, relating to the localhost (ie the local machine)
</para>
</sect3>
<sect3 id="cfgs-xtermapps">
<title>X Terminal and Application Server</title>
<para>
XDM runs on the application server :
<itemizedlist>
<listitem>
<para>
Xserver : Contains no entries
</para>
</listitem>
<listitem>
<para>
Xaccess : Must permit the X terminal to connect
</para>
</listitem>
</itemizedlist>
</para>
<para>
X terminal runs X using a direct query to the application server :
<screen>
/usr/X11R6/bin/X -query the.application.server
</screen>
</para>
</sect3>
<sect3 id="cfgs-mngexterm">
<title>Group of Managed X Terminals</title>
<para>
XDM runs on an application server :
<itemizedlist>
<listitem>
<para>
Xserver : Lists each X terminal to be managed
</para>
</listitem>
<listitem>
<para>
Xaccess : Must permit each X terminal to connect
</para>
</listitem>
</itemizedlist>
</para>
<para>
Each X terminal, just runs X, with suitable access control to
permit XDM to connect to it.
<screen>
/usr/X11R6/bin/X -ac
</screen>
</para>
</sect3>
</sect2>
<!-- Section2: Linux to Other -->
<sect2 id="cfgs-toother">
<title>Linux to Other Systems</title>
<para>
It is possible to use a Linux X terminal to connect to another
system running XDM. The same principles as above apply, but
the specifics of configuring XDM (or its equivalent) will be
specific to that system.
</para>
<sect3 id="cfgs-linsol">
<title> Linux and Solaris </title>
<para>
You can run X on a Linux box, instructing it to query
a Solaris machine as previously described :
<screen>
/usr/X11R6/bin/X -query the.solaris.server
</screen>
</para>
<para>
Note that you may have to configure X on the Linux
machine to use a font server from the Solaris box.
I have not got this to work yet, as I don't have a
Solaris box that I have any control over - but I am
told that a font entry in /etc/XF86config similar to
the following should work (I think - WARNING this is
to be checked ...):
<screen>
tcp/solaris.box:7200
</screen>
</para>
</sect3>
</sect2>
<!-- Section2: Other to Linux -->
<sect2 id="cfgs-tolinux">
<title>Other Systems to Linux</title>
<para>
If you have an X server for your system, it should be able to connect
to a Linux XDM application server.
</para>
<sect3 id="cfgs-sollin">
<title>Solaris and Linux </title>
<para>
I assume that you would run XDM on the Linux box as usual, and
instruct X on Solaris to query the Linux box - does anyone have
any information on this ?
</para>
</sect3>
<sect3 id="winlin">
<title> Windows and Linux </title>
<para>
If you have an X server for windows that supports XDMCP queries, then
it should be possible to configure it to query the Linux box. You should
just run XDM on the Linux box as usual. Again - any specifics anyone ?
</para>
</sect3>
</sect2>
</sect1>
<!-- Section1: resources -->
@ -1107,6 +1364,12 @@
<ulink url="http://www.linuxdoc.org">LDP</ulink>)
</para>
</listitem>
<listitem>
<para>
Linux Terminal Server Project :
<ulink url="http://www.ltsp.org/">http://www.ltsp.org/</ulink>)
</para>
</listitem>
<listitem>
<para>
Diskless Howto Document (from the
@ -1118,13 +1381,20 @@
<ulink url="http://dns.solucorp.qc.ca/xterminals">X terminal pages</ulink>
</para>
</listitem>
<listitem>
<para>
Richard Kaszeta :
<ulink url="http://www.menet.umn.edu/~kaszeta/unix/xterminal/">Converting old PCs into Standalone X Terminals
</ulink>)
</para>
</listitem>
</itemizedlist>
</para>
</listitem>
</varlistentry>
<varlistentry>
<term> XDM
<term> XDM, etc
</term>
<listitem>
<para>