summaryrefslogtreecommitdiffstats
path: root/doc/ktalkd
diff options
context:
space:
mode:
authorTimothy Pearson <kb9vqf@pearsoncomputing.net>2012-01-22 00:32:11 -0600
committerTimothy Pearson <kb9vqf@pearsoncomputing.net>2012-01-22 00:32:11 -0600
commitfa36c3f25d27eadec4ce1605790e519df6234e51 (patch)
tree1d227e9ba55bf08f9e4fcea2af38b3defdce6b64 /doc/ktalkd
parent9f97121b38893c64311d29529eb686126ac84bc1 (diff)
downloadtdenetwork-fa36c3f25d27eadec4ce1605790e519df6234e51.tar.gz
tdenetwork-fa36c3f25d27eadec4ce1605790e519df6234e51.zip
Part 1 of 2 of kdm rename
Diffstat (limited to 'doc/ktalkd')
-rw-r--r--doc/ktalkd/index.docbook10
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/ktalkd/index.docbook b/doc/ktalkd/index.docbook
index b35fa3d4..7a09ac2e 100644
--- a/doc/ktalkd/index.docbook
+++ b/doc/ktalkd/index.docbook
@@ -329,7 +329,7 @@ announcements?
<para>
Because this would be security hole, with the current user
detection. You can bypass the limitation by adding two lines in
-<command>xdm</command> config files (which are the same as &kdm; ones).
+<command>xdm</command> config files (which are the same as &tdm; ones).
</para>
<note>
@@ -375,10 +375,10 @@ DisplayManager._0.reset: /etc/X11/xdm/Xreset </screen>
</procedure>
<para>
-This will make &kdm; (or <command>xdm</command>) log
+This will make &tdm; (or <command>xdm</command>) log
the user into utmp, which is the right thing to do. It's not up to
&konsole;, nor <command>xterm</command>, to log the user, but to
-<command>xdm</command> and &kdm;, in my
+<command>xdm</command> and &tdm;, in my
opinion. However, this will not log the user as an X user when using
<command>startx</command>... Any hint about that ?
</para>
@@ -404,7 +404,7 @@ If you're running &Linux; 2.0.35, this is a known bug in the kernel,
which doesn't let <systemitem class="username">root</systemitem> read
<filename class="directory">/proc</filename>. The solution is the same
as in the previous question, provided that you run
-&kdm; or <command>xdm</command> to log into X. Or
+&tdm; or <command>xdm</command> to log into X. Or
upgrade!
</para>
@@ -413,7 +413,7 @@ Otherwise, this is normal. &ktalkd; can't find the user, as &kde;
doesn't log him into utmp and the &Linux; based (<filename
class="directory">/proc</filename>) detection is disabled. The solution
is the same as in the previous question, provided that you run
-<acronym>kdm</acronym> or <acronym>xdm</acronym> to log into X. Another
+<acronym>tdm</acronym> or <acronym>xdm</acronym> to log into X. Another
solution is to make sure you always have an
<application>xterm</application> running.
</para>