source: general/sysutils/systemd.xml@ af8b2d9

<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
   "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
  <!ENTITY % general-entities SYSTEM "../../general.ent">
  %general-entities;

  <!ENTITY systemd-download-http       "http://anduin.linuxfromscratch.org/sources/other/systemd/systemd-&lfs-systemd-version;.tar.xz">
]>

<sect1 id="systemd" xreflabel="Systemd-&lfs-systemd-version;">
  <?dbhtml filename="systemd.html"?>

  <sect1info>
    <othername>$LastChangedBy$</othername>
    <date>$Date$</date>
  </sect1info>

  <title>Systemd-&lfs-systemd-version;</title>

  <indexterm zone="systemd">
    <primary sortas="a-systemd">systemd</primary>
  </indexterm>

  <sect2 role="package">
    <title>Introduction to systemd</title>

    <para>
      Even though <application>systemd</application> was installed while
      building LFS, there are many features provided by the package that
      were not included in the initial installation due to unmet dependencies.
      The <application>systemd</application> package needs to be
      rebuilt to provide a working <command>systemd-logind</command> service,
      among many others.
    </para>
    
    &lfs79_checked;&gcc6_checked;

    <bridgehead renderas="sect3">Package Information</bridgehead>
    <itemizedlist spacing="compact">
      <listitem>
        <para>Systemd Download (HTTP): <ulink url="&systemd-download-http;"/></para>
      </listitem>
    </itemizedlist>

    <bridgehead renderas="sect3">systemd Dependencies</bridgehead>

    <bridgehead renderas="sect4">Required</bridgehead>
    <para role="required">
      <xref linkend="linux-pam"/>
    </para>

    <bridgehead renderas="sect4">Recommended Runtime Dependency</bridgehead>
    <para role="recommended">
      <xref linkend="polkit"/>
    </para>

    <bridgehead renderas="sect4">Optional</bridgehead>
    <para role="optional">
      <xref linkend="cacerts"/>,
      <xref linkend="curl"/>,
      <xref linkend="elfutils"/>,
      <xref linkend="gnutls"/>,
      <xref linkend="iptables"/>,
      <xref linkend="libgcrypt"/>,
      <xref linkend="libidn"/>,
      <xref linkend="libxkbcommon"/>,
      <xref linkend="python2"/> or
      <xref linkend="python3"/>,
      <xref linkend="qemu"/>,
      <xref linkend="valgrind"/>,
      <ulink url="https://www.kernel.org/pub/linux/utils/cryptsetup/">cryptsetup</ulink>,
      <ulink url="http://sourceforge.net/projects/gnu-efi/">gnu-efi</ulink>,
      <ulink url="https://www.kernel.org/pub/linux/utils/kernel/kexec/">kexec-tools</ulink>,
      <ulink url="https://www.gnu.org/software/libmicrohttpd/">libmicrohttpd</ulink>,
      <ulink url="http://sourceforge.net/projects/libseccomp/">libseccomp</ulink>,
      <ulink url="http://lxml.de/">lxml</ulink> (Python Module),
      <ulink url="https://code.google.com/p/lz4/">lz4</ulink>,
      <ulink url="http://fukuchi.org/works/qrencode/">qrencode</ulink>,
      <ulink url="http://sourceforge.net/projects/linuxquota/">quota-tools</ulink> and
      <ulink url="https://pypi.python.org/pypi/Sphinx">Sphinx</ulink>
    </para>

    <note>
      <para>
        In order to build the <application>systemd</application>
        <application>Python</application> module, lxml package
        needs to be installed for the corresponding
        <application>Python</application> version (2 or 3).
        Note that <command>configure</command> defaults to
        <application>Python 2</application>. In order to build
        the module for <application>Python 3</application>,
        make sure you pass the <envar>PYTHON=python3</envar>
        environment variable to the <command>configure</command>
        command below.
      </para>
    </note>

    <bridgehead renderas="sect4">Optional (to rebuild the manual pages)</bridgehead>
    <para role="optional">
      <xref linkend="DocBook"/>,
      <xref linkend="docbook-xsl"/> and
      <xref linkend="libxslt"/>
    </para>

    <para condition="html" role="usernotes">User Notes:
      <ulink url="&blfs-wiki;/systemd"/>
    </para>
  </sect2>

  <sect2 role="installation">
    <title>Installation of systemd</title>

    <para>First, fix a potential security issue with framebuffer
    devices:</para>

<screen><userinput>sed -e 's@DRI and frame buffer@DRI@' \
    -e '/SUBSYTEM==\"graphics\", KERNEL==\"fb\*\"/d' \
    -i  src/login/70-uaccess.rules</userinput></screen>

    <para>
      Disable two tests that always fail:
    </para>

<screen><userinput>sed -e 's:test/udev-test.pl ::g'  \
    -e 's:test-copy$(EXEEXT) ::g' \
    -i Makefile.in</userinput></screen>

    <para>
      Rebuild <application>systemd</application> by running the
      following commands:
    </para>

