From 7021f40c13f949b7cb5ded32d0241d648a43bf6c Mon Sep 17 00:00:00 2001 From: Timothy Pearson Date: Sun, 22 Jan 2012 00:28:18 -0600 Subject: Part 1 of 2 of kdm rename --- doc/kdm/CMakeLists.txt | 2 +- doc/kdm/Makefile.am | 6 +- doc/kdm/index.docbook | 258 +++++++++++++++++++++++----------------------- doc/kdm/kdmrc-ref.docbook | 230 ++++++++++++++++++++--------------------- 4 files changed, 248 insertions(+), 248 deletions(-) (limited to 'doc/kdm') diff --git a/doc/kdm/CMakeLists.txt b/doc/kdm/CMakeLists.txt index fe876f955..9a29fa8f8 100644 --- a/doc/kdm/CMakeLists.txt +++ b/doc/kdm/CMakeLists.txt @@ -9,4 +9,4 @@ # ################################################# -tde_create_handbook( DESTINATION kdm ) +tde_create_handbook( DESTINATION tdm ) diff --git a/doc/kdm/Makefile.am b/doc/kdm/Makefile.am index c04fe0908..3db537e3f 100644 --- a/doc/kdm/Makefile.am +++ b/doc/kdm/Makefile.am @@ -1,6 +1,6 @@ -conf_def = $(top_srcdir)/kdm/config.def -ref: $(conf_def) $(top_srcdir)/kdm/confproc.pl - $(PERL) -w $(top_srcdir)/kdm/confproc.pl --doc $(conf_def) kdmrc-ref.docbook +conf_def = $(top_srcdir)/tdm/config.def +ref: $(conf_def) $(top_srcdir)/tdm/confproc.pl + $(PERL) -w $(top_srcdir)/tdm/confproc.pl --doc $(conf_def) tdmrc-ref.docbook KDE_LANG = en KDE_DOCS = AUTO diff --git a/doc/kdm/index.docbook b/doc/kdm/index.docbook index 43cec1bde..dde535328 100644 --- a/doc/kdm/index.docbook +++ b/doc/kdm/index.docbook @@ -1,21 +1,21 @@ + - kdmrc"> + tdmrc"> ksmserver"> kdesktop"> XDMCP"> xdm"> - + ]> -The &kdm; Handbook +The &tdm; Handbook @@ -53,13 +53,13 @@ 0.05.02 -This document describes &kdm; the &kde; Display Manager. &kdm; +This document describes &tdm; the &kde; Display Manager. &tdm; is also known as the Login Manager. KDE -kdm +tdm xdm display manager login manager @@ -70,9 +70,9 @@ is also known as the Login Manager. Introduction -&kdm; provides a graphical interface that allows you to log in to a +&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 session. &kdm; is superior to &xdm;, the X +and starts a session. &tdm; is superior to &xdm;, the X Display Manager, in a number of ways. @@ -81,7 +81,7 @@ Display Manager, in a number of ways. - -Configuring &kdm; + +Configuring &tdm; -This chapter assumes that &kdm; is already up and running on your +This chapter assumes that &tdm; is already up and running on your system, and that you simply want to change its behavior in some way. -When &kdm; starts up, it reads its configuration from the folder -$TDEDIR/share/config/kdm/ (this may -be /etc/trinity/kdm/ or something else +When &tdm; starts up, it reads its configuration from the folder +$TDEDIR/share/config/tdm/ (this may +be /etc/trinity/tdm/ or something else on your system). -The main configuration file is &kdmrc;; all other files are +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 &kdm; is installed, +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;). -Since &kdm; must run before any user is logged in, it is not +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 &kdmrc;. It -follows from this that the configuration of &kdm; can only be altered by +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 -$TDEDIR/share/config/kdm/kdmrc (normally +$TDEDIR/share/config/tdm/tdmrc (normally restricted to system administrators logged in as root). -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 +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 System AdministrationLogin Manager), which is described in the &kcontrolcenter; help files. -The remainder of this chapter describes configuration of &kdm; -via the &kcontrolcenter; module, and the next -chapter describes the options available in &kdmrc; itself. If +The remainder of this chapter describes configuration of &tdm; +via the &kcontrolcenter; module, and the next +chapter describes the options available in &tdmrc; itself. If you only need to configure for local users, the &kcontrolcenter; 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 +logins, or have multiple &tdm; sessions running, you will need to read on. - + &Thomas.Tanghus; &Thomas.Tanghus.mail; @@ -346,31 +346,31 @@ on. The Login Manager &kcontrolcenter; Module Using this module, you can configure the &kde; graphical login -manager, &kdm;. You can change how the login screen looks, who has +manager, &tdm;. You can change how the login screen looks, who has access using the login manager and who can shutdown the computer. All settings will be written to the configuration file -&kdmrc;, which in its original state has many comments to help you -configure &kdm;. Using this &kcontrolcenter; module will strip these -comments from the file. All available options in &kdmrc; are covered -in . +&tdmrc;, which in its original state has many comments to help you +configure &tdm;. Using this &kcontrolcenter; module will strip these +comments from the file. All available options in &tdmrc; are covered +in . 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 +their equivalents in &tdmrc;. All options available in the &kcontrol; +module are also available directly in &tdmrc; but the reverse is not true. In order to organize all of these options, this module is divided into several sections: Appearance, -Font, Background, +linkend="tdmconfig-appearance">Appearance, +Font, Background, Shutdown, -Users and +linkend="tdmconfig-shutdown">Shutdown, +Users and Convenience. +linkend="tdmconfig-convenience">Convenience. You can switch between the sections using the tabs at the top of the window. @@ -381,10 +381,10 @@ Button. You will then be asked for a superuser password. Entering a correct password will allow you to modify the settings of this module. - + Appearance -From this page you can change the visual appearance of &kdm;, +From this page you can change the visual appearance of &tdm;, &kde;'s graphical login manager. The Greeting: is the title of the login @@ -392,13 +392,13 @@ module. may log in to. You may use various placeholders, which are described along with the corresponding key - in &kdmrc;. + in &tdmrc;. 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 labeled Logo area:. This corresponds to in &kdmrc; +linkend="option-logoarea"> in &tdmrc; If you chose Show logo you can now choose a logo: @@ -414,7 +414,7 @@ dialog. If you do not specify a logo the default -$TDEDIR/share/apps/kdm/pics/kdelogo.xpm +$TDEDIR/share/apps/tdm/pics/kdelogo.xpm will be displayed. Normally the login box is centered on the screen. Use the @@ -425,23 +425,23 @@ relative to the top left of the display, in the fields labeled X: and Y: respectively. These correspond to the key -in &kdmrc;. +in &tdmrc;. While &kde;'s style depends on the settings of the user logged -in, the style used by &kdm; can be configured using the GUI +in, the style used by &tdm; can be configured using the GUI Style: and Color Scheme: options. These correspond to the keys and in -&kdmrc; respectively. +&tdmrc; respectively. Below that, you have a drop down box to choose the language for your login box, corresponding to setting in -&kdmrc;. +&tdmrc;. - + Font From this section of the module you can change the fonts used in the @@ -474,7 +474,7 @@ fonts if you want smoothed fonts in the login dialog. - + Background Here you can change the desktop background which will be displayed @@ -612,7 +612,7 @@ stretched to fit all four corners. - + <guilabel>Shutdown</guilabel> Allow Shutdown @@ -620,13 +620,13 @@ stretched to fit all four corners. Nobody: No one can shutdown the computer using -&kdm;. You must be logged in, and execute a command. +&tdm;. You must be logged in, and execute a command. Everybody: Everyone can shutdown the computer using -&kdm;. +&tdm;. -Only Root: &kdm; requires that the +Only Root: &tdm; requires that the root password be entered before shutting down the computer. @@ -638,12 +638,12 @@ shutdown command for the Local: and Commands Use these text fields to define the exact shutdown command. The Halt: command defaults to +correct? they disagree with what's in --> /sbin/halt. The Restart: command defaults to /sbin/reboot. -When Show boot options is enabled, &kdm; +When Show boot options 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 lilo command and to lilo's map file. Note that this @@ -651,13 +651,13 @@ option is not available on all operating systems. - + Users From here you can change the way users are represented in the login window. -You may disable the user list in &kdm; entirely in the +You may disable the user list in &tdm; entirely in the Show Users section. You can choose from: @@ -692,7 +692,7 @@ over 65000, are not shown. You can also enable the Sort users checkbox, to have the user list sorted alphabetically. If this is disabled, users will appear in the order they are listed in the -password file. &kdm; will also autocomplete user names if you enable the +password file. &tdm; will also autocomplete user names if you enable the Autocompletion option. If you choose to show users, then the login window will show @@ -714,7 +714,7 @@ this terminal. - + Convenience In the convenience tab you can configure @@ -758,12 +758,12 @@ password-less login, ⪚ guest. You can also choose which user is preselected -when &kdm; starts. The default is None, but you -can choose Previous to have &kdm; default to the +when &tdm; starts. The default is None, but you +can choose Previous to have &tdm; default to the last successfully logged in user, or you can Specify 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 +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. The Automatically login after X server crash @@ -778,18 +778,18 @@ server accidentally crashed. -&kdmrc-ref; +&tdmrc-ref; - -Configuring your system to use &kdm; + +Configuring your system to use &tdm; This chapter assumes that your system is already configured to run the &X-Window;, and that you only need to reconfigure it to allow graphical login. - -Setting up &kdm; + +Setting up &tdm; The fundamental thing that controls whether your computer boots to a terminal prompt (console mode) or a graphical login prompt is the default @@ -829,11 +829,11 @@ distributions is: 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 +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. -To test &kdm;, you must first bring your system to a runlevel +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: /sbin/init @@ -847,23 +847,23 @@ systems, you should check that your PAM configuration permits login through the service named kde. If you previously used &xdm; successfully, you should not need to make any changes to your PAM configuration in order to use -&kdm;. /etc/pam.conf or +&tdm;. /etc/pam.conf or /etc/pam.d/kde. Information on configuring PAM is beyond the scope of this handbook, but PAM comes with comprehensive documentation (try looking in /usr/share/doc/*pam*/html/). -Now it's time for you to test &kdm; by issuing the following +Now it's time for you to test &tdm; by issuing the following command: -kdm +tdm -If you get a &kdm; login dialog and you are able to log in, +If you get a &tdm; login dialog 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 +&tdm; is installed where the libraries believe &kde; is installed and try setting some environment variables to point to your &kde; and &Qt; libraries. @@ -883,8 +883,8 @@ libraries. make sure that you are not suffering from a more serious X configuration problem. -When you are able to start &kdm; successfully, you can start to -replace &xdm; by &kdm;. Again, this is distribution-dependent. +When you are able to start &tdm; successfully, you can start to +replace &xdm; by &tdm;. Again, this is distribution-dependent. @@ -892,16 +892,16 @@ replace &xdm; by &kdm;. Again, this is distribution-dependent. line: x:5:respawn:/usr/X11/bin/xdm -nodaemon and replace with: -x:5:respawn:/opt/kde/bin/kdm -This tells init(8) to respawn &kdm; when the -system is in run level 5. Note that &kdm; does not need the +x:5:respawn:/opt/kde/bin/tdm +This tells init(8) to respawn &tdm; when the +system is in run level 5. Note that &tdm; does not need the option. For &Mandrake;, the X11 runlevel in /etc/inittab invokes the shell script /etc/X11/prefdm, which is set up to select from -amongst several display managers, including &kdm;. Make sure that all +amongst several display managers, including &tdm;. Make sure that all the paths are correct for your installation. @@ -909,22 +909,22 @@ the paths are correct for your installation. first line: . /etc/rc.config -DISPLAYMANAGER=kdm +DISPLAYMANAGER=tdm export DISPLAYMANAGER For FreeBSD, edit /etc/ttys and find the line like this: ttyv8 "/usr/X11R6/bin/xdm -nodaemon" xterm off secure and edit it to this: -ttyv8 "/usr/local/bin/kdm" xterm on secure +ttyv8 "/usr/local/bin/tdm" xterm on secure Most other distributions are a variation of one of these. -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 +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: /sbin/init @@ -950,7 +950,7 @@ at your peril. id:5:initdefault: When you reboot your system, you should end up with the -graphical &kdm; login dialog. +graphical &tdm; login dialog. 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 @@ -964,24 +964,24 @@ some way. - + Supporting multiple window managers -&kdm; detects most available window manager and desktop environments when +&tdm; detects most available window manager and desktop environments when it is run. Installing a new one should make it automatically available in -the &kdm; main dialog Session Type:. +the &tdm; main dialog Session Type:. -If you have a very new window manager, or something that &kdm; does +If you have a very new window manager, or something that &tdm; does not support, the first thing you should check is that the application to be run is in the PATH and has not been renamed during the install into something unexpected. If the case is that the application is too new and not yet supported -by &kdm;, you can quite simply add a new session. +by &tdm;, you can quite simply add a new session. The sessions are defined in .desktop files in $TDEDIR/share/apps/kdm/sessions. +class="directory">$TDEDIR/share/apps/tdm/sessions. You can simply add an appropriately named .desktop file in this directory. The fields are: @@ -995,7 +995,7 @@ Exec=executable name Passed to eval exec in a Bourne shell TryExec=executable name Supported but not required -Name=name to show in the &kdm; session list +Name=name to show in the &tdm; session list There are also three magic: @@ -1004,7 +1004,7 @@ Name=name to show in the &kdm; session listdefault -The default session for &kdm; is normally &kde; but can be configured by the +The default session for &tdm; is normally &kde; but can be configured by the system administrator. @@ -1032,14 +1032,14 @@ purposes. to the config dir and edit it at will. Removing the shipped session types can be accomplished by shadowing them with .desktop files containing Hidden=true. For the magic session types no .desktop files exist -by default, but &kdm; pretends they would, so you can override them like any +by default, but &tdm; pretends they would, so you can override them like any other type. I guess you already know how to add a new session type by now. ;-) - -Using &kdm; for Remote Logins (&XDMCP;) + +Using &tdm; for Remote Logins (&XDMCP;) &XDMCP; is the Open Group standard, the X Display Manager Control Protocol. This is used to set up connections between @@ -1068,7 +1068,7 @@ this. Command Sockets -This is a feature you can use to remote-control &kdm;. It's mostly +This is a feature you can use to remote-control &tdm;. It's mostly intended for use by &ksmserver; and &kdesktop; from a running session, but other applications are possible as well. @@ -1149,9 +1149,9 @@ is attempted, but a scheduled "login" command will be executed. -&kdm; +&tdm; -identifies &kdm;, in case some other DM implements this protocol, +identifies &tdm;, in case some other DM implements this protocol, too @@ -1280,7 +1280,7 @@ means immediately. end is the latest time at which the shutdown should be performed if active sessions are still running. If it starts with a plus-sign, the start time is added. -1 means wait infinitely. If end is -through and active sessions are still running, &kdm; can do one of the +through and active sessions are still running, &tdm; can do one of the following: cancel - give up the @@ -1346,21 +1346,21 @@ $DM_CONTROL; the name of per-display sockets can be derived from $DISPLAY. -By using the kdmctl command (⪚ from within a -shell script). Try kdmctl to find out +By using the tdmctl command (⪚ from within a +shell script). Try tdmctl to find out more. Here is an example bash script reboot into FreeBSD: -if kdmctl | grep -q shutdown; then +if tdmctl | grep -q shutdown; then IFS=$'\t' - set -- `kdmctl listbootoptions` + set -- `tdmctl listbootoptions` if [ "$1" = ok ]; then fbsd=$(echo "$2" | tr ' ' '\n' | sed -ne 's,\\s, ,g;/freebsd/I{p;q}') if [ -n "$fbsd" ]; then - kdmctl shutdown reboot "=$fbsd" ask > /dev/null + tdmctl shutdown reboot "=$fbsd" ask > /dev/null else echo "FreeBSD boot unavailable." fi @@ -1372,14 +1372,14 @@ else fi - @@ -1388,12 +1388,12 @@ and Theme=/path/to/theme.xml. Other sources of information -Since &kdm; is descended from &xdm;, the Since &tdm; is descended from &xdm;, the &xdm; man page may provide useful background information. For X-related problems try the man pages X and startx. 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 &GNU; +questions about &tdm; that are not answered by this handbook, take advantage of +the fact the &tdm; is provided under the terms of the &GNU; General Public License: look at the source code. @@ -1402,19 +1402,19 @@ General Public License: look at the source code. Credits and License -&kdm; is derived from, and includes code from, +&tdm; is derived from, and includes code from, &xdm; (C) Keith Packard, MIT X Consortium. -&kdm; 0.1 was written by &Matthias.Ettrich;. Later versions till &kde; +&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;. -Other parts of the &kdm; code are copyright by the authors, and +Other parts of the &tdm; code are copyright by the authors, and licensed under the terms of the &GNU; -GPL. Anyone is allowed to change &kdm; and redistribute the result +GPL. Anyone is allowed to change &tdm; and redistribute the result as long as the names of the authors are mentioned. -&kdm; requires the &Qt; library, which is copyright Troll Tech AS. +&tdm; requires the &Qt; library, which is copyright Troll Tech AS. Documentation contributors: @@ -1449,7 +1449,7 @@ man page, which is © Keith Packard. greeter -The greeter is the login dialog, &ie; the part of &kdm; +The greeter is the login dialog, &ie; the part of &tdm; which the user sees. diff --git a/doc/kdm/kdmrc-ref.docbook b/doc/kdm/kdmrc-ref.docbook index 9ebcfbdd3..f2cfd2f0e 100644 --- a/doc/kdm/kdmrc-ref.docbook +++ b/doc/kdm/kdmrc-ref.docbook @@ -1,19 +1,19 @@ - + - -The Files &kdm; Uses for Configuration + +The Files &tdm; Uses for Configuration -This chapter documents the files that control &kdm;'s behavior. +This chapter documents the files that control &tdm;'s behavior. Some of this can be also controlled from the &kcontrol; module, but not all. - -&kdmrc; - The &kdm; master configuration file + +&tdmrc; - The &tdm; master configuration file The basic format of the file is INI-like. Options are key/value pairs, placed in sections. Everything in the file is case sensitive. -Syntactic errors and unrecognized key/section identifiers cause &kdm; to +Syntactic errors and unrecognized key/section identifiers cause &tdm; to issue non-fatal error messages. Lines beginning with # are comments; empty lines @@ -124,13 +124,13 @@ have the usual meaning; the backslash quotes everything (not only special characters). Note that the backslashes need to be doubled because of the two levels of quoting. -A pristine &kdmrc; is very thoroughly commented. +A pristine &tdmrc; is very thoroughly commented. All comments will be lost if you change this file with the kcontrol frontend. - -The [General] section of &kdmrc; + +The [General] section of &tdmrc; This section contains global options that do not fit into any specific section. @@ -144,7 +144,7 @@ This section contains global options that do not fit into any specific section. This option exists solely for the purpose of clean automatic upgrades. Do not change it, you may interfere with future -upgrades and this could result in &kdm; failing to run. +upgrades and this could result in &tdm; failing to run. @@ -153,12 +153,12 @@ upgrades and this could result in &kdm; failing to run. -List of displays (&X-Server;s) permanently managed by &kdm;. Displays with a +List of displays (&X-Server;s) permanently managed by &tdm;. Displays with a hostname are foreign displays which are expected to be already running, -the others are local displays for which &kdm; starts an own &X-Server;; +the others are local displays for which &tdm; starts an own &X-Server;; see . Each display may belong to a display class; append it to the display name separated by an underscore. -See for the details. +See for the details. The default is :0. @@ -180,7 +180,7 @@ List of on-demand displays. See for syntax. List of Virtual Terminals to allocate to &X-Server;s. For negative numbers the absolute value is used, and the VT will be allocated only -if the kernel says it is free. If &kdm; exhausts this list, it will allocate +if the kernel says it is free. If &tdm; exhausts this list, it will allocate free VTs greater than the absolute value of the last entry in this list. Currently Linux only. @@ -194,14 +194,14 @@ Currently Linux only. This option is for operating systems (OSs) with support -for virtual terminals (VTs), by both &kdm; and the +for virtual terminals (VTs), by both &tdm; and the OSs itself. Currently this applies only to Linux. -When &kdm; switches to console mode, it starts monitoring all +When &tdm; switches to console mode, it starts monitoring all TTY lines listed here (without the leading /dev/). -If none of them is active for some time, &kdm; switches back to the X login. +If none of them is active for some time, &tdm; switches back to the X login. Empty by default. @@ -212,7 +212,7 @@ If none of them is active for some time, &kdm; switches back to the X login. The filename specified will be created to contain an ASCII representation -of the process ID of the main &kdm; process; the PID will not be stored +of the process ID of the main &tdm; process; the PID will not be stored if the filename is empty. Empty by default. @@ -223,7 +223,7 @@ if the filename is empty. -This option controls whether &kdm; uses file locking to keep multiple +This option controls whether &tdm; uses file locking to keep multiple display managers from running onto each other. The default is true. @@ -234,8 +234,8 @@ display managers from running onto each other. -This names a directory under which &kdm; stores &X-Server; authorization -files while initializing the session. &kdm; expects the system to clean up +This names a directory under which &tdm; stores &X-Server; authorization +files while initializing the session. &tdm; expects the system to clean up this directory from stale files on reboot. The authorization file to be used for a particular display can be @@ -249,7 +249,7 @@ specified with the option in [X-*-Core]. -This boolean controls whether &kdm; automatically re-reads its +This boolean controls whether &tdm; automatically re-reads its configuration files if it finds them to have changed. The default is true. @@ -260,7 +260,7 @@ configuration files if it finds them to have changed. -Additional environment variables &kdm; should pass on to all programs it runs. +Additional environment variables &tdm; should pass on to all programs it runs. LD_LIBRARY_PATH and XCURSOR_THEME are good candidates; otherwise, it should not be necessary very often. @@ -275,7 +275,7 @@ otherwise, it should not be necessary very often. If the system has no native entropy source like /dev/urandom (see ) and no entropy daemon like EGD (see and ) is running, -&kdm; will fall back to its own pseudo-random number generator +&tdm; will fall back to its own pseudo-random number generator that will, among other things, successively checksum parts of this file (which, obviously, should change frequently). @@ -313,7 +313,7 @@ Same as , only use a TCP socket on localhost. -The path to a character device which &kdm; should read random data from. +The path to a character device which &tdm; should read random data from. Empty means to use the system's preferred entropy device if there is one. This option does not exist on OpenBSD, as it uses the arc4_random @@ -348,10 +348,10 @@ can be either a name or a numerical ID. -The directory in which &kdm; should store persistent working data; such data +The directory in which &tdm; should store persistent working data; such data is, for example, the previous user that logged in on a particular display. -The default is /var/lib/kdm. +The default is /var/lib/tdm. @@ -359,7 +359,7 @@ is, for example, the previous user that logged in on a particular display. -The directory in which &kdm; should store users' .dmrc files. This is only +The directory in which &tdm; should store users' .dmrc files. This is only needed if the home directories are not readable before actually logging in (like with AFS). @@ -371,11 +371,11 @@ needed if the home directories are not readable before actually logging in - -The [Xdmcp] section of &kdmrc; + +The [Xdmcp] section of &tdmrc; -This section contains options that control &kdm;'s handling of +This section contains options that control &tdm;'s handling of &XDMCP; requests. @@ -385,7 +385,7 @@ This section contains options that control &kdm;'s handling of -Whether &kdm; should listen to incoming &XDMCP; requests. +Whether &tdm; should listen to incoming &XDMCP; requests. The default is true. @@ -395,7 +395,7 @@ Whether &kdm; should listen to incoming &XDMCP; requests. -This indicates the UDP port number which &kdm; uses to listen for incoming +This indicates the UDP port number which &tdm; uses to listen for incoming &XDMCP; requests. Unless you need to debug the system, leave this with its default value. @@ -408,7 +408,7 @@ default value. XDM-AUTHENTICATION-1 style &XDMCP; authentication requires a private -key to be shared between &kdm; and the terminal. This option specifies +key to be shared between &tdm; and the terminal. This option specifies the file containing those values. Each entry in the file consists of a display name and the shared key. @@ -424,9 +424,9 @@ To prevent unauthorized &XDMCP; service and to allow forwarding of &XDMCP; IndirectQuery requests, this file contains a database of hostnames which are either allowed direct access to this machine, or have a list of hosts to which queries should be forwarded to. The format of this file is -described in . +described in . -The default is ${kde_confdir}/kdm/Xaccess. +The default is ${kde_confdir}/tdm/Xaccess. @@ -450,7 +450,7 @@ is offered again. When computing the display name for &XDMCP; clients, the name resolver will typically create a fully qualified host name for the terminal. As this is -sometimes confusing, &kdm; will remove the domain name portion of the host +sometimes confusing, &tdm; will remove the domain name portion of the host name if it is the same as the domain name of the local host when this option is enabled. @@ -489,8 +489,8 @@ displayed in a chooser window. If no program is specified, the string - -The [Shutdown] section of &kdmrc; + +The [Shutdown] section of &tdmrc; This section contains global options concerning system shutdown. @@ -504,7 +504,7 @@ This section contains global options concerning system shutdown. The command (subject to word splitting) to run to halt/poweroff the system. -The default is something reasonable for the system on which &kdm; was built, like +The default is something reasonable for the system on which &tdm; was built, like /sbin/shutdown  now. @@ -516,7 +516,7 @@ The default is something reasonable for the system on which &kdm; was built, lik The command (subject to word splitting) to run to reboot the system. -The default is something reasonable for the system &kdm; on which was built, like +The default is something reasonable for the system &tdm; on which was built, like /sbin/shutdown  now. @@ -549,7 +549,7 @@ This will have no effect unless is enabled. -The boot manager &kdm; should use for offering boot options in the +The boot manager &tdm; should use for offering boot options in the shutdown dialog. @@ -574,12 +574,12 @@ shutdown dialog. - -The [X-*-Core] section class of &kdmrc; + +The [X-*-Core] section class of &tdmrc; This section class contains options concerning the configuration -of the &kdm; backend (core). +of the &tdm; backend (core). @@ -608,7 +608,7 @@ See . -These options control the behavior of &kdm; when attempting to open a +These options control the behavior of &tdm; when attempting to open a connection to an &X-Server;. is the length of the pause (in seconds) between successive attempts, is the number of attempts to make and @@ -625,7 +625,7 @@ connection attempt, the start attempt is considered failed. -How many times &kdm; should attempt to start a foreign +How many times &tdm; should attempt to start a foreign display listed in before giving up and disabling it. Local displays are attempted only once, and &XDMCP; displays are retried @@ -640,7 +640,7 @@ was given to the &X-Server;). -How many times &kdm; should attempt to start up a local &X-Server;. +How many times &tdm; should attempt to start up a local &X-Server;. Starting up includes executing it and waiting for it to come up. The default is 1. @@ -651,7 +651,7 @@ Starting up includes executing it and waiting for it to come up. -How many seconds &kdm; should wait for a local &X-Server; to come up. +How many seconds &tdm; should wait for a local &X-Server; to come up. The default is 15. @@ -664,7 +664,7 @@ How many seconds &kdm; should wait for a local &X-Server; to come up. The command line to start the &X-Server;, without display number and VT spec. This string is subject to word splitting. -The default is something reasonable for the system on which &kdm; was built, +The default is something reasonable for the system on which &tdm; was built, like /usr/X11R6/bin/X. @@ -698,7 +698,7 @@ This string is subject to word splitting. The VT the &X-Server; should run on. should be used instead of this option. -Leave it zero to let &kdm; assign a VT automatically. +Leave it zero to let &tdm; assign a VT automatically. Set it to -1 to avoid assigning a VT alltogether - this is required for setups with multiple physical consoles. Currently Linux only. @@ -711,13 +711,13 @@ Currently Linux only. This option is for OSs without support for -VTs, either by &kdm; or the OS itself. +VTs, either by &tdm; or the OS itself. Currently this applies to all OSs but Linux. -When &kdm; switches to console mode, it starts monitoring this +When &tdm; switches to console mode, it starts monitoring this TTY line (specified without the leading /dev/) for activity. If the line is not used for some time, -&kdm; switches back to the X login. +&tdm; switches back to the X login. Empty by default. @@ -737,7 +737,7 @@ See . -To discover when remote displays disappear, &kdm; +To discover when remote displays disappear, &tdm; regularly pings them. specifies the time (in minutes) between the pings and specifies the maximum amount of @@ -757,7 +757,7 @@ accidentally disabled. -Whether &kdm; should restart the local &X-Server; after session exit instead +Whether &tdm; should restart the local &X-Server; after session exit instead of resetting it. Use this if the &X-Server; leaks memory or crashes the system on reset attempts. @@ -789,7 +789,7 @@ The signal number to use to terminate the local &X-Server;. -Controls whether &kdm; generates and uses authorization for +Controls whether &tdm; generates and uses authorization for local &X-Server; connections. For &XDMCP; displays the authorization requested by the display is used; foreign non-&XDMCP; displays do not support authorization at all. @@ -817,9 +817,9 @@ depending on the build configuration. Some old &X-Server;s re-read the authorization file at &X-Server; reset time, instead of when checking the initial connection. -As &kdm; generates the authorization information just before connecting to +As &tdm; generates the authorization information just before connecting to the display, an old &X-Server; would not get up-to-date authorization -information. This option causes &kdm; to send SIGHUP to the &X-Server; +information. This option causes &tdm; to send SIGHUP to the &X-Server; after setting up the file, causing an additional &X-Server; reset to occur, during which time the new authorization information will be read. @@ -831,7 +831,7 @@ during which time the new authorization information will be read. -This file is used to communicate the authorization data from &kdm; to +This file is used to communicate the authorization data from &tdm; to the &X-Server;, using the &X-Server; command line option. It should be kept in a directory which is not world-writable as it could easily be removed, disabling the authorization mechanism in @@ -879,7 +879,7 @@ greeter window. This may be used to change the appearance of the screen around the greeter window or to put up other windows (e.g., you may want to run xconsole here). The conventional name for a program used here is Xsetup. -See . +See . Empty by default. @@ -894,7 +894,7 @@ It specifies a program which is run (as root) after the user authentication process succeeds. The conventional name for a program used here is Xstartup. -See . +See . Empty by default. @@ -909,7 +909,7 @@ It specifies a program which is run (as root) after the session terminates. The conventional name for a program used here is Xreset. -See . +See . Empty by default. @@ -923,7 +923,7 @@ This string is subject to word splitting. It specifies the session program to be executed (as the user owning the session). The conventional name for a program used here is Xsession. -See . +See . The default is ${x_bindir}/xterm -ls -T. @@ -933,10 +933,10 @@ See . -If the program fails to execute, &kdm; will +If the program fails to execute, &tdm; will fall back to this program. This program is executed with no arguments, but executes using the same environment variables as the session would -have had (see ). +have had (see ). The default is ${x_bindir}/xterm. @@ -949,7 +949,7 @@ have had (see ). The PATH environment variable for non-root s. -The default depends on the system &kdm; was built on. +The default depends on the system &tdm; was built on. @@ -963,7 +963,7 @@ non-root s. Note that it is good practice not to include . (the current directory) into this entry. -The default depends on the system &kdm; was built on. +The default depends on the system &tdm; was built on. @@ -983,7 +983,7 @@ The SHELL environment variable for all programs but the -When &kdm; is unable to write to the usual user authorization file +When &tdm; is unable to write to the usual user authorization file ($HOME/.Xauthority), it creates a unique file name in this directory and points the environment variable XAUTHORITY at the created file. @@ -996,7 +996,7 @@ at the created file. -If enabled, &kdm; will automatically restart a session after an &X-Server; +If enabled, &tdm; will automatically restart a session after an &X-Server; crash (or if it is killed by Alt-Ctrl-BackSpace). Note that enabling this feature opens a security hole: a secured display lock can be circumvented (unless &kde;'s built-in screen locker is used). @@ -1196,7 +1196,7 @@ The user to log in automatically. Never specify The password for the user to log in automatically. This is not required unless the user is logged into a NIS or Kerberos domain. If you use this -option, you should chmod  kdmrc for obvious reasons. +option, you should chmod  tdmrc for obvious reasons. Empty by default. @@ -1219,7 +1219,7 @@ KDE sessions. A list of directories containing session type definitions. -The default is ${kde_datadir}/kdm/sessions. +The default is ${kde_datadir}/tdm/sessions. @@ -1240,7 +1240,7 @@ literal %. -Specify whether &kdm;'s built-in utmp/wtmp/lastlog registration should +Specify whether &tdm;'s built-in utmp/wtmp/lastlog registration should be used. If it is not, the tool sessreg should be used in the and scripts, or, alternatively, the pam_lastlog module should be used on @@ -1254,12 +1254,12 @@ alternatively, the pam_lastlog module should be used on - -The [X-*-Greeter] section class of &kdmrc; + +The [X-*-Greeter] section class of &tdmrc; This section class contains options concerning the configuration -of the &kdm; frontend (greeter). +of the &tdm; frontend (greeter). @@ -1329,7 +1329,7 @@ The image to show in the greeter if is The relative coordinates (percentages of the screen size; X,Y) at which -the center of the greeter is put. &kdm; aligns the greeter to the edges +the center of the greeter is put. &tdm; aligns the greeter to the edges of the screen it would cross otherwise. The default is 50,50. @@ -1563,7 +1563,7 @@ See . -If is enabled, this specifies where &kdm; gets the +If is enabled, this specifies where &tdm; gets the images from: @@ -1587,7 +1587,7 @@ images from: The images can be in any format Qt recognizes, but the filename -must match &kdm;'s expectations: .face.icon should be a +must match &tdm;'s expectations: .face.icon should be a 48x48 icon, while .face should be a 300x300 image. Currently the big image is used only as a fallback and is scaled down, but in the future it might be displayed full-size in the logo area or a @@ -1603,7 +1603,7 @@ tooltip. See . -The default is ${kde_datadir}/kdm/faces. +The default is ${kde_datadir}/tdm/faces. @@ -1692,7 +1692,7 @@ character -If enabled, &kdm; will automatically start the krootimage +If enabled, &tdm; will automatically start the krootimage program to set up the background; otherwise, the program is responsible for the background. @@ -1709,7 +1709,7 @@ It contains a section named [Desktop0] like kdesktoprc does. Its options are not described herein; guess their meanings or use the control center. -The default is ${kde_confdir}/kdm/backgroundrc. +The default is ${kde_confdir}/tdm/backgroundrc. @@ -1735,11 +1735,11 @@ grabbed until just before the session begins. -This option specifies the maximum time &kdm; will wait for the grabs to +This option specifies the maximum time &tdm; will wait for the grabs to succeed. A grab may fail if some other X-client has the &X-Server; or the keyboard grabbed, or possibly if the network latencies are very high. You should be cautious when raising the timeout, as a user can be spoofed by -a look-alike window on the display. If a grab fails, &kdm; kills and +a look-alike window on the display. If a grab fails, &tdm; kills and restarts the &X-Server; (if possible) and the session. The default is 3. @@ -1826,10 +1826,10 @@ login domain. -Enable &kdm;'s built-in xconsole. +Enable &tdm;'s built-in xconsole. Note that this can be enabled for only one display at a time. -This option is available only if &kdm; was configured -with . +This option is available only if &tdm; was configured +with . The default is false. @@ -1839,7 +1839,7 @@ with . -The data source for &kdm;'s built-in xconsole. +The data source for &tdm;'s built-in xconsole. If empty, a console log redirection is requested from /dev/console. Has no effect if is disabled. @@ -1950,13 +1950,13 @@ file. - + Specifying permanent &X-Server;s Each entry in the list indicates a display which should constantly be managed and which is not using &XDMCP;. This method is typically used only for -local &X-Server;s that are started by &kdm;, but &kdm; can manage externally +local &X-Server;s that are started by &tdm;, but &tdm; can manage externally started (foreign) &X-Server;s as well, may they run on the local machine or rather remotely. @@ -1975,7 +1975,7 @@ The display name of &XDMCP; displays is derived from the display's address by reverse host name resolution. For configuration purposes, the localhost prefix from locally running &XDMCP; displays is not stripped to make them distinguishable from local -&X-Server;s started by &kdm;. +&X-Server;s started by &tdm;. The display class portion is also used in the display-specific sections. This is useful if you have a large collection of @@ -1983,11 +1983,11 @@ similar displays (such as a corral of X terminals) and would like to set options for groups of them. When using &XDMCP;, the display is required to specify the display class, so the manual for your particular X terminal should document the display -class string for your device. If it does not, you can run &kdm; in debug +class string for your device. If it does not, you can run &tdm; in debug mode and grep the log for class. The displays specified in will not be -started when &kdm; starts up, but when it is explicitly requested via +started when &tdm; starts up, but when it is explicitly requested via the command socket (or FiFo). If reserve displays are specified, the &kde; menu will have a Start New Session item near the bottom; use that to @@ -1995,26 +1995,26 @@ activate a reserve display with a new login session. The monitor will switch to the new display, and you will have a minute to login. If there are no more reserve displays available, the menu item will be disabled. -When &kdm; starts a session, it sets up authorization data for the -&X-Server;. For local servers, &kdm; passes +When &tdm; starts a session, it sets up authorization data for the +&X-Server;. For local servers, &tdm; passes  filename on the &X-Server;'s command line to point it at its authorization data. -For &XDMCP; displays, &kdm; passes the authorization data to the &X-Server; +For &XDMCP; displays, &tdm; passes the authorization data to the &X-Server; via the Accept &XDMCP; message. - + &XDMCP; access control The file specified by the option provides -information which &kdm; uses to control access from displays requesting service +information which &tdm; uses to control access from displays requesting service via &XDMCP;. The file contains four types of entries: entries which control the response to Direct and Broadcast queries, entries which control the response to Indirect queries, macro definitions for Indirect entries, and entries which control on which network -interfaces &kdm; listens for &XDMCP; queries. +interfaces &tdm; listens for &XDMCP; queries. Blank lines are ignored, # is treated as a comment delimiter causing the rest of that line to be ignored, and \ causes an immediately following newline to be ignored, allowing indirect host @@ -2039,7 +2039,7 @@ Preceding the entry with a ! character causes hosts which match that entry to be excluded. To only respond to Direct queries for a host or pattern, it can be followed by the optional NOBROADCAST keyword. -This can be used to prevent a &kdm; server from appearing on menus based on +This can be used to prevent a &tdm; server from appearing on menus based on Broadcast queries. An Indirect entry also contains a host name or pattern, @@ -2057,7 +2057,7 @@ the hop count is used as the TTL. --> If the indirect host list contains the keyword CHOOSER, Indirect queries are not forwarded, but instead a host chooser -dialog is displayed by &kdm;. The chooser will send a Direct +dialog is displayed by &tdm;. The chooser will send a Direct query to each of the remaining host names in the list and offer a menu of all the hosts that respond. The host list may contain the keyword BROADCAST, to make the chooser send a @@ -2079,21 +2079,21 @@ The formal syntax is  LISTEN [interface [multicast list]] -If one or more LISTEN lines are specified, &kdm; listens +If one or more LISTEN lines are specified, &tdm; listens for &XDMCP; requests only on the specified interfaces. interface may be a hostname or IP address representing a network interface on this machine, or the wildcard * to represent all available network interfaces. If multicast group addresses are listed on a LISTEN line, -&kdm; joins the multicast groups on the given interface. For IPv6 multicasts, +&tdm; joins the multicast groups on the given interface. For IPv6 multicasts, the IANA has assigned ff0X:0:0:0:0:0:0:12b as the permanently assigned range of multicast addresses for &XDMCP;. The X in the prefix may be replaced by any valid scope identifier, such as 1 for Node-Local, 2 for Link-Local, 5 for Site-Local, and so on (see IETF RFC 2373 or its replacement for further details and scope -definitions). &kdm; defaults to listening on the Link-Local scope address +definitions). &tdm; defaults to listening on the Link-Local scope address ff02:0:0:0:0:0:0:12b to most closely match the IPv4 subnet broadcast behavior. -If no LISTEN lines are given, &kdm; listens on all +If no LISTEN lines are given, &tdm; listens on all interfaces and joins the default &XDMCP; IPv6 multicast group (when compiled with IPv6 support). To disable listening for &XDMCP; requests altogether, a @@ -2103,11 +2103,11 @@ the [Xdmcp] option is preferred. - + Supplementary programs -The following programs are run by &kdm; at various stages of a session. +The following programs are run by &tdm; at various stages of a session. They typically are shell scripts. @@ -2119,7 +2119,7 @@ Their first argument is auto if the session results from an automatic login; otherwise, no arguments are passed to them. - + Setup program @@ -2156,7 +2156,7 @@ the following environment variables are passed: - Note that since &kdm; grabs the keyboard, any other windows will not be + Note that since &tdm; grabs the keyboard, any other windows will not be able to receive keyboard input. They will be able to interact with the mouse, however; beware of potential security holes here. If is set, Xsetup will not be able to connect to the display @@ -2166,7 +2166,7 @@ at all. Resources for this program can be put into the file named by - + Startup program The Xstartup program is run as @@ -2215,13 +2215,13 @@ the following environment variables are passed: -&kdm; waits until this program exits before starting the user session. -If the exit value of this program is non-zero, &kdm; discontinues the session +&tdm; waits until this program exits before starting the user session. +If the exit value of this program is non-zero, &tdm; discontinues the session and starts another authentication cycle. - + Session program The Xsession program is the command which is run @@ -2295,7 +2295,7 @@ the following environment variables are passed: - + Reset program Symmetrical with Xstartup, the -- cgit v1.2.1