Part 1 of 2 of kdm rename

4 files changed, 248 insertions, 248 deletions

diff --git a/doc/kdm/CMakeLists.txt b/doc/kdm/CMakeLists.txt
index fe876f955..9a29fa8f8 100644
--- a/doc/kdm/CMakeLists.txt
+++ b/doc/kdm/CMakeLists.txt
@@ -9,4 +9,4 @@
 #
 #################################################
 
-tde_create_handbook( DESTINATION kdm )
+tde_create_handbook( DESTINATION tdm )
diff --git a/doc/kdm/Makefile.am b/doc/kdm/Makefile.am
index c04fe0908..3db537e3f 100644
--- a/doc/kdm/Makefile.am
+++ b/doc/kdm/Makefile.am
@@ -1,6 +1,6 @@
-conf_def = $(top_srcdir)/kdm/config.def
-ref: $(conf_def) $(top_srcdir)/kdm/confproc.pl
-	$(PERL) -w $(top_srcdir)/kdm/confproc.pl --doc $(conf_def) kdmrc-ref.docbook
+conf_def = $(top_srcdir)/tdm/config.def
+ref: $(conf_def) $(top_srcdir)/tdm/confproc.pl
+	$(PERL) -w $(top_srcdir)/tdm/confproc.pl --doc $(conf_def) tdmrc-ref.docbook
 
 KDE_LANG = en
 KDE_DOCS = AUTO
diff --git a/doc/kdm/index.docbook b/doc/kdm/index.docbook
index 43cec1bde..dde535328 100644
--- a/doc/kdm/index.docbook
+++ b/doc/kdm/index.docbook
@@ -1,21 +1,21 @@
 <?xml version="1.0" ?>
 <!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
 "dtd/kdex.dtd" [
-  <!ENTITY kappname "&kdm;">
+  <!ENTITY kappname "&tdm;">
   <!ENTITY package "tdebase">
-  <!ENTITY kdmrc "<filename>kdmrc</filename>">
+  <!ENTITY tdmrc "<filename>tdmrc</filename>">
   <!ENTITY ksmserver "<application>ksmserver</application>">
   <!ENTITY kdesktop "<application>kdesktop</application>">
   <!ENTITY XDMCP "<acronym>XDMCP</acronym>">
   <!ENTITY xdm "<application>xdm</application>">
-  <!ENTITY kdmrc-ref SYSTEM "kdmrc-ref.docbook">
+  <!ENTITY tdmrc-ref SYSTEM "tdmrc-ref.docbook">
   <!ENTITY % addindex "INCLUDE">
   <!ENTITY % English "INCLUDE" > <!-- change language only here -->
 ]>
 
 <book lang="&language;">
 <bookinfo>
-<title>The &kdm; Handbook</title>
+<title>The &tdm; Handbook</title>
 
 <authorgroup>
 <author>
@@ -53,13 +53,13 @@
 <releaseinfo>0.05.02</releaseinfo>
 
 <abstract>
-<para>This document describes &kdm; the &kde; Display Manager. &kdm;
+<para>This document describes &tdm; the &kde; Display Manager. &tdm;
 is also known as the <quote>Login Manager</quote>.</para>
 </abstract>
 
 <keywordset>
 <keyword>KDE</keyword>
-<keyword>kdm</keyword>
+<keyword>tdm</keyword>
 <keyword>xdm</keyword>
 <keyword>display manager</keyword>
 <keyword>login manager</keyword>
@@ -70,9 +70,9 @@ is also known as the <quote>Login Manager</quote>.</para>
 <chapter id="introduction">
 <title>Introduction</title>
 
-<para>&kdm; provides a graphical interface that allows you to log in to a
+<para>&tdm; provides a graphical interface that allows you to log in to a
 system. It prompts for login (username) and password, authenticates the user
-and starts a <quote>session</quote>.  &kdm; is superior to &xdm;, the X
+and starts a <quote>session</quote>.  &tdm; is superior to &xdm;, the X
 Display Manager, in a number of ways.</para>
 
 </chapter>
@@ -81,7 +81,7 @@ Display Manager, in a number of ways.</para>
 <!-- * Just enough config to get it to run and login to KDE 
      * Adding more session types (GNOME, etc)
      * Adding other customizations to XSession (ssh/gpg-agent, etc)
-     * Further customization to KDM (via the kcontrol module, and by 
+     * Further customization to TDM (via the kcontrol module, and by 
        hand)
      * XDMCP by query
      * XDMCP by broadcast
@@ -137,10 +137,10 @@ look in their documentation for the correct command.</para>
 
 <para>At this point, typing <userinput><command>startx</command></userinput>
 on the commandline should start X, with a &kde; session.  The next task is
-to try &kdm;.</para>
+to try &tdm;.</para>
 
 <para>As <systemitem class="username">root</systemitem>, type
-<userinput><command>kdm</command></userinput> at the prompt.</para>
+<userinput><command>tdm</command></userinput> at the prompt.</para>
 
 <para>You should see a login window, which is described more fully in <xref
 linkend="login" />.</para>
@@ -154,7 +154,7 @@ above for each of them.</para>
 
 <note>
 <para>This is a quick guide to getting up and running only.  You probably
-will want to customize &kdm; further, for example, to hide the names of the
+will want to customize &tdm; further, for example, to hide the names of the
 system accounts, to allow further sessions, and much more.  Please read
 through the rest of this manual to find out how to do these things.</para>
 </note>
@@ -164,7 +164,7 @@ through the rest of this manual to find out how to do these things.</para>
 <chapter id="login"> 
 <title>The Login Window</title> 
 
-<para> The user interface to &kdm; consists of two dialog boxes.  The main
+<para> The user interface to &tdm; consists of two dialog boxes.  The main
 dialog box has these controls:</para>
 
 <itemizedlist> 
@@ -186,7 +186,7 @@ imitation of the login box on &IRIX;).</para>
 </listitem>
 
 <listitem>
-<para>A <guilabel>Menu</guilabel> drop down box that allows &kdm; to be used
+<para>A <guilabel>Menu</guilabel> drop down box that allows &tdm; to be used
 to start sessions with various different window managers or desktop
 environments installed on the system.</para>
 </listitem>
@@ -233,7 +233,7 @@ and bring up the login dialog again.</para>
 <listitem>
 <para>(Optionally on local displays) A <guimenuitem>Console
 Mode</guimenuitem> item that terminates the currently running &X-Server; and
-leaves you alone with a console login. &kdm; will resume the graphical login
+leaves you alone with a console login. &tdm; will resume the graphical login
 if nobody is logged in at the console for some time.</para>
 </listitem>
 </itemizedlist>
@@ -285,56 +285,56 @@ software.</para>
 
 <para>Pressing the <guibutton>OK</guibutton> button initiates the selected
 action; pressing the <guibutton>Cancel</guibutton> button returns to the
-main &kdm; dialog box. </para>
+main &tdm; dialog box. </para>
 
 </chapter>
 
 <!-- *********************************************************************** -->
-<chapter id="configuring-kdm">
-<title>Configuring &kdm;</title>
+<chapter id="configuring-tdm">
+<title>Configuring &tdm;</title>
 
-<para>This chapter assumes that &kdm; is already up and running on your
+<para>This chapter assumes that &tdm; is already up and running on your
 system, and that you simply want to change its behavior in some way.</para>
 
