Ignore:
Timestamp:
Apr 20, 2014, 8:57:39 AM (11 years ago)
Author:
Chris Staub <chris@…>
Children:
0be79ea
Parents:
88ef769 (diff), 578ca586 (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the (diff) links above to see all the changes relative to each parent.
Message:

Merge branch 'systemd' into simp

Conflicts:

BOOK/final-system/common/bash.xml
BOOK/final-system/mips64-chapter.xml
BOOK/final-system/multilib/bash.xml
BOOK/final-system/ppc64-chapter.xml
BOOK/final-system/sparc64-chapter.xml
BOOK/final-system/x86_64-chapter.xml
BOOK/general.ent
BOOK/packages.ent
BOOK/temp-system/common/bash.xml
BOOK/temp-system/mips64-64-chapter.xml
BOOK/temp-system/mips64-chapter.xml
BOOK/temp-system/multilib/bash.xml
BOOK/temp-system/ppc64-64-chapter.xml
BOOK/temp-system/ppc64-chapter.xml
BOOK/temp-system/sparc64-64-chapter.xml
BOOK/temp-system/sparc64-chapter.xml
BOOK/temp-system/x86_64-64-chapter.xml
BOOK/temp-system/x86_64-chapter.xml

File:
1 moved

Legend:

Unmodified
Added
Removed

  • BOOK/network/common/sysconfig-network.xml

    r88ef769 r03e6a40  
    1616    <para>Which interfaces are brought up and down by the network script
    1717    depends on the files and directories in the <filename
    18     class="directory">/etc/sysconfig/network-devices</filename> hierarchy.
     18    class="directory">/etc/sysconfig</filename> hierarchy.
    1919    This directory should contain a sub-directory for each interface to be
    2020    configured, such as <filename>ifconfig.xyz</filename>, where
    … …  
    2323    address(es), subnet masks, and so forth.</para>
    2424
     25    <note><para>Udev may assign random Network Card Interface names
     26    for some network cards such as enp2s1. If you are not sure what
     27    your Network Card Interface name is, you can always run
     28    <command>ip l</command> after you have booted your system. Again,
     29    it is important that <filename>ifconfig.xyz</filename> is named
     30    after correct Network Card Interface name (e.g.
     31    <filename>ifconfig.enp2s1</filename> or
     32    <filename>ifconfig.eth0</filename>) or Systemd will fail to bring
     33    up your network interface.</para></note>
     34
    2535    <para>The following command creates a sample <filename>ipv4</filename>
    2636    file for the <emphasis>eth0</emphasis> device:</para>
    2737
    28 <screen><userinput>cd /etc/sysconfig/network-devices &amp;&amp;
    29 mkdir -v ifconfig.eth0 &amp;&amp;
    30 cat &gt; ifconfig.eth0/ipv4 &lt;&lt; "EOF"
    31 <literal>ONBOOT="yes"
     38<screen><userinput>mkdir -pv /etc/sysconfig &amp;&amp;
     39cd /etc/sysconfig &amp;&amp;
     40cat &gt; ifconfig.eth0 &lt;&lt; "EOF"
     41<literal>IFACE="eth0"
    3242SERVICE="ipv4-static"
    3343IP="192.168.1.1"
    … …  
    3747EOF</userinput></screen>
    3848
    39     <para os="var-ob">The values of these variables must be changed in every file to match
    40     the proper setup. If the <envar>ONBOOT</envar> variable is set to
    41     <quote>yes</quote> the network script will bring up the Network Interface
    42     Card (NIC) during booting of the system. If set to anything but
    43     <quote>yes</quote> the NIC will be ignored by the network script and not
    44     be brought up.</para>
     49    <para os="var-ob">The values of these variables must be changed in every
     50    file to match the proper setup.</para>
    4551
    46     <para os="var-s">The <envar>SERVICE</envar> variable defines the method used for
    47     obtaining the IP address. The CLFS-Bootscripts package has a modular IP
    48     assignment format, and creating additional files in the <filename
    49     class="directory">/etc/sysconfig/network-devices/services</filename>
     52    <para os="var-i">The <envar>IFACE</envar> variable defines the interface
     53    name, for example, eth0. It is required for all network device configuration
     54    files.</para>
     55
     56    <para os="var-s">The <envar>SERVICE</envar> variable defines the method used
     57    for obtaining the IP address. The CLFS-Network-Scripts package has a modular
     58    IP assignment format, and creating additional files in the <filename
     59    class="directory">/lib/services</filename>
    5060    directory allows other IP assignment methods.</para>
    5161
    … …  
    6373    <envar>PREFIX</envar> variable according to your specific subnet.</para>
    6474
    65     <para>To configure another DHCP Interface, Follow <xref linkend="ch-network-dhcp"/>.</para>
     75    <para>For more information see the <command>ifup</command> man page.</para>
     76
     77    <para>To configure another DHCP Interface, Follow <xref linkend="ch-network-dhcpcd"/>.</para>
     78
     79  </sect2>
     80
     81  <sect2>
     82    <title>Configuring the Network Interface at boot</title>
     83
     84    <para>Enabling of the Network Interface configuration is
     85    done per interface. To enable Network Interface
     86    configuration at boot, run:</para>
     87
     88<screen role="nodump"><userinput>systemctl enable ifupdown@eth0</userinput></screen>
     89
     90    <para>To disable previously enabled Network Interface
     91    configuration at boot, run:</para>
     92
     93<screen role="nodump"><userinput>systemctl disable ifupdown@eth0</userinput></screen>
     94
     95    <para>To manually start the Network Interface configuration,
     96    run:</para>
     97
     98<screen role="nodump"><userinput>systemctl start ifupdown@eth0</userinput></screen>
     99
     100    <para>Replace eth0 with the correct Network Interface
     101    name as described on the beginning of this page.</para>
    66102
    67103  </sect2>
Note: See TracChangeset for help on using the changeset viewer.