Changeset dbdc2d7 for kde/core/config-systemd.xml
- Timestamp:
- 10/28/2014 08:29:21 PM (10 years ago)
- Branches:
- krejzi/svn
- Children:
- 44ed64ac
- Parents:
- 70eab9cd
- File:
-
- 1 moved
Legend:
- Unmodified
- Added
- Removed
-
kde/core/config-systemd.xml
r70eab9cd rdbdc2d7 36 36 <literal># Begin .xinitrc 37 37 38 exec ck-launch-sessiondbus-launch --exit-with-session startkde38 exec dbus-launch --exit-with-session startkde 39 39 40 40 # End .xinitrc</literal> 41 41 EOF</userinput></screen> 42 43 <note><para>If you are not using <application>ConsoleKit</application>, remove44 <userinput>ck-launch-session</userinput>.</para></note>45 42 46 43 <para>You can now start KDE using the <command>startx</command> command.</para> … … 53 50 <para>KDE comes with a graphical login interface called KDM (the KDE Display 54 51 Manager), which provides a customizable graphical login at boot. To use KDM, 55 you need to edit your <filename>/etc/inittab</filename> file (as the 56 <systemitem class="username">root</systemitem> user). 57 First, setup run-level 5 to start KDM (adjust 58 the path to kdm according to your system):</para> 52 you need to create and enable a systemd unit by running the following commands 53 as the <systemitem class="username">root</systemitem> user:</para> 59 54 60 <screen><userinput>cat >> /etc/inittab << EOF 61 <literal>kd:5:respawn:/opt/kde/bin/kdm</literal> 62 EOF</userinput></screen> 55 <screen role="root"><userinput>cat > /lib/systemd/system/kdm.service << EOF && 56 <literal>[Unit] 57 Description=K Display Manager 58 After=systemd-user-sessions.service 63 59 64 <para>Additionally, you need to change the default run-level from 3 to 5:</para> 60 [Service] 61 ExecStart=&kde-dir;/bin/kdm -nodaemon 65 62 66 <screen><userinput>sed -i 's#id:3:initdefault:#id:5:initdefault:#' /etc/inittab</userinput></screen> 63 [Install] 64 Alias=display-manager.service</literal> 65 EOF 66 systemctl enable kdm</userinput></screen> 67 67 68 68 <para>You can now restart your system and see the KDE login … … 88 88 <para>Every subsequent package can be built while having 89 89 <application>KDE</application> up and running, but remember to keep 90 <envar>&kde-dir;</envar> and <envar>&qt4-dir;</envar>set.</para>90 <envar>&kde-dir;</envar> set.</para> 91 91 92 92 </sect2>
Note:
See TracChangeset
for help on using the changeset viewer.