-<para>When &kdm; starts up, it reads its configuration from the folder
-<filename class="directory">$TDEDIR/share/config/kdm/</filename> (this may
-be <filename class="directory">/etc/trinity/kdm/</filename> or something else
+<para>When &tdm; starts up, it reads its configuration from the folder
+<filename class="directory">$TDEDIR/share/config/tdm/</filename> (this may
+be <filename class="directory">/etc/trinity/tdm/</filename> or something else
 on your system).</para>
 
-<para>The main configuration file is &kdmrc;; all other files are
+<para>The main configuration file is &tdmrc;; all other files are
 referenced from there and could be stored under any name anywhere on
 the system - but usually that would not make much sense for obvious
 reasons (one particular exception is referencing configuration files
-of an already installed &xdm; - however when a new &kdm; is installed,
+of an already installed &xdm; - however when a new &tdm; is installed,
 it will import settings from those files if it finds an already installed
 &xdm;).</para>
 
-<para>Since &kdm; must run before any user is logged in, it is not
+<para>Since &tdm; must run before any user is logged in, it is not
 associated with any particular user. Therefore, it is not possible to have
-user-specific configuration files; all users share the common &kdmrc;.  It
-follows from this that the configuration of &kdm; can only be altered by
+user-specific configuration files; all users share the common &tdmrc;.  It
+follows from this that the configuration of &tdm; can only be altered by
 those users that have write access to
-<filename>$<envar>TDEDIR</envar>/share/config/kdm/kdmrc</filename> (normally
+<filename>$<envar>TDEDIR</envar>/share/config/tdm/tdmrc</filename> (normally
 restricted to system administrators logged in as <systemitem
 class="username">root</systemitem>).</para>
 
-<para>You can view the &kdmrc; file currently in use on your system, and you
-can configure &kdm; by editing this file. Alternatively, you can use the
+<para>You can view the &tdmrc; file currently in use on your system, and you
+can configure &tdm; by editing this file. Alternatively, you can use the
 graphical configuration tool provided by the &kcontrolcenter; (under
 <menuchoice><guisubmenu>System Administration</guisubmenu><guimenuitem>Login
 Manager</guimenuitem></menuchoice>), which is described in <ulink
 url="help:/kcontrol/login-manager.html">the &kcontrolcenter; help files</ulink>.
 </para>
 
-<para>The remainder of this chapter describes configuration of &kdm;
-via the &kcontrolcenter; module, and the <link linkend="kdm-files">next
-chapter</link> describes the options available in &kdmrc; itself. If
+<para>The remainder of this chapter describes configuration of &tdm;
+via the &kcontrolcenter; module, and the <link linkend="tdm-files">next
+chapter</link> describes the options available in &tdmrc; itself. If
 you only need to configure for local users, the &kcontrolcenter; module
 should be sufficient for your needs.  If you need to configure remote
-logins, or have multiple &kdm; sessions running, you will need to read
+logins, or have multiple &tdm; sessions running, you will need to read
 on.</para>
 
-<sect1 id="kdm-kcontrol-module">
+<sect1 id="tdm-kcontrol-module">
 <sect1info>
 <authorgroup>
 <author>&Thomas.Tanghus; &Thomas.Tanghus.mail;</author>
@@ -346,31 +346,31 @@ on.</para>
 <title>The Login Manager &kcontrolcenter; Module</title>
 
 <para>Using this module, you can configure the &kde; graphical login
-manager, &kdm;.  You can change how the login screen looks, who has
+manager, &tdm;.  You can change how the login screen looks, who has
 access using the login manager and who can shutdown the
 computer.</para>
 
 <note><para>All settings will be written to the configuration file
-&kdmrc;, which in its original state has many comments to help you
-configure &kdm;.  Using this &kcontrolcenter; module will strip these
-comments from the file.  All available options in &kdmrc; are covered
-in <xref linkend="kdm-files"/>.</para>
+&tdmrc;, which in its original state has many comments to help you
+configure &tdm;.  Using this &kcontrolcenter; module will strip these
+comments from the file.  All available options in &tdmrc; are covered
+in <xref linkend="tdm-files"/>.</para>
 
 <para>The options listed in this chapter are cross referenced with
-their equivalents in &kdmrc;. All options available in the &kcontrol;
-module are also available directly in &kdmrc; but the reverse is not
+their equivalents in &tdmrc;. All options available in the &kcontrol;
+module are also available directly in &tdmrc; but the reverse is not
 true.</para></note>
 
 <para>In order to organize all of these options, this module is
 divided into several sections: <link
-linkend="kdmconfig-appearance"><guilabel>Appearance</guilabel></link>,
-<link linkend="kdmconfig-font"><guilabel>Font</guilabel></link>, <link
-linkend="kdmconfig-background"><guilabel>Background</guilabel></link>,
+linkend="tdmconfig-appearance"><guilabel>Appearance</guilabel></link>,
+<link linkend="tdmconfig-font"><guilabel>Font</guilabel></link>, <link
+linkend="tdmconfig-background"><guilabel>Background</guilabel></link>,
 <link
-linkend="kdmconfig-shutdown"><guilabel>Shutdown</guilabel></link>,
-<link linkend="kdmconfig-users"><guilabel>Users</guilabel></link> and
+linkend="tdmconfig-shutdown"><guilabel>Shutdown</guilabel></link>,
+<link linkend="tdmconfig-users"><guilabel>Users</guilabel></link> and
 <link
-linkend="kdmconfig-convenience"><guilabel>Convenience</guilabel></link>.</para>
+linkend="tdmconfig-convenience"><guilabel>Convenience</guilabel></link>.</para>
 
 <para>You can switch between the sections using the tabs at the top of
 the window.</para>
@@ -381,10 +381,10 @@ Button. You will then be asked for a superuser password.  Entering a
 correct password will allow you to modify the settings of this
 module.</para></note>
 
-<sect2 id="kdmconfig-appearance">
+<sect2 id="tdmconfig-appearance">
 <title>Appearance</title>
 
-<para>From this page you can change the visual appearance of &kdm;,
+<para>From this page you can change the visual appearance of &tdm;,
 &kde;'s graphical login manager.</para>
 
 <para>The <guilabel>Greeting:</guilabel> is the title of the login
@@ -392,13 +392,13 @@ module.</para></note>
  may log in to.  You may use various placeholders, which are described
  along with the corresponding key
  <link linkend="option-greetstring"><option>GreetString</option></link>
- in &kdmrc;.
+ in &tdmrc;.
 </para>
 
 <para>You can then choose to show either the current system time, a logo or
 nothing special in the login box.  Make your choice in the radio buttons
 labeled <guilabel>Logo area:</guilabel>. This corresponds to <link
-linkend="option-logoarea"><option>LogoArea</option></link> in &kdmrc;</para>
+linkend="option-logoarea"><option>LogoArea</option></link> in &tdmrc;</para>
 
 <para>If you chose <guilabel>Show logo</guilabel> you can now choose a
 logo:</para>
@@ -414,7 +414,7 @@ dialog.</para>
 </itemizedlist>
 
 <para>If you do not specify a logo the default
-<filename>$<envar>TDEDIR</envar>/share/apps/kdm/pics/kdelogo.xpm</filename>
+<filename>$<envar>TDEDIR</envar>/share/apps/tdm/pics/kdelogo.xpm</filename>
 will be displayed.</para>
 
 <para>Normally the login box is centered on the screen.  Use the
@@ -425,23 +425,23 @@ relative to the top left of the display, in the fields labeled
 <guilabel>X:</guilabel> and <guilabel>Y:</guilabel> respectively.
 These correspond to the key
 <link linkend="option-greeterpos"><option>GreeterPos</option></link>
-in &kdmrc;.</para>
+in &tdmrc;.</para>
 
 <para>While &kde;'s style depends on the settings of the user logged
-in, the style used by &kdm; can be configured using the <guilabel>GUI
+in, the style used by &tdm; can be configured using the <guilabel>GUI
 Style:</guilabel> and <guilabel>Color Scheme:</guilabel> options.
 These correspond to the keys <link
 linkend="option-guistyle"><option>GUIStyle</option></link> and <link
 linkend="option-colorscheme"><option>ColorScheme</option></link> in
-&kdmrc; respectively.</para>
+&tdmrc; respectively.</para>
 
 <para>Below that, you have a drop down box to choose the language for
 your login box, corresponding to setting <option>Language</option> in
-&kdmrc;.</para>
+&tdmrc;.</para>
 
 </sect2>
 
-<sect2 id="kdmconfig-font">
+<sect2 id="tdmconfig-font">
 <title>Font</title>
 
 <para>From this section of the module you can change the fonts used in the
@@ -474,7 +474,7 @@ fonts</guilabel> if you want smoothed fonts in the login dialog.</para>
 
 </sect2>
 
-<sect2 id="kdmconfig-background">
+<sect2 id="tdmconfig-background">
 <title>Background</title>
 
 <para>Here you can change the desktop background which will be displayed
@@ -612,7 +612,7 @@ stretched to fit all four corners.</para> </listitem>
 
 </sect2>
 
-<sect2 id="kdmconfig-shutdown">
+<sect2 id="tdmconfig-shutdown">
 <title><guilabel>Shutdown</guilabel></title>
 
 <para><guilabel>Allow Shutdown</guilabel></para>
@@ -620,13 +620,13 @@ stretched to fit all four corners.</para> </listitem>
 <itemizedlist>
 <listitem>
 <para><guilabel>Nobody</guilabel>: No one can shutdown the computer using
-&kdm;.  You must be logged in, and execute a command.</para>
+&tdm;.  You must be logged in, and execute a command.</para>
 </listitem>
 <listitem>
 <para><guilabel>Everybody</guilabel>:  Everyone can shutdown the computer using
-&kdm;.</para>
+&tdm;.</para>
 </listitem>
-<listitem><para><guilabel>Only Root</guilabel>: &kdm; requires that the
+<listitem><para><guilabel>Only Root</guilabel>: &tdm; requires that the
 <systemitem>root</systemitem> password be entered before shutting down the
 computer.</para></listitem> 
 </itemizedlist>
@@ -638,12 +638,12 @@ shutdown command for the <guilabel>Local:</guilabel> and
 <para><emphasis>Commands</emphasis></para> <para>Use these text fields to
 define the exact shutdown command.</para> <para>The
 <guilabel>Halt:</guilabel> command defaults to <!-- Are these defaults still
-correct? they disagree with what's in --> <!-- kdmrc -->
+correct? they disagree with what's in --> <!-- tdmrc -->
 <command>/sbin/halt</command>.  The <guilabel>Restart:</guilabel> command
 defaults to
 <command>/sbin/reboot</command>.</para>
 
-<para>When <guilabel>Show boot options</guilabel> is enabled, &kdm;
+<para>When <guilabel>Show boot options</guilabel> is enabled, &tdm;
 will on reboot offer you options for the lilo boot manager. For this
 feature to work, you will need to supply the correct paths to your
 <command>lilo</command> command and to lilo's map file.  Note that this
@@ -651,13 +651,13 @@ option is not available on all operating systems.</para>
 
 </sect2>
 
-<sect2 id="kdmconfig-users">
+<sect2 id="tdmconfig-users">
 <title>Users</title>
 
 <para>From here you can change the way users are represented in the
 login window.</para>
 
-<para>You may disable the user list in &kdm; entirely in the
+<para>You may disable the user list in &tdm; entirely in the
 <guilabel>Show Users</guilabel> section.  You can choose from:</para>
 
 <variablelist>
@@ -692,7 +692,7 @@ over 65000, are not shown.</para>
 <para>You can also enable the <guilabel>Sort users</guilabel>
 checkbox, to have the user list sorted alphabetically.  If this is
 disabled, users will appear in the order they are listed in the
-password file.  &kdm; will also autocomplete user names if you enable the
+password file.  &tdm; will also autocomplete user names if you enable the
 <guilabel>Autocompletion</guilabel> option.</para>
 
 <para>If you choose to show users, then the login window will show
@@ -714,7 +714,7 @@ this terminal.</para>
 
 </sect2>
 
-<sect2 id="kdmconfig-convenience">
+<sect2 id="tdmconfig-convenience">
 <title>Convenience</title>
 
 <para>In the <guilabel>convenience</guilabel> tab you can configure
@@ -758,12 +758,12 @@ password-less login, &eg;
 <systemitem>guest</systemitem>.</para></important>
 
 <para>You can also choose which user is <quote>preselected</quote>
-when &kdm; starts. The default is <guilabel>None</guilabel>, but you
-can choose <guilabel>Previous</guilabel> to have &kdm; default to the
+when &tdm; starts. The default is <guilabel>None</guilabel>, but you
+can choose <guilabel>Previous</guilabel> to have &tdm; default to the
 last successfully logged in user, or you can
 <guilabel>Specify</guilabel> a particular user to always be selected
-from the list.  You can also have &kdm; set the focus to the password
-field, so that when you reach the &kdm; login screen, you can type the
+from the list.  You can also have &tdm; set the focus to the password
+field, so that when you reach the &tdm; login screen, you can type the
 password immediately.</para>
 
 <para>The <guilabel>Automatically login after X server crash</guilabel>
@@ -778,18 +778,18 @@ server accidentally crashed.</para>
 
 </chapter>
 
-&kdmrc-ref;
+&tdmrc-ref;
 
 <!-- ************************************************************ -->   
-<chapter id="configuring-your-system-for-kdm">
-<title>Configuring your system to use &kdm;</title>
+<chapter id="configuring-your-system-for-tdm">
+<title>Configuring your system to use &tdm;</title>
 
 <para>This chapter assumes that your system is already configured to
 run the &X-Window;, and that you only need to reconfigure it to
 allow graphical login.</para>
 
-<sect1 id="setting-up-kdm">
-<title>Setting up &kdm;</title>
+<sect1 id="setting-up-tdm">
+<title>Setting up &tdm;</title>
 
 <para>The fundamental thing that controls whether your computer boots to a
 terminal prompt (console mode) or a graphical login prompt is the default
@@ -829,11 +829,11 @@ distributions is:</para>
 </itemizedlist>
 
 <para>The first step in configuring your system is to ensure that you
-can start &kdm; from the command line. Once this is working, you can
-change your system configuration so that &kdm; starts automatically
+can start &tdm; from the command line. Once this is working, you can
+change your system configuration so that &tdm; starts automatically
 each time you reboot your system.</para>
 
-<para>To test &kdm;, you must first bring your system to a runlevel
+<para>To test &tdm;, you must first bring your system to a runlevel
 that does not run &xdm;. To do so, issue a command like this:</para>
 
 <screen><command>/sbin/init <option>3</option></command></screen>
@@ -847,23 +847,23 @@ systems, you should check that your <abbrev>PAM</abbrev> configuration permits
 login through the service named <literal>kde</literal>. If you previously used
 &xdm; successfully, you should not need to make any
 changes to your <abbrev>PAM</abbrev> configuration in order to use
-&kdm;. <filename>/etc/pam.conf</filename> or
+&tdm;. <filename>/etc/pam.conf</filename> or
 <filename>/etc/pam.d/kde</filename>. Information on configuring
 <abbrev>PAM</abbrev> is beyond the scope of this handbook, but
 <abbrev>PAM</abbrev> comes with comprehensive documentation (try looking in
 <filename>/usr/share/doc/*pam*/html/</filename>).</para>
 
-<para>Now it's time for you to test &kdm; by issuing the following
+<para>Now it's time for you to test &tdm; by issuing the following
 command:</para>
 
-<screen><command>kdm <option>-nodaemon</option></command>
+<screen><command>tdm <option>-nodaemon</option></command>
 </screen>
 
-<para>If you get a &kdm; login dialog and you are able to log in,
+<para>If you get a &tdm; login dialog and you are able to log in,
 things are going well.  The main thing that can go wrong here is that
 the run-time linker might not find the shared &Qt; or &kde; libraries.
 If you have a binary distribution of the &kde; libraries, make sure
-&kdm; is installed where the libraries believe &kde; is installed and
+&tdm; is installed where the libraries believe &kde; is installed and
 try setting some environment variables to point to your &kde; and &Qt;
 libraries.</para>
 
@@ -883,8 +883,8 @@ libraries.</para>
 make sure that you are not suffering from a more serious X
 configuration problem.</para>
 
-<para>When you are able to start &kdm; successfully, you can start to
-replace &xdm; by &kdm;. Again, this is distribution-dependent.</para>
+<para>When you are able to start &tdm; successfully, you can start to
+replace &xdm; by &tdm;. Again, this is distribution-dependent.</para>
 
 <itemizedlist>
 <listitem>
@@ -892,16 +892,16 @@ replace &xdm; by &kdm;. Again, this is distribution-dependent.</para>
  line:</para>
 <screen>x:5:respawn:/usr/X11/bin/xdm -nodaemon</screen>
 <para>and replace with:</para>
-<screen>x:5:respawn:/opt/kde/bin/kdm</screen>
-<para>This tells <command>init</command>(8) to respawn &kdm; when the
-system is in run level  5. Note that &kdm; does not need the
+<screen>x:5:respawn:/opt/kde/bin/tdm</screen>
+<para>This tells <command>init</command>(8) to respawn &tdm; when the
+system is in run level  5. Note that &tdm; does not need the
  <option>-nodaemon</option> option.</para>
 </listitem>
 <listitem>
 <para>For &Mandrake;, the X11 runlevel in
 <filename>/etc/inittab</filename> invokes the shell script
 <filename>/etc/X11/prefdm</filename>, which is set up to select from
-amongst several display managers, including &kdm;. Make sure that all
+amongst several display managers, including &tdm;. Make sure that all
 the paths are correct for your installation.</para> 
 </listitem>
 <listitem>
@@ -909,22 +909,22 @@ the paths are correct for your installation.</para>
 first line:</para>
 
 <screen>. /etc/rc.config
-DISPLAYMANAGER=kdm
+DISPLAYMANAGER=tdm
 export DISPLAYMANAGER</screen>
 </listitem>
 <listitem><para>For FreeBSD, edit <filename>/etc/ttys</filename> and find
 the line like this:</para>
 <screen>ttyv8   "/usr/X11R6/bin/xdm -nodaemon"  xterm   off secure</screen>
 <para>and edit it to this:</para>
-<screen>ttyv8   "/usr/local/bin/kdm"  xterm   on secure</screen>
+<screen>ttyv8   "/usr/local/bin/tdm"  xterm   on secure</screen>
 </listitem>
 
 <listitem><para>Most other distributions are a variation of one of
 these.</para></listitem>
 </itemizedlist>
 
-<para>At this stage, you can test &kdm; again by bringing your system
-to the runlevel that should now run &kdm;. To do so, issue a command
+<para>At this stage, you can test &tdm; again by bringing your system
+to the runlevel that should now run &tdm;. To do so, issue a command
 like this:</para>
 
 <screen><command>/sbin/init <option>5</option></command>
@@ -950,7 +950,7 @@ at your peril.</para></warning>
 <screen>id:5:initdefault:</screen>
 
 <para>When you reboot your system, you should end up with the
-graphical &kdm; login dialog.</para>
+graphical &tdm; login dialog.</para>
 
 <para>If this step is unsuccessful the most likely problem is that the
 environment used at boot time differs from the environment that you used for
@@ -964,24 +964,24 @@ some way.</para>
 
 </chapter>
 
-<chapter id="different-window-managers-with-kdm">
+<chapter id="different-window-managers-with-tdm">
 <title>Supporting multiple window managers</title>
 
-<para>&kdm; detects most available window manager and desktop environments when
+<para>&tdm; detects most available window manager and desktop environments when
 it is run.  Installing a new one should make it automatically available in
-the &kdm; main dialog <guilabel>Session Type:</guilabel>.</para>
+the &tdm; main dialog <guilabel>Session Type:</guilabel>.</para>
 
-<para>If you have a very new window manager, or something that &kdm; does
+<para>If you have a very new window manager, or something that &tdm; does
 not support, the first thing you should check is that the application to be
 run is in the <envar>PATH</envar> and has not been renamed during the
 install into something unexpected.</para>
 
 <para>If the case is that the application is too new and not yet supported
-by &kdm;, you can quite simply add a new session.</para>
+by &tdm;, you can quite simply add a new session.</para>
 
 <para>The sessions are defined in <firstterm>.desktop</firstterm> files in
 <filename
-class="directory">$<envar>TDEDIR</envar>/share/apps/kdm/sessions</filename>.
+class="directory">$<envar>TDEDIR</envar>/share/apps/tdm/sessions</filename>.
 You can simply add an appropriately named <literal
 role="extension">.desktop</literal> file in this directory. The fields
 are:</para>
@@ -995,7 +995,7 @@ Exec=<replaceable>executable name</replaceable> <lineannotation>Passed to
 <command>eval exec</command> in a Bourne shell</lineannotation>
 TryExec=<replaceable>executable name</replaceable> <lineannotation>Supported
 but not required</lineannotation>
-Name=<replaceable>name to show in the &kdm; session list</replaceable></programlisting>
+Name=<replaceable>name to show in the &tdm; session list</replaceable></programlisting>
 
 <para>There are also three <quote>magic</quote>:</para>
 
@@ -1004,7 +1004,7 @@ Name=<replaceable>name to show in the &kdm; session list</replaceable></programl
 <term>default</term>
 <listitem>
 <para>
-The default session for &kdm; is normally &kde; but can be configured by the
+The default session for &tdm; is normally &kde; but can be configured by the
 system administrator.
 </para>
 </listitem>
@@ -1032,14 +1032,14 @@ purposes.
 to the config dir and edit it at will. Removing the shipped session types
 can be accomplished by <quote>shadowing</quote> them with .desktop files
 containing Hidden=true.  For the magic session types no .desktop files exist
-by default, but &kdm; pretends they would, so you can override them like any
+by default, but &tdm; pretends they would, so you can override them like any
 other type.  I guess you already know how to add a new session type by
 now. ;-)</para>
 
 </chapter>
 
-<chapter id="xdmcp-with-kdm">
-<title>Using &kdm; for Remote Logins (&XDMCP;)</title>
+<chapter id="xdmcp-with-tdm">
+<title>Using &tdm; for Remote Logins (&XDMCP;)</title>
 
 <para>&XDMCP; is the Open Group standard, the <quote>X Display Manager
 Control Protocol</quote>.  This is used to set up connections between
@@ -1068,7 +1068,7 @@ this.</para>
 <sect1 id="command-sockets">
 <title>Command Sockets</title>
 
-<para>This is a feature you can use to remote-control &kdm;. It's mostly
+<para>This is a feature you can use to remote-control &tdm;. It's mostly
 intended for use by &ksmserver; and &kdesktop; from a running session, but
 other applications are possible as well.</para>
 
@@ -1149,9 +1149,9 @@ is attempted, but a scheduled "login" command will be executed.</para>
 
 <variablelist>
 <varlistentry>
-<term><returnvalue>&kdm;</returnvalue></term>
+<term><returnvalue>&tdm;</returnvalue></term>
 <listitem>
-<para>identifies &kdm;, in case some other DM implements this protocol,
+<para>identifies &tdm;, in case some other DM implements this protocol,
 too</para>
 </listitem>
 </varlistentry>
@@ -1280,7 +1280,7 @@ means immediately.</para>
 <para><parameter>end</parameter> is the latest time at which the shutdown
 should be performed if active sessions are still running.  If it starts with
 a plus-sign, the start time is added.  -1 means wait infinitely.  If end is
-through and active sessions are still running, &kdm; can do one of the
+through and active sessions are still running, &tdm; can do one of the
 following:</para>
 <itemizedlist>
 <listitem><para><parameter>cancel</parameter> - give up the
@@ -1346,21 +1346,21 @@ $<envar>DM_CONTROL</envar>; the name of per-display sockets can be derived
 from $<envar>DISPLAY</envar>.</para>
 </listitem>
 <listitem>
-<para>By using the <command>kdmctl</command> command (&eg; from within a
-shell script). Try <command>kdmctl</command> <option>-h</option> to find out
+<para>By using the <command>tdmctl</command> command (&eg; from within a
+shell script). Try <command>tdmctl</command> <option>-h</option> to find out
 more.</para>
 </listitem>
 </itemizedlist>
 
 <para>Here is an example bash script <quote>reboot into FreeBSD</quote>:</para>
 
-<programlisting>if kdmctl | grep -q shutdown; then
+<programlisting>if tdmctl | grep -q shutdown; then
   IFS=$'\t'
-  set -- `kdmctl listbootoptions`
+  set -- `tdmctl listbootoptions`
   if [ "$1" = ok ]; then
         fbsd=$(echo "$2" | tr ' ' '\n' | sed -ne 's,\\s, ,g;/freebsd/I{p;q}')
         if [ -n "$fbsd" ]; then
-      kdmctl shutdown reboot "=$fbsd" ask &gt; /dev/null
+      tdmctl shutdown reboot "=$fbsd" ask &gt; /dev/null
         else
           echo "FreeBSD boot unavailable."
         fi
@@ -1372,14 +1372,14 @@ else
 fi</programlisting>
 
 </sect1>
-<!-- Riddell: so there's no GUI you need to edit kdmrc to say UseTheme=true and Theme=/path/to/theme.xml
+<!-- Riddell: so there's no GUI you need to edit tdmrc to say UseTheme=true and Theme=/path/to/theme.xml
 [13:31] <Riddell> jriddell.org/programs has an example theme 
 
 <sect1 id="dm-themes">
 <title>Themes</title>
 
-&kdm; has limited support for desktop manager themes.  You may enable them
-by adding <userinput>UseTheme=true</userinput> to <filename>kdmrc</filename>
+&tdm; has limited support for desktop manager themes.  You may enable them
+by adding <userinput>UseTheme=true</userinput> to <filename>tdmrc</filename>
 and <userinput>Theme=/path/to/theme.xml</userinput>.  
 </sect1>
 -->
@@ -1388,12 +1388,12 @@ and <userinput>Theme=/path/to/theme.xml</userinput>.
 <chapter id="Other-Information">
 <title>Other sources of information</title>
 
-<para>Since &kdm; is descended from &xdm;, the <ulink
+<para>Since &tdm; is descended from &xdm;, the <ulink
 url="man:xdm">&xdm; man page</ulink> may provide useful background
 information. For X-related problems try the man pages <ulink
 url="man:X">X</ulink> and <ulink url="man:startx">startx</ulink>. If you have
-questions about &kdm; that are not answered by this handbook, take advantage of
-the fact the &kdm; is provided under the terms of the <abbrev>&GNU;</abbrev>
+questions about &tdm; that are not answered by this handbook, take advantage of
+the fact the &tdm; is provided under the terms of the <abbrev>&GNU;</abbrev>
 General Public License: look at the source code.
 </para>
 
@@ -1402,19 +1402,19 @@ General Public License: look at the source code.
 
 <chapter id="credits"><title>Credits and License</title>
 
-<para>&kdm; is derived from, and includes code from,
+<para>&tdm; is derived from, and includes code from,
 &xdm; (C) Keith Packard, MIT X Consortium.</para>
 
-<para>&kdm; 0.1 was written by &Matthias.Ettrich;.  Later versions till &kde;
+<para>&tdm; 0.1 was written by &Matthias.Ettrich;.  Later versions till &kde;
 2.0.x were written by &Steffen.Hansen;.  Some new features for &kde; 2.1.x and
 a major rewrite for &kde; 2.2.x made by &Oswald.Buddenhagen;.</para>
 
-<para>Other parts of the &kdm; code are copyright by the authors, and
+<para>Other parts of the &tdm; code are copyright by the authors, and
 licensed under the terms of the <ulink url="common/gpl-license.html">&GNU;
-GPL</ulink>. Anyone is allowed to change &kdm; and redistribute the result
+GPL</ulink>. Anyone is allowed to change &tdm; and redistribute the result
 as long as the names of the authors are mentioned.</para>
 
-<para>&kdm; requires the &Qt; library, which is copyright Troll Tech AS.</para>
+<para>&tdm; requires the &Qt; library, which is copyright Troll Tech AS.</para>
 
 <para>Documentation contributors:
 <itemizedlist>
@@ -1449,7 +1449,7 @@ man page, which is &copy; Keith Packard.</para>
 
 <glossentry id="gloss-greeter">
 <glossterm>greeter</glossterm>
-<glossdef><para>The greeter is the login dialog, &ie; the part of &kdm;
+<glossdef><para>The greeter is the login dialog, &ie; the part of &tdm;
 which the user sees.</para>
 </glossdef>
 </glossentry>
diff --git a/doc/kdm/kdmrc-ref.docbook b/doc/kdm/kdmrc-ref.docbook
index 9ebcfbdd3..f2cfd2f0e 100644
--- a/doc/kdm/kdmrc-ref.docbook
+++ b/doc/kdm/kdmrc-ref.docbook
@@ -1,19 +1,19 @@
-<!-- generated from ../../kdm/config.def - DO NOT EDIT! -->
+<!-- generated from ../../tdm/config.def - DO NOT EDIT! -->
 
-<chapter id="kdm-files">
-<title>The Files &kdm; Uses for Configuration</title>
+<chapter id="tdm-files">
+<title>The Files &tdm; Uses for Configuration</title>
 
-<para>This chapter documents the files that control &kdm;'s behavior.
+<para>This chapter documents the files that control &tdm;'s behavior.
 Some of this can be also controlled from the &kcontrol; module, but
 not all.</para>
 
-<sect1 id="kdmrc">
-<title>&kdmrc; - The &kdm; master configuration file</title>
+<sect1 id="tdmrc">
+<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 unrecognized key/section identifiers cause &kdm; to
+Syntactic errors and unrecognized key/section identifiers cause &tdm; to
 issue non-fatal error messages.</para>
 
 <para>Lines beginning with <literal>#</literal> are comments; empty lines
@@ -124,13 +124,13 @@ have the usual meaning; the backslash quotes everything (not only special
 characters). Note that the backslashes need to be doubled because of the
 two levels of quoting.</para>
 
-<note><para>A pristine &kdmrc; is very thoroughly commented.
+<note><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">
-<title>The [General] section of &kdmrc;</title>
+<sect2 id="tdmrc-general">
+<title>The [General] section of &tdmrc;</title>
 
 <para>
 This section contains global options that do not fit into any specific section.
@@ -144,7 +144,7 @@ This section contains global options that do not fit into any specific section.
 <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.
+upgrades and this could result in &tdm; failing to run.
 </para>
 </listitem>
 </varlistentry>
@@ -153,12 +153,12 @@ upgrades and this could result in &kdm; failing to run.
 <term id="option-staticservers"><option>StaticServers</option></term>
 <listitem>
 <para>
-List of displays (&X-Server;s) permanently managed by &kdm;. Displays with a
+List of displays (&X-Server;s) permanently managed by &tdm;. Displays with a
 hostname are foreign displays which are expected to be already running,
-the others are local displays for which &kdm; starts an own &X-Server;;
+the others are local displays for which &tdm; starts an own &X-Server;;
 see <option>ServerCmd</option>. Each display may belong to a display class;
 append it to the display name separated by an underscore.
-See <xref linkend="kdmrc-xservers"/> for the details.
+See <xref linkend="tdmrc-xservers"/> for the details.
 </para>
 <para>The default is <quote>:0</quote>.</para>
 </listitem>
@@ -180,7 +180,7 @@ List of on-demand displays. See <option>StaticServers</option> for syntax.
 <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
+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.
 Currently Linux only.
@@ -194,14 +194,14 @@ Currently Linux only.
 <listitem>
 <para>
 This option is for operating systems (<acronym>OS</acronym>s) with support
-for virtual terminals (<acronym>VT</acronym>s), by both &kdm; and the
+for virtual terminals (<acronym>VT</acronym>s), by both &tdm; and the
 <acronym>OS</acronym>s itself.
 Currently this applies only to Linux.
 </para><para>
-When &kdm; switches to console mode, it starts monitoring all
+When &tdm; switches to console mode, it starts monitoring all
 <acronym>TTY</acronym> lines listed here (without the leading
 <literal>/dev/</literal>).
-If none of them is active for some time, &kdm; switches back to the X login.
+If none of them is active for some time, &tdm; switches back to the X login.
 </para>
 <para>Empty by default.</para>
 </listitem>
@@ -212,7 +212,7 @@ If none of them is active for some time, &kdm; switches back to the X login.
 <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
+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>
@@ -223,7 +223,7 @@ if the filename is empty.
 <term id="option-lockpidfile"><option>LockPidFile</option></term>
 <listitem>
 <para>
-This option controls whether &kdm; uses file locking to keep multiple
+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>.</para>
@@ -234,8 +234,8 @@ display managers from running onto each other.
 <term id="option-authdir"><option>AuthDir</option></term>
 <listitem>
 <para>
-This names a directory under which &kdm; stores &X-Server; authorization
-files while initializing the session. &kdm; expects the system to clean up
+This names a directory under which &tdm; stores &X-Server; authorization
+files while initializing the session. &tdm; expects the system to clean up
 this directory from stale files on reboot.
 </para><para>
 The authorization file to be used for a particular display can be
@@ -249,7 +249,7 @@ specified with the <option>AuthFile</option> option in [X-*-Core].
 <term id="option-autorescan"><option>AutoRescan</option></term>
 <listitem>
 <para>
-This boolean controls whether &kdm; automatically re-reads its
+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>.</para>
@@ -260,7 +260,7 @@ configuration files if it finds them to have changed.
 <term id="option-exportlist"><option>ExportList</option></term>
 <listitem>
 <para>
-Additional environment variables &kdm; should pass on to all programs it runs.
+Additional environment variables &tdm; should pass on to all programs it runs.
 <envar>LD_LIBRARY_PATH</envar> and <envar>XCURSOR_THEME</envar> are good candidates;
 otherwise, it should not be necessary very often.
 </para>
@@ -275,7 +275,7 @@ otherwise, it should not be necessary very often.
 If the system has no native entropy source like /dev/urandom (see
 <option>RandomDevice</option>) and no entropy daemon like EGD (see
 <option>PrngdSocket</option> and <option>PrngdPort</option>) is running,
-&kdm; will fall back to its own pseudo-random number generator
+&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>
@@ -313,7 +313,7 @@ Same as <option>PrngdSocket</option>, only use a TCP socket on localhost.
 <term id="option-randomdevice"><option>RandomDevice</option></term>
 <listitem>
 <para>
-The path to a character device which &kdm; should read random data from.
+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
@@ -348,10 +348,10 @@ can be either a name or a numerical ID.
 <term id="option-datadir"><option>DataDir</option></term>
 <listitem>
 <para>
-The directory in which &kdm; should store persistent working data; such data
+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>.</para>
+<para>The default is <quote>/var/lib/tdm</quote>.</para>
 </listitem>
 </varlistentry>
 
@@ -359,7 +359,7 @@ is, for example, the previous user that logged in on a particular display.
 <term id="option-dmrcdir"><option>DmrcDir</option></term>
 <listitem>
 <para>
-The directory in which &kdm; should store users' <filename>.dmrc</filename> files. This is only
+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>
@@ -371,11 +371,11 @@ needed if the home directories are not readable before actually logging in
 </sect2>
 
 
-<sect2 id="kdmrc-xdmcp">
-<title>The [Xdmcp] section of &kdmrc;</title>
+<sect2 id="tdmrc-xdmcp">
+<title>The [Xdmcp] section of &tdmrc;</title>
 
 <para>
-This section contains options that control &kdm;'s handling of
+This section contains options that control &tdm;'s handling of
 &XDMCP; requests.
 </para>
 
@@ -385,7 +385,7 @@ This section contains options that control &kdm;'s handling of
 <term id="option-enable"><option>Enable</option></term>
 <listitem>
 <para>
-Whether &kdm; should listen to incoming &XDMCP; requests.
+Whether &tdm; should listen to incoming &XDMCP; requests.
 </para>
 <para>The default is <quote>true</quote>.</para>
 </listitem>
@@ -395,7 +395,7 @@ Whether &kdm; should listen to incoming &XDMCP; requests.
 <term id="option-port"><option>Port</option></term>
 <listitem>
 <para>
-This indicates the UDP port number which &kdm; uses to listen for incoming
+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>
@@ -408,7 +408,7 @@ default value.
 <listitem>
 <para>
 XDM-AUTHENTICATION-1 style &XDMCP; authentication requires a private
-key to be shared between &kdm; and the terminal. This option specifies
+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>
@@ -424,9 +424,9 @@ To prevent unauthorized &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"/>.
+described in <xref linkend="tdmrc-xaccess"/>.
 </para>
-<para>The default is <quote>${<envar>kde_confdir</envar>}/kdm/Xaccess</quote>.</para>
+<para>The default is <quote>${<envar>kde_confdir</envar>}/tdm/Xaccess</quote>.</para>
 </listitem>
 </varlistentry>
 
@@ -450,7 +450,7 @@ is offered again.
 <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
+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>
@@ -489,8 +489,8 @@ displayed in a chooser window. If no program is specified, the string
 </sect2>
 
 
-<sect2 id="kdmrc-shutdown">
-<title>The [Shutdown] section of &kdmrc;</title>
+<sect2 id="tdmrc-shutdown">
+<title>The [Shutdown] section of &tdmrc;</title>
 
 <para>
 This section contains global options concerning system shutdown.
@@ -504,7 +504,7 @@ This section contains global options concerning system shutdown.
 <para>
 The command (subject to word splitting) to run to halt/poweroff the system.
 </para><para>
-The default is something reasonable for the system on which &kdm; was built, like
+The default is something reasonable for the system on which &tdm; was built, like
 <command>/sbin/shutdown&nbsp;<option>-h</option>&nbsp;<parameter>now</parameter></command>.
 </para>
 </listitem>
@@ -516,7 +516,7 @@ The default is something reasonable for the system on which &kdm; was built, lik
 <para>
 The command (subject to word splitting) to run to reboot the system.
 </para><para>
-The default is something reasonable for the system &kdm; on which was built, like
+The default is something reasonable for the system &tdm; on which was built, like
 <command>/sbin/shutdown&nbsp;<option>-r</option>&nbsp;<parameter>now</parameter></command>.
 </para>
 </listitem>
@@ -549,7 +549,7 @@ This will have no effect unless <option>AllowFifo</option> is enabled.
 <term id="option-bootmanager"><option>BootManager</option></term>
 <listitem>
 <para>
-The boot manager &kdm; should use for offering boot options in the
+The boot manager &tdm; should use for offering boot options in the
 shutdown dialog.
 </para>
 <variablelist>
@@ -574,12 +574,12 @@ shutdown dialog.
 </sect2>
 
 
-<sect2 id="kdmrc-core">
-<title>The [X-*-Core] section class of &kdmrc;</title>
+<sect2 id="tdmrc-core">
+<title>The [X-*-Core] section class of &tdmrc;</title>
 
 <para>
 This section class contains options concerning the configuration
-of the &kdm; backend (core).
+of the &tdm; backend (core).
 </para>
 
 <variablelist>
@@ -608,7 +608,7 @@ See <option>OpenRepeat</option>.
 <term id="option-openrepeat"><option>OpenRepeat</option></term>
 <listitem>
 <para>
-These options control the behavior of &kdm; when attempting to open a
+These options control the behavior 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> is the number of attempts to make and
@@ -625,7 +625,7 @@ connection attempt, the start attempt is considered failed.
 <term id="option-startattempts"><option>StartAttempts</option></term>
 <listitem>
 <para>
-How many times &kdm; should attempt to start a <literal>foreign</literal>
+How many times &tdm; should attempt to start a <literal>foreign</literal>
 display listed in <option>StaticServers</option> before giving up
 and disabling it.
 Local displays are attempted only once, and &XDMCP; displays are retried
@@ -640,7 +640,7 @@ was given to the &X-Server;).
 <term id="option-serverattempts"><option>ServerAttempts</option></term>
 <listitem>
 <para>
