- Timestamp:
- 08/01/2015 11:47:07 PM (9 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 7.10, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- fc580439
- Parents:
- 7b88d5a
- Location:
- x/dm
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
x/dm/dm.xml
r7b88d5a r1def00f 23 23 <para> 24 24 Display Managers are graphical programs used for starting the graphical 25 display (currently, the X server) and loging in a Windows Manageror26 Desktop Environment.25 display (currently, the X server) and providing a login capability for 26 a Window Manager or Desktop Environment. 27 27 </para> 28 28 29 29 <para> 30 30 There are many Display Managers available. Some of the more well 31 known include 31 known include: 32 32 <application>GDM</application>, 33 <application>KDM</application> ,33 <application>KDM</application> (deprecated), 34 34 <application>LightDM</application>, 35 35 <application>LXDM</application>, … … 39 39 40 40 <para> 41 Between the Desktop Environments available for Linux you find41 Among the Desktop Environments available for Linux you find: 42 42 <application>Enlightenment</application>, 43 43 <application>GNOME</application>, … … 49 49 50 50 <para> 51 Choosing a Display Manager or D isplayEnvironment is highly subjective.51 Choosing a Display Manager or Desktop Environment is highly subjective. 52 52 The choice depends on the look and feel of the packages, the resources 53 ( RAM,disk space) required, and the utilities included.53 (memory and disk space) required, and the utilities included. 54 54 </para> 55 55 … … 57 57 In this chapter, the installation instructions of some Display Managers 58 58 are presented. Later in the book, you will find other ones, which are 59 provided as part of some Desktop Envir eonments.59 provided as part of some Desktop Environments. 60 60 </para> 61 61 -
x/dm/lxdm.xml
r7b88d5a r1def00f 39 39 alternative to other Display Managers such as 40 40 <application>GNOME's</application> <application>GDM</application> or 41 <application> KDE's</application> <application>KDM</application>.41 <application>LightDM</application>. 42 42 </para> 43 43 … … 83 83 <para role="required"> 84 84 <xref linkend="gtk2"/>, 85 <xref linkend="iso-codes"/> and85 <xref linkend="iso-codes"/>, and 86 86 <xref linkend="librsvg"/> (runtime, for default theme background) 87 87 </para> … … 228 228 229 229 <para> 230 The LXDM daemon configuration <filename>/etc/lxdm/lxdm.conf</filename> 231 file options includes numlock on/off, backgraound image (bg), session, 232 etc. You can set a default session by uncommenting the line: 230 The LXDM daemon configuration file 231 (<filename>/etc/lxdm/lxdm.conf</filename>) specifies options that 232 include numlock on/off, backgraound image (bg), session, etc. You can 233 set a default session by uncommenting the line: 233 234 session=/usr/bin/startlxde and replacing <command>startlxde</command> 234 235 with your session of choice. For <application>GNOME</application> … … 246 247 247 248 <para> 248 You can replace the default dummy face in the greeting screen by other249 You can replace the default dummy face in the greeting screen by another 249 250 image representing your user. For that, copy or symlink the desired 250 image to your home directory ,with the name <filename>.face</filename>.251 image to your home directory with the name <filename>.face</filename>. 251 252 </para> 252 253 … … 265 266 266 267 <para> 267 By definition, X should be executed at runlevel 5, consequently, the268 same is true for <application>lxdm</application>. However, BLFS default269 runlevel is 3. Changing to runlevel 5, from the terminal,as270 <systemitem class="username">root</systemitem> user , makes the271 <command>lxdm</command> bootscript to be executed, obtainingthe268 By convention, X should be executed at runlevel 5, consequently, the 269 same is true for <application>lxdm</application>. However, the LFS default 270 runlevel is 3. Changing to runlevel 5, from the console (as 271 <systemitem class="username">root</systemitem> user) starts the 272 <command>lxdm</command> bootscript and presents the 272 273 greeter screen: 273 274 </para> … … 276 277 277 278 <para> 278 In order to permanently set the default to 5, obtaining the279 In order to permanently set the default to 5, starting the 279 280 <command>lxdm</command> greeter screen automatically, you can modify 280 <filename>/etc/inittab</filename>, as <systemitem 281 class="username">root</systemitem> user (the instructions below also 282 make a backup, so you can easily revert the modification): 281 <filename>/etc/inittab</filename>. As the <systemitem 282 class="username">root</systemitem> user: 283 283 </para> 284 284 … … 286 286 sed -i '/initdefault/ s/3/5/' /etc/inittab</userinput></screen> 287 287 288 <para> 289 One important script, executed after login, is 290 <filename>/etc/lxdm/Xsession</filename>, which we have fixed to fit 288 <note> 289 <para> 290 One important script, executed after login is 291 <filename>/etc/lxdm/Xsession</filename> which we have fixed to fit 291 292 BLFS specifications. 292 293 </para> 294 </note> 293 295 294 296 </sect3> -
x/dm/sddm.xml
r7b88d5a r1def00f 36 36 <para> 37 37 The <application>SDDM</application> package contains a lightweight 38 display manager written in <application>Qt</application> and QML.38 display manager based upon <application>Qt</application> and QML. 39 39 </para> 40 40 … … 107 107 108 108 <para> 109 It is recommended to have a dedicated user and group to take109 First, create a dedicated user and group to take 110 110 control of the <command>sddm</command> daemon after it is 111 111 started. Issue the following commands as the … … 114 114 115 115 <screen role="root"><userinput>groupadd -g 64 sddm && 116 useradd -c "SDDM Daemon Owner" -d /var/lib/sddm -u 64 \ 117 -g sddm -s /bin/false sddm</userinput></screen> 116 useradd -c "SDDM Daemon" -d /var/lib/sddm -u 64 -g sddm -s /bin/false sddm</userinput></screen> 118 117 119 118 <para> … … 150 149 <para> 151 150 <parameter>-DCMAKE_BUILD_TYPE=Release</parameter>: This switch is used to 152 apply higher level of thecompiler optimizations.151 apply additional compiler optimizations. 153 152 </para> 154 153 … … 162 161 <sect2 role="configuration"> 163 162 <title>Configuring SDDM</title> 163 164 <sect3 id="sddm-bootscript"> 165 <title>Boot Script</title> 166 167 <para> 168 Install the <filename>/etc/rc.d/init.d/sddm</filename> init script from 169 the <xref linkend="bootscripts"/> package. 170 </para> 171 172 <indexterm zone="sddm sddm-bootscript"> 173 <primary sortas="f-sddm">sddm</primary> 174 </indexterm> 175 176 <screen role="root"><userinput>make install-sddm</userinput></screen> 177 178 </sect3> 164 179 165 180 <sect3> … … 191 206 # End /etc/pam.d/sddm</literal> 192 207 EOF 208 193 209 cat > /etc/pam.d/sddm-autologin << "EOF" && 194 210 <literal># Begin /etc/pam.d/sddm-autologin … … 209 225 # End /etc/pam.d/sddm-autologin</literal> 210 226 EOF 227 211 228 cat > /etc/pam.d/sddm-greeter << "EOF" 212 229 <literal># Begin /etc/pam.d/sddm-greeter … … 229 246 230 247 <para> 231 You can manually start <command>sddm</command>, e.g, if the bootscript 232 has been installed, by running, as <systemitem 248 If the sddm bootscript has been installed, start it by running, as 249 <systemitem class="username">root</systemitem> user: 250 </para> 251 252 <screen role="root"><userinput>/etc/rc.d/init.d/sddm start</userinput></screen> 253 254 <para> 255 By convertion, X should be executed at runlevel 5, consequently, the 256 same is true for <application>sddm</application>. However, LFS default 257 runlevel is 3. Changing to runlevel 5, from a console terminal, as 258 <systemitem class="username">root</systemitem> user, starts the 259 <command>sddm</command> bootscript, bringing up the greeter screen: 260 </para> 261 262 <screen role="root"><userinput>init 5</userinput></screen> 263 264 <para> 265 In order to permanently set the default to 5, starting the 266 <command>sddm</command> greeter screen automatically, modify 267 <filename>/etc/inittab</filename>. As the <systemitem 233 268 class="username">root</systemitem> user: 234 </para>235 236 <screen role="root"><userinput>/etc/rc.d/init.d/sddm start</userinput></screen>237 238 <para>239 By definition, X should be executed at runlevel 5, consequently, the240 same is true for <application>sddm</application>. However, BLFS default241 runlevel is 3. Changing to runlevel 5, from the terminal, as242 <systemitem class="username">root</systemitem> user, makes the243 <command>sddm</command> bootscript to be executed, obtaining the244 greeter screen:245 </para>246 247 <screen role="root"><userinput>init 5</userinput></screen>248 249 <para>250 In order to permanently set the default to 5, obtaining the251 <command>sddm</command> greeter screen automatically, you can modify252 <filename>/etc/inittab</filename>, as <systemitem253 class="username">root</systemitem> user (the instructions below also254 make a backup, so you can easily revert the modification):255 269 </para> 256 270 … … 279 293 <seg> 280 294 $QT5DIR/qml/SddmComponents, 281 /usr/share/sddm and295 /usr/share/sddm, and 282 296 /var/lib/sddm 283 297 </seg> … … 295 309 <para> 296 310 is a display and login manager based on 297 <application>Qt</application> technologies.311 <application>Qt</application> libraries. 298 312 </para> 299 313 <indexterm zone="sddm sddm-prog"> … … 308 322 <para> 309 323 is an auxiliary process that displays the greeter, 310 a graphical user interface to perform the 311 authentication and select the session to run. 324 a graphical user interface that performs user 325 authentication and initiates the selected window manager 326 or display environment. 312 327 </para> 313 328 <indexterm zone="sddm sddm-greeter">
Note:
See TracChangeset
for help on using the changeset viewer.