gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-07-10 14:24:10 +01:00
Code Issues Packages Projects Releases Wiki Activity

Automatic merge of trunk into multilib

Browse Source
This commit is contained in:
Thomas Trepl (Moody) 2022-02-01 05:45:10 +01:00
commit 8f3b8fa415
3 changed files with 31 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
appendices/dependencies.xml
View File

@ -442,7 +442,7 @@
<segtitle>&dependencies;</segtitle> <segtitle>&dependencies;</segtitle>
<seglistitem> <seglistitem>
<seg>Bash, Binutils, Coreutils, GCC, Gettext, Glibc, GMP, Grep, <seg>Bash, Binutils, Coreutils, GCC, Gettext, Glibc, GMP, Grep,
Libcap, Make, Patch, Perl, Sed, and Texinfo</seg> Libcap, Make, OpenSSL, Patch, Perl, Sed, and Texinfo</seg>
</seglistitem> </seglistitem>
</segmentedlist> </segmentedlist>
@ -2305,8 +2305,8 @@
</seglistitem> </seglistitem>
</segmentedlist> </segmentedlist>
<!-- Begin Openssl dependency info --> <!-- Begin OpenSSL dependency info -->
<bridgehead renderas="sect2" id="openssl-dep">Openssl</bridgehead> <bridgehead renderas="sect2" id="openssl-dep">OpenSSL</bridgehead>
<segmentedlist id="openssl-depends"> <segmentedlist id="openssl-depends">
<segtitle>&dependencies;</segtitle> <segtitle>&dependencies;</segtitle>
@ -2332,7 +2332,7 @@
<segmentedlist id="openssl-before"> <segmentedlist id="openssl-before">
<segtitle>&before;</segtitle> <segtitle>&before;</segtitle>
<seglistitem> <seglistitem>
<seg>Linux</seg> <seg>Coreutils and Linux</seg>
</seglistitem> </seglistitem>
</segmentedlist> </segmentedlist>

22
chapter09/network.xml
View File

@ -27,12 +27,22 @@
address(es), subnet masks, and so forth. It is necessary that the stem of address(es), subnet masks, and so forth. It is necessary that the stem of
the filename be <emphasis>ifconfig</emphasis>.</para> the filename be <emphasis>ifconfig</emphasis>.</para>
<note><para>If the procedure in the previous section was not used, udev <note>
will assign network card interface names based on system physical <para>If the procedure in the previous section was not used, udev
characteristics such as enp2s1. If you are not sure what your interface will assign network card interface names based on system physical
name is, you can always run <command>ip link</command> or <command>ls characteristics such as enp2s1. If you are not sure what your interface
/sys/class/net</command> after you have booted your system. name is, you can always run <command>ip link</command> or <command>ls
</para></note> /sys/class/net</command> after you have booted your system.
</para>
<para>The interface names depend on the implementation and
configuration of the udev daemon running on the system. The udev
daemon for LFS (installed in <xref linkend="ch-system-eudev"/>) will
not run until the LFS system is booted. So it's unreliable to
determine the interface names being used in LFS system by running
those commands on the host distro,
<emphasis>even though in the chroot environment</emphasis>.</para>
</note>
<para>The following command creates a sample file for the <para>The following command creates a sample file for the
<emphasis>eth0</emphasis> device with a static IP address:</para> <emphasis>eth0</emphasis> device with a static IP address:</para>

11
chapter09/networkd.xml
View File

@ -53,6 +53,17 @@
<command>ip link</command> after you have booted your system. <command>ip link</command> after you have booted your system.
</para> </para>
<note>
<para>The interface names depend on the implementation and
configuration of the udev daemon running on the system. The udev
daemon for LFS (<command>systemd-udevd</command>, installed in
<xref linkend="ch-system-systemd"/>) will not run unless the LFS
system is booted. So it's unreliable to determine the interface
names being used in LFS system by running those commands on the host
distro,
<emphasis>even though in the chroot environment</emphasis>.</para>
</note>
<para> <para>
For most systems, there is only one network interface for For most systems, there is only one network interface for
each type of connection. For example, the classic interface each type of connection. For example, the classic interface