-How many times &kdm; should attempt to start up a local &X-Server;.
+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>.</para>
@@ -651,7 +651,7 @@ Starting up includes executing it and waiting for it to come up.
 <term id="option-servertimeout"><option>ServerTimeout</option></term>
 <listitem>
 <para>
-How many seconds &kdm; should wait for a local &X-Server; to come up.
+How many seconds &tdm; should wait for a local &X-Server; to come up.
 </para>
 <para>The default is <quote>15</quote>.</para>
 </listitem>
@@ -664,7 +664,7 @@ How many seconds &kdm; should wait for a local &X-Server; to come up.
 The command line to start the &X-Server;, without display number and VT spec.
 This string is subject to word splitting.
 </para><para>
-The default is something reasonable for the system on which &kdm; was built,
+The default is something reasonable for the system on which &tdm; was built,
 like <command>/usr/X11R6/bin/X</command>.
 </para>
 </listitem>
@@ -698,7 +698,7 @@ This string is subject to word splitting.
 <para>
 The VT the &X-Server; should run on.
 <option>ServerVTs</option> should be used instead of this option.
-Leave it zero to let &kdm; assign a <acronym>VT</acronym> automatically.
+Leave it zero to let &tdm; assign a <acronym>VT</acronym> automatically.
 Set it to <literal>-1</literal> to avoid assigning a <acronym>VT</acronym>
 alltogether - this is required for setups with multiple physical consoles.
 Currently Linux only.
