Changeset 89d204ea

Timestamp:

06/19/2004 08:11:58 PM (20 years ago)

Author:

Matthew Burgess <matthew@…>

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.0, 6.1, 6.1.1, 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:

0c012ac

Parents:

fe8b2f3

Message:

Improved wording of keymap related paragraphs (bug 741)

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3818 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

Files:

• chapter01/changelog.xml (modified) (1 diff)
• chapter07/console.xml (modified) (1 diff)
• chapter08/kernel.xml (modified) (5 diffs)

chapter01/changelog.xml

@@ -77 +77 @@
 </listitem>
 
+<listitem><para>June 19, 2004 [matt]: chapter07 - console &amp; 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>

chapter07/console.xml

@@ -92 +92 @@
 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>

chapter08/kernel.xml

@@ -44 +44 @@
 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> &gt; \
+    <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>
@@ -70 +80 @@
 
 <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>
 
@@ -121 +131 @@
 
 <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>
 
@@ -155 +165 @@
 <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>
 
@@ -190 +200 @@
 <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>