Minor tweaks to systemd

chapter07/createfiles.xml

@@ -74,7 +74,6 @@ EOF</userinput></screen>
 bin:x:1:1:bin:/dev/null:/usr/bin/false
 daemon:x:6:6:Daemon User:/dev/null:/usr/bin/false
 messagebus:x:18:18:D-Bus Message Daemon User:/run/dbus:/usr/bin/false
-systemd-bus-proxy:x:72:72:systemd Bus Proxy:/:/usr/bin/false
 systemd-journal-gateway:x:73:73:systemd Journal Gateway:/:/usr/bin/false
 systemd-journal-remote:x:74:74:systemd Journal Remote:/:/usr/bin/false
 systemd-journal-upload:x:75:75:systemd Journal Upload:/:/usr/bin/false

chapter08/systemd.xml

@@ -131,7 +131,8 @@ meson --prefix=/usr                 \
           services responsible for setting up the
           <filename>/etc/group</filename> and
           <filename>/etc/passwd</filename> files. Both files
-          were created earlier in this chapter.</para>
+          were created earlier in this chapter. This daemon is not useful
+          on an LFS system since user accounts are manually created.</para>
         </listitem>
       </varlistentry>
 

chapter09/networkd.xml

@@ -184,15 +184,21 @@ EOF</userinput></screen>
       or any other software that generates an <filename>/etc/resolv.conf</filename>
       (ex: a <command>resolvconf</command> program other than the one
       provided by systemd), the <command>systemd-resolved</command> service
-      should not be used.</para></note>
+      should not be used.</para>
+
+      <para>To disable systemd-resolved, issue the following command:</para>
+
+<screen role="nodump"><userinput>systemctl disable systemd-resolved</userinput></screen></note>
 
       <para>When using <command>systemd-resolved</command> for DNS
       configuration, it creates the file
-      <filename>/run/systemd/resolve/resolv.conf</filename>. Create a
+      <filename>/run/systemd/resolve/resolv.conf</filename>.</para>
+      <!--Create a
       symlink in <filename>/etc</filename> to use the generated file:</para>
 
 <screen><userinput>ln -sfv /run/systemd/resolve/resolv.conf /etc/resolv.conf</userinput></screen>
-
+      At least in systemd-250, this file gets created on first bootup.
+      -->
     </sect3>
 
     <sect3 id="resolv-conf-static">