From 6a0f666ea3548cbef751d251e6d86b7a1885fd73 Mon Sep 17 00:00:00 2001 From: Gerard Beekmans Date: Wed, 29 Aug 2001 20:58:28 +0000 Subject: explained in more detail why we remove the defkeymap.map.gz file, and how to create it if you need it anyways git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@1123 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter06/kbd-exp.xml | 23 +++++++++++++++++++---- 1 file changed, 19 insertions(+), 4 deletions(-) (limited to 'chapter06/kbd-exp.xml') diff --git a/chapter06/kbd-exp.xml b/chapter06/kbd-exp.xml index a4260d5db..95ceff0b6 100644 --- a/chapter06/kbd-exp.xml +++ b/chapter06/kbd-exp.xml @@ -6,10 +6,25 @@ data files (fonts, keymaps, and such) in the /usr/share/kbd directory, as the FHS suggests. rm -/usr/share/kbd/keymaps/i386/qwerty/defkeymap.map.gz: We -remove this file because we don't know which keymap you -need to use. We will be defining the default keymap in -chapter 7 when the system configuration files are created. +/usr/share/kbd/keymaps/i386/qwerty/defkeymap.map.gz: There +are some problems with having a defkeymap.map.gz when that file +wants to load another keymap file. Instead of running loadkeys with the -d +option to load the defkeymap.map.gz file, we have come up with a slightly +modified method that we use in the loadkeys bootscript (see chapter 7). +We don't load a default keymap, but instead load the proper keymap +directly, which you will need to specify in a configuration file which +that bootscript uses. This method overcomes this bug. + +However, if you want to create a defkeymap.map.gz file regardless, +here's how you should do it: + +cd /usr/share/kbd/keymaps && +ln -s <path-to-keymap> defkeymap.map.gz + +Replace <path-to-keymap> with the path to the keymap you have +selected, relative to the /usr/share/kbd/keymaps/ directory. For +example, if you have chosen the US keymap, you would replace it with +i386/qwerty/us.map.gz. -- cgit v1.2.3-54-g00ecf