Changeset 0a75d62


Ignore:
Timestamp:
02/05/2022 01:54:13 AM (8 months ago)
Author:
Douglas R. Reno <renodr@…>
Branches:
11.1, 11.1-rc1, 11.2, 11.2-rc1, arm, multilib, s6-init, trunk, xry111/arm64, xry111/clfs-ng, xry111/lfs-next, xry111/queue-11.3
Children:
21dd2f0, 3e09569
Parents:
1f8c0b9
Message:

Minor tweaks to systemd

Files:
3 edited

Legend:

Unmodified
Added
Removed
  • chapter07/createfiles.xml

    r1f8c0b9 r0a75d62  
    7575daemon:x:6:6:Daemon User:/dev/null:/usr/bin/false
    7676messagebus:x:18:18:D-Bus Message Daemon User:/run/dbus:/usr/bin/false
    77 systemd-bus-proxy:x:72:72:systemd Bus Proxy:/:/usr/bin/false
    7877systemd-journal-gateway:x:73:73:systemd Journal Gateway:/:/usr/bin/false
    7978systemd-journal-remote:x:74:74:systemd Journal Remote:/:/usr/bin/false
  • chapter08/systemd.xml

    r1f8c0b9 r0a75d62  
    132132          <filename>/etc/group</filename> and
    133133          <filename>/etc/passwd</filename> files. Both files
    134           were created earlier in this chapter.</para>
     134          were created earlier in this chapter. This daemon is not useful
     135          on an LFS system since user accounts are manually created.</para>
    135136        </listitem>
    136137      </varlistentry>
  • chapter09/networkd.xml

    r1f8c0b9 r0a75d62  
    185185      (ex: a <command>resolvconf</command> program other than the one
    186186      provided by systemd), the <command>systemd-resolved</command> service
    187       should not be used.</para></note>
     187      should not be used.</para>
     188
     189      <para>To disable systemd-resolved, issue the following command:</para>
     190
     191<screen role="nodump"><userinput>systemctl disable systemd-resolved</userinput></screen></note>
    188192
    189193      <para>When using <command>systemd-resolved</command> for DNS
    190194      configuration, it creates the file
    191       <filename>/run/systemd/resolve/resolv.conf</filename>. Create a
     195      <filename>/run/systemd/resolve/resolv.conf</filename>.</para>
     196      <!--Create a
    192197      symlink in <filename>/etc</filename> to use the generated file:</para>
    193198
    194199<screen><userinput>ln -sfv /run/systemd/resolve/resolv.conf /etc/resolv.conf</userinput></screen>
    195 
     200      At least in systemd-250, this file gets created on first bootup.
     201      -->
    196202    </sect3>
    197203
Note: See TracChangeset for help on using the changeset viewer.