Index: introduction/welcome/changelog.xml
===================================================================
--- introduction/welcome/changelog.xml	(revision 01dfd5459f0b402296e3089e3cdc6cb5b3b0569e)
+++ introduction/welcome/changelog.xml	(revision c0b5bbac7bcda0a5f02c321caf6e65e6a826300a)
@@ -59,4 +59,19 @@
         <listitem>
           <para>[cjg] - Added systemd notes to cyrus-sasl page.</para>
+        </listitem>
+        <listitem>
+          <para>[cjg] - Added systemd notes to libcap page.</para>
+        </listitem>   
+        <listitem>
+          <para>[cjg] - Added systemd notes to mitkrb page.</para>
+        </listitem>
+        <listitem>
+          <para>[cjg] - Added systemd notes to openssh page.</para>
+        </listitem>
+        <listitem>
+          <para>[cjg] - Added systemd notes to polkit page.</para>
+        </listitem>
+        <listitem>
+          <para>[cjg] - Added systemd notes to stunnel page.</para>
         </listitem>
       </itemizedlist>
Index: postlfs/security/libcap.xml
===================================================================
--- postlfs/security/libcap.xml	(revision 01dfd5459f0b402296e3089e3cdc6cb5b3b0569e)
+++ postlfs/security/libcap.xml	(revision c0b5bbac7bcda0a5f02c321caf6e65e6a826300a)
@@ -69,4 +69,11 @@
   <sect2 role="installation">
     <title>Installation of libcap</title>
+
+     <note>
+     <para>
+     Systemd users don't need to install this package since it has 
+     already been installed as part of LFS.
+     </para>
+     </note>
 
     <para>Install <application>libcap</application> by running the following
Index: postlfs/security/mitkrb.xml
===================================================================
--- postlfs/security/mitkrb.xml	(revision 01dfd5459f0b402296e3089e3cdc6cb5b3b0569e)
+++ postlfs/security/mitkrb.xml	(revision c0b5bbac7bcda0a5f02c321caf6e65e6a826300a)
@@ -474,4 +474,33 @@
 
       <indexterm zone="mitkrb mitkrb-init">
+        <primary sortas="f-krb5">krb5</primary>
+      </indexterm>
+
+<screen role="root"><userinput>make install-krb5</userinput></screen>
+
+    </sect3>
+
+
+    <sect3 id="mitkrb-init-systemd">
+      <title>Systemd Unit File</title>
+
+      <note>
+      <para>
+        Note that Kerberos KDC server needs to be configured first, so don't 
+        install systemd units unless krb5kdc has been tested to work according to 
+        the BLFS instructions. The install process installs 3 units, one for krb5kdc, 
+        one for kpropd the Kerberos Propagation Server and the one for kadmind 
+        the Kerberos Admin Server.
+      </para>
+      </note>
+
+      <para>
+        Instead of using the classic boot script, the systemd-units package 
+        provides native unit files.
+        Install the Systemd Unit included in the <xref linkend="systemd-units"/> 
+        package using the following command:
+      </para>
+
+      <indexterm zone="mitkrb mitkrb-init-systemd">
         <primary sortas="f-krb5">krb5</primary>
       </indexterm>
Index: postlfs/security/openssh.xml
===================================================================
--- postlfs/security/openssh.xml	(revision 01dfd5459f0b402296e3089e3cdc6cb5b3b0569e)
+++ postlfs/security/openssh.xml	(revision c0b5bbac7bcda0a5f02c321caf6e65e6a826300a)
@@ -316,4 +316,50 @@
 <screen role="root"><userinput>make install-sshd</userinput></screen>
     </sect3>