<screen><userinput>cc_cv_CFLAGS__flto=no                \
./configure --prefix=/usr            \
            --sysconfdir=/etc        \
            --localstatedir=/var     \
            --with-rootprefix=       \
            --with-rootlibdir=/lib   \
            --enable-split-usr       \
            --disable-firstboot      \
            --disable-ldconfig       \
            --disable-sysusers       \
            --without-python         \
            --with-default-dnssec=no \
            --docdir=/usr/share/doc/systemd-&lfs-systemd-version; &amp;&amp;
make</userinput></screen>

    <note>
      <para>
        For the best results, make sure you run the testsuite from
        a system that is booted by the same
        <application>systemd</application> version you are rebuilding.
      </para>
    </note>

    <para>
      To test the results, issue: <command>make -k check</command>.
    </para>

    <warning>
      <para>
        Installing the package will override all files installed by
        <application>systemd</application> in LFS. It is critical that
        nothing uses either <application>systemd</application> or
        <application>Udev</application> libraries or programs during
        the installation phrase. Best way to achieve that is to do the
        installation in the rescue mode. To switch to the rescue mode,
        issue the following command as the
        <systemitem class="username">root</systemitem> user from a TTY:
      </para>

<screen role="root"><userinput>systemctl start rescue.target</userinput></screen>
    </warning>

   <para>
     Now, as the <systemitem class="username">root</systemitem> user:
   </para>

<screen role="root"><userinput>make install</userinput></screen>

    <para>
      Move NSS libraries to <filename class="directory">/lib</filename>
      by running the following command as the <systemitem
      class="username">root</systemitem> user:
    </para>

<screen role="root"><userinput>mv -v /usr/lib/libnss_{myhostname,mymachines,resolve}.so.2 /lib</userinput></screen>

    <para>
      Remove an unnecessary directory by running the following command
      as the <systemitem class="username">root</systemitem> user:
    </para>

<screen role="root"><userinput>rm -rfv /usr/lib/rpm</userinput></screen>

  </sect2>

  <sect2 role="configuration">
    <title>Configuring systemd</title>

    <para>
      The <filename>/etc/pam.d/system-sesion</filename> file needs to
      be modified and a new file needs to be created in order for
      <command>systemd-logind</command> to work correctly. To accomplish
      that, run the following commands as the <systemitem
     class="username">root</systemitem> user:
    </para>

<screen role="root"><userinput>cat &gt;&gt; /etc/pam.d/system-session &lt;&lt; "EOF"
<literal># Begin Systemd addition
    
session   required    pam_loginuid.so
session   optional    pam_systemd.so

# End Systemd addition</literal>
EOF

cat &gt; /etc/pam.d/systemd-user &lt;&lt; "EOF"
<literal># Begin /etc/pam.d/systemd-user

account  required pam_access.so
account  include  system-account

session  required pam_env.so
session  required pam_limits.so
session  include  system-session

auth     required pam_deny.so
password required pam_deny.so

# End /etc/pam.d/systemd-user</literal>
EOF</userinput></screen>

    <para>
      At this point, you should reload the systemd daemon, and reenter
      multi-user mode with the following commands as the
      <systemitem class="username">root</systemitem> user:
    </para>

<screen role="root"><userinput>systemctl daemon-reload
systemctl start multi-user.target</userinput></screen>

    <warning><para>If upgrading from a previous version of systemd and you
    use an initrd, the system will hang during boot if you do not generate a
    new initrd with systemd-root-device.target included.</para></warning>

  </sect2>

  <sect2 role="content">
    <title>Contents</title>

      <para>
        A list of the installed files, along with their short
        descriptions can be found at
        <ulink url="&lfs-root;/chapter06/systemd.html#contents-systemd"/>.
      </para>

      <para>
        Below are listed newly installed libraries and directories
        along with short descriptions.
      </para>

    <segmentedlist>
      <segtitle>Installed Programs</segtitle>
      <segtitle>Installed Libraries</segtitle>
      <segtitle>Installed Directories</segtitle>

      <seglistitem>
        <seg>
          None
        </seg>
        <seg>
          pam_systemd.so
          (in <filename class="directory">/lib/security</filename>)
        </seg>
        <seg>
          None
        </seg>
      </seglistitem>
    </segmentedlist>

    <variablelist>
      <bridgehead renderas="sect3">Short Descriptions</bridgehead>
      <?dbfo list-presentation="list"?>
      <?dbhtml list-presentation="table"?>

      <varlistentry id="pam_systemd">
        <term><filename class="libraryfile">pam_systemd.so</filename></term>
        <listitem>
          <para>
            is a PAM module used to register user sessions with the
            <application>systemd</application> login manager,
            <command>systemd-logind</command>.
          </para>
          <indexterm zone="systemd pam_systemd">
            <primary sortas="c-pam_systemd">pam_systemd.so</primary>
          </indexterm>
        </listitem>
      </varlistentry>

    </variablelist>

  </sect2>

</sect1>