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

Fixed the identation of /etc/fstab and some tagins regresions.

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3819 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Manuel Canales Esparcia 2004-06-19 20:41:59 +00:00
parent 89d204ea76
commit 0c012ac2c9
3 changed files with 19 additions and 22 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
chapter07/console.xml
View File

@ -95,7 +95,7 @@ EOF</userinput></screen>
setting it every time from the <command>console</command> bootscript, then setting it every time from the <command>console</command> bootscript, then
instructions are given in <xref linkend="ch-bootable-kernel"/>. Doing this instructions are given in <xref linkend="ch-bootable-kernel"/>. Doing this
ensures that your keyboard will always work as expected, even when you boot into ensures that your keyboard will always work as expected, even when you boot into
maintenance mode (by passing `init=/bin/sh' to the kernel), as in that maintenance mode (by passing <parameter>init=/bin/sh</parameter> to the kernel), as in that
situation, the <command>console</command> bootscript won't be run.</para> situation, the <command>console</command> bootscript won't be run.</para>
<para>Since the kernel will set up the keymap, you can omit the KEYMAP variable <para>Since the kernel will set up the keymap, you can omit the KEYMAP variable

27
chapter08/kernel.xml
View File

@ -51,8 +51,7 @@ to userspace until userspace specifies that it is ready:</para>
<para>If, in <xref linkend="ch-scripts-console"/>, you decided you want <para>If, in <xref linkend="ch-scripts-console"/>, you decided you want
to compile the keymap into the kernel, issue the command below:</para> to compile the keymap into the kernel, issue the command below:</para>
<screen><userinput>loadkeys -m <screen><userinput>loadkeys -m /usr/share/kbd/keymaps/<replaceable>[path to keymap]</replaceable> &gt; \
/usr/share/kbd/keymaps/<replaceable>[path to keymap]</replaceable> &gt; \
<replaceable>[unpacked sources dir]</replaceable>/linux-&linux-version;/drivers/char/defkeymap.c</userinput></screen> <replaceable>[unpacked sources dir]</replaceable>/linux-&linux-version;/drivers/char/defkeymap.c</userinput></screen>
<para>For example, if you have a Dutch keyboard, you would use <para>For example, if you have a Dutch keyboard, you would use
@ -62,7 +61,7 @@ to compile the keymap into the kernel, issue the command below:</para>
<screen><userinput>make menuconfig</userinput></screen> <screen><userinput>make menuconfig</userinput></screen>
<para><userinput>make oldconfig</userinput> may be more appropriate in some <para><command>make oldconfig</command> may be more appropriate in some
situations. See the <filename>README</filename> file for more situations. See the <filename>README</filename> file for more
information.</para> information.</para>
@ -79,9 +78,9 @@ scratch.</para>
the <quote>File systems</quote> menu and is normally enabled by default.</para> the <quote>File systems</quote> menu and is normally enabled by default.</para>
<para>LFS bootscripts make the assumption that you either compile <para>LFS bootscripts make the assumption that you either compile
both "Support for Host-side USB" and both <quote>Support for Host-side USB</quote> and
"USB device filesystem" directly into the kernel, or don't compile them at <quote>USB device filesystem</quote> directly into the kernel, or don't compile them at
all. Bootscripts will not work properly if it is a module (usbcore.ko).</para> all. Bootscripts will not work properly if it is a module (<filename>usbcore.ko</filename>).</para>
<note><para>NPTL requires the kernel to be compiled with GCC 3.x, in this case <note><para>NPTL requires the kernel to be compiled with GCC 3.x, in this case
&gcc-version;. Compiling with 2.95.x is known to cause failures in the glibc &gcc-version;. Compiling with 2.95.x is known to cause failures in the glibc
@ -96,14 +95,12 @@ unless you know what you're getting yourself into.</para></note>
<filename>/etc/modprobe.conf</filename> file. Information pertaining <filename>/etc/modprobe.conf</filename> file. Information pertaining
to modules and to kernel configuration in general may be found in the to modules and to kernel configuration in general may be found in the
kernel documentation, which is found in the kernel documentation, which is found in the
<filename>linux-&linux-version;/Documentation</filename> directory. <filename class="directory">linux-&linux-version;/Documentation</filename> directory.
The The modprobe.conf man page
modprobe.conf man page
<!-- removed for review from tldp.org <!-- removed for review from tldp.org
and the kernel HOWTO at and the kernel HOWTO at
<ulink url="http://www.tldp.org/HOWTO/Kernel-HOWTO.html"/> --> <ulink url="http://www.tldp.org/HOWTO/Kernel-HOWTO.html"/> -->
may also be of may also be of interest to you.</para>
interest to you.</para>
<para>Be very suspicious while reading other documentation, because it <para>Be very suspicious while reading other documentation, because it
usually applies to 2.4.x kernels only. As far as the editors know, kernel usually applies to 2.4.x kernels only. As far as the editors know, kernel
@ -130,7 +127,7 @@ isn't worth the trouble, but if you're really pressed for space, then have a loo
<ulink url="http://www.linux-mips.org/archives/linux-mips/2002-04/msg00031.html"/>.</para> <ulink url="http://www.linux-mips.org/archives/linux-mips/2002-04/msg00031.html"/>.</para>
<para>Kernel compilation has finished but more steps are required to complete <para>Kernel compilation has finished but more steps are required to complete
the installation. Some files need to be copied to the <filename>/boot</filename> the installation. Some files need to be copied to the <filename class="directory">/boot</filename>
directory.</para> directory.</para>
<para>The path to the kernel image may vary depending on the platform you're <para>The path to the kernel image may vary depending on the platform you're
@ -163,8 +160,8 @@ the packager used will be assigned to somebody on your machine and then that
person would have write access to the kernel source.</para> person would have write access to the kernel source.</para>
<para>If you are going to keep the kernel source tree around, you may want to <para>If you are going to keep the kernel source tree around, you may want to
run <userinput>chown -R 0:0</userinput> on the run <command>chown -R 0:0</command> on the
<filename>linux-&linux-version;</filename> directory to ensure all files are <filename class="directory">linux-&linux-version;</filename> directory to ensure all files are
owned by user <emphasis>root</emphasis>.</para> owned by user <emphasis>root</emphasis>.</para>
</sect2> </sect2>
@ -199,7 +196,7 @@ of running scores of programs seemingly at the same time.</para>
<indexterm zone="ch-bootable-kernel kernel-headers"><primary sortas="e-kernel-headers">kernel headers</primary></indexterm> <indexterm zone="ch-bootable-kernel kernel-headers"><primary sortas="e-kernel-headers">kernel headers</primary></indexterm>
<para>define the interface to the <para>define the interface to the
services that the kernel provides. The headers in your system's services that the kernel provides. The headers in your system's
<filename>include</filename> directory should <emphasis>always</emphasis> be <filename class="directory">include</filename> directory should <emphasis>always</emphasis> be
the ones against which Glibc was compiled and should therefore the ones against which Glibc was compiled and should therefore
<emphasis>not</emphasis> be replaced when upgrading the kernel.</para> <emphasis>not</emphasis> be replaced when upgrading the kernel.</para>
</listitem> </listitem>