Moved /etc/resolv.conf symlink to Chapter 7.

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@11138 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

chapter01/changelog.xml

@@ -42,6 +42,15 @@
     <listitem revision="sysv"> or <listitem revision="systemd"> as
     appropriate for the entry or if needed the entire day's listitem.
 -->
+    <listitem revision="systemd">
+      <para>2016-10-27</para>
+      <itemizedlist>
+        <listitem>
+          <para>[dj] - Moved /etc/resolv.conf symlink to Chapter 7.</para>
+        </listitem>
+      </itemizedlist>
+    </listitem>
+
     <listitem revision="systemd">
       <para>2016-10-23</para>
       <itemizedlist>

chapter06/systemd.xml

@@ -220,10 +220,6 @@ ln -sfv ../lib/systemd/systemd /sbin/init</userinput></screen>
 
 <screen><userinput remap="install">systemd-machine-id-setup</userinput></screen>
 
-    <para>Fix a broken symlink created by the systemd installation process:</para>
-<screen><userinput remap="install">rm -fv /etc/resolv.conf
-ln -sv /run/systemd/resolve/resolv.conf /etc/resolv.conf</userinput></screen>
-
     <para>Since the testsuite largely depends on the host system kernel
     configuration, some tests may fail. It also needs a modification in
     order not to look for a program that will be installed by Util-Linux

chapter07/networkd.xml

@@ -25,7 +25,7 @@
     basic network configuration. Additionally, since version 213, DNS name
     resolution can be handled by <command>systemd-resolved</command> in place
     of a static <filename>/etc/resolv.conf</filename> file. Both services are
-    enabled by default, and absolutely should not be disabled.</para>
+    enabled by default.</para>
 
     <para>Configuration files for <command>systemd-networkd</command> (and
     <command>systemd-resolved</command>) can be placed in
@@ -119,10 +119,11 @@ EOF</userinput></screen>
       used.</para></note>
 
       <para>When using <command>systemd-resolved</command> for DNS
-      configuration, it is responsible for creating the
-      <filename>/etc/resolv.conf</filename> file. Since version 226, the
-      symlink for <filename>/etc/resolv.conf</filename> is created by systemd
-      when needed, so no further configuration is necessary.</para>
+      configuration, it creates the file
+      <filename>/run/systemd/resolve/resolv.conf</filename>. Create a
+      symlink in <filename>/etc</filename> to use the generatd file:</para>
+
+<screen><userinput remap="install">ln -sfv /run/systemd/resolve/resolv.conf /etc/resolv.conf</userinput></screen>
 
     </sect3>
 

general.ent

@@ -1,13 +1,13 @@
-<!ENTITY version         "SVN-20161023">
+<!ENTITY version         "SVN-20161027">
 <!ENTITY short-version   "svn">  <!-- Used below in &blfs-book; 
                                       Change to x.y for release but not -rc releases -->
 <!ENTITY generic-version "development"> <!-- Use "development"  or "x.y[-pre{x}]" -->
 
-<!ENTITY versiond        "20161023-systemd">
+<!ENTITY versiond        "20161027-systemd">
 <!ENTITY short-versiond  "systemd">
 <!ENTITY generic-versiond "systemd"> 
 
-<!ENTITY releasedate     "October 23, 2016">
+<!ENTITY releasedate     "October 27, 2016">
 <!ENTITY copyrightdate   "1999-2016"><!-- jhalfs needs a literal dash, not &ndash; -->
 <!ENTITY milestone       "7.11">