Changeset 4b59d59
- Timestamp:
- 07/02/2005 06:29:36 PM (19 years ago)
- 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:
- 3ca3978
- Parents:
- 4122675
- Files:
-
- 4 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter01/changelog.xml
r4122675 r4b59d59 96 96 97 97 <listitem><para>July 2nd, 2005 [archaic]: Several minor wording changes in 98 chapters 8 and 9 (matt). Also removed the paragraph about compressing kernel 99 modules as it is hint material at best.</para></listitem> 100 101 <listitem><para>July 2nd, 2005 [archaic]: Several minor wording changes in 98 102 chapter 8 (matt).</para></listitem> 99 103 -
chapter08/fstab.xml
r4122675 r4b59d59 10 10 <indexterm zone="ch-bootable-fstab"><primary sortas="e-/etc/fstab">/etc/fstab</primary></indexterm> 11 11 12 <para>The <filename>/etc/fstab</filename> file is used by some 13 programs to determine where file systems are to be mounted by default, 14 which must be checked , and in which order. Create a new file systems15 table like this:</para>12 <para>The <filename>/etc/fstab</filename> file is used by some programs to 13 determine where file systems are to be mounted by default, in which order, and 14 which must be checked (for integrity errors) prior to mounting. Create a new 15 file systems table like this:</para> 16 16 17 17 <screen><userinput>cat > /etc/fstab << "EOF" -
chapter08/kernel.xml
r4122675 r4b59d59 11 11 12 12 <sect2 role="package"><title/> 13 <para>The Linux package contains the kernel and the header files.</para>13 <para>The Linux package contains the Linux kernel.</para> 14 14 15 15 <segmentedlist> … … 30 30 <title>Installation of the kernel</title> 31 31 32 <para>Building the kernel involves a few steps—configuration, 33 compilation, and installation. Read the <filename>README</filename> 34 file in the kernel source tree for alternate methods to the way this 35 book configures the kernel.</para> 32 <para>Building the kernel involves a few steps—configuration, compilation, 33 and installation. Read the <filename>README</filename> file in the kernel source 34 tree for alternative methods to the way this book configures the kernel.</para> 36 35 37 36 <para>Prepare for compilation by running the following command:</para> … … 90 89 <screen><userinput>make</userinput></screen> 91 90 92 <para>If using kernel modules, an 93 <filename>/etc/modprobe.conf</filename> file may be needed. 94 Information pertaining to modules and kernel configuration is 91 <para>If using kernel modules, an <filename>/etc/modprobe.conf</filename> file 92 may be needed. Information pertaining to modules and kernel configuration is 95 93 located in the kernel documentation in the <filename 96 class="directory">linux-&linux-version;/Documentation</filename> 97 directory. The <emphasis>modprobe.conf</emphasis> man page may also be 98 of interest.</para> 99 100 <para>Be very careful when reading other documentation because it 101 usually applies to 2.4.x kernels only. As far as we know, kernel 102 configuration issues specific to Hotplug and Udev are not documented. 103 The problem is that Udev will create a device node only if Hotplug or 104 a user-written script inserts the corresponding module into the 105 kernel, and not all modules are detectable by Hotplug. Note that 106 statements like the one below in the 107 <filename>/etc/modprobe.conf</filename> file do not work with 94 class="directory">linux-&linux-version;/Documentation</filename> directory. The 95 <emphasis>modprobe.conf</emphasis> <command>man</command> page may also be of 96 interest.</para> 97 98 <para>Be very careful when reading other documentation relating to kernel 99 modules because it usually applies to 2.4.x kernels only. As far as we know, 100 kernel configuration issues specific to Hotplug and Udev are not documented. 101 The problem is that Udev will create a device node only if Hotplug or a 102 user-written script inserts the corresponding module into the kernel, and not 103 all modules are detectable by Hotplug. Note that statements like the one below 104 in the <filename>/etc/modprobe.conf</filename> file do not work with 108 105 Udev:</para> 109 106 … … 117 114 118 115 <screen><userinput>make modules_install</userinput></screen> 119 120 <para>If there are many modules and very little space, consider121 stripping and compressing the modules. For most users, such122 compression is not worth the time, but if the system is pressed for123 space, see <ulink124 url="http://www.linux-mips.org/archives/linux-mips/2002-04/msg00031.html"/>.</para>125 116 126 117 <para>After kernel compilation is complete, additional steps are -
chapter09/reboot.xml
r4122675 r4b59d59 55 55 56 56 <para>When the reboot is complete, the LFS system is ready for use and 57 software can be added.</para>57 more software may be added to suit your needs.</para> 58 58 59 59 </sect1>
Note:
See TracChangeset
for help on using the changeset viewer.