cvs commit: LFS/BOOK/chapter08 kernel.xml

matthew at linuxfromscratch.org matthew at linuxfromscratch.org
Sat Jun 19 13:11:58 PDT 2004


matthew     04/06/19 14:11:58

  Modified:    BOOK/chapter01 changelog.xml
               BOOK/chapter07 console.xml
               BOOK/chapter08 kernel.xml
  Log:
  Improved wording of keymap related paragraphs (bug 741)
  
  Revision  Changes    Path
  1.826     +4 -0      LFS/BOOK/chapter01/changelog.xml
  
  Index: changelog.xml
  ===================================================================
  RCS file: /home/cvsroot/LFS/BOOK/chapter01/changelog.xml,v
  retrieving revision 1.825
  retrieving revision 1.826
  diff -u -r1.825 -r1.826
  --- changelog.xml	19 Jun 2004 17:38:49 -0000	1.825
  +++ changelog.xml	19 Jun 2004 20:11:58 -0000	1.826
  @@ -76,6 +76,10 @@
   </itemizedlist>
   </listitem>
   
  +<listitem><para>June 19, 2004 [matt]: chapter07 - console & chapter 08 -
  +kernel.  Improved wording and re-introduced the option for compiling the keymap
  +directly into the kernel.</para></listitem>
  +
   <listitem><para>June 19, 2004 [matt]: chapter06 - e2fsprogs, brought
   instructions inline with upstream recommendations.</para></listitem>
   
  
  
  
  1.7       +12 -11    LFS/BOOK/chapter07/console.xml
  
  Index: console.xml
  ===================================================================
  RCS file: /home/cvsroot/LFS/BOOK/chapter07/console.xml,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- console.xml	19 Jun 2004 16:54:58 -0000	1.6
  +++ console.xml	19 Jun 2004 20:11:58 -0000	1.7
  @@ -91,17 +91,18 @@
   KEYMAP_CORRECTION="/etc/kbd/bs-sends-del"
   EOF</userinput></screen>
   
  -<para>If you decided to
  -compile your keymap directly into the kernel later on in <xref
  -linkend="chapter-bootable"/> instead of setting it every time from the
  -<command>console</command> bootscript, then you don't need to run the
  -<command>loadkeys</command> program. Since the kernel will set up the keymap,
  -you can omit the KEYMAP variable from the
  -<filename>/etc/sysconfig/console</filename>
  -configuration file. If you wish,
  -you can still have it, this isn't going to hurt you. Keeping it could even
  -be beneficial, in case you run a lot of different kernels and can't be sure
  -that the keymap is compiled into every one of them.</para>
  +<para>If you want to compile your keymap directly into the kernel instead of
  +setting it every time from the <command>console</command> bootscript, then
  +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
  +maintenance mode (by passing `init=/bin/sh' to the kernel), as in that
  +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
  +from the <filename>/etc/sysconfig/console</filename> configuration file. If you
  +wish, you can still have it, this isn't going to hurt you. Keeping it could even
  +be beneficial, in case you run a lot of different kernels and can't be sure that
  +the keymap is compiled into every one of them.</para>
   
   </sect1>
   
  
  
  
  1.43      +17 -7     LFS/BOOK/chapter08/kernel.xml
  
  Index: kernel.xml
  ===================================================================
  RCS file: /home/cvsroot/LFS/BOOK/chapter08/kernel.xml,v
  retrieving revision 1.42
  retrieving revision 1.43
  diff -u -r1.42 -r1.43
  --- kernel.xml	19 Jun 2004 17:46:53 -0000	1.42
  +++ kernel.xml	19 Jun 2004 20:11:58 -0000	1.43
  @@ -43,16 +43,26 @@
   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 @@
   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 @@
   <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 @@
   
   <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 @@
   <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>
  
  
  



More information about the lfs-book mailing list