Part 1 of 2 of kdm rename

1 files changed, 99 insertions, 99 deletions

diff --git a/tde-i18n-en_GB/docs/tdebase/kdm/kdmrc-ref.docbook b/tde-i18n-en_GB/docs/tdebase/kdm/kdmrc-ref.docbook
index 18d6a847588..a778a4b0d2f 100644
--- a/tde-i18n-en_GB/docs/tdebase/kdm/kdmrc-ref.docbook
+++ b/tde-i18n-en_GB/docs/tdebase/kdm/kdmrc-ref.docbook
@@ -1,20 +1,20 @@
-<!-- generated from ../../kdm/kfrontend/config.def - DO NOT EDIT! -->
+<!-- generated from ../../tdm/kfrontend/config.def - DO NOT EDIT! -->
 
-<chapter id="kdm-files">
+<chapter id="tdm-files">
 <title
->The Files &kdm; Uses for Configuration</title>
+>The Files &tdm; Uses for Configuration</title>
 
 <para
->This chapter documents the files that control &kdm;'s behaviour. Some of this can be also controlled from the &kcontrol; module, but not all.</para>
+>This chapter documents the files that control &tdm;'s behaviour. Some of this can be also controlled from the &kcontrol; module, but not all.</para>
 
 <sect1>
 <title
->&kdmrc; - The &kdm; master configuration file</title>
+>&tdmrc; - The &tdm; master configuration file</title>
 
 <para
 >The basic format of the file is <quote
 >INI-like</quote
->. Options are key/value pairs, placed in sections. Everything in the file is case sensitive. Syntactic errors and unrecognised key/section identifiers cause &kdm; to issue non-fatal error messages.</para>
+>. Options are key/value pairs, placed in sections. Everything in the file is case sensitive. Syntactic errors and unrecognised key/section identifiers cause &tdm; to issue non-fatal error messages.</para>
 
 <para
 >Lines beginning with <literal
@@ -161,13 +161,13 @@
 
 <note
 ><para
->A pristine &kdmrc; is very thoroughly commented. All comments will be lost if you change this file with the kcontrol frontend.</para
+>A pristine &tdmrc; is very thoroughly commented. All comments will be lost if you change this file with the kcontrol frontend.</para
 ></note>
 
 
-<sect2 id="kdmrc-general">
+<sect2 id="tdmrc-general">
 <title
->The [General] section of &kdmrc;</title>
+>The [General] section of &tdmrc;</title>
 
 <para
 >This section contains global options that do not fit into any specific section. </para>
@@ -183,7 +183,7 @@
 <para
 >This option exists solely for the purpose of clean automatic upgrades. <emphasis
 >Do not</emphasis
-> change it, you may interfere with future upgrades and this could result in &kdm; failing to run. </para>
+> change it, you may interfere with future upgrades and this could result in &tdm; failing to run. </para>
 </listitem>
 </varlistentry>
 
@@ -194,9 +194,9 @@
 ></term>
 <listitem>
 <para
->If the value starts with a slash (/), it specifies a file to read &X-Server; definitions from; otherwise, it is an &X-Server; definition by itself. See <xref linkend="kdmrc-xservers"/> for the details. </para
+>If the value starts with a slash (/), it specifies a file to read &X-Server; definitions from; otherwise, it is an &X-Server; definition by itself. See <xref linkend="tdmrc-xservers"/> for the details. </para
 ><para
->The default is an &X-Server; definition that is usually reasonable for the system on which &kdm; was built. </para>
+>The default is an &X-Server; definition that is usually reasonable for the system on which &tdm; was built. </para>
 </listitem>
 </varlistentry>
 
@@ -209,7 +209,7 @@
 <para
 >List of Virtual Terminals to allocate to &X-Server;s. For negative numbers the absolute value is used, and the <acronym
 >VT</acronym
-> will be allocated only if the kernel says it is free. If &kdm; exhausts this list, it will allocate free <acronym
+> will be allocated only if the kernel says it is free. If &tdm; exhausts this list, it will allocate free <acronym
 >VT</acronym
 >s greater than the absolute value of the last entry in this list. </para>
 <para
@@ -224,7 +224,7 @@
 ></term>
 <listitem>
 <para
->The filename specified will be created to contain an ASCII representation of the process ID of the main &kdm; process; the PID will not be stored if the filename is empty. </para>
+>The filename specified will be created to contain an ASCII representation of the process ID of the main &tdm; process; the PID will not be stored if the filename is empty. </para>
 <para
 >Empty by default.</para>
 </listitem>
