Ignore:
Timestamp:
10/27/2016 11:22:45 PM (8 years ago)
Author:
DJ Lucas <dj@…>
Branches:
10.0, 10.0-rc1, 10.1, 10.1-rc1, 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, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, 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:
5fcd09b
Parents:
201167db
Message:

Moved /etc/resolv.conf symlink to Chapter 7.

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

File:
1 edited

Legend:

Unmodified
Added
Removed
  • chapter07/networkd.xml

    r201167db re053117  
    2626    resolution can be handled by <command>systemd-resolved</command> in place
    2727    of a static <filename>/etc/resolv.conf</filename> file. Both services are
    28     enabled by default, and absolutely should not be disabled.</para>
     28    enabled by default.</para>
    2929
    3030    <para>Configuration files for <command>systemd-networkd</command> (and
     
    120120
    121121      <para>When using <command>systemd-resolved</command> for DNS
    122       configuration, it is responsible for creating the
    123       <filename>/etc/resolv.conf</filename> file. Since version 226, the
    124       symlink for <filename>/etc/resolv.conf</filename> is created by systemd
    125       when needed, so no further configuration is necessary.</para>
     122      configuration, it creates the file
     123      <filename>/run/systemd/resolve/resolv.conf</filename>. Create a
     124      symlink in <filename>/etc</filename> to use the generatd file:</para>
     125
     126<screen><userinput remap="install">ln -sfv /run/systemd/resolve/resolv.conf /etc/resolv.conf</userinput></screen>
    126127
    127128    </sect3>
Note: See TracChangeset for help on using the changeset viewer.