Chris Staub wrote:
I'm in the process of updating CLFS to account for the changed keymap
files location in the final system, as well as the text in the "boot"
section. I think jhalfs should have 2 separate KEYMAP options - one for
the "boot" section and one for the final-system. There are likely to be
users (like me, for instance) who generally just use the console
bootscript to set the keymap at boot time, but would like to compile it
into the kernel when building a system by the boot method (simply
because kbd isn't installed at that point so using the bootscript or
loadkeys program is impossible). Also, the option for the "boot" section
should ask for the entire path to the keymap (rather than assuming
/usr/share/kbd or /lib/kbd, since you don't really know where those
files will be on the host).
I've also attached a patch with a number of text updates for jhalfs, as
well as changing the path to the keymap to match what's in the book.
------------------------------------------------------------------------
Thanks for the patches Chris. I applied all of your patches except
for the mod to KEYMAP. Although the text states "keymap file relative to
/usr/share/kbd/keymaps/" the code only utilizes the contents of KEYMAP.
Manuel does some xsl wizardry and substitues KEYMAP here...
(clfs) loadkeys -m /lib/kbd/keymaps/[path to keymap] > \
drivers/char/defkeymap.c
(clfs2 loadkeys -m ${CLFS}/lib/kbd/keymaps/[path to keymap] > \
drivers/char/defkeymap.c
(hlfs) loadkeys -m /usr/share/kbd/keymaps/[path to keymap] > \
drivers/char/defkeymap.c
The requirement for a known path is to allow validation of the keymap
name. If the requested keymap does not exist on the host the test fails
and jhalfs aborts.
I will look into what is needed to support BOOT_KEYMAP
G
--
http://linuxfromscratch.org/mailman/listinfo/alfs-discuss
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