@@ -237,7 +237,7 @@
 ></term>
 <listitem>
 <para
->This option controls whether &kdm; uses file locking to keep multiple display managers from running onto each other. </para>
+>This option controls whether &tdm; uses file locking to keep multiple display managers from running onto each other. </para>
 <para
 >The default is <quote
 >true</quote
@@ -252,7 +252,7 @@
 ></term>
 <listitem>
 <para
->This names a directory under which &kdm; stores &X-Server; authorisation files while initialising the session. &kdm; expects the system to clean up this directory from stale files on reboot. </para
+>This names a directory under which &tdm; stores &X-Server; authorisation files while initialising the session. &tdm; expects the system to clean up this directory from stale files on reboot. </para
 ><para
 >The authorisation file to be used for a particular display can be specified with the <option
 >AuthFile</option
@@ -271,7 +271,7 @@
 ></term>
 <listitem>
 <para
->This boolean controls whether &kdm; automatically re-reads its configuration files if it finds them to have changed. </para>
+>This boolean controls whether &tdm; automatically re-reads its configuration files if it finds them to have changed. </para>
 <para
 >The default is <quote
 >true</quote
@@ -286,7 +286,7 @@
 ></term>
 <listitem>
 <para
->Additional environment variables &kdm; should pass on to all programs it runs. <envar
+>Additional environment variables &tdm; should pass on to all programs it runs. <envar
 >LD_LIBRARY_PATH</envar
 > and <envar
 >XCURSOR_THEME</envar
@@ -309,7 +309,7 @@
 >PrngdSocket</option
 > and <option
 >PrngdPort</option
->) is running, &kdm; will fall back to its own pseudo-random number generator that will, among other things, successively checksum parts of this file (which, obviously, should change frequently). </para
+>) is running, &tdm; will fall back to its own pseudo-random number generator that will, among other things, successively checksum parts of this file (which, obviously, should change frequently). </para
 ><para
 >This option does not exist on Linux and various BSDs. </para>
 <para
@@ -356,7 +356,7 @@
 ></term>
 <listitem>
 <para
->The path to a character device which KDM should read random data from. Empty means to use the system's preferred entropy device if there is one. </para
+>The path to a character device which TDM should read random data from. Empty means to use the system's preferred entropy device if there is one. </para
 ><para
 >This option does not exist on OpenBSD, as it uses the arc4_random function instead. </para>
 <para
@@ -401,10 +401,10 @@
 ></term>
 <listitem>
 <para
->The directory in which &kdm; should store persistent working data; such data is, for example, the previous user that logged in on a particular display. </para>
+>The directory in which &tdm; should store persistent working data; such data is, for example, the previous user that logged in on a particular display. </para>
 <para
 >The default is <quote
->/var/lib/kdm</quote
+>/var/lib/tdm</quote
 >.</para>
 </listitem>
 </varlistentry>
@@ -416,7 +416,7 @@
 ></term>
 <listitem>
 <para
->The directory in which &kdm; should store users' <filename
+>The directory in which &tdm; should store users' <filename
 >.dmrc</filename
 > files. This is only needed if the home directories are not readable before actually logging in (like with AFS). </para>
 <para
@@ -428,12 +428,12 @@
 </sect2>
 
 
-<sect2 id="kdmrc-xdmcp">
+<sect2 id="tdmrc-xdmcp">
 <title
->The [Xdmcp] section of &kdmrc;</title>
+>The [Xdmcp] section of &tdmrc;</title>
 
 <para
->This section contains options that control &kdm;'s handling of &XDMCP; requests. </para>
+>This section contains options that control &tdm;'s handling of &XDMCP; requests. </para>
 
 <variablelist>
 
@@ -444,7 +444,7 @@
 ></term>
 <listitem>
 <para
->Whether &kdm; should listen to incoming &XDMCP; requests. </para>
+>Whether &tdm; should listen to incoming &XDMCP; requests. </para>
 <para
 >The default is <quote
 >true</quote
@@ -459,7 +459,7 @@
 ></term>
 <listitem>
 <para
->This indicates the UDP port number which &kdm; uses to listen for incoming &XDMCP; requests. Unless you need to debug the system, leave this with its default value. </para>
+>This indicates the UDP port number which &tdm; uses to listen for incoming &XDMCP; requests. Unless you need to debug the system, leave this with its default value. </para>
 <para
 >The default is <quote
 >177</quote
