Closed Ricky-Tigg closed 1 day ago
There is indeed a mistake. The path where defkeymap.map is alternatively searched is slightly different. The second path is /usr/src/linux/drivers/tty/vt
. This is an optional path to the linux kernel source code.
But then, if this is so, on my system none of these paths will lead to defkeymap.map.gz. Could this have been intentional?
@Ricky-Tigg The loadkeys utility uses multiple directories to search for keymaps. At the beginning defkeymap is searched among other keymaps. If defkeymap is not found, loadkeys will try searching the kernel source tree if the directory exists.
https://github.com/legionus/kbd/blob/master/data/keymaps/i386/qwerty/defkeymap.map
Can I infer that when defkeymap.map.gz exists, it will inexorably be found by this tool?
I think so.
There is indeed a mistake. The path where defkeymap.map is alternatively searched is slightly different. The second path is
/usr/src/linux/drivers/tty/vt
. This is an optional path to the linux kernel source code.
Fixed in master.
kbd package installed from Fedora repository
Hello.
reference in
LOADKEYS(1)
:If the -d (or --default ) option is given, loadkeys loads a default keymap, probably the file defkeymap.map either in /usr/lib/kbd/keymaps or in /usr/src/linux/drivers/char.
/usr/lib/kbd/keymaps
exists./usr/src/linux/drivers/char
doesn't exist.