gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-03-09 15:39:51 +00:00
Code Issues Packages Projects Releases Wiki Activity

Several minor wording changes in chapters 8 and 9 (matt). Also removed the paragraph about compressing kernel modules. (merged from trunk r6340)

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/branches/6.1/BOOK@6342 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Archaic 2005-07-02 18:40:47 +00:00
parent 82fd24a40e
commit 68b786c273
4 changed files with 25 additions and 30 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
chapter01/changelog.xml
View File

@ -87,6 +87,10 @@ First a summary, then a detailed log.</para>
</itemizedlist>
</listitem>
<listitem><para>July 2nd, 2005 [archaic]: Several minor wording changes in
chapters 8 and 9 (matt). Also removed the paragraph about compressing kernel
modules as it is hint material at best.</para></listitem>
<listitem><para>July 2nd, 2005 [archaic]: Several minor wording changes in
chapter 8 (matt).</para></listitem>

8
chapter08/fstab.xml
View File

@ -9,10 +9,10 @@
<indexterm zone="ch-bootable-fstab"><primary sortas="e-/etc/fstab">/etc/fstab</primary></indexterm>
<para>The <filename>/etc/fstab</filename> file is used by some
programs to determine where file systems are to be mounted by default,
which must be checked, and in which order. Create a new file systems
table like this:</para>
<para>The <filename>/etc/fstab</filename> file is used by some programs to
determine where file systems are to be mounted by default, in which order, and
which must be checked (for integrity errors) prior to mounting. Create a new
file systems table like this:</para>
<screen><userinput>cat &gt; /etc/fstab &lt;&lt; "EOF"
<literal># Begin /etc/fstab

41
chapter08/kernel.xml
View File

@ -10,7 +10,7 @@
<indexterm zone="ch-bootable-kernel"><primary sortas="a-Linux">Linux</primary></indexterm>
<sect2 role="package"><title/>
<para>The Linux package contains the kernel and the header files.</para>
<para>The Linux package contains the Linux kernel.</para>
<segmentedlist>
<segtitle>&buildtime;</segtitle>
@ -29,10 +29,9 @@ GCC, Glibc, Grep, Gzip, Make, Modutils, Perl, and Sed</seg></seglistitem>
<sect2 role="installation">
<title>Installation of the kernel</title>
<para>Building the kernel involves a few steps&mdash;configuration,
compilation, and installation. Read the <filename>README</filename>
file in the kernel source tree for alternate methods to the way this
book configures the kernel.</para>
<para>Building the kernel involves a few steps&mdash;configuration, compilation,
and installation. Read the <filename>README</filename> file in the kernel source
tree for alternative methods to the way this book configures the kernel.</para>
<para>Prepare for compilation by running the following command:</para>
@ -91,22 +90,20 @@ with gcc 2.95.x.</para></note>
<screen><userinput>make</userinput></screen>
<para>If using kernel modules, an
<filename>/etc/modprobe.conf</filename> file may be needed.
Information pertaining to modules and kernel configuration is
<para>If using kernel modules, an <filename>/etc/modprobe.conf</filename> file
may be needed. Information pertaining to modules and kernel configuration is
located in the kernel documentation in the <filename
class="directory">linux-&linux-version;/Documentation</filename>
directory. The <emphasis>modprobe.conf</emphasis> man page may also be
of interest.</para>
class="directory">linux-&linux-version;/Documentation</filename> directory. The
<emphasis>modprobe.conf</emphasis> <command>man</command> page may also be of
interest.</para>
<para>Be very careful when reading other documentation because it
usually applies to 2.4.x kernels only. As far as we know, kernel
configuration issues specific to Hotplug and Udev are not documented.
The problem is that Udev will create a device node only if Hotplug or
a user-written script inserts the corresponding module into the
kernel, and not all modules are detectable by Hotplug. Note that
statements like the one below in the
<filename>/etc/modprobe.conf</filename> file do not work with
<para>Be very careful when reading other documentation relating to kernel
modules because it usually applies to 2.4.x kernels only. As far as we know,
kernel configuration issues specific to Hotplug and Udev are not documented.
The problem is that Udev will create a device node only if Hotplug or a
user-written script inserts the corresponding module into the kernel, and not
all modules are detectable by Hotplug. Note that statements like the one below
in the <filename>/etc/modprobe.conf</filename> file do not work with
Udev:</para>
<para><screen>alias char-major-XXX some-module</screen></para>
@ -119,12 +116,6 @@ configuration, especially if this is the first time using Udev.</para>
<screen><userinput>make modules_install</userinput></screen>
<para>If there are many modules and very little space, consider
stripping and compressing the modules. For most users, such
compression is not worth the time, but if the system is pressed for
space, see <ulink
url="http://www.linux-mips.org/archives/linux-mips/2002-04/msg00031.html"/>.</para>
<para>After kernel compilation is complete, additional steps are
required to complete the installation. Some files need to be copied to
the <filename class="directory">/boot</filename> directory.</para>

2
chapter09/reboot.xml
View File

@ -54,7 +54,7 @@ umount $LFS</userinput></screen>
is set to boot <emphasis>LFS &version;</emphasis> automatically.</para>
<para>When the reboot is complete, the LFS system is ready for use and
software can be added.</para>
more software may be added to suit your needs.</para>
</sect1>