@@ -711,13 +711,13 @@ Currently Linux only.
 <listitem>
 <para>
 This option is for <acronym>OS</acronym>s without support for
-<acronym>VT</acronym>s, either by &kdm; or the <acronym>OS</acronym> itself.
+<acronym>VT</acronym>s, either by &tdm; or the <acronym>OS</acronym> itself.
 Currently this applies to all <acronym>OS</acronym>s but Linux.
 </para><para>
-When &kdm; switches to console mode, it starts monitoring this
+When &tdm; switches to console mode, it starts monitoring this
 <acronym>TTY</acronym> line (specified without the leading
 <literal>/dev/</literal>) for activity. If the line is not used for some time,
-&kdm; switches back to the X login.
+&tdm; switches back to the X login.
 </para>
 <para>Empty by default.</para>
 </listitem>
@@ -737,7 +737,7 @@ See <option>PingTimeout</option>.
 <term id="option-pingtimeout"><option>PingTimeout</option></term>
 <listitem>
 <para>
-To discover when <emphasis>remote</emphasis> displays disappear, &kdm;
+To discover when <emphasis>remote</emphasis> displays disappear, &tdm;
 regularly pings them.
 <option>PingInterval</option> specifies the time (in minutes) between the
 pings and <option>PingTimeout</option> specifies the maximum amount of
