Ignore:
Timestamp:
03/12/2021 06:40:05 AM (3 years ago)
Author:
Xi Ruoyao <xry111@…>
Branches:
11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 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, ml-11.0, 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:
0d0e874
Parents:
1f28ed12
Message:

systemd: network configuration: network-manager is now compatible with systemd-resolved

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

File:
1 edited

Legend:

Unmodified
Added
Removed
  • chapter09/networkd.xml

    r1f28ed12 rc53ff08  
    168168      <title>systemd-resolved Configuration</title>
    169169
    170       <note><para>If using another means to configure your network
    171       interfaces (ex: ppp, network-manager, etc.), or if using any type of
    172       local resolver (ex: bind, dnsmasq, unbound, etc.), or any other software
    173       that generates an <filename>/etc/resolv.conf</filename> (ex: resolvconf),
    174       the <command>systemd-resolved</command> service should not be
    175       used.</para></note>
     170      <note><para>If using methods incompatible with systemd-resolved to
     171      configure your network interfaces (ex: ppp, etc.), or if using any
     172      type of local resolver (ex: bind, dnsmasq, unbound, etc.),
     173      or any other software that generates an <filename>/etc/resolv.conf</filename>
     174      (ex: a <command>resolvconf</command> program other than the one
     175      provided by systemd), the <command>systemd-resolved</command> service
     176      should not be used.</para></note>
    176177
    177178      <para>When using <command>systemd-resolved</command> for DNS
Note: See TracChangeset for help on using the changeset viewer.