Changeset 1966b8d


Ignore:
Timestamp:
01/31/2022 11:42:18 AM (8 months ago)
Author:
Xi Ruoyao <xry111@…>
Branches:
11.1, 11.1-rc1, 11.2, 11.2-rc1, arm, multilib, s6-init, trunk, xry111/arm64, xry111/clfs-ng, xry111/lfs-next, xry111/queue-11.3
Children:
8f3b8fa4, a5d31dd
Parents:
4d323c3
git-author:
Xi Ruoyao <xry111@…> (01/31/2022 11:41:34 AM)
git-committer:
Xi Ruoyao <xry111@…> (01/31/2022 11:42:18 AM)
Message:

network cfg: mention that LFS and the host may name interfaces differently

Location:
chapter09
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • chapter09/network.xml

    r4d323c3 r1966b8d  
    2828    the filename be <emphasis>ifconfig</emphasis>.</para>
    2929
    30     <note><para>If the procedure in the previous section was not used, udev
    31     will assign network card interface names based on system physical
    32     characteristics such as enp2s1. If you are not sure what your interface
    33     name is, you can always run <command>ip link</command> or <command>ls
    34     /sys/class/net</command> after you have booted your system.
    35     </para></note>
     30    <note>
     31      <para>If the procedure in the previous section was not used, udev
     32      will assign network card interface names based on system physical
     33      characteristics such as enp2s1. If you are not sure what your interface
     34      name is, you can always run <command>ip link</command> or <command>ls
     35      /sys/class/net</command> after you have booted your system.
     36      </para>
     37
     38      <para>The interface names depend on the implementation and
     39      configuration of the udev daemon running on the system.  The udev
     40      daemon for LFS (installed in <xref linkend="ch-system-eudev"/>) will
     41      not run until the LFS system is booted.  So it's unreliable to
     42      determine the interface names being used in LFS system by running
     43      those commands on the host distro,
     44      <emphasis>even though in the chroot environment</emphasis>.</para>
     45    </note>
    3646
    3747    <para>The following command creates a sample file for the
  • chapter09/networkd.xml

    r4d323c3 r1966b8d  
    5454      </para>
    5555
     56      <note>
     57        <para>The interface names depend on the implementation and
     58        configuration of the udev daemon running on the system.  The udev
     59        daemon for LFS (<command>systemd-udevd</command>, installed in
     60        <xref linkend="ch-system-systemd"/>) will not run unless the LFS
     61        system is booted.  So it's unreliable to determine the interface
     62        names being used in LFS system by running those commands on the host
     63        distro,
     64        <emphasis>even though in the chroot environment</emphasis>.</para>
     65      </note>
     66
    5667      <para>
    5768        For most systems, there is only one network interface for
Note: See TracChangeset for help on using the changeset viewer.