@@ -757,7 +757,7 @@ accidentally disabled.
 <term id="option-terminateserver"><option>TerminateServer</option></term>
 <listitem>
 <para>
-Whether &kdm; should restart the local &X-Server; after session exit instead
+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>
@@ -789,7 +789,7 @@ The signal number to use to terminate the local &X-Server;.
 <term id="option-authorize"><option>Authorize</option></term>
 <listitem>
 <para>
-Controls whether &kdm; generates and uses authorization for
+Controls whether &tdm; generates and uses authorization for
 <emphasis>local</emphasis> &X-Server; connections.
 For &XDMCP; displays the authorization requested by the display is used;
 foreign non-&XDMCP; displays do not support authorization at all.
@@ -817,9 +817,9 @@ depending on the build configuration.
 <para>
 Some <emphasis>old</emphasis> &X-Server;s re-read the authorization file
 at &X-Server; reset time, instead of when checking the initial connection.
-As &kdm; generates the authorization information just before connecting to
+As &tdm; generates the authorization information just before connecting to
 the display, an old &X-Server; would not get up-to-date authorization
-information. This option causes &kdm; to send SIGHUP to the &X-Server;
+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 authorization information will be read.
 </para>
@@ -831,7 +831,7 @@ during which time the new authorization information will be read.
 <term id="option-authfile"><option>AuthFile</option></term>
 <listitem>
 <para>
