gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-06-19 03:39:20 +01:00
Code Issues Packages Projects Releases Wiki Activity

Fixes to chapter07.

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/branches/systemd/BOOK@10723 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Krejzi 2014-08-22 15:10:02 +00:00
parent db05718c43
commit acbb08fa7d
2 changed files with 20 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
chapter07/clock.xml
View File

@ -82,12 +82,14 @@ EOF</userinput></screen>
<para>The daemon is not intended as a replacement for the well <para>The daemon is not intended as a replacement for the well
established NTP daemon, but as a client only implementation established NTP daemon, but as a client only implementation
of the SNTP protocol which can be used for less advanced of the SNTP protocol which can be used for less advanced
tasks and on a resource limited systems.</para> tasks and on resource limited systems.</para>
<para>To enable the <command>systemd-timesyncd</command> daemon, <para>Starting with systemd version 216, the
issue the following command:</para> <command>systemd-timesyncd</command> daemon is enabled by
default. If you want to disable it, issue the following
command:</para>
<screen role="nodump"><userinput>systemctl enable systemd-timesyncd</userinput></screen> <screen role="nodump"><userinput>systemctl disable systemd-timesyncd</userinput></screen>
<para>The <filename>/etc/systemd/timesyncd.conf</filename> file <para>The <filename>/etc/systemd/timesyncd.conf</filename> file
can be used to change the NTP servers that can be used to change the NTP servers that

24
chapter07/network.xml
View File

@ -101,19 +101,10 @@ EOF</userinput></screen>
from the ISP or network administrator, into from the ISP or network administrator, into
<filename>/etc/resolv.conf</filename>.</para> <filename>/etc/resolv.conf</filename>.</para>
<para>When using <command>systemd-networkd</command> for network
configuration, another daemon, <command>systemd-resolved</command>,
is responsible for creating the <filename>/etc/resolv.conf</filename>
file. It is, however, placed in a non-standard location which is
writable since early boot, so it is necessary to create a symlink
to it by running the following command:</para>
<screen><userinput>ln -sfv /run/systemd/resolve/resolv.conf /etc/resolv.conf</userinput></screen>
<para>If static <filename>/etc/resolv.conf</filename> is desired, create <para>If static <filename>/etc/resolv.conf</filename> is desired, create
it by running the following command:</para> it by running the following command:</para>
<screen><userinput>cat &gt; /etc/resolv.conf &lt;&lt; "EOF" <screen role="nodump"><userinput>cat &gt; /etc/resolv.conf &lt;&lt; "EOF"
<literal># Begin /etc/resolv.conf <literal># Begin /etc/resolv.conf
domain <replaceable>&lt;Your Domain Name&gt;</replaceable> domain <replaceable>&lt;Your Domain Name&gt;</replaceable>
@ -136,6 +127,19 @@ EOF</userinput></screen>
<note><para>The Google Public IPv4 DNS addresses are 8.8.8.8 and 8.8.4.4.</para></note> <note><para>The Google Public IPv4 DNS addresses are 8.8.8.8 and 8.8.4.4.</para></note>
<para>When using <command>systemd-networkd</command> for network
configuration, another daemon, <command>systemd-resolved</command>,
is responsible for creating the <filename>/etc/resolv.conf</filename>
file. It is, however, placed in a non-standard location which is
writable since early boot, so it is necessary to create a symlink
to it by running the following command:</para>
<screen><userinput>ln -sfv /run/systemd/resolve/resolv.conf /etc/resolv.conf</userinput></screen>
<para>This is required if you are specifying DNS entries in <filename
class="extension">.network</filename> files or using the built in
DHCP client to obtain DNS addresses.</para>
</sect2> </sect2>
<sect2 id="ch-scripts-hostname"> <sect2 id="ch-scripts-hostname">