From fa36c3f25d27eadec4ce1605790e519df6234e51 Mon Sep 17 00:00:00 2001 From: Timothy Pearson Date: Sun, 22 Jan 2012 00:32:11 -0600 Subject: Part 1 of 2 of kdm rename --- doc/ktalkd/index.docbook | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'doc/ktalkd') 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? Because this would be security hole, with the current user detection. You can bypass the limitation by adding two lines in -xdm config files (which are the same as &kdm; ones). +xdm config files (which are the same as &tdm; ones). @@ -375,10 +375,10 @@ DisplayManager._0.reset: /etc/X11/xdm/Xreset -This will make &kdm; (or xdm) log +This will make &tdm; (or xdm) log the user into utmp, which is the right thing to do. It's not up to &konsole;, nor xterm, to log the user, but to -xdm and &kdm;, in my +xdm and &tdm;, in my opinion. However, this will not log the user as an X user when using startx... Any hint about that ? @@ -404,7 +404,7 @@ If you're running &Linux; 2.0.35, this is a known bug in the kernel, which doesn't let root read /proc. The solution is the same as in the previous question, provided that you run -&kdm; or xdm to log into X. Or +&tdm; or xdm to log into X. Or upgrade! @@ -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 (/proc) detection is disabled. The solution is the same as in the previous question, provided that you run -kdm or xdm to log into X. Another +tdm or xdm to log into X. Another solution is to make sure you always have an xterm running. -- cgit v1.2.1