From 89d204ea76f9105b3539bf58c36e598266661fb4 Mon Sep 17 00:00:00 2001 From: Matthew Burgess Date: Sat, 19 Jun 2004 20:11:58 +0000 Subject: [PATCH] Improved wording of keymap related paragraphs (bug 741) git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3818 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter01/changelog.xml | 4 ++++ chapter07/console.xml | 23 ++++++++++++----------- chapter08/kernel.xml | 24 +++++++++++++++++------- 3 files changed, 33 insertions(+), 18 deletions(-) diff --git a/chapter01/changelog.xml b/chapter01/changelog.xml index 36ca6f7a1..433c03bb0 100644 --- a/chapter01/changelog.xml +++ b/chapter01/changelog.xml @@ -76,6 +76,10 @@ first a summary, then a detailed log. +June 19, 2004 [matt]: chapter07 - console & chapter 08 - +kernel. Improved wording and re-introduced the option for compiling the keymap +directly into the kernel. + June 19, 2004 [matt]: chapter06 - e2fsprogs, brought instructions inline with upstream recommendations. diff --git a/chapter07/console.xml b/chapter07/console.xml index 553f27473..0e3cbe2ca 100644 --- a/chapter07/console.xml +++ b/chapter07/console.xml @@ -91,17 +91,18 @@ after the main keymap: KEYMAP_CORRECTION="/etc/kbd/bs-sends-del" EOF -If you decided to -compile your keymap directly into the kernel later on in instead of setting it every time from the -console bootscript, then you don't need to run the -loadkeys program. Since the kernel will set up the keymap, -you can omit the KEYMAP variable from the -/etc/sysconfig/console -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. +If you want to compile your keymap directly into the kernel instead of +setting it every time from the console bootscript, then +instructions are given in . 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 console bootscript won't be run. + +Since the kernel will set up the keymap, you can omit the KEYMAP variable +from the /etc/sysconfig/console 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. diff --git a/chapter08/kernel.xml b/chapter08/kernel.xml index 27e58abff..099eb4254 100644 --- a/chapter08/kernel.xml +++ b/chapter08/kernel.xml @@ -43,16 +43,26 @@ recommends that this command be issued prior to each kernel compilation. You shouldn't rely on the source tree being clean after un-tarring. -Also, assure that the kernel does not attempt to pass hotplugging events +Also, ensure that the kernel does not attempt to pass hotplugging events to userspace until userspace specifies that it is ready: sed -i 's@/sbin/hotplug@/bin/true@' kernel/kmod.c +If, in , you decided you want +to compile the keymap into the kernel, issue the command below: + +loadkeys -m +/usr/share/kbd/keymaps/[path to keymap] > \ + [unpacked sources dir]/linux-&linux-version;/drivers/char/defkeymap.c + +For example, if you have a Dutch keyboard, you would use +/usr/share/kbd/keymaps/i386/qwerty/nl.map.gz. + Configure the kernel via a menu-driven interface: make menuconfig -make oldconfig may be more appropriate in some +make oldconfig may be more appropriate in some situations. See the README file for more information. @@ -69,8 +79,8 @@ scratch. the File systems menu and is normally enabled by default. LFS bootscripts make the assumption that you either compile -both Support for Host-side USB and -USB device filesystem 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). 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 . Kernel compilation has finished but more steps are required to complete -the installation. Some files need to be copied to the /boot +the installation. Some files need to be copied to the /boot directory. 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. If you are going to keep the kernel source tree around, you may want to run chown -R 0:0 on the -linux-&linux-version; directory to ensure all files are +linux-&linux-version; directory to ensure all files are owned by user root. @@ -189,7 +199,7 @@ of running scores of programs seemingly at the same time. kernel headers define the interface to the services that the kernel provides. The headers in your system's -include directory should always be +include directory should always be the ones against which Glibc was compiled and should therefore not be replaced when upgrading the kernel.