Changeset 0a75d62

Timestamp:

02/05/2022 01:54:13 AM (2 years ago)

Author:

Douglas R. Reno <renodr@…>

Branches:

11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, arm, bdubbs/gcc13, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc

Children:

21dd2f0, 3e09569

Parents:

1f8c0b9

Message:

Minor tweaks to systemd

Files:

• chapter07/createfiles.xml (modified) (1 diff)
• chapter08/systemd.xml (modified) (1 diff)
• chapter09/networkd.xml (modified) (1 diff)

chapter07/createfiles.xml

@@ -75 +75 @@
 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

chapter08/systemd.xml

@@ -132 +132 @@
           <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

@@ -185 +185 @@
       (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>