| Newsgroups |
gmane.linux.lfs.book |
| Message-ID |
<[email protected]> |
This is an automated email from the git hooks/post-receive script.
git pushed a commit to branch xry111/clfs-ng
in repository lfs.
commit e9525058ef4248e4fa6b12a9d596b7e7a835b669
Author: Xi Ruoyao <[email protected]>
AuthorDate: Wed Sep 3 21:59:57 2025 +0800
cross-ng: Remove/adapt various reference to "host kernel"/"host distro" in chapter 8 or later
---
chapter08/coreutils.xml | 8 ++++----
chapter08/glibc.xml | 10 +++++-----
chapter08/openssl.xml | 2 +-
chapter08/procps.xml | 2 +-
chapter08/tar.xml | 2 +-
chapter08/util-linux.xml | 11 ++++++-----
chapter09/network.xml | 3 ++-
chapter10/kernel.xml | 4 ++--
8 files changed, 22 insertions(+), 20 deletions(-)
diff --git a/chapter08/coreutils.xml b/chapter08/coreutils.xml
index 0e7957f35..274bf50af 100644
--- a/chapter08/coreutils.xml
+++ b/chapter08/coreutils.xml
@@ -144,15 +144,15 @@ FORCE_UNSAFE_CONFIGURE=1 ./configure \
so the test failures are not reproducible in jhalfs even if
running the build in a PTY. Don't use jhalfs to test if we can
remove < /dev/null. -->
- <para>Now run the tests (using <filename>/dev/null</filename> for the
+ <para>Now run the tests<!-- (using <filename>/dev/null</filename> for the
standard input, or two tests may be broken if building LFS in a
graphical terminal or a session in SSH or GNU Screen because the
standard input is connected to a PTY from host distro, and the device
node for such a PTY cannot be accessed from the LFS chroot
- environment):</para>
+ environment)-->:</para>
-<screen><userinput remap="test">su tester -c "PATH=$PATH make -k RUN_EXPENSIVE_TESTS=yes check" \
- < /dev/null</userinput></screen>
+<screen><userinput remap="test">su tester -c "PATH=$PATH make -k RUN_EXPENSIVE_TESTS=yes check"<!-- \
+ < /dev/null--></userinput></screen>
<para>Remove the temporary group:</para>
diff --git a/chapter08/glibc.xml b/chapter08/glibc.xml
index 4cdbe4955..adea7d370 100644
--- a/chapter08/glibc.xml
+++ b/chapter08/glibc.xml
@@ -145,8 +145,8 @@ cd build</userinput></screen>
<screen><userinput remap="test">make check</userinput></screen>
- <para>You may see some test failures. The Glibc test suite is
- somewhat dependent on the host system. A few failures out of
+ <para>You may see some test failures. <!--The Glibc test suite is
+ somewhat dependent on the host system.--> A few failures out of
over 6000 tests can generally be ignored. This is a list of the
most common issues seen for recent versions of LFS:</para>
@@ -155,7 +155,7 @@ cd build</userinput></screen>
<listitem>
<para><emphasis>misc/tst-preadvwritev2</emphasis> and
<emphasis>misc/tst-preadvwritev64v2</emphasis> are known to fail
- if the host kernel is Linux-6.14 or later.</para>
+ <!--if the host kernel is Linux-6.14 or later-->.</para>
</listitem>
<listitem>
@@ -181,9 +181,9 @@ cd build</userinput></screen>
<listitem>
<para>Additionally, some tests may fail with a relatively old CPU
model (for example
- <emphasis>elf/tst-cpu-features-cpuinfo</emphasis>) or host kernel
+ <emphasis>elf/tst-cpu-features-cpuinfo</emphasis>)<!-- or host kernel
version (for example
- <emphasis>stdlib/tst-arc4random-thread</emphasis>).</para>
+ <emphasis>stdlib/tst-arc4random-thread</emphasis>)-->.</para>
</listitem>
</itemizedlist>
diff --git a/chapter08/openssl.xml b/chapter08/openssl.xml
index 446dd226a..ed4befa01 100644
--- a/chapter08/openssl.xml
+++ b/chapter08/openssl.xml
@@ -65,7 +65,7 @@
<screen><userinput remap="test">HARNESS_JOBS=<replaceable>$(nproc)</replaceable> make test</userinput></screen>
- <para>One test, 30-test_afalg.t, is known to fail if the host kernel
+ <para>One test, 30-test_afalg.t, is known to fail if the temporary kernel
does not have <option>CONFIG_CRYPTO_USER_API_SKCIPHER</option> enabled,
or does not have any options providing an AES with CBC implementation
(for example, the combination of <option>CONFIG_CRYPTO_AES</option>
diff --git a/chapter08/procps.xml b/chapter08/procps.xml
index eb7d277dc..b36347b75 100644
--- a/chapter08/procps.xml
+++ b/chapter08/procps.xml
@@ -90,7 +90,7 @@ su tester -c "PATH=$PATH make check"</userinput></screen>
<para>One test named
<literal>ps with output flag bsdtime,cputime,etime,etimes</literal>
- is known to fail if the host kernel is not built with
+ is known to fail if the temporary kernel is not built with
<literal>CONFIG_BSD_PROCESS_ACCT</literal> enabled. In
addition, one pgrep test may fail in the chroot environment.</para>
diff --git a/chapter08/tar.xml b/chapter08/tar.xml
index 1d51203ba..182f99453 100644
--- a/chapter08/tar.xml
+++ b/chapter08/tar.xml
@@ -73,7 +73,7 @@
<screen><userinput remap="test">make check</userinput></screen>
<para>One test, capabilities: binary store/restore, is known to fail if it is
- run because LFS lacks selinux, but will be skipped if the host kernel does
+ run because LFS lacks selinux, but will be skipped if the temporary kernel does
not support extended attributes or security labels on the filesystem
used for building LFS.</para>
diff --git a/chapter08/util-linux.xml b/chapter08/util-linux.xml
index 3c5feb221..1851df1ee 100644
--- a/chapter08/util-linux.xml
+++ b/chapter08/util-linux.xml
@@ -97,9 +97,10 @@
Two tests need a /etc/fstab file. They are skipped if the host
distro isn't using systemd as the init system, so don't remove
the creation of /etc/fstab unless you've tested it with such a
- host distro (for example LFS systemd or Debian). -->
- <para>If desired, create a dummy <filename>/etc/fstab</filename> file
- to satisfy two tests and run the test suite as a non-&root;
+ host distro (for example LFS systemd or Debian).
+ It shouldn't affect CLFS??? -->
+ <para>If desired, <!--create a dummy <filename>/etc/fstab</filename> file
+ to satisfy two tests and -->run the test suite as a non-&root;
user:</para>
<warning><para>Running the test suite as the
@@ -113,8 +114,8 @@
<screen role="nodump"><userinput>bash tests/run.sh --srcdir=$PWD --builddir=$PWD</userinput></screen>
</warning>
-<screen><userinput remap="test">touch /etc/fstab
-chown -R tester .
+<screen><userinput remap="test"><!--touch /etc/fstab
+-->chown -R tester .
su tester -c "make -k check"</userinput></screen>
<para>
diff --git a/chapter09/network.xml b/chapter09/network.xml
index 4c6caafc5..f270c54f7 100644
--- a/chapter09/network.xml
+++ b/chapter09/network.xml
@@ -34,7 +34,7 @@
name is, you can always run <command>ip link</command> or <command>ls
/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-udev"/>) will
@@ -42,6 +42,7 @@
in the LFS system cannot always be determined by running
those commands on the host distro,
<emphasis>even in the chroot environment</emphasis>.</para>
+-->
</note>
<para>The following command creates a sample file for the
diff --git a/chapter10/kernel.xml b/chapter10/kernel.xml
index 411f0b983..de5a6c5f8 100644
--- a/chapter10/kernel.xml
+++ b/chapter10/kernel.xml
@@ -175,8 +175,8 @@
<para>If your host hardware is using UEFI and you wish to boot the
LFS system with it, you should adjust some kernel configuration
following <ulink url="&blfs-book;postlfs/grub-setup.html#uefi-kernel">
- the BLFS page</ulink> <emphasis role='bold'>even if you'll use the
- UEFI bootloader from the host distro</emphasis>.</para>
+ the BLFS page</ulink><!--emphasis role='bold'>even if you'll use the
+ UEFI bootloade</emphasis-->.</para>
</note>
<variablelist>
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
--
http://lists.linuxfromscratch.org/sympa/info/lfs-book
Unsubscribe: See the above information page