-This file is used to communicate the authorization data from &kdm; to
+This file is used to communicate the authorization 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 authorization mechanism in
@@ -879,7 +879,7 @@ greeter window. This may be used to change the appearance of the screen
 around the greeter window or to put up other windows (e.g., you may want
 to run <command>xconsole</command> here).
 The conventional name for a program used here is <command>Xsetup</command>.
-See <xref linkend="kdmrc-xsetup"/>.
+See <xref linkend="tdmrc-xsetup"/>.
 </para>
 <para>Empty by default.</para>
 </listitem>
@@ -894,7 +894,7 @@ It specifies a program which is run (as
 <systemitem class="username">root</systemitem>) after the user
 authentication process succeeds.
 The conventional name for a program used here is <command>Xstartup</command>.
-See <xref linkend="kdmrc-xstartup"/>.
+See <xref linkend="tdmrc-xstartup"/>.
 </para>
 <para>Empty by default.</para>
 </listitem>
@@ -909,7 +909,7 @@ It specifies a program which is run (as
 <systemitem class="username">root</systemitem>) after the session
 terminates.
 The conventional name for a program used here is <command>Xreset</command>.
-See <xref linkend="kdmrc-xreset"/>.
+See <xref linkend="tdmrc-xreset"/>.
 </para>
 <para>Empty by default.</para>
 </listitem>
