|
@@ -43,16 +43,26 @@ recommends that this command be issued prior to <emphasis>each</emphasis>
|
|
|
kernel compilation. You shouldn't rely on the source tree being clean after
|
|
|
un-tarring.</para>
|
|
|
|
|
|
-<para>Also, assure that the kernel does not attempt to pass hotplugging events
|
|
|
+<para>Also, ensure that the kernel does not attempt to pass hotplugging events
|
|
|
to userspace until userspace specifies that it is ready:</para>
|
|
|
|
|
|
<screen><userinput>sed -i 's@/sbin/hotplug@/bin/true@' kernel/kmod.c</userinput></screen>
|
|
|
|
|
|
+<para>If, in <xref linkend="ch-scripts-console"/>, you decided you want
|
|
|
+to compile the keymap into the kernel, issue the command below:</para>
|
|
|
+
|
|
|
+<screen><userinput>loadkeys -m
|
|
|
+/usr/share/kbd/keymaps/<replaceable>[path to keymap]</replaceable> > \
|
|
|
+ <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
|
|
|
+<filename>/usr/share/kbd/keymaps/i386/qwerty/nl.map.gz</filename>.</para>
|
|
|
+
|
|
|
<para>Configure the kernel via a menu-driven interface:</para>
|
|
|
|
|
|
<screen><userinput>make menuconfig</userinput></screen>
|
|
|
|
|
|
-<para><command>make oldconfig</command> may be more appropriate in some
|
|
|
+<para><userinput>make oldconfig</userinput> may be more appropriate in some
|
|
|
situations. See the <filename>README</filename> file for more
|
|
|
information.</para>
|
|
|
|
|
@@ -69,8 +79,8 @@ scratch.</para>
|
|
|
the <quote>File systems</quote> menu and is normally enabled by default.</para>
|
|
|
|
|
|
<para>LFS bootscripts make the assumption that you either compile
|
|
|
-both <quote>Support for Host-side USB</quote> and
|
|
|
-<quote>USB device filesystem</quote> directly into the kernel, or don't compile them at
|
|
|
+both "Support for Host-side USB" and
|
|
|
+"USB device filesystem" directly into the kernel, or don't compile them at
|
|
|
all. Bootscripts will not work properly if it is a module (usbcore.ko).</para>
|
|
|
|
|
|
<note><para>NPTL requires the kernel to be compiled with GCC 3.x, in this case
|
|
@@ -120,7 +130,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>
|
|
|
|
|
|
<para>Kernel compilation has finished but more steps are required to complete
|
|
|
-the installation. Some files need to be copied to the <filename class="directory">/boot</filename>
|
|
|
+the installation. Some files need to be copied to the <filename>/boot</filename>
|
|
|
directory.</para>
|
|
|
|
|
|
<para>The path to the kernel image may vary depending on the platform you're
|
|
@@ -154,7 +164,7 @@ 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
|
|
|
run <userinput>chown -R 0:0</userinput> on the
|
|
|
-<filename class="directory">linux-&linux-version;</filename> directory to ensure all files are
|
|
|
+<filename>linux-&linux-version;</filename> directory to ensure all files are
|
|
|
owned by user <emphasis>root</emphasis>.</para>
|
|
|
|
|
|
</sect2>
|
|
@@ -189,7 +199,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>
|
|
|
<para>define the interface to the
|
|
|
services that the kernel provides. The headers in your system's
|
|
|
-<filename class="directory">include</filename> directory should <emphasis>always</emphasis> be
|
|
|
+<filename>include</filename> directory should <emphasis>always</emphasis> be
|
|
|
the ones against which Glibc was compiled and should therefore
|
|
|
<emphasis>not</emphasis> be replaced when upgrading the kernel.</para>
|
|
|
</listitem>
|