+
+    <sect3  id="openssh-init-systemd">
+      <title>Systemd Unit File</title>
+
+      <para>
+       Instead of using the classic boot script, the systemd-units package provides 
+       native unit files. To start the SSH server at system boot, install the
+       systemd unit included in the <xref linkend="systemd-units"/> package.as the 
+       <systemitem class="username">root</systemitem> user:
+       </para>
+
+      <indexterm zone="openssh openssh-init-systemd">
+        <primary sortas="f-sshd">sshd</primary>
+      </indexterm>
+
+<screen role="root"><userinput>make install-sshd</userinput></screen>
+
+      <note>
+      <para>
+        Note that this package comes with two types of units: A service file and a socket file. 
+        The service file will start sshd daemon once at boot and it will keep running until the 
+        system shuts down. The socket file will make systemd listen to sshd port (Default 22, needs 
+        to be edited for anything else) and will start sshd daemon when something tries to connect 
+        to that port and stop the daemon when the connection is terminated. This is 
+        called socket activation.
+
+        By default, the first method is used - sshd daemon is started at boot and stopped at shutdown. 
+        If the socket method is desired, you need to run as the <systemitem class="username">root</systemitem> user:
+
+ 
+<screen role="root">
+
+<userinput>         
+
+systemctl stop sshd &amp;&amp; 
+systemctl disable sshd.service &amp;&amp;
+systemctl enable sshd.socket &amp;&amp;
+systemctl start sshd.socket
+
+</userinput>
+</screen>
+
+      </para>
+      </note>
+    </sect3>
+
   </sect2>
 
Index: postlfs/security/polkit.xml
===================================================================
--- postlfs/security/polkit.xml	(revision 01dfd5459f0b402296e3089e3cdc6cb5b3b0569e)
+++ postlfs/security/polkit.xml	(revision c0b5bbac7bcda0a5f02c321caf6e65e6a826300a)
@@ -90,8 +90,19 @@
       <xref linkend="DocBook"/>,
       <xref linkend="docbook-xsl"/>,
-      <xref linkend="gtk-doc"/>,
-      <xref linkend="libxslt"/> and
+      <xref linkend="gtk-doc"/>, and
+      <xref linkend="libxslt"/>
+    </para>
+
+    <bridgehead renderas="sect4">Optional (Required if using systemd and building GNOME)</bridgehead>
+    <para role="optional">
       <xref linkend="linux-pam"/>
     </para>
+
+    <note>
+      <para>
+        This package will link against systemd libraries by default, since they are always installed 
+        and in doing that, it doesn't require ConsoleKit anymore.
+      </para>
+    </note>
 
     <note>
@@ -162,4 +173,15 @@
       replace "no" by "yes".
     </para>
+
+    <note>
+    <para>
+     Systemd users, if this package is going to be used, ie on desktops or if an 
+     user wants to grant unprivileged users to be able to shut down, 
+     reboot, etc the systemd PAM module needs to be built and set up. 
+     It is also a good idea to build Polkit with PAM support, so the Polkit can take 
+     advantage of the PAM module, so you need to remove the below parameter from
+     the configure line, and create the PAM file mentioned in the configuration section.
+    </para>
+    </note>
 
     <para>
Index: postlfs/security/stunnel.xml
===================================================================
--- postlfs/security/stunnel.xml	(revision 01dfd5459f0b402296e3089e3cdc6cb5b3b0569e)
+++ postlfs/security/stunnel.xml	(revision c0b5bbac7bcda0a5f02c321caf6e65e6a826300a)
@@ -241,4 +241,29 @@
 
 <screen role="root"><userinput>make install-stunnel</userinput></screen>
+
+    </sect3>
+
+    <sect3  id="stunnel-init-systemd">
+      <title>Systemd Unit File</title>
+
+      <para>This package provides a systemd unit in the source tarball.
+       To install it run the following commands as the 
+     <systemitem class="username">root</systemitem> user:
+      </para>
+      <indexterm zone="stunnel stunnel-init-systemd">
+        <primary sortas="f-stunnel">stunnel</primary>
+      </indexterm>
+
+      <para>Remove an unnecessary dependency:</para>
+
+<screen role="root"><userinput>sed -i /syslog.target/d tools/stunnel.service</userinput></screen>
+
+      <para>Install the service:</para>
+
+<screen role="root"><userinput>install -v -m644 tools/stunnel.service /lib/systemd/system/stunnel.service</userinput></screen>
+
+      <para>Enable the service:</para>
+
+<screen role="root"><userinput>systemctl enable stunnel</userinput></screen>
 
     </sect3>