@@ -923,7 +923,7 @@ This string is subject to word splitting.
 It specifies the session program to be executed (as the user owning
 the session).
 The conventional name for a program used here is <command>Xsession</command>.
-See <xref linkend="kdmrc-xsession"/>.
+See <xref linkend="tdmrc-xsession"/>.
 </para>
 <para>The default is <quote>${<envar>x_bindir</envar>}/xterm -ls -T</quote>.</para>
 </listitem>
@@ -933,10 +933,10 @@ See <xref linkend="kdmrc-xsession"/>.
 <term id="option-failsafeclient"><option>FailsafeClient</option></term>
 <listitem>
 <para>
-If the <option>Session</option> program fails to execute, &kdm; will
+If the <option>Session</option> 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="kdmrc-xsession"/>).
+have had (see <xref linkend="tdmrc-xsession"/>).
 </para>
 <para>The default is <quote>${<envar>x_bindir</envar>}/xterm</quote>.</para>
 </listitem>
@@ -949,7 +949,7 @@ have had (see <xref linkend="kdmrc-xsession"/>).
 The <envar>PATH</envar> environment variable for
 non-<systemitem class="username">root</systemitem> <option>Session</option>s.
 </para><para>
-The default depends on the system &kdm; was built on.
+The default depends on the system &tdm; was built on.
 </para>
 </listitem>
 </varlistentry>
@@ -963,7 +963,7 @@ non-<systemitem class="username">root</systemitem>
 <option>Session</option>s. Note that it is good practice not to include
 <literal>.</literal> (the current directory) into this entry.
 </para><para>
-The default depends on the system &kdm; was built on.
+The default depends on the system &tdm; was built on.
 </para>
 </listitem>
 </varlistentry>
@@ -983,7 +983,7 @@ The <envar>SHELL</envar> environment variable for all programs but the
 <term id="option-userauthdir"><option>UserAuthDir</option></term>
 <listitem>
 <para>
-When &kdm; is unable to write to the usual user authorization file
+When &tdm; is unable to write to the usual user authorization file
 ($<envar>HOME</envar>/.Xauthority), it creates a unique file name in this
 directory and points the environment variable <envar>XAUTHORITY</envar>
 at the created file.
@@ -996,7 +996,7 @@ at the created file.
 <term id="option-autorelogin"><option>AutoReLogin</option></term>
 <listitem>
 <para>
-If enabled, &kdm; will automatically restart a session after an &X-Server;
+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).
@@ -1196,7 +1196,7 @@ The user to log in automatically. <emphasis>Never</emphasis> specify <systemitem
 <para>
 The password for the user to log in automatically. This is <emphasis>not</emphasis> required
 unless the user is logged into a <acronym>NIS</acronym> or Kerberos domain. If you use this
-option, you should <command>chmod&nbsp;<option>600</option>&nbsp;<filename>kdmrc</filename></command> for obvious reasons.
+option, you should <command>chmod&nbsp;<option>600</option>&nbsp;<filename>tdmrc</filename></command> for obvious reasons.
 </para>
 <para>Empty by default.</para>
 </listitem>
@@ -1219,7 +1219,7 @@ KDE sessions.
 <para>
 A list of directories containing session type definitions.
 </para>
-<para>The default is <quote>${<envar>kde_datadir</envar>}/kdm/sessions</quote>.</para>
+<para>The default is <quote>${<envar>kde_datadir</envar>}/tdm/sessions</quote>.</para>
 </listitem>
 </varlistentry>
 
@@ -1240,7 +1240,7 @@ literal <literal>%</literal>.
 <term id="option-usesessreg"><option>UseSessReg</option></term>
 <listitem>
 <para>
-Specify whether &kdm;'s built-in utmp/wtmp/lastlog registration should
+Specify whether &tdm;'s built-in utmp/wtmp/lastlog registration should
 be used. If it is not, the tool <command>sessreg</command> should be used
 in the <option>Startup</option> and <option>Reset</option> scripts, or,
 alternatively, the pam_lastlog module should be used on
@@ -1254,12 +1254,12 @@ alternatively, the pam_lastlog module should be used on
 </sect2>
 
 
-<sect2 id="kdmrc-greeter">
-<title>The [X-*-Greeter] section class of &kdmrc;</title>
+<sect2 id="tdmrc-greeter">
+<title>The [X-*-Greeter] section class of &tdmrc;</title>
 
 <para>
 This section class contains options concerning the configuration
-of the &kdm; frontend (greeter).
+of the &tdm; frontend (greeter).
 </para>
 
 <variablelist>
