Changeset fde4f7d for chapter06

Timestamp:

07/01/2005 08:39:25 PM (19 years ago)

Author:

Archaic <archaic@…>

Branches:

10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc

Children:

d001e2b

Parents:

4d938ef

Message:

Brought all occurences of LFS-Bootscripts into conformity.

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/trunk/BOOK@6288 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

Location:

chapter06

Files:

• devices.xml (modified) (2 diffs)
• hotplug.xml (modified) (2 diffs)
• iproute2.xml (modified) (1 diff)
• psmisc.xml (modified) (1 diff)
• util-linux.xml (modified) (1 diff)

chapter06/devices.xml

@@ -31 +31 @@
 be created dynamically on that virtual filesystem as they are detected or
 accessed. This is generally done during the boot process. Since this new system
-has not been booted, it is necessary to do what the bootscripts would otherwise
-do by mounting <filename class="directory">/dev</filename>:</para>
+has not been booted, it is necessary to do what the LFS-Bootscripts package would
+otherwise do by mounting <filename class="directory">/dev</filename>:</para>
 
 <screen><userinput>mount -n -t tmpfs none /dev</userinput></screen>
@@ -52 +52 @@
 
 <para>There are some symlinks and directories required by LFS that are created
-during system startup by the bootscripts. Since this is a chroot environment and
-not a booted environment, those symlinks and directories need to be created
-here:</para>
+during system startup by the LFS-Bootscripts package. Since this is a chroot
+environment and not a booted environment, those symlinks and directories need to
+be created here:</para>
 
 <screen><userinput>ln -s /proc/self/fd /dev/fd

chapter06/hotplug.xml

@@ -43 +43 @@
 <screen><userinput>cp etc/hotplug/pnp.distmap /etc/hotplug</userinput></screen>
 
-<para>Remove the init script that Hotplug installs, since we're going to be
-using the script included with LFS-Bootscripts:</para>
+<para>Remove the init script that Hotplug installs since we are going to be
+using the script included in the LFS-Bootscripts package:</para>
 
 <screen><userinput>rm -rf /etc/init.d</userinput></screen>
 
-<para>Network device hotplugging is not supported by LFS-Bootscripts yet. For
-that reason, remove the network hotplug agent:</para>
+<para>Network device hotplugging is not yet supported by the LFS-Bootscripts
+package. For that reason, remove the network hotplug agent:</para>
 
 <screen><userinput>rm -f /etc/hotplug/net.agent</userinput></screen>
@@ -92 +92 @@
 <listitem>
 <para>These scripts are used for cold plugging, i.e., detecting and acting upon
-hardware already present during system startup.  They are called by the
-<filename>hotplug</filename> initscript that comes from the LFS-Bootscripts
-package.  The <command>*.rc</command> scripts try to recover hotplug events that
-were lost during system boot because, for example, the root filesystem was not
-mounted by the kernel</para>
+hardware already present during system startup. They are called by the
+<filename>hotplug</filename> initscript included in the LFS-Bootscripts package.
+The <command>*.rc</command> scripts try to recover hotplug events that were lost
+during system boot because, for example, the root filesystem was not mounted by
+the kernel</para>
 <indexterm zone="ch-system-hotplug hotplug-rc"><primary
 sortas="d-/etc/hotplug/*.rc">/etc/hotplug/*.rc</primary></indexterm>

chapter06/iproute2.xml

@@ -57 +57 @@
     <varlistentry>
     <term><parameter>SBINDIR=/sbin</parameter></term>
-    <listitem><para>This makes sure that the IPRoute2 binaries will install into
-      <filename class="directory">/sbin</filename>.  This is the correct
-      location according to the FHS, because some of the IPRoute2 binaries are used
-      in the bootscripts.</para>
+    <listitem><para>This ensures that the IPRoute2 binaries will install into
+      <filename class="directory">/sbin</filename>. This is the correct location
+      according to the FHS, because some of the IPRoute2 binaries are used by
+      the LFS-Bootscripts package.</para>
     </listitem>
     </varlistentry>

chapter06/psmisc.xml

@@ -41 +41 @@
 <varlistentry>
 <term><parameter>--exec-prefix=""</parameter></term>
-<listitem><para>This causes the binaries to be installed in <filename
-class="directory">/bin</filename> instead of <filename
-class="directory">/usr/bin</filename>. Because the Psmisc programs are
-often used in bootscripts, they should be available when the <filename
-class="directory">/usr</filename> file system is not
-mounted.</para></listitem>
+<listitem><para>This ensures that the Psmisc binaries will install into
+<filename class="directory">/bin</filename> instead of <filename
+class="directory">/usr/bin</filename>. This is the correct location according to
+the FHS, because some of the Psmisc binaries are used by the LFS-Bootscripts
+package.</para></listitem>
 </varlistentry>
 </variablelist>

chapter06/util-linux.xml

@@ -83 +83 @@
 
 <para>Install the package and move the <command>logger</command> binary to
-<filename class="directory">/bin</filename> as it is needed by the bootscripts:
-</para>
+<filename class="directory">/bin</filename> as it is needed by the
+LFS-Bootscripts package:</para>
 
 <screen><userinput>make HAVE_KILL=yes HAVE_SLN=yes install