@@ -474,7 +474,7 @@
 ></term>
 <listitem>
 <para
->XDM-AUTHENTICATION-1 style &XDMCP; authentication requires a private key to be shared between &kdm; and the terminal. This option specifies the file containing those values. Each entry in the file consists of a display name and the shared key. </para>
+>XDM-AUTHENTICATION-1 style &XDMCP; authentication requires a private key to be shared between &tdm; and the terminal. This option specifies the file containing those values. Each entry in the file consists of a display name and the shared key. </para>
 <para
 >Empty by default.</para>
 </listitem>
@@ -487,12 +487,12 @@
 ></term>
 <listitem>
 <para
->To prevent unauthorised &XDMCP; service and to allow forwarding of &XDMCP; IndirectQuery requests, this file contains a database of hostnames which are either allowed direct access to this machine, or have a list of hosts to which queries should be forwarded to. The format of this file is described in <xref linkend="kdmrc-xaccess"/>. </para>
+>To prevent unauthorised &XDMCP; service and to allow forwarding of &XDMCP; IndirectQuery requests, this file contains a database of hostnames which are either allowed direct access to this machine, or have a list of hosts to which queries should be forwarded to. The format of this file is described in <xref linkend="tdmrc-xaccess"/>. </para>
 <para
 >The default is <quote
 >${<envar
 >kde_confdir</envar
->}/kdm/Xaccess</quote
+>}/tdm/Xaccess</quote
 >.</para>
 </listitem>
 </varlistentry>
@@ -519,7 +519,7 @@
 ></term>
 <listitem>
 <para
->When computing the display name for &XDMCP; clients, the name resolver will typically create a fully qualified host name for the terminal. As this is sometimes confusing, &kdm; will remove the domain name portion of the host name if it is the same as the domain name of the local host when this option is enabled. </para>
+>When computing the display name for &XDMCP; clients, the name resolver will typically create a fully qualified host name for the terminal. As this is sometimes confusing, &tdm; will remove the domain name portion of the host name if it is the same as the domain name of the local host when this option is enabled. </para>
 <para
 >The default is <quote
 >true</quote
@@ -563,9 +563,9 @@
 </sect2>
 
 
-<sect2 id="kdmrc-shutdown">
+<sect2 id="tdmrc-shutdown">
 <title
->The [Shutdown] section of &kdmrc;</title>
+>The [Shutdown] section of &tdmrc;</title>
 
 <para
 >This section contains global options concerning system shutdown. </para>
@@ -581,7 +581,7 @@
 <para
 >The command to run to halt/poweroff the system. </para
 ><para
->The default is something reasonable for the system on which &kdm; was built, like <command
+>The default is something reasonable for the system on which &tdm; was built, like <command
 >/sbin/shutdown&nbsp;<option
 >-h</option
 >&nbsp;<parameter
@@ -600,7 +600,7 @@
 <para
 >The command to run to reboot the system. </para
 ><para
->The default is something reasonable for the system &kdm; on which was built, like <command
+>The default is something reasonable for the system &tdm; on which was built, like <command
 >/sbin/shutdown&nbsp;<option
 >-r</option
 >&nbsp;<parameter
@@ -655,7 +655,7 @@
 ></term>
 <listitem>
 <para
->Instructs &kdm; to offer LiLo boot options in the shutdown dialogue. </para
+>Instructs &tdm; to offer LiLo boot options in the shutdown dialogue. </para
 ><para
 >Only available on Linux i386 &amp; x86-64. </para>
 <para
@@ -703,12 +703,12 @@
 </sect2>
 
 
-<sect2 id="kdmrc-core">
+<sect2 id="tdmrc-core">
 <title
->The [X-*-Core] section class of &kdmrc;</title>
+>The [X-*-Core] section class of &tdmrc;</title>
 
 <para
->This section class contains options concerning the configuration of the &kdm; backend (core). </para>
+>This section class contains options concerning the configuration of the &tdm; backend (core). </para>
 
 <variablelist>
 
@@ -753,7 +753,7 @@
 ></term>
 <listitem>
 <para
->These options control the behaviour of &kdm; when attempting to open a connection to an &X-Server;. <option
+>These options control the behaviour of &tdm; when attempting to open a connection to an &X-Server;. <option
 >OpenDelay</option
 > is the length of the pause (in seconds) between successive attempts, <option
 >OpenRepeat</option