@@ -1329,7 +1329,7 @@ The image to show in the greeter if <option>LogoArea</option> is
 <listitem>
 <para>
 The relative coordinates (percentages of the screen size; X,Y) at which
-the center of the greeter is put. &kdm; aligns the greeter to the edges
+the center 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>.</para>
@@ -1563,7 +1563,7 @@ See <option>ShowUsers</option>.
 <term id="option-facesource"><option>FaceSource</option></term>
 <listitem>
 <para>
-If <option>UserList</option> is enabled, this specifies where &kdm; gets the
+If <option>UserList</option> is enabled, this specifies where &tdm; gets the
 images from:
 </para>
 <variablelist>
@@ -1587,7 +1587,7 @@ images from:
 
 <para>
 The images can be in any format Qt recognizes, but the filename
-must match &kdm;'s expectations: <literal>.face.icon</literal> should be a
+must match &tdm;'s expectations: <literal>.face.icon</literal> should be a
 48x48 icon, while <literal>.face</literal> should be a 300x300 image.
 Currently the big image is used only as a fallback and is scaled down,
 but in the future it might be displayed full-size in the logo area or a
@@ -1603,7 +1603,7 @@ tooltip.
 <para>
 See <option>FaceSource</option>.
 </para>
-<para>The default is <quote>${<envar>kde_datadir</envar>}/kdm/faces</quote>.</para>
+<para>The default is <quote>${<envar>kde_datadir</envar>}/tdm/faces</quote>.</para>
 </listitem>
 </varlistentry>
 
@@ -1692,7 +1692,7 @@ character</para></listitem>
 <term id="option-usebackground"><option>UseBackground</option></term>
 <listitem>
 <para>
-If enabled, &kdm; will automatically start the <command>krootimage</command>
+If enabled, &tdm; will automatically start the <command>krootimage</command>
 program to set up the background; otherwise, the <option>Setup</option>
 program is responsible for the background.
 </para>
@@ -1709,7 +1709,7 @@ It contains a section named <literal>[Desktop0]</literal> like
 <filename>kdesktoprc</filename> does. Its options are not described
 herein; guess their meanings or use the control center.
 </para>
-<para>The default is <quote>${<envar>kde_confdir</envar>}/kdm/backgroundrc</quote>.</para>
+<para>The default is <quote>${<envar>kde_confdir</envar>}/tdm/backgroundrc</quote>.</para>
 </listitem>
 </varlistentry>
 
@@ -1735,11 +1735,11 @@ grabbed until just before the session begins.
 <term id="option-grabtimeout"><option>GrabTimeout</option></term>
 <listitem>
 <para>
-This option specifies the maximum time &kdm; will wait for the grabs to
+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, &kdm; kills and
+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>.</para>
@@ -1826,10 +1826,10 @@ login domain.
 <term id="option-showlog"><option>ShowLog</option></term>
 <listitem>
 <para>
-Enable &kdm;'s built-in <command>xconsole</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>configure</command>d
-with <option>--enable-kdm-xconsole</option>.
+This option is available only if &tdm; was <command>configure</command>d
+with <option>--enable-tdm-xconsole</option>.
 </para>
 <para>The default is <quote>false</quote>.</para>
 </listitem>
@@ -1839,7 +1839,7 @@ with <option>--enable-kdm-xconsole</option>.
 <term id="option-logsource"><option>LogSource</option></term>
 <listitem>
 <para>
-The data source for &kdm;'s built-in <command>xconsole</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>.
 Has no effect if <option>ShowLog</option> is disabled.
@@ -1950,13 +1950,13 @@ file.
 
 </sect1>
 
-<sect1 id="kdmrc-xservers">
+<sect1 id="tdmrc-xservers">
 <title>Specifying permanent &X-Server;s</title>
 
 <para>Each entry in the <option>StaticServers</option> list 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
+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>
 
@@ -1975,7 +1975,7 @@ The display name of &XDMCP; displays is derived from the display's address by
 reverse host name resolution. For configuration purposes, the
 <literal>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>
+&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
@@ -1983,11 +1983,11 @@ 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
+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>.</para>
 
 <para>The displays specified in <option>ReserveServers</option> will not be
-started when &kdm; starts up, but when it is explicitly requested via
+started when &tdm; starts up, but when it is explicitly requested via
 the command socket (or <acronym>FiFo</acronym>).
 If reserve displays are specified, the &kde; menu will have a
 <guilabel>Start New Session</guilabel> item near the bottom; use that to
@@ -1995,26 +1995,26 @@ activate a reserve display with a new login session. The monitor will switch
 to the new display, and you will have a minute to login. If there are no more
 reserve displays available, the menu item will be disabled.</para>
 
-<para>When &kdm; starts a session, it sets up authorization data for the
-&X-Server;. For local servers, &kdm; passes
+<para>When &tdm; starts a session, it sets up authorization data for the
+&X-Server;. For local servers, &tdm; passes
 <command><option>-auth</option>&nbsp;<filename><replaceable>filename</replaceable></filename></command>
 on the &X-Server;'s command line to point it at its authorization data.
-For &XDMCP; displays, &kdm; passes the authorization data to the &X-Server;
+For &XDMCP; displays, &tdm; passes the authorization 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
+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> queries, entries which
 control the response to <quote>Indirect</quote> queries, macro definitions for
 <quote>Indirect</quote> entries, and entries which control on which network
-interfaces &kdm; listens for &XDMCP; queries.
+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>
 causes an immediately following newline to be ignored, allowing indirect host
@@ -2039,7 +2039,7 @@ Preceding the entry with a <literal>!</literal> character causes hosts which
 match that entry to be excluded.
 To only respond to <quote>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
+This can be used to prevent a &tdm; server from appearing on menus based on
 <quote>Broadcast</quote> queries.</para>
 
 <para>An <quote>Indirect</quote> entry also contains a host name or pattern,
@@ -2057,7 +2057,7 @@ the hop count is used as the TTL.
 -->
 If the indirect host list contains the keyword <literal>CHOOSER</literal>,
 <quote>Indirect</quote> queries are not forwarded, but instead a host chooser
-dialog is displayed by &kdm;. The chooser will send a <quote>Direct</quote>
+dialog 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>, to make the chooser send a
@@ -2079,21 +2079,21 @@ The formal syntax is
 <screen>
 <userinput>&nbsp;<literal>LISTEN</literal>&nbsp;[<replaceable>interface</replaceable>&nbsp;[<replaceable>multicast&nbsp;list</replaceable>]]</userinput>
 </screen>
-If one or more <literal>LISTEN</literal> lines are specified, &kdm; listens
+If one or more <literal>LISTEN</literal> 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,
+&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
+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
+If no <literal>LISTEN</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
@@ -2103,11 +2103,11 @@ the <literal>[Xdmcp]</literal> <option>Enable</option> option is preferred.
 
 </sect1>
 
-<sect1 id="kdm-scripts">
+<sect1 id="tdm-scripts">
 <title>Supplementary programs</title>
 
 <para>
-The following programs are run by &kdm; at various stages of a session.
+The following programs are run by &tdm; at various stages of a session.
 They typically are shell scripts.
 </para>
 
@@ -2119,7 +2119,7 @@ Their first argument is <literal>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>
 
 <para>
@@ -2156,7 +2156,7 @@ the following environment variables are passed:</para>
  </varlistentry>
 </variablelist>
 
-<para> Note that since &kdm; grabs the keyboard, any other windows will not be
+<para> 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> will not be able to connect to the display
@@ -2166,7 +2166,7 @@ at all. Resources for this program can be put into the file named by
 
 </sect2>
 
-<sect2 id="kdmrc-xstartup">
+<sect2 id="tdmrc-xstartup">
 <title>Startup program</title>
 
 <para>The <filename>Xstartup</filename> program is run as
@@ -2215,13 +2215,13 @@ the following environment variables are passed:</para>
  </varlistentry>
 </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
+<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>
 
 <para>The <filename>Xsession</filename> program is the command which is run
@@ -2295,7 +2295,7 @@ the following environment variables are passed:</para>
 
 </sect2>
 
-<sect2 id="kdmrc-xreset">
+<sect2 id="tdmrc-xreset">
 <title>Reset program</title>
 
 <para>Symmetrical with <filename>Xstartup</filename>, the