10.0
10.0-rc1
10.1
10.1-rc1
11.0
11.0-rc1
11.0-rc2
11.0-rc3
11.1
11.1-rc1
11.2
11.2-rc1
11.3
11.3-rc1
12.0
12.0-rc1
12.1
12.1-rc1
12.2
12.2-rc1
6.0
6.1
6.1.1
6.3
6.4
6.5
6.6
6.7
6.8
7.0
7.1
7.2
7.3
7.4
7.5
7.5-systemd
7.6
7.6-systemd
7.7
7.7-systemd
7.8
7.8-systemd
7.9
7.9-systemd
8.0
8.1
8.2
8.3
8.4
9.0
9.1
arm
bdubbs/gcc13
ml-11.0
multilib
renodr/libudev-from-systemd
s6-init
trunk
v5_1
v5_1_1
xry111/arm64
xry111/arm64-12.0
xry111/clfs-ng
xry111/lfs-next
xry111/loongarch
xry111/loongarch-12.0
xry111/loongarch-12.1
xry111/loongarch-12.2
xry111/mips64el
xry111/multilib
xry111/pip3
xry111/rust-wip-20221008
xry111/update-glibc
| Line | |
|---|
| 1 | <sect1 id="ch-scripts-loadkeys">
|
|---|
| 2 | <title>Do I need the loadkeys script?</title>
|
|---|
| 3 | <?dbhtml filename="loadkeys.html" dir="chapter07"?>
|
|---|
| 4 |
|
|---|
| 5 | <para>If back in <xref linkend="chapter-building-system"/> you decided to go
|
|---|
| 6 | compile your keymap directly into the kernel (later on in <xref
|
|---|
| 7 | linkend="chapter-mixture"/>), then strictly speaking you don't need to run this
|
|---|
| 8 | loadkeys script, since the kernel will set up the keymap for you. If you wish,
|
|---|
| 9 | you can still run the script, it isn't going to hurt you. Keeping it could even
|
|---|
| 10 | be beneficial, in case you run a lot of different kernels and can't be sure
|
|---|
| 11 | that the keymap is compiled into every one of them.</para>
|
|---|
| 12 |
|
|---|
| 13 | <para>If you decided you don't need or don't want to use the loadkeys script,
|
|---|
| 14 | remove the <filename
|
|---|
| 15 | class="symlink">/etc/rc.d/rcsysinit.d/S70loadkeys</filename> symlink.</para>
|
|---|
| 16 |
|
|---|
| 17 | </sect1>
|
|---|
| 18 |
|
|---|
Note:
See
TracBrowser
for help on using the repository browser.