@@ -778,7 +778,7 @@
 ></term>
 <listitem>
 <para
->How many times &kdm; should attempt to start a <literal
+>How many times &tdm; should attempt to start a <literal
 >foreign</literal
 > display listed in the <filename
 >Xservers</filename
@@ -799,7 +799,7 @@
 ></term>
 <listitem>
 <para
->How many times &kdm; should attempt to start up a local &X-Server;. Starting up includes executing it and waiting for it to come up. </para>
+>How many times &tdm; should attempt to start up a local &X-Server;. Starting up includes executing it and waiting for it to come up. </para>
 <para
 >The default is <quote
 >1</quote
@@ -814,7 +814,7 @@
 ></term>
 <listitem>
 <para
->How many seconds &kdm; should wait for a local &X-Server; to come up. </para>
+>How many seconds &tdm; should wait for a local &X-Server; to come up. </para>
 <para
 >The default is <quote
 >15</quote
@@ -848,7 +848,7 @@
 <para
 >To discover when <emphasis
 >remote</emphasis
-> displays disappear, &kdm; regularly pings them. <option
+> displays disappear, &tdm; regularly pings them. <option
 >PingInterval</option
 > specifies the time (in minutes) between the pings and <option
 >PingTimeout</option
@@ -869,7 +869,7 @@
 ></term>
 <listitem>
 <para
->Whether &kdm; should restart the local &X-Server; after session exit instead of resetting it. Use this if the &X-Server; leaks memory or crashes the system on reset attempts. </para>
+>Whether &tdm; should restart the local &X-Server; after session exit instead of resetting it. Use this if the &X-Server; leaks memory or crashes the system on reset attempts. </para>
 <para
 >The default is <quote
 >false</quote
@@ -914,7 +914,7 @@
 ></term>
 <listitem>
 <para
->Controls whether &kdm; generates and uses authorisation for <emphasis
+>Controls whether &tdm; generates and uses authorisation for <emphasis
 >local</emphasis
 > &X-Server; connections. For &XDMCP; displays the authorisation requested by the display is used; foreign non-&XDMCP; displays do not support authorisation at all. </para>
 <para
@@ -950,7 +950,7 @@
 <para
 >Some <emphasis
 >old</emphasis
-> &X-Server;s re-read the authorisation file at &X-Server; reset time, instead of when checking the initial connection. As &kdm; generates the authorisation information just before connecting to the display, an old &X-Server; would not get up-to-date authorisation information. This option causes &kdm; to send SIGHUP to the &X-Server; after setting up the file, causing an additional &X-Server; reset to occur, during which time the new authorisation information will be read. </para>
+> &X-Server;s re-read the authorisation file at &X-Server; reset time, instead of when checking the initial connection. As &tdm; generates the authorisation information just before connecting to the display, an old &X-Server; would not get up-to-date authorisation information. This option causes &tdm; to send SIGHUP to the &X-Server; after setting up the file, causing an additional &X-Server; reset to occur, during which time the new authorisation information will be read. </para>
 <para
 >The default is <quote
 >false</quote
@@ -965,7 +965,7 @@
 ></term>
 <listitem>
 <para
->This file is used to communicate the authorisation data from &kdm; to the &X-Server;, using the <option
+>This file is used to communicate the authorisation data from &tdm; to the &X-Server;, using the <option
 >-auth</option
 > &X-Server; command line option. It should be kept in a directory which is not world-writable as it could easily be removed, disabling the authorisation mechanism in the &X-Server;. If not specified, a random name is generated from <option
 >AuthDir</option
@@ -1026,7 +1026,7 @@
 >xconsole</command
 > here). The conventional name for a file used here is <command
 >Xsetup</command
->. See <xref linkend="kdmrc-xsetup"/>. </para>
+>. See <xref linkend="tdmrc-xsetup"/>. </para>
 <para
 >Empty by default.</para>
 </listitem>
@@ -1043,7 +1043,7 @@
 >root</systemitem
 >) after the user authentication process succeeds. The conventional name for a file used here is <command
 >Xstartup</command
->. See <xref linkend="kdmrc-xstartup"/>. </para>
+>. See <xref linkend="tdmrc-xstartup"/>. </para>
 <para
 >Empty by default.</para>
 </listitem>
@@ -1060,7 +1060,7 @@
 >root</systemitem
 >) after the session terminates. The conventional name for a file used here is <command
 >Xreset</command
