summaryrefslogtreecommitdiffstats
path: root/tde-i18n-en_GB/docs/tdebase/kdm/index.docbook
diff options
context:
space:
mode:
authorTimothy Pearson <kb9vqf@pearsoncomputing.net>2012-01-22 00:25:42 -0600
committerTimothy Pearson <kb9vqf@pearsoncomputing.net>2012-01-22 00:25:42 -0600
commite198274bd57f0df7acf739d62cc17d9aa2960593 (patch)
treef838211d3cb6d2afd5c90539562108cd3b9c2f92 /tde-i18n-en_GB/docs/tdebase/kdm/index.docbook
parent1da9a128f97a0a873e8675322fd4f0f8eaa241db (diff)
downloadtde-i18n-e198274bd57f0df7acf739d62cc17d9aa2960593.tar.gz
tde-i18n-e198274bd57f0df7acf739d62cc17d9aa2960593.zip
Part 1 of 2 of kdm rename
Diffstat (limited to 'tde-i18n-en_GB/docs/tdebase/kdm/index.docbook')
-rw-r--r--tde-i18n-en_GB/docs/tdebase/kdm/index.docbook216
1 files changed, 108 insertions, 108 deletions
diff --git a/tde-i18n-en_GB/docs/tdebase/kdm/index.docbook b/tde-i18n-en_GB/docs/tdebase/kdm/index.docbook
index 8a207a0ffa8..c0c5a7e2a2a 100644
--- a/tde-i18n-en_GB/docs/tdebase/kdm/index.docbook
+++ b/tde-i18n-en_GB/docs/tdebase/kdm/index.docbook
@@ -1,10 +1,10 @@
<?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 XDMCP "<acronym
>XDMCP</acronym
@@ -12,7 +12,7 @@
<!ENTITY xdm "<application
>xdm</application
>">
- <!ENTITY kdmrc-ref SYSTEM "kdmrc-ref.docbook">
+ <!ENTITY tdmrc-ref SYSTEM "tdmrc-ref.docbook">
<!ENTITY % addindex "INCLUDE">
<!ENTITY % British-English "INCLUDE"
> <!-- change language only here -->
@@ -21,7 +21,7 @@
<book lang="&language;">
<bookinfo>
<title
->The &kdm; Handbook</title>
+>The &tdm; Handbook</title>
<authorgroup>
<author
@@ -85,7 +85,7 @@
<abstract>
<para
->This document describes &kdm; the &kde; Display Manager. &kdm; is also known as the <quote
+>This document describes &tdm; the &kde; Display Manager. &tdm; is also known as the <quote
>Login Manager</quote
>.</para>
</abstract>
@@ -94,7 +94,7 @@
<keyword
>KDE</keyword>
<keyword
->kdm</keyword>
+>tdm</keyword>
<keyword
>xdm</keyword>
<keyword
@@ -110,9 +110,9 @@
>Introduction</title>
<para
->&kdm; 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
+>&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 Display Manager, in a number of ways.</para>
+>. &tdm; is superior to &xdm;, the X Display Manager, in a number of ways.</para>
</chapter>
@@ -120,7 +120,7 @@
<!-- * 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
@@ -201,14 +201,14 @@
><command
>startx</command
></userinput
-> on the commandline should start X, with a &kde; session. The next task is to try &kdm;.</para>
+> on the commandline should start X, with a &kde; session. The next task is to try &tdm;.</para>
<para
>As <systemitem class="username"
>root</systemitem
>, type <userinput
><command
->kdm</command
+>tdm</command
></userinput
> at the prompt.</para>
@@ -225,7 +225,7 @@
<note>
<para
->This is a quick guide to getting up and running only. You probably will want to customise &kdm; 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>
+>This is a quick guide to getting up and running only. You probably will want to customise &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>
</chapter>
@@ -237,7 +237,7 @@
>
<para
->The user interface to &kdm; consists of two dialogue boxes. The main dialogue box has these controls:</para>
+>The user interface to &tdm; consists of two dialogue boxes. The main dialogue box has these controls:</para>
<itemizedlist
>
@@ -266,7 +266,7 @@
<para
>A <guilabel
>Menu</guilabel
-> drop-down box that allows &kdm; to be used to start sessions with various different window managers or desktop environments installed on the system.</para>
+> 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>
<listitem>
@@ -333,7 +333,7 @@
<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 if nobody is logged in at the console for some time. To make this work, you need to use the local@&lt;console&gt; syntax in the <filename
+> item that terminates the currently running &X-Server; and leaves you alone with a console login. &tdm; will resume the graphical login if nobody is logged in at the console for some time. To make this work, you need to use the local@&lt;console&gt; syntax in the <filename
>Xservers</filename
> file (see comments in that file).</para>
</listitem>
@@ -398,39 +398,39 @@
>OK</guibutton
> button initiates the selected action; pressing the <guibutton
>Cancel</guibutton
-> button returns to the main &kdm; dialogue box. </para>
+> button returns to the main &tdm; dialogue box. </para>
</chapter>
<!-- *********************************************************************** -->
-<chapter id="configuring-kdm">
+<chapter id="configuring-tdm">
<title
->Configuring &kdm;</title>
+>Configuring &tdm;</title>
<para
->This chapter assumes that &kdm; is already up and running on your system, and that you simply want to change its behaviour in some way.</para>
+>This chapter assumes that &tdm; is already up and running on your system, and that you simply want to change its behaviour in some way.</para>
<para
->When &kdm; starts up, it reads its configuration from the folder <filename class="directory"
->$TDEDIR/share/config/kdm/</filename
+>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/kde3/kdm/</filename
+>/etc/kde3/tdm/</filename
> or something else on your system).</para>
<para
->The main configuration file is &kdmrc;; 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, it will import settings from those files if it finds an already installed &xdm;).</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 &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 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 those users that have write access to <filename
+>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 &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
+>/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 graphical configuration tool provided by the &kcontrolcenter; (under <menuchoice
+>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
@@ -441,11 +441,11 @@
>. </para>
<para
->The remainder of this chapter describes configuration of &kdm; via the &kcontrol; module, and the <link linkend="kdm-files"
+>The remainder of this chapter describes configuration of &tdm; via the &kcontrol; module, and the <link linkend="tdm-files"
>next chapter</link
-> describes the options available in &kdmrc; itself. If you only need to configure for local users, the &kcontrol; 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 on.</para>
+> describes the options available in &tdmrc; itself. If you only need to configure for local users, the &kcontrol; module should be sufficient for your needs. If you need to configure remote 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
@@ -476,38 +476,38 @@
>The Login Manager &kcontrol; 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 access using the login manager and who can shutdown the computer.</para>
+>Using this module, you can configure the &kde; graphical login 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 it's original state has many comments to help you configure &kdm;. Using this &kcontrol; module will strip these comments from the file. All available options in &kdmrc; are covered in <xref linkend="kdm-files"/>.</para>
+>All settings will be written to the configuration file &tdmrc;, which in it's original state has many comments to help you configure &tdm;. Using this &kcontrol; 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 true.</para
+>The options listed in this chapter are cross referenced with 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 organise all of these options, this module is divided into several sections: <link linkend="kdmconfig-appearance"
+>In order to organise all of these options, this module is divided into several sections: <link linkend="tdmconfig-appearance"
><guilabel
>Appearance</guilabel
></link
->, <link linkend="kdmconfig-font"
+>, <link linkend="tdmconfig-font"
><guilabel
>Font</guilabel
></link
->, <link linkend="kdmconfig-background"
+>, <link linkend="tdmconfig-background"
><guilabel
>Background</guilabel
></link
->, <link linkend="kdmconfig-shutdown"
+>, <link linkend="tdmconfig-shutdown"
><guilabel
>Shutdown</guilabel
></link
->, <link linkend="kdmconfig-users"
+>, <link linkend="tdmconfig-users"
><guilabel
>Users</guilabel
></link
-> and <link linkend="kdmconfig-convenience"
+> and <link linkend="tdmconfig-convenience"
><guilabel
>Convenience</guilabel
></link
@@ -523,12 +523,12 @@
> 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;, &kde;'s graphical login manager.</para>
+>From this page you can change the visual appearance of &tdm;, &kde;'s graphical login manager.</para>
<para
>The <guilabel
@@ -537,7 +537,7 @@
><option
>GreetString</option
></link
-> in &kdmrc;. </para>
+> 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 labelled <guilabel
@@ -546,7 +546,7 @@
><option
>LogoArea</option
></link
-> in &kdmrc;</para>
+> in &tdmrc;</para>
<para
>If you chose <guilabel
@@ -568,7 +568,7 @@
>If you do not specify a logo the default <filename
>$<envar
>TDEDIR</envar
->/share/apps/kdm/pics/kdelogo.xpm</filename
+>/share/apps/tdm/pics/kdelogo.xpm</filename
> will be displayed.</para>
<para
@@ -582,10 +582,10 @@
><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
+>While &kde;'s style depends on the settings of the user logged in, the style used by &tdm; can be configured using the <guilabel
>GUI Style:</guilabel
> and <guilabel
>Colour Scheme:</guilabel
@@ -597,16 +597,16 @@
><option
>ColorScheme</option
></link
-> in &kdmrc; respectively.</para>
+> in &tdmrc; respectively.</para>
<para
>Below that, you have a dropdown box to choose the language for your login box, corresponding to setting <option
>Language</option
-> in &kdmrc;.</para>
+> in &tdmrc;.</para>
</sect2>
-<sect2 id="kdmconfig-font">
+<sect2 id="tdmconfig-font">
<title
>Font</title>
@@ -657,7 +657,7 @@
</sect2>
-<sect2 id="kdmconfig-background">
+<sect2 id="tdmconfig-background">
<title
>Background</title>
@@ -856,7 +856,7 @@
</sect2>
-<sect2 id="kdmconfig-shutdown">
+<sect2 id="tdmconfig-shutdown">
<title
><guilabel
>Shutdown</guilabel
@@ -873,19 +873,19 @@
<para
><guilabel
>Nobody</guilabel
->: No one can shutdown the computer using &kdm;. You must be logged in, and execute a command.</para>
+>: No one can shutdown the computer using &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>
+>: Everyone can shutdown the computer using &tdm;.</para>
</listitem>
<listitem
><para
><guilabel
>Only Root</guilabel
->: &kdm; requires that the <systemitem
+>: &tdm; requires that the <systemitem
>root</systemitem
> password be entered before shutting down the computer.</para
></listitem
@@ -917,12 +917,12 @@
<para
>When <guilabel
>Show boot options</guilabel
-> is enabled, &kdm; 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
+> 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.</para>
-<sect3 id="kdmconfig-sess">
+<sect3 id="tdmconfig-sess">
<title
>Session types</title>
@@ -952,7 +952,7 @@
</sect3>
</sect2>
-<sect2 id="kdmconfig-users">
+<sect2 id="tdmconfig-users">
<title
>Users</title>
@@ -960,7 +960,7 @@
>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 <guilabel
+>You may disable the user list in &tdm; entirely in the <guilabel
>Show Users</guilabel
> section. You can choose from:</para>
<variablelist>
@@ -1028,7 +1028,7 @@
<para
>If you choose not to show users, then the login window will be more traditional. Users will need to type their username and password to gain entrance. This is the preferred way if you have many users on this terminal.</para>
-<sect3 id="kdmconfig-showusers">
+<sect3 id="tdmconfig-showusers">
<title
>To show (and sort) or not to show users</title>
@@ -1049,7 +1049,7 @@
</sect3>
-<sect3 id="kdmconfig-whichusers">
+<sect3 id="tdmconfig-whichusers">
<title
>How to determine which users to show and which users to hide</title>
@@ -1081,7 +1081,7 @@
</sect3>
-<sect3 id="kdmconfig-select">
+<sect3 id="tdmconfig-select">
<title
>Select users</title>
@@ -1100,7 +1100,7 @@
</sect3>
-<sect3 id="kdmconfig-image">
+<sect3 id="tdmconfig-image">
<title
>Images</title>
@@ -1115,13 +1115,13 @@
>Every user on the system can be represented by an image. The image for each user is kept in a file called <filename
>$<envar
>TDEDIR</envar
->/share/apps/kdm/pics/users/$<envar
+>/share/apps/tdm/pics/users/$<envar
>USER</envar
>.xpm</filename
>. If there is no such file for a particular user, the file <filename
>$<envar
>TDEDIR</envar
->/share/apps/kdm/pics/users/default.xpm</filename
+>/share/apps/tdm/pics/users/default.xpm</filename
> will be used instead.</para>
<para
@@ -1140,7 +1140,7 @@
</sect3>
</sect2>
-<sect2 id="kdmconfig-convenience">
+<sect2 id="tdmconfig-convenience">
<title
>Convenience</title>
@@ -1201,13 +1201,13 @@
<para
>You can also choose which user is <quote
>preselected</quote
-> when &kdm; starts. The default is <guilabel
+> when &tdm; starts. The default is <guilabel
>None</guilabel
>, but you can choose <guilabel
>Previous</guilabel
-> to have &kdm; default to the last successfully logged in user, or you can <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 password immediately.</para>
+> a particular user to always be selected 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>
</sect3>
@@ -1217,19 +1217,19 @@
</chapter>
-&kdmrc-ref;
+&tdmrc-ref;
<!-- ************************************************************ -->
-<chapter id="configuring-your-system-for-kdm">
+<chapter id="configuring-your-system-for-tdm">
<title
->Configuring your system to use &kdm;</title>
+>Configuring your system to use &tdm;</title>
<para
>This chapter assumes that your system is already configured to run the X Window System, and that you only need to reconfigure it to allow graphical login.</para>
-<sect1 id="setting-up-kdm">
+<sect1 id="setting-up-tdm">
<title
->Setting up &kdm;</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 runlevel. The runlevel is set by the program <application
@@ -1277,10 +1277,10 @@ id:3:initdefault:
</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 each time you reboot your system.</para>
+>The first step in configuring your system is to ensure that you 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 that does not run &xdm;. To do so, issue a command like this:</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
@@ -1303,7 +1303,7 @@ id:3:initdefault:
>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
+> configuration in order to use &tdm;. <filename
>/etc/pam.conf</filename
> or <filename
>/etc/pam.d/kde</filename
@@ -1316,18 +1316,18 @@ id:3:initdefault:
>).</para>
<para
->Now it's time for you to test &kdm; by issuing the following command:</para>
+>Now it's time for you to test &tdm; by issuing the following command:</para>
<screen
><command
->kdm <option
+>tdm <option
>-nodaemon</option
></command
>
</screen>
<para
->If you get a &kdm; login dialogue 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 try setting some environment variables to point to your &kde; and &Qt; libraries.</para>
+>If you get a &tdm; login dialogue 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 &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>
<para
>For example:</para>
@@ -1368,14 +1368,14 @@ id:3:initdefault:
>If you are still unsuccessful, try starting &xdm; instead, to 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>
+>When you are able to start &tdm; successfully, you can start to replace &xdm; by &tdm;. Again, this is distribution-dependent.</para>
<itemizedlist>
<listitem>
<para
>For &RedHat;, edit <filename
>/etc/inittab</filename
->, look for the string xdm and replace it with &kdm; (including all paths).</para>
+>, look for the string xdm and replace it with &tdm; (including all paths).</para>
</listitem>
<listitem>
<para
@@ -1383,7 +1383,7 @@ id:3:initdefault:
>/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 the paths are correct for your installation.</para
+>, which is set up to select from amongst several display managers, including &tdm;. Make sure that all the paths are correct for your installation.</para
>
</listitem>
<listitem>
@@ -1394,7 +1394,7 @@ id:3:initdefault:
<screen
>. /etc/rc.config
-DISPLAYMANAGER=kdm
+DISPLAYMANAGER=tdm
export DISPLAYMANAGER</screen>
</listitem>
<listitem
@@ -1404,7 +1404,7 @@ export DISPLAYMANAGER</screen>
> and find the line like this: <screen
>ttyv8 "/usr/X11R6/bin/xdm -nodaemon" xterm off secure</screen
> and edit it to this: <screen
->ttyv8 "/usr/local/bin/kdm -nodaemon" xterm on secure</screen>
+>ttyv8 "/usr/local/bin/tdm -nodaemon" xterm on secure</screen>
</para>
</listitem>
@@ -1415,7 +1415,7 @@ export DISPLAYMANAGER</screen>
</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 like this:</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
@@ -1449,7 +1449,7 @@ export DISPLAYMANAGER</screen>
></warning>
<para
->When you reboot your system, you should end up with the graphical &kdm; login dialogue.</para>
+>When you reboot your system, you should end up with the graphical &tdm; login dialogue.</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 testing at the command line. If you are trying to get two versions of KDE to co-exist, be particularly careful that the settings you use for your <envar
@@ -1462,26 +1462,26 @@ export DISPLAYMANAGER</screen>
</chapter>
-<chapter id="different-window-managers-with-kdm">
+<chapter id="different-window-managers-with-tdm">
<title
>Supporting multiple window managers</title>
<para
->The main dialogue box for &kdm; includes a <guilabel
+>The main dialogue box for &tdm; includes a <guilabel
>Session Type:</guilabel
> drop-down box, which allows you to select a window manager to use for your session. This chapter describes the changes that you must make to your configuration files in order to support this feature.</para>
<para
>The options that appear in the <guilabel
>Session Type:</guilabel
-> drop-down box are <ulink url="KDM"
+> drop-down box are <ulink url="TDM"
>configured</ulink
> by entries in the <literal
->KDM</literal
-> section of &kdmrc;.</para>
+>TDM</literal
+> section of &tdmrc;.</para>
<para
->When you log in using &kdm;, the shell script <filename
+>When you log in using &tdm;, the shell script <filename
>Xsession</filename
> is executed. The session type that you select is passed as a command-line argument. (<filename
>Xsession</filename
@@ -1511,7 +1511,7 @@ export DISPLAYMANAGER</screen>
>:</para>
<screen
-># now, we see if xdm/gdm/kdm has asked for a specific environment
+># now, we see if xdm/gdm/tdm has asked for a specific environment
case $# in
1)
case $1 in
@@ -1638,9 +1638,9 @@ exec $WINDOWMANAGER
</chapter>
-<chapter id="xdmcp-with-kdm">
+<chapter id="xdmcp-with-tdm">
<title
->Using &kdm; for Remote Logins (&XDMCP;)</title>
+>Using &tdm; for Remote Logins (&XDMCP;)</title>
<para
>&XDMCP; is the Open Group standard, the <quote
@@ -1662,13 +1662,13 @@ exec $WINDOWMANAGER
>Other sources of information</title>
<para
->Since &kdm; is descended from &xdm;, the <ulink url="man:xdm"
+>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
+>. If you have 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 Licence: look at the source code. </para>
@@ -1680,18 +1680,18 @@ exec $WINDOWMANAGER
>Credits and Licence</title>
<para
->&kdm; is derived from, and includes code from, &xdm; (C) Keith Packard, MIT X Consortium.</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; 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>
+>&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 licensed under the terms of the <ulink url="common/gpl-license.html"
+>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 as long as the names of the authors are mentioned.</para>
+>. 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>
+>&tdm; requires the Qt library, which is copyright Troll Tech AS.</para>
<para
>Documentation contributors: <itemizedlist>
@@ -1737,12 +1737,12 @@ exec $WINDOWMANAGER
>
&underFDL; &underGPL; </chapter>
-<appendix id="building-and-installing-kdm">
+<appendix id="building-and-installing-tdm">
<title
->Building and Installing kdm</title>
+>Building and Installing tdm</title>
<para
->&kdm; is part of the KDE project. The various component parts of the KDE project are broken into sections, called packages. &kdm; is part of the package called tdebase. You can get KDE source code from various Linux and BSD distribution CDs, or by download from <ulink url="http://www.kde.org"
+>&tdm; is part of the KDE project. The various component parts of the KDE project are broken into sections, called packages. &tdm; is part of the package called tdebase. You can get KDE source code from various Linux and BSD distribution CDs, or by download from <ulink url="http://www.kde.org"
>www.kde.org</ulink
> or its mirrors. If you have an out-of-date source code tree, you can use one of the KDE cvsup servers to bring it up-to-date whilst using minimal network bandwidth. </para>
@@ -1760,7 +1760,7 @@ exec $WINDOWMANAGER
>If the last few paragraphs seemed like a foreign language, then either you have strayed into an Inappropriate Area of this handbook, or you are about to undergo a Great Learning Experience.</para>
<para
->If you managed to satisfy all of the prerequisites, you are unlikely to have any problems with building and installing tdebase. &kdm; is installed in your <filename
+>If you managed to satisfy all of the prerequisites, you are unlikely to have any problems with building and installing tdebase. &tdm; is installed in your <filename
>$TDEDIR/bin</filename
> folder.</para>
@@ -1772,7 +1772,7 @@ exec $WINDOWMANAGER
></command
> will <emphasis
>not</emphasis
-> overwrite your previous &kdm; config files including &kdmrc;.</para
+> overwrite your previous &tdm; config files including &tdmrc;.</para
></note>
</appendix>
@@ -1786,7 +1786,7 @@ exec $WINDOWMANAGER
>greeter</glossterm>
<glossdef
><para
->The greeter is the login dialogue, &ie; the part of &kdm; which the user sees.</para>
+>The greeter is the login dialogue, &ie; the part of &tdm; which the user sees.</para>
</glossdef>
</glossentry>