From 33b3a04e4e7c13112517e266a9367101f6823dab Mon Sep 17 00:00:00 2001
From: "Douglas R. Reno" <renodr@linuxfromscratch.org>
Date: Thu, 19 Dec 2024 15:05:20 -0600
Subject: [PATCH] Revert "systemd: Update the test suite failures list for
 257."

This reverts commit 8f493a63774a200a9be7f1543f85b4fa155ed26f.

When I was building LFS, I somehow forgot to mount /dev/sdb7 to
/mnt/lfs on my system. I ended up chrooting into /mnt/lfs, and it was a
directory, not a filesystem.

This happens from time to time, not sure why I did it this time!

The tests that I had marked as failed no longer fail, but at the same
time, now test-namespace does. Let's undo this commit...
---
 chapter08/systemd.xml | 11 +++--------
 1 file changed, 3 insertions(+), 8 deletions(-)

diff --git a/chapter08/systemd.xml b/chapter08/systemd.xml
index acd90aef9..1e17c60ce 100644
--- a/chapter08/systemd.xml
+++ b/chapter08/systemd.xml
@@ -225,14 +225,9 @@ meson setup ..                \
 ninja test</userinput></screen>
 
     <!-- test-namespace needs /run/systemd/inaccessible/sock, which only exists
-         after initializing the system with systemd.
-         This seems to pass now in chroot -->
-    <!-- test-fd-util, test-mount-util, and test-mountpoint-util seem to fail
-         due to being unable to remount the root directory as MS_SLAVE. -->
-    <para>Three tests named <literal>systemd:test / test-fd-util</literal>,
-    <literal>systemd:test / test-mount-util</literal>, and
-    <literal>systemd:test / test-mountpoint-util</literal>,
-    are known to fail in the LFS chroot environment. Some other tests may
+         after initializing the system with systemd.  -->
+    <para>One test named <literal>systemd:core / test-namespace</literal>
+    is known to fail in the LFS chroot environment.  Some other tests may
     fail because they depend on various kernel configuration options.</para>
 
     <para>Install the package:</para>