->. See <xref linkend="kdmrc-xreset"/>. </para>
+>. See <xref linkend="tdmrc-xreset"/>. </para>
 <para
 >Empty by default.</para>
 </listitem>
@@ -1075,7 +1075,7 @@
 <para
 >This specifies the session program to be executed (as the user owning the session). The conventional name for a file used here is <command
 >Xsession</command
->. See <xref linkend="kdmrc-xsession"/>. </para>
+>. See <xref linkend="tdmrc-xsession"/>. </para>
 <para
 >The default is <quote
 >${<envar
@@ -1094,7 +1094,7 @@
 <para
 >If the <option
 >Session</option
-> program fails to execute, &kdm; will fall back to this program. This program is executed with no arguments, but executes using the same environment variables as the session would have had (see <xref linkend="kdmrc-xsession"/>). </para>
+> program fails to execute, &tdm; will fall back to this program. This program is executed with no arguments, but executes using the same environment variables as the session would have had (see <xref linkend="tdmrc-xsession"/>). </para>
 <para
 >The default is <quote
 >${<envar
@@ -1119,7 +1119,7 @@
 >Session</option
 >s. </para
 ><para
->The default depends on the system &kdm; was built on. </para>
+>The default depends on the system &tdm; was built on. </para>
 </listitem>
 </varlistentry>
 
@@ -1140,7 +1140,7 @@
 >.</literal
 > (the current directory) into this entry. </para
 ><para
->The default depends on the system &kdm; was built on. </para>
+>The default depends on the system &tdm; was built on. </para>
 </listitem>
 </varlistentry>
 
@@ -1170,7 +1170,7 @@
 ></term>
 <listitem>
 <para
->When &kdm; is unable to write to the usual user authorisation file ($<envar
+>When &tdm; is unable to write to the usual user authorisation file ($<envar
 >HOME</envar
 >/.Xauthority), it creates a unique file name in this directory and points the environment variable <envar
 >XAUTHORITY</envar
@@ -1189,7 +1189,7 @@
 ></term>
 <listitem>
 <para
->If enabled, &kdm; will automatically restart a session after an &X-Server; crash (or if it is killed by Alt-Ctrl-BackSpace). Note that enabling this feature opens a security hole: a secured display lock can be circumvented (unless &kde;'s built-in screen locker is used). </para>
+>If enabled, &tdm; will automatically restart a session after an &X-Server; crash (or if it is killed by Alt-Ctrl-BackSpace). Note that enabling this feature opens a security hole: a secured display lock can be circumvented (unless &kde;'s built-in screen locker is used). </para>
 <para
 >The default is <quote
 >false</quote
@@ -1514,7 +1514,7 @@
 >chmod&nbsp;<option
 >600</option
 >&nbsp;<filename
->kdmrc</filename
+>tdmrc</filename
 ></command
 > for obvious reasons. </para>
 <para
@@ -1534,7 +1534,7 @@
 >The default is <quote
 >${<envar
 >kde_datadir</envar
->}/kdm/sessions</quote
+>}/tdm/sessions</quote
 >.</para>
 </listitem>
 </varlistentry>
@@ -1564,12 +1564,12 @@
 </sect2>
 
 
-<sect2 id="kdmrc-greeter">
+<sect2 id="tdmrc-greeter">
 <title
->The [X-*-Greeter] section class of &kdmrc;</title>
+>The [X-*-Greeter] section class of &tdmrc;</title>
 
 <para
->This section class contains options concerning the configuration of the &kdm; frontend (greeter). </para>
+>This section class contains options concerning the configuration of the &tdm; frontend (greeter). </para>
 
 <variablelist>
 
@@ -1678,7 +1678,7 @@
 ></term>
 <listitem>
 <para
->The relative coordinates (percentages of the screen size; X,Y) at which the centre of the greeter is put. &kdm; aligns the greeter to the edges of the screen it would cross otherwise. </para>
+>The relative coordinates (percentages of the screen size; X,Y) at which the centre of the greeter is put. &tdm; aligns the greeter to the edges of the screen it would cross otherwise. </para>
 <para
 >The default is <quote
 >50,50</quote
@@ -2069,7 +2069,7 @@
 <para
 >If <option
 >UserList</option
-> is enabled, this specifies where &kdm; gets the images from: </para>
+> is enabled, this specifies where &tdm; gets the images from: </para>
 <variablelist>
 <varlistentry>
 <term
@@ -2128,7 +2128,7 @@
 </variablelist>
 
 <para
->The images can be in any format Qt recognises, but the filename must match &kdm;'s expectations: <literal
+>The images can be in any format Qt recognises, but the filename must match &tdm;'s expectations: <literal
 >.face.icon</literal
 > should be a 48x48 icon, while <literal
 >.face</literal
@@ -2154,7 +2154,7 @@
 >The default is <quote
 >${<envar
 >kde_datadir</envar
->}/kdm/faces</quote
+>}/tdm/faces</quote
 >.</para>
 </listitem>
 </varlistentry>
@@ -2312,7 +2312,7 @@
 ></term>
 <listitem>
 <para
->If enabled, &kdm; will automatically start the <command
+>If enabled, &tdm; will automatically start the <command
 >krootimage</command
 > program to set up the background; otherwise, the <option
 >Setup</option
@@ -2342,7 +2342,7 @@
 >The default is <quote
 >${<envar
 >kde_confdir</envar
->}/kdm/backgroundrc</quote
+>}/tdm/backgroundrc</quote
 >.</para>
 </listitem>
 </varlistentry>
@@ -2378,7 +2378,7 @@
 ></term>
 <listitem>
 <para
->This option specifies the maximum time &kdm; will wait for the grabs to succeed. A grab may fail if some other X-client has the &X-Server; or the keyboard grabbed, or possibly if the network latencies are very high. You should be cautious when raising the timeout, as a user can be spoofed by a look-alike window on the display. If a grab fails, &kdm; kills and restarts the &X-Server; (if possible) and the session. </para>
+>This option specifies the maximum time &tdm; will wait for the grabs to succeed. A grab may fail if some other X-client has the &X-Server; or the keyboard grabbed, or possibly if the network latencies are very high. You should be cautious when raising the timeout, as a user can be spoofed by a look-alike window on the display. If a grab fails, &tdm; kills and restarts the &X-Server; (if possible) and the session. </para>
 <para
 >The default is <quote
 >3</quote
@@ -2515,12 +2515,12 @@
 ></term>
 <listitem>
 <para
->Enable &kdm;'s built-in <command
+>Enable &tdm;'s built-in <command
 >xconsole</command
->. Note that this can be enabled for only one display at a time. This option is available only if &kdm; was <command
+>. Note that this can be enabled for only one display at a time. This option is available only if &tdm; was <command
 >configure</command
 >d with <option
->--enable-kdm-xconsole</option
+>--enable-tdm-xconsole</option
 >. </para>
 <para
 >The default is <quote
@@ -2536,7 +2536,7 @@
 ></term>
 <listitem>
 <para
->The data source for &kdm;'s built-in <command
+>The data source for &tdm;'s built-in <command
 >xconsole</command
 >. If empty, a console log redirection is requested from <filename
 >/dev/console</filename
@@ -2618,7 +2618,7 @@
 <para
 >Show the <guilabel
 >Console Login</guilabel
-> action in the greeter. For this to work, a console must be configured for this particular display, see <xref linkend="kdmrc-xservers"/>. </para>
+> action in the greeter. For this to work, a console must be configured for this particular display, see <xref linkend="tdmrc-xservers"/>. </para>
 <para
 >The default is <quote
 >true</quote
@@ -2665,12 +2665,12 @@
 
 </sect1>
 
-<sect1 id="kdmrc-xservers">
+<sect1 id="tdmrc-xservers">
 <title
 >Specifying permanent &X-Server;s</title>
 
 <para
->Each specification indicates a display which should constantly be managed and which is not using &XDMCP;. This method is typically used only for local &X-Server;s that are started by &kdm;, but &kdm; can manage externally started (<quote
+>Each specification indicates a display which should constantly be managed and which is not using &XDMCP;. This method is typically used only for local &X-Server;s that are started by &tdm;, but &tdm; can manage externally started (<quote
 >foreign</quote
 >) &X-Server;s as well, may they run on the local machine or rather remotely.</para>
 
@@ -2714,12 +2714,12 @@
 >localhost</literal
 > prefix from locally running &XDMCP; displays is <emphasis
 >not</emphasis
-> stripped to make them distinguishable from local &X-Server;s started by &kdm;.</para>
+> stripped to make them distinguishable from local &X-Server;s started by &tdm;.</para>
 
 <para
 >The <replaceable
 >display class</replaceable
-> portion is also used in the display-specific sections. This is useful if you have a large collection of similar displays (such as a corral of X terminals) and would like to set options for groups of them. When using &XDMCP;, the display is required to specify the display class, so the manual for your particular X terminal should document the display class string for your device. If it does not, you can run &kdm; in debug mode and <command
+> portion is also used in the display-specific sections. This is useful if you have a large collection of similar displays (such as a corral of X terminals) and would like to set options for groups of them. When using &XDMCP;, the display is required to specify the display class, so the manual for your particular X terminal should document the display class string for your device. If it does not, you can run &tdm; in debug mode and <command
 >grep</command
 > the log for <quote
 >class</quote
@@ -2730,7 +2730,7 @@
 >tty</replaceable
 > specifies which text console an &X-Server; is <quote
 >covering</quote
->, so &kdm; knows which console it should monitor for activity after switching to <guilabel
+>, so &tdm; knows which console it should monitor for activity after switching to <guilabel
 >Console login</guilabel
 > to find out when the console session ends. Note that this concept (originating from Solaris) is not perfectly suited for Linux, as there &X-Server;s run on separate virtual terminals and consequently do not actually cover consoles (<command
 >getty</command
@@ -2739,7 +2739,7 @@
 <para
 >The <literal
 >reserve</literal
-> keyword instructs &kdm; to start the display not when &kdm; starts up, but when it is explicitly requested via the command <acronym
+> keyword instructs &tdm; to start the display not when &tdm; starts up, but when it is explicitly requested via the command <acronym
 >FiFo</acronym
 >. If reserve displays are specified, the &kde; menu will have a <guilabel
 >Start New Session</guilabel
@@ -2748,7 +2748,7 @@
 <para
 >The <replaceable
 >server command</replaceable
-> specifies the complete &X-Server; command line, including a display number for secondary displays. When &kdm; starts a session, it sets up authorisation data for the &X-Server;. For local servers, &kdm; passes <command
+> specifies the complete &X-Server; command line, including a display number for secondary displays. When &tdm; starts a session, it sets up authorisation data for the &X-Server;. For local servers, &tdm; passes <command
 ><option
 >-auth</option
 >&nbsp;<filename
@@ -2756,20 +2756,20 @@
 >filename</replaceable
 ></filename
 ></command
-> on the &X-Server;'s command line to point it at its authorisation data. For &XDMCP; displays, &kdm; passes the authorisation data to the &X-Server; via the <quote
+> on the &X-Server;'s command line to point it at its authorisation data. For &XDMCP; displays, &tdm; passes the authorisation data to the &X-Server; via the <quote
 >Accept</quote
 > &XDMCP; message.</para>
 
 </sect1>
 
-<sect1 id="kdmrc-xaccess">
+<sect1 id="tdmrc-xaccess">
 <title
 >&XDMCP; access control</title>
 
 <para
 >The file specified by the <option
 >AccessFile</option
-> option provides information which &kdm; uses to control access from displays requesting service via &XDMCP;. The file contains four types of entries: entries which control the response to <quote
+> option provides information which &tdm; uses to control access from displays requesting service via &XDMCP;. The file contains four types of entries: entries which control the response to <quote
 >Direct</quote
 > and <quote
 >Broadcast</quote
@@ -2777,7 +2777,7 @@
 >Indirect</quote
 > queries, macro definitions for <quote
 >Indirect</quote
-> entries and entries which control on which network interfaces &kdm; listens for &XDMCP; queries. Blank lines are ignored, <literal
+> entries and entries which control on which network interfaces &tdm; listens for &XDMCP; queries. Blank lines are ignored, <literal
 >#</literal
 > is treated as a comment delimiter causing the rest of that line to be ignored and <literal
 >\</literal
@@ -2796,7 +2796,7 @@
 >Direct</quote
 > queries for a host or pattern, it can be followed by the optional <literal
 >NOBROADCAST</literal
-> keyword. This can be used to prevent a &kdm; server from appearing on menus based on <quote
+> keyword. This can be used to prevent a &tdm; server from appearing on menus based on <quote
 >Broadcast</quote
 > queries.</para>
 
@@ -2811,7 +2811,7 @@
 >CHOOSER</literal
 >, <quote
 >Indirect</quote
-> queries are not forwarded, but instead a host chooser dialogue is displayed by &kdm;. The chooser will send a <quote
+> queries are not forwarded, but instead a host chooser dialogue is displayed by &tdm;. The chooser will send a <quote
 >Direct</quote
 > query to each of the remaining host names in the list and offer a menu of all the hosts that respond. The host list may contain the keyword <literal
 >BROADCAST</literal
@@ -2848,19 +2848,19 @@
 </screen
 > If one or more <literal
 >LISTEN</literal
-> lines are specified, &kdm; listens for &XDMCP; requests only on the specified interfaces. <replaceable
+> lines are specified, &tdm; listens for &XDMCP; requests only on the specified interfaces. <replaceable
 >interface</replaceable
 > may be a hostname or IP address representing a network interface on this machine, or the wildcard <literal
 >*</literal
 > to represent all available network interfaces. If multicast group addresses are listed on a <literal
 >LISTEN</literal
-> line, &kdm; joins the multicast groups on the given interface. For IPv6 multicasts, the IANA has assigned ff0<replaceable
+> line, &tdm; joins the multicast groups on the given interface. For IPv6 multicasts, the IANA has assigned ff0<replaceable
 >X</replaceable
 >:0:0:0:0:0:0:12b as the permanently assigned range of multicast addresses for &XDMCP;. The <replaceable
 >X</replaceable
-> in the prefix may be replaced by any valid scope identifier, such as 1 for Node-Local, 2 for Link-Local, 5 for Site-Local, and so on (see IETF RFC 2373 or its replacement for further details and scope definitions). &kdm; defaults to listening on the Link-Local scope address ff02:0:0:0:0:0:0:12b to most closely match the IPv4 subnet broadcast behavior. If no <literal
+> in the prefix may be replaced by any valid scope identifier, such as 1 for Node-Local, 2 for Link-Local, 5 for Site-Local, and so on (see IETF RFC 2373 or its replacement for further details and scope definitions). &tdm; defaults to listening on the Link-Local scope address ff02:0:0:0:0:0:0:12b to most closely match the IPv4 subnet broadcast behavior. If no <literal
 >LISTEN</literal
-> lines are given, &kdm; listens on all interfaces and joins the default &XDMCP; IPv6 multicast group (when compiled with IPv6 support). To disable listening for &XDMCP; requests altogether, a <literal
+> lines are given, &tdm; listens on all interfaces and joins the default &XDMCP; IPv6 multicast group (when compiled with IPv6 support). To disable listening for &XDMCP; requests altogether, a <literal
 >LISTEN</literal
 > line with no addresses may be specified, but using the <literal
 >[Xdmcp]</literal
@@ -2875,7 +2875,7 @@
 >Supplementary programs</title>
 
 <para
->The following programs are run by &kdm; at various stages of a session. They typically are shell scripts. </para>
+>The following programs are run by &tdm; at various stages of a session. They typically are shell scripts. </para>
 
 <para
 >The Setup, Startup and Reset programs are run as <systemitem class="username"
@@ -2884,7 +2884,7 @@
 >auto</literal
 > if the session results from an automatic login; otherwise, no arguments are passed to them. </para>
 
-<sect2 id="kdmrc-xsetup">
+<sect2 id="tdmrc-xsetup">
 <title
 >Setup program</title>
 
@@ -2949,7 +2949,7 @@
 </variablelist>
 
 <para
->Note that since &kdm; grabs the keyboard, any other windows will not be able to receive keyboard input. They will be able to interact with the mouse, however; beware of potential security holes here. If <option
+>Note that since &tdm; grabs the keyboard, any other windows will not be able to receive keyboard input. They will be able to interact with the mouse, however; beware of potential security holes here. If <option
 >GrabServer</option
 > is set, <filename
 >Xsetup</filename
@@ -2959,7 +2959,7 @@
 
 </sect2>
 
-<sect2 id="kdmrc-xstartup">
+<sect2 id="tdmrc-xstartup">
 <title
 >Startup program</title>
 
@@ -3054,11 +3054,11 @@
 </variablelist>
 
 <para
->&kdm; waits until this program exits before starting the user session. If the exit value of this program is non-zero, &kdm; discontinues the session and starts another authentication cycle.</para>
+>&tdm; waits until this program exits before starting the user session. If the exit value of this program is non-zero, &tdm; discontinues the session and starts another authentication cycle.</para>
 
 </sect2>
 
-<sect2 id="kdmrc-xsession">
+<sect2 id="tdmrc-xsession">
 <title
 >Session program</title>
 
@@ -3190,7 +3190,7 @@
 
 </sect2>
 
-<sect2 id="kdmrc-xreset">
+<sect2 id="tdmrc-xreset">
 <title
 >Reset program</title>