version 1, including all changes.
.
| Rev |
Author |
# |
Line |
| 1 |
perry |
1 |
INSTALL-KEYMAP |
| |
|
2 |
!!!INSTALL-KEYMAP |
| |
|
3 |
NAME |
| |
|
4 |
SYNOPSIS |
| |
|
5 |
DESCRIPTION |
| |
|
6 |
FILES |
| |
|
7 |
SEE ALSO |
| |
|
8 |
AUTHOR |
| |
|
9 |
---- |
| |
|
10 |
!!NAME |
| |
|
11 |
|
| |
|
12 |
|
| |
|
13 |
install-keymap -- expand a given keymap and install it as boot-time keymap |
| |
|
14 |
!!SYNOPSIS |
| |
|
15 |
|
| |
|
16 |
|
| |
|
17 |
__install-keymap__ [[''keymap-name'' | NONE | |
| |
|
18 |
KERNEL] |
| |
|
19 |
!!DESCRIPTION |
| |
|
20 |
|
| |
|
21 |
|
| |
|
22 |
__install-keymap__ usually takes a ''keymap-name'' as |
| |
|
23 |
argument. The file is passed to __loadkeys__ for loading, |
| |
|
24 |
so that valid values for this argument are the same than |
| |
|
25 |
that of arguments to __loadkeys__. __install-keymap__ |
| |
|
26 |
expands include-like statements in that file, and puts the |
| |
|
27 |
result in __/etc/console/boottime.kmap.gz__, which will |
| |
|
28 |
be loaded into the kernel at boot-time. |
| |
|
29 |
|
| |
|
30 |
|
| |
|
31 |
One may also specify __KERNEL__ instead of a keymap name, |
| |
|
32 |
causing __/etc/console/boottime.kmap.gz__ to be removed, |
| |
|
33 |
making sure that no custom keymap will replace the kernel's |
| |
|
34 |
builtin keymap at next reboot. |
| |
|
35 |
|
| |
|
36 |
|
| |
|
37 |
An argument of __NONE__ tells the command to do nothing. |
| |
|
38 |
It can be used by caller scripts to avoid handling this |
| |
|
39 |
special case and needlessly duplicate code. |
| |
|
40 |
|
| |
|
41 |
|
| |
|
42 |
The purpose of this processing is to solve an annoying |
| |
|
43 |
problem, of 2 apparently conflicting issues. The first one |
| |
|
44 |
is an important goal of keymap management in Debian, namely |
| |
|
45 |
ensuring that whenever the user or admin is expected to use |
| |
|
46 |
the keyboard, the keymap selected as boot-time keymap is in |
| |
|
47 |
use; this means the keymap has to be loaded before a shell |
| |
|
48 |
is ever proposed, which means very early in the booting |
| |
|
49 |
process, and especially before all local filesystems are |
| |
|
50 |
mounted (__/etc/rcS.d/S10checkroot.sh__ can spawn |
| |
|
51 |
__sulogin__). |
| |
|
52 |
|
| |
|
53 |
|
| |
|
54 |
The second issue is that for flexibility we allow that |
| |
|
55 |
__/usr__ or __/usr/share__ may live on their own |
| |
|
56 |
partition(s), and thus __/usr/share/keymaps__, where |
| |
|
57 |
keymap files live, may not be available for reading at the |
| |
|
58 |
time we need a keymap file. And no, we won't put 1Mb of |
| |
|
59 |
keymaps in the root partition just for this. |
| |
|
60 |
|
| |
|
61 |
|
| |
|
62 |
And the problem is, most keymap files are not |
| |
|
63 |
self-contained, so it does not help to just copy the |
| |
|
64 |
selected file into the root partition. The best known |
| |
|
65 |
solution so far is to expand the keymap file so that it |
| |
|
66 |
becomes self-contained, and put it in the root partition. |
| |
|
67 |
That's what this tool does. |
| |
|
68 |
!!FILES |
| |
|
69 |
|
| |
|
70 |
|
| |
|
71 |
__/etc/console/boottime.kmap.gz__ |
| |
|
72 |
|
| |
|
73 |
|
| |
|
74 |
Where the boot-time keymap is stored |
| |
|
75 |
!!SEE ALSO |
| |
|
76 |
|
| |
|
77 |
|
| |
|
78 |
loadkeys (8). |
| |
|
79 |
!!AUTHOR |
| |
|
80 |
|
| |
|
81 |
|
| |
|
82 |
This program and manual page were written by Yann Dirson |
| |
|
83 |
dirson@debian.org for the __Debian GNU/Linux__ system, |
| |
|
84 |
but as it should not include any Debian-specific code, it |
| |
|
85 |
may be used by others. |
| |
|
86 |
---- |
