From 0a75d626580d57ee3bf31bba07769886c015e9f7 Mon Sep 17 00:00:00 2001
From: "Douglas R. Reno" <renodr@linuxfromscratch.org>
Date: Fri, 4 Feb 2022 19:54:13 -0600
Subject: Minor tweaks to systemd

---
 chapter09/networkd.xml | 12 +++++++++---
 1 file changed, 9 insertions(+), 3 deletions(-)

(limited to 'chapter09/networkd.xml')

diff --git a/chapter09/networkd.xml b/chapter09/networkd.xml
index 82a0740ad..42c7dc730 100644
--- a/chapter09/networkd.xml
+++ b/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">
-- 
cgit v1.2.3-54-g00ecf