[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-commits
Subject:    kdebase/doc/kdm
From:       Lauri Watts <lauri () kde ! org>
Date:       2003-05-28 9:30:49
[Download RAW message or body]

CVS commit by lauri: 

Update from Ossi


  M +5 -28     index.docbook   1.25


--- kdebase/doc/kdm/index.docbook  #1.24:1.25
@@ -993,31 +993,15 @@
 appropriate runlevel for console mode on your system.</para>
 
-<para>Next you need to locate your &xdm; configuration directory;
-normally <filename>/etc/X11/xdm/</filename> or
-<filename>/usr/X11R6/lib/X11/xdm/</filename>. The configuration
-directory contains the file <filename>Xsetup_0</filename>. If you
-build &kdm; from source code and the <filename>configure</filename>
-step is unable to find this directory, it will install a new version
-of <filename>Xsetup_0</filename> from a template file in the &kdm;
-source tree. You can include the line:</para>
-
-<screen><userinput>kdmdesktop</userinput></screen>
-
-<para>In your file to display some nice backgrounds (pictures and
-background colors). If your <envar>KDEDIR</envar> is not
-<filename>/opt/kde</filename> you may have to change the path to
-<filename>kdmdesktop</filename>.</para>
-
 <para>If your system uses Pluggable Authentication Modules
 (<abbrev>PAM</abbrev>), which is normal with recent &Linux; and Solaris
 systems, you should check that your <abbrev>PAM</abbrev> configuration permits
-login through the service named <literal>xdm</literal>. If you previously used
+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
-<filename>/etc/pam.d/xdm</filename>. Information on configuring
+<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/doc/pam*/html</filename>).</para>
+<filename>/usr/share/doc/*pam*/html/</filename>).</para>
 
 <para>Now it's time for you to test &kdm; by issuing the following
@@ -1086,9 +1070,4 @@
 </itemizedlist>
 
-<para>If you don't like changing <filename>inittab</filename>, an
-alternative is to rename <filename>xdm</filename> to
-<filename>xdm.bak</filename> and make <filename>xdm</filename> a
-symbolic link to &kdm;.</para>
-
 <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
@@ -1117,8 +1096,6 @@
 <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. Check files like
-<filename>/etc/X11/xdm/Xsetup_0</filename> (and any scripts that it
-invokes) to make sure that your path is not being changed without your
-knowledge. If you are trying to get two versions of KDE to co-exist,
+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>PATH</envar> and <envar>LD_LIBRARY_PATH</envar> environent


[prev in list] [next in list] [prev in thread] [next in thread]