Changeset 138bdf6 for networking/connect/dhcpcd.xml

Timestamp:

06/09/2016 05:34:10 AM (8 years ago)

Author:

DJ Lucas <dj@…>

Branches:

10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 7.10, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal

Children:

2bbb3379

Parents:

0098ace6

Message:

[Systemd merge] - Chapter 14

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@17469 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:

• networking/connect/dhcpcd.xml (modified) (1 diff)

networking/connect/dhcpcd.xml

@@ -240 +240 @@
 nameserver 208.67.220.220</literal>
 EOF</userinput></screen>
+
+    </sect3>
+
+   <sect3 id="dhcpcd-init3" revision="systemd">
+      <title>General Configuration Information</title>
+
+      <para>
+        If you want to configure network interfaces at boot using
+        <command>dhcpcd</command>, you need to install the
+        systemd unit included in <xref linkend="systemd-units"/>
+        package by running the following command as the
+        <systemitem class="username">root</systemitem> user:
+      </para>
+
+<screen role="root"><userinput>make install-dhcpcd</userinput></screen>
+
+      <indexterm zone="dhcpcd dhcpcd-init3">
+        <primary sortas="f-dhcpcd">dhcpcd</primary>
+      </indexterm>
+
+      <para>
+        Whenever <command>dhcpcd</command> configures or shuts down
+        a network interface, it executes hook scripts. For more details
+        about those scripts, see the <command>dhcpcd-run-hooks</command> and
+        <command>dhcpcd</command> man pages.
+      </para>
+
+      <note>
+        <para id="dhcpcd-config5">The default behavior of
+        <command>dhcpcd</command> sets the hostname and mtu settings. It also
+        overwrites <filename>/etc/resolv.conf</filename> and
+        <filename>/etc/ntp.conf</filename>.
+
+        These modifications to system files and settings on system
+        configuration files are done by hooks which are stored in <filename
+        class="directory">/lib/dhcpcd/dhcpcd-hooks</filename>.
+
+        Setup <command>dhcpcd</command> by removing or adding hooks from/to
+        that directory.  The execution of hooks can be disabled by using the
+        <option>--nohook</option> (<option>-C</option>) command line option or
+        by the <option>nohook</option> option in the
+        <filename>/etc/dhcpcd.conf</filename> file.</para>
+      </note>
+
+      <indexterm zone="dhcpcd dhcpcd-config5">
+        <primary sortas="e-etc-resolv.conf">/etc/resolv.conf</primary>
+      </indexterm>
+
+    <note>
+      <para>
+        Make sure that you disable the <command>systemd-networkd</command>
+        service or configure it not to manage the interfaces you want to manage
+        with <application>dhcpcd</application>.
+      </para>
+    </note>
+
+      <para>
+        At this point you can test if <command>dhcpcd</command> is
+        behaving as expected by running the following command as the
+        <systemitem class="username">root</systemitem> user:
+      </para>
+
+<screen role="root"><userinput>systemctl start dhcpcd@<replaceable>eth0</replaceable></userinput></screen>
+
+      <para>
+        To start <command>dhcpcd</command> on a specific interface
+        at boot, enable the previously installed systemd unit by
+        running the following command as the
+        <systemitem class="username">root</systemitem> user:
+      </para>
+
+<screen role="root"><userinput>systemctl enable dhcpcd@<replaceable>eth0</replaceable></userinput></screen>
+
+      <para>
+        Replace <replaceable>eth0</replaceable> with the actual interface name.
+      </para>
 
     </sect3>