Changeset 52250565


Ignore:
Timestamp:
10/06/2020 12:16:17 PM (4 years ago)
Author:
Pierre Labastie <pieere@…>
Branches:
10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, 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:
6d44b69
Parents:
a6b95b9d
Message:

Various clean-up and modifications to the dm pages in view of the recent
change to the bootscripts.

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@23788 af4574ff-66df-0310-9fd7-8a98e5e911e0

Files:
4 edited

Legend:

Unmodified
Added
Removed

  • general.ent

    ra6b95b9d r52250565  
    11<!-- $LastChangedBy$ $Date$ -->
    22
    3 <!ENTITY day          "05">                   <!-- Always 2 digits -->
     3<!ENTITY day          "06">                   <!-- Always 2 digits -->
    44<!ENTITY month        "10">                   <!-- Always 2 digits -->
    55<!ENTITY year         "2020">
    … …  
    77<!ENTITY copyholder   "The BLFS Development Team">
    88<!ENTITY version      "&year;-&month;-&day;">
    9 <!ENTITY releasedate  "October 5th, &year;">
     9<!ENTITY releasedate  "October 6th, &year;">
    1010<!ENTITY pubdate      "&year;-&month;-&day;"> <!-- metadata req. by TLDP -->
    1111<!ENTITY blfs-version "svn">                  <!-- svn|[release #] -->

  • gnome/platform/gdm.xml

    ra6b95b9d r52250565  
    128128passwd -ql gdm</userinput></screen>
    129129
    130 <!--
    131     <note revision="sysv">
    132       <para>
    133         The <application>gdm</application> login screen is managed by
    134         <application>gnome-shell</application>, which relies on the
    135         <command>systemd-localed</command> daemon to get the system
    136         settings. Since this daemon is not present on this system, a
    137         <command>sed</command> is applied in the <xref
    138         linkend="gnome-shell"/> instructions to change this behavior,
    139         but then <application>gdm</application> uses the system settings,
    140         which default to a US <quote>qwerty</quote> keyboard layout. This may
    141         be an inconvience to enter a password when the machine keyboard
    142         has a different layout. One possibility is to use the screen-keyboard
    143         from the accessibility menu. Another possibility is to change the
    144         defaults at compile time, by creating the following file:
    145       </para>
    146 
    147 <screen><userinput>cat &gt; data/dconf/defaults/01-keyboard &lt;&lt; EOF
    148 <literal>[org/gnome/desktop/input-sources]
    149 sources=[('xkb','<replaceable>layout</replaceable>')]</literal>
    150 EOF</userinput></screen>
    151 
    152       <para>
    153         where <replaceable>layout</replaceable> should be replaced with
    154         the acronym for your keyboard layout (one of the filenames in
    155         <filename class="directory">/usr/share/X11/xkb/symbols</filename>).
    156       </para>
    157     </note>
    158 -->
    159130    <para>
    160131      Install <application>GDM</application> by running the following
    … …  
    270241
    271242      <para revision="sysv">
    272         To start the <command>gdm</command> automatically when the system
    273         is booted, install the <filename>/etc/rc.d/init.d/gdm</filename>
    274         init script included in the <xref linkend="bootscripts"/> package and
    275         set the default runlevel to 5 (graphical login) as the
    276         <systemitem class="username">root</systemitem> user:
    277       </para>
    278 
    279       <para revision="systemd">
    280         To start the <command>gdm</command> daemon at boot, enable
    281         the previously installed systemd unit by running the following command
     243        To start <command>gdm</command> automatically when the system is
     244        switched to runlevel 5, install the
     245        <filename>/etc/rc.d/init.d/xdm</filename> script and the
     246        <filename>/etc/sysconfig/xdm</filename> configuration file
     247        included in the <xref linkend="bootscripts"/> package
     248        and adjust <filename>/etc/inittab</filename> by running
    282249        as the <systemitem class="username">root</systemitem> user:
    283250      </para>
    … …  
    294261<screen role="root" revision="sysv"><userinput>sed /initdefault/s/3/5/ -i /etc/inittab</userinput></screen>
    295262
     263      <para revision="systemd">
     264        To start the <command>gdm</command> daemon at boot, enable
     265        the previously installed systemd unit by running the following command
     266        as the <systemitem class="username">root</systemitem> user:
     267      </para>
     268
     269<screen role="root" revision="systemd"><userinput>systemctl enable gdm</userinput></screen>
     270
     271<!-- [pierre October 2020] I don't understand why this is here: power
     272     management works perfectly well
    296273      <para revision="sysv">
    297274          You should also disable default elogind power management:
    … …  
    302279AllowHibernation=no</literal>
    303280EOF</userinput></screen>
    304 
    305 <screen role="root" revision="systemd"><userinput>systemctl enable gdm</userinput></screen>
     281-->
    306282
    307283    </sect3>

  • x/dm/lightdm.xml

    ra6b95b9d r52250565  
    310310             <phrase revision="systemd">Systemd Unit</phrase></title>
    311311
    312       <para revision="sysv">
    313         Install the <filename revision="sysv">/etc/rc.d/init.d/lightdm</filename>
    314         init script from the <xref linkend="bootscripts"/>
    315       </para>
    316 
    317 <screen role="root" revision="sysv"><userinput>make install-lightdm</userinput></screen>
    318312      <indexterm zone="lightdm lightdm-bootscript">
    319313        <primary sortas="f-lightdm">lightdm</primary>
    320314      </indexterm>
    321315
     316      <para revision="sysv">
     317        To start <command>lightdm</command> automatically when the system is
     318        switched to runlevel 5, install the
     319        <filename>/etc/rc.d/init.d/xdm</filename> script and the
     320        <filename>/etc/sysconfig/xdm</filename> configuration file
     321        included in the <xref linkend="bootscripts"/> package
     322        and adjust <filename>/etc/inittab</filename> by running
     323        as the <systemitem class="username">root</systemitem> user:
     324      </para>
     325
     326<screen role="root" revision="sysv"><userinput>make install-lightdm</userinput></screen>
     327
    322328      <para revision="systemd">
    323329        Install and enable the systemd unit.  From the
    … …  
    334340
    335341      <para>
    336         If the lightdm bootscript has been installed, start lightdm by running, as the
    337         <systemitem class="username">root</systemitem> user:
    338       </para>
    339 
    340 <screen role="root"><userinput>/etc/rc.d/init.d/lightdm start</userinput></screen>
     342        The <command>lightdm</command> greeter can be started from the
     343        command line as the <systemitem class="username">root</systemitem>
     344        user:
     345      </para>
     346
     347<screen role="root"><userinput>telinit 5</userinput></screen>
    341348
    342349      <para>
    343         By convention, X should be executed at runlevel 5, consequently, the
    344         same is true for <application>lightdm</application>. However, LFS default
    345         runlevel is 3. Changing to runlevel 5, from a console terminal, as
    346         <systemitem class="username">root</systemitem> user, starts the
    347         <command>lightdm</command> bootscript, bringing up the greeter screen:
    348       </para>
    349 
    350 <screen role="root"><userinput>init 5</userinput></screen>
    351 
    352       <para>
    353         In order to permanently set the default to 5, starting the
    354         <command>lightdm</command> greeter screen automatically, modify
     350        Alternatively the runlevel can be permanently set to 5, starting the
     351        <command>lightdm</command> greeter screen automatically, by modifying
    355352        <filename>/etc/inittab</filename>.  As the <systemitem
    356353        class="username">root</systemitem> user:

  • x/dm/lxdm.xml

    ra6b95b9d r52250565  
    221221
    222222   <sect3 id="lxdm-init">
    223       <title>Boot Script</title>
     223      <title><phrase revision="sysv">Boot Script</phrase>
     224             <phrase revision="systemd">Systemd Unit</phrase></title>
     225
     226      <indexterm zone="lxdm lxdm-init">
     227        <primary sortas="f-lxdm">lxdm</primary>
     228      </indexterm>
    224229
    225230      <para revision="sysv">
    226         Install the <filename>/etc/rc.d/init.d/lxdm</filename> init script from
    227         the <xref linkend="bootscripts"/> package.
    228       </para>
     231        To start <command>lxdm</command> automatically when the system is
     232        switched to runlevel 5, install the
     233        <filename>/etc/rc.d/init.d/xdm</filename> script and the
     234        <filename>/etc/sysconfig/xdm</filename> configuration file
     235        included in the <xref linkend="bootscripts"/> package
     236        and adjust <filename>/etc/inittab</filename> by running
     237        as the <systemitem class="username">root</systemitem> user:
     238      </para>
     239
     240<screen role="root" revision="sysv"><userinput>make install-lxdm</userinput></screen>
    229241
    230242      <para revision="systemd">
    … …  
    233245      </para>
    234246
    235       <indexterm zone="lxdm lxdm-init">
    236         <primary sortas="f-lxdm">lxdm</primary>
    237       </indexterm>
    238 
    239 <screen role="root" revision="sysv"><userinput>make install-lxdm</userinput></screen>
    240247<screen role="root" revision="systemd"><userinput>systemctl enable lxdm</userinput></screen>
    241248
    … …  
    276283
    277284      <para>
    278         You can manually start <command>lxdm</command>, e.g, if the bootscript
    279         has been installed, by running, as <systemitem
     285        The <command>lxdm</command> greeter can be started from the command
     286        line as the <systemitem class="username">root</systemitem> user:
     287      </para>
     288
     289<screen role="root"><userinput>telinit 5</userinput></screen>
     290
     291      <para>
     292        Alternatively the runlevel can be permanently set to 5, starting the
     293        <command>lxdm</command> greeter screen automatically, by modifying
     294        <filename>/etc/inittab</filename>. As the  <systemitem
    280295        class="username">root</systemitem> user:
    281       </para>
    282 
    283 <screen role="root"><userinput>/etc/rc.d/init.d/lxdm start</userinput></screen>
    284 
    285       <para>
    286         By convention, X should be executed at runlevel 5, consequently, the
    287         same is true for <application>lxdm</application>. However, the LFS default
    288         runlevel is 3. Changing to runlevel 5, from the console (as
    289         <systemitem class="username">root</systemitem> user) starts the
    290         <command>lxdm</command> bootscript and presents the
    291         greeter screen:
    292       </para>
    293 
    294 <screen role="root"><userinput>init 5</userinput></screen>
    295 
    296       <para>
    297           In order to permanently set the default to 5, starting the
    298           <command>lxdm</command> greeter screen automatically, you can modify
    299           <filename>/etc/inittab</filename>. As the  <systemitem
    300           class="username">root</systemitem> user:
    301296      </para>
    302297
    … …  
    304299sed -i '/initdefault/ s/3/5/' /etc/inittab</userinput></screen>
    305300
    306       <para>
    307           You should also disable default elogind power management:
    308       </para>
    309  
    310 <screen role="root"><userinput>cat &gt;&gt; /etc/elogind/logind.conf &lt;&lt; "EOF"
    311 <literal>AllowSuspend=no
    312 AllowHibernation=no</literal>
    313 EOF</userinput></screen>
    314 
    315301      <note>
    316       <para>
     302        <para>
    317303          One important script, executed after login is
    318304          <filename>/etc/lxdm/Xsession</filename> which we have fixed to fit
    319305          BLFS specifications.
    320       </para>
     306        </para>
    321307      </note>
    322308
    … …  
    324310
    325311  </sect2>
    326   <!--Required section-->
     312 
    327313  <sect2 role="content">
    328314    <title>Contents</title>
    … …  
    352338      <?dbhtml list-presentation="table"?>
    353339
    354       <!-- If the program or library name conflicts (is the same) as the
    355       package name, add -prog or -lib to the varlistentry entity id
    356       and the 2nd entry of the indexterm zone entity -->
    357 
    358340      <varlistentry id="lxdm-prog">
    359341        <term><command>lxdm</command></term>
Note: See TracChangeset for help on using the changeset viewer.