Broken command to build the keymap into the kernel

[manuel@…]

Due that now the Kbd keymap files are installed into /lib/kbd, the commands found in the book to build the keymap into the kernel are broken.

The fix for the bootable chapter is as easy as to change in bootable/x86/kernel.xml

loadkeys -m /usr/share/kbd/keymaps/[path to keymap] > drivers/char/defkeymap.c

by

loadkeys -m /lib/kbd/keymaps/[path to keymap] > drivers/char/defkeymap.c

Fixing also the path in the paragraph below that command.

But that don't will work for the boot chapter due that we can't know beforehand where the keymap files are installed on the host.

Thus in the boot chapter the XIncludes to that blocks must be replaced by a proper command and text, or full removed.

[Joe Ciccone]

I'd either replace this command with

loadkeys -m [path to keymap] > drivers/char/devkeymap.c

or

loadkeys -m ${CLFS}/lib/kbd/keymaps/[path to keymap] > drivers/char/defkeymap.c

Because we're so close to a release I would opt for the first one for now. we also don't know that /usr/share/keymaps are where the keymaps are.

[chris@…]

I would think the 2nd one isn't even an option since kbd isn't installed onto ${CLFS} until the final-system.

[chris@…]

Of course, that 2nd one is what we would want for CLFS 2.

[chris@…]

I don't believe that text in the boot section should be removed, as anyone using the boot method has no other way of using alternative keyboard layouts (since kbd is not installed in the temp-system). I'm

[chris@…]

Oops, I didn't finish typing (was going to remove what I typed anyway and just assign the ticket to myself :p ).

[chris@…]

For anyone here who knows how distros do things, would it be reasonable to state in the "boot" section that a typical location for keymap files is in /usr/share/kbd? Or do most distros do something different?

[chris@…]

Ok, I've updated the book with the needed command changes - just need to look at the text in the "boot" section. I am seeing a few different possibilities to account for the fact that we don't necessarily know where keymap files may be on the host...

1. Say to "consult the host's documentation" for the info
2. Mention that /usr/share/kbd is a typical location
3. Tell the user to run a command like "find / -type d -name keymaps"
4. Any combination of the above

[alexander@…]

You obvuously don't follow LFS lists and bug reports:

​http://archives.linuxfromscratch.org/mail-archives/lfs-support/2005-January/025877.html ​http://archives.linuxfromscratch.org/mail-archives/blfs-support/2005-December/057972.html

Even for non-UTF-8 case, compiling keymap into the kernel sometimes doesn't work. This happens because some keymaps expect themselves to be loaded after (i.e., on top of) the default keymap, not instead of it. So the only really working solution for the boot scenario is to install kbd into /tools.

[alexander@…]

See also ​http://wiki.linuxfromscratch.org/lfs/ticket/1671

[manuel@…]

For CLFS-1.0.0, and due that we are very near to release, maybe a note discussing that some keymaps may not work properly when compiled into the kernel could prevent the issue.

For CLFS-1.1.0 I thing also that Kbd should be installed in /tools to can have a working keyboard when using the boot method.

[Jim Gifford]

From what I found out this is not the preferred method. I vote to remove this entire section of building the keymap into the kernel.

[chris@…]

I would say, remove it entirely from the final system, but keep it in the boot section, at least until kbd is added to the temp-system.

[Jim Gifford]

1.0.0 book was updated to the proper location.

1.1.0 book will have this section removed from the entire book, it will be replaced with notes on the website.

This ticket is going to be assigned up to 1.1.0 branch, until the note page is up on the website.