From 7574a7287e2e121c9d5c91a5f4ea38c5b3ae2a04 Mon Sep 17 00:00:00 2001 From: Timothy Pearson Date: Sun, 6 Nov 2011 02:28:57 -0600 Subject: Additional kde to tde renaming --- doc/userguide/base-kde-applications.docbook | 4 +- doc/userguide/kde-as-root.docbook | 6 +-- doc/userguide/kde-for-admins.docbook | 84 ++++++++++++++--------------- doc/userguide/konsole-intro.docbook | 4 +- 4 files changed, 49 insertions(+), 49 deletions(-) (limited to 'doc/userguide') diff --git a/doc/userguide/base-kde-applications.docbook b/doc/userguide/base-kde-applications.docbook index 863271b37..917855c69 100644 --- a/doc/userguide/base-kde-applications.docbook +++ b/doc/userguide/base-kde-applications.docbook @@ -128,7 +128,7 @@ - + @@ -229,7 +229,7 @@ Related Information - See http://kontact.kde.org and http://kdepim.kde.org for more information. + See http://kontact.kde.org and http://tdepim.kde.org for more information. &kontact; Handbook diff --git a/doc/userguide/kde-as-root.docbook b/doc/userguide/kde-as-root.docbook index 7e6bb6fe9..c97f2e5f5 100644 --- a/doc/userguide/kde-as-root.docbook +++ b/doc/userguide/kde-as-root.docbook @@ -19,14 +19,14 @@ Some &Linux; distributions have tried to stress this point so much that they have disabled the root account altogether, and instead use the sudo model. Nevertheless, the basic security model in sudo is the same as su, and thus they share the same security strengths and weaknesses, essentially. -If you should ever need to run a program with Super User privileges, then it is always recommend that you use &kdesu;. From &konsole; or from hitting &Alt;F2, enter kdesu application, and the application will be run with the appropriate Super User privileges. +If you should ever need to run a program with Super User privileges, then it is always recommend that you use &tdesu;. From &konsole; or from hitting &Alt;F2, enter tdesu application, and the application will be run with the appropriate Super User privileges. -Even if you have set up your system to use sudo, or you are on a distribution that uses sudo, such as &kubuntu;, you should still use &kdesu;. The program will be appropriately modified by the developers to use the correct settings. You should not, however, ever use sudo application to run an application with root permissions; it can derange permissions of certain configuration files for a program. Running a graphical applications as root in general is not a good idea, but using &kdesu; will always be your safest bet with it. +Even if you have set up your system to use sudo, or you are on a distribution that uses sudo, such as &kubuntu;, you should still use &tdesu;. The program will be appropriately modified by the developers to use the correct settings. You should not, however, ever use sudo application to run an application with root permissions; it can derange permissions of certain configuration files for a program. Running a graphical applications as root in general is not a good idea, but using &tdesu; will always be your safest bet with it. Related Information -&kdesu; Handbook +&tdesu; Handbook diff --git a/doc/userguide/kde-for-admins.docbook b/doc/userguide/kde-for-admins.docbook index f5d98e019..6424ea965 100644 --- a/doc/userguide/kde-for-admins.docbook +++ b/doc/userguide/kde-for-admins.docbook @@ -833,22 +833,22 @@ are two very important lines in the startkde script: -LD_BIND_NOW=true kdeinit +kcminit +knotify and kwrapper +LD_BIND_NOW=true tdeinit +kcminit +knotify and kwrapper ksmserver $KDEWM -The first line starts the kdeinit master process. -The kdeinit master process is used to start all other +The first line starts the tdeinit master process. +The tdeinit master process is used to start all other &kde; processes. It show up in the output of ps - as kdeinit: -Running.... The arguments after kdeinit + as tdeinit: +Running.... The arguments after tdeinit are the names of additional processes to be started. The + -indicates that kdeinit needs to wait till the process has -finished. kdeinit also starts +indicates that tdeinit needs to wait till the process has +finished. tdeinit also starts dcopserver, klauncher and kded. -The second of the two lines asks kdeinit to start +The second of the two lines asks tdeinit to start the ksmserver session manager process. The session manager determines the lifetime of the session. When this process exits, the user is logged out. @@ -910,18 +910,18 @@ needed - -<command>kdeinit</command> -kdeinit is used to start all other &kde; -programs. kdeinit can start normal binary program files -as well as kdeinit loadable modules + +<command>tdeinit</command> +tdeinit is used to start all other &kde; +programs. tdeinit can start normal binary program files +as well as tdeinit loadable modules (KLMs). KLMs work just like binary program files but can be started more efficiently. KLMs live in $KDEDIR/lib/trinity The drawback is that programs started this way appear as -kdeinit in the output of +tdeinit in the output of top and ps. Use top or ps to see the actual program name: @@ -929,20 +929,20 @@ to see the actual program name: %ps -waba 23184 0.2 2.1 23428 11124 ? S 21:41 0:00 kdeinit: Running... -waba 23187 0.1 2.1 23200 11124 ? S 21:41 0:00 kdeinit: dcopserver --nosid -waba 23189 0.2 2.4 25136 12496 ? S 21:41 0:00 kdeinit: klauncher -waba 23192 0.7 2.8 25596 14772 ? S 21:41 0:00 kdeinit: kded -waba 23203 0.8 3.4 31516 17892 ? S 21:41 0:00 kdeinit: +waba 23184 0.2 2.1 23428 11124 ? S 21:41 0:00 tdeinit: Running... +waba 23187 0.1 2.1 23200 11124 ? S 21:41 0:00 tdeinit: dcopserver --nosid +waba 23189 0.2 2.4 25136 12496 ? S 21:41 0:00 tdeinit: klauncher +waba 23192 0.7 2.8 25596 14772 ? S 21:41 0:00 tdeinit: kded +waba 23203 0.8 3.4 31516 17892 ? S 21:41 0:00 tdeinit: knotify -kdeinit: Running... indicates the -master kdeinit process. The other processes listed are +tdeinit: Running... indicates the +master tdeinit process. The other processes listed are programs started as KLMs. -When kdeinit starts for the first time it will +When tdeinit starts for the first time it will launch dcopserver, klauncher, and kded, as well as any additional programs specified on its command line in the startkde script, normally @@ -1019,7 +1019,7 @@ startup problems. klauncher is a daemon which is responsible for service activation within &kde;. It operates in close connection with the -kdeinit master process to start new processes. &kde; +tdeinit master process to start new processes. &kde; applications communicate with klauncher over &DCOP; in order to start new applications or services. @@ -1029,7 +1029,7 @@ either indicates a serious problem with the dcopserver or that klauncher crashed. klauncher can be restarted by restarting -kdeinit from a console window. Make sure that +tdeinit from a console window. Make sure that $HOME, $DISPLAY and the various $KDEDIR(S) are set correctly when doing so! @@ -1205,7 +1205,7 @@ on a multi-head system. (Since &kde; 3.2.3) Set this variable to spawn KIO-slaves directly from the application process itself. By default KIO-slaves are spawned using -klauncher/kdeinit. This option is +klauncher/tdeinit. This option is useful if the KIO-slave should run in the same environment as the application. This can be the case with Clearcase. @@ -1228,7 +1228,7 @@ lookups. $KDE_IS_PRELINKED (Since &kde; 3.2) - Set this variable to indicate that you have prelinked your &kde; binaries and libraries. This will turn off -kdeinit. +tdeinit. @@ -1243,7 +1243,7 @@ locale. (Since &kde; 3.2) Automatically set to true by &kde; startup, it is used by ⪚ &konqueror; to know if it should consider remaining in memory for future re-use when being closed. If not set, &konqueror; will exit -after being closed (⪚ &kdesu; does that, it's also useful for +after being closed (⪚ &tdesu; does that, it's also useful for debugging). @@ -1314,21 +1314,21 @@ $KDEDIRS and profiles as well. Used by - -The kdeinit Mystery + +The tdeinit Mystery -kdeinit is used to start all other &kde; -programs. kdeinit can start normal binary program f iles -as well as kdeinit loadable modules +tdeinit is used to start all other &kde; +programs. tdeinit can start normal binary program f iles +as well as tdeinit loadable modules (KLMs). KLMs work just like binary program files but can be started more efficiently. KLMs live in $KDEDIR/lib/trinity The drawback is that programs started this way appear as -kdeinit in the +tdeinit in the output of top and ps. Use top or ps to see the actual program name: @@ -1336,14 +1336,14 @@ output of top and ps. Use % ps aux | grep bastian -bastian 26061 0.0 2.2 24284 11492 ? S 21:27 0:00 kdeinit: Running... -bastian 26064 0.0 2.2 24036 11524 ? S 21:27 0:00 kdeinit: dcopserver -bastian 26066 0.1 2.5 26056 12988 ? S 21:27 0:00 kdeinit: klauncher -bastian 26069 0.4 3.2 27356 16744 ? S 21:27 0:00 kdeinit: kded -bastian 26161 0.2 2.7 25344 14096 ? S 21:27 0:00 kdeinit: ksmserver -bastian 26179 1.1 3.4 29716 17812 ? S 21:27 0:00 kdeinit: kicker -bastian 26192 0.4 3.0 26776 15452 ? S 21:27 0:00 kdeinit: klipper -bastian 26195 1.0 3.5 29200 18368 ? S 21:27 0:00 kdeinit: kdesktop +bastian 26061 0.0 2.2 24284 11492 ? S 21:27 0:00 tdeinit: Running... +bastian 26064 0.0 2.2 24036 11524 ? S 21:27 0:00 tdeinit: dcopserver +bastian 26066 0.1 2.5 26056 12988 ? S 21:27 0:00 tdeinit: klauncher +bastian 26069 0.4 3.2 27356 16744 ? S 21:27 0:00 tdeinit: kded +bastian 26161 0.2 2.7 25344 14096 ? S 21:27 0:00 tdeinit: ksmserver +bastian 26179 1.1 3.4 29716 17812 ? S 21:27 0:00 tdeinit: kicker +bastian 26192 0.4 3.0 26776 15452 ? S 21:27 0:00 tdeinit: klipper +bastian 26195 1.0 3.5 29200 18368 ? S 21:27 0:00 tdeinit: kdesktop As you might have noticed, this has another side effect, making it @@ -1353,7 +1353,7 @@ difficult to kill a process that is causing trouble: kdesktop: no process killed You might be tempted to try killall -kdeinit, but killing all kdeinit processes will have +tdeinit, but killing all tdeinit processes will have the effect of shutting down all of &kde;. In effect, total destruction! diff --git a/doc/userguide/konsole-intro.docbook b/doc/userguide/konsole-intro.docbook index d42b4f59a..ec168ac22 100644 --- a/doc/userguide/konsole-intro.docbook +++ b/doc/userguide/konsole-intro.docbook @@ -81,8 +81,8 @@ action="simul">&Ctrl;&Alt;S and enter the new name. If you find the need to run any &kde; program with root privileges, you can use the &kdesu; command with the switch -from the command line like this: kdesu +class="username">root privileges, you can use the &tdesu; command with the switch +from the command line like this: tdesu , using the switch will prevent &kde; from remembering your passwords. -- cgit v1.2.1