.TH "INSTALL-KEYMAP" "8" 
.SH "NAME" 
install-keymap \(em expand a given keymap and install it as boot-time keymap 
.SH "SYNOPSIS" 
.PP 
\fBinstall-keymap\fR [\fIkeymap-name\fR | NONE | KERNEL]  
.SH "DESCRIPTION" 
.PP 
\fBinstall-keymap\fR usually takes a 
\fIkeymap-name\fR as argument.  The file is passed to 
\fBloadkeys\fR for loading, so that valid values for this 
argument are the same than that of arguments to 
\fBloadkeys\fR.  \fBinstall-keymap\fR expands include-like 
statements in that file, and puts the result in 
\fB/etc/console/boottime.kmap.gz\fP, which will be 
loaded into the kernel at boot-time. 
.PP 
One may also specify \fBKERNEL\fP instead of a keymap 
name, causing \fB/etc/console/boottime.kmap.gz\fP     to be removed, making sure that no custom keymap will replace the 
kernel's builtin keymap at next reboot. 
.PP 
An argument of \fBNONE\fP tells the command to do 
nothing.  It can be used by caller scripts to avoid handling this 
special case and needlessly duplicate code. 
.PP 
The purpose of this processing is to solve an annoying 
problem, of 2 apparently conflicting issues.  The first one is an 
important goal of keymap management in Debian, namely ensuring 
that whenever the user or admin is expected to use the keyboard, 
the keymap selected as boot-time keymap is in use; this means the 
keymap has to be loaded before a shell is ever proposed, which 
means very early in the booting process, and especially before all 
local filesystems are mounted 
(\fB/etc/rcS.d/S10checkroot.sh\fP can spawn 
\fBsulogin\fR). 
.PP 
The second issue is that for flexibility we allow that 
\fB/usr\fP or \fB/usr/share\fP may 
live on their own partition(s), and thus 
\fB/usr/share/keymaps\fP, where keymap files live, 
may not be available for reading at the time we need a keymap 
file.  And no, we won't put 1Mb of keymaps in the root 
partition just for this. 
.PP 
And the problem is, most keymap files are not 
self-contained, so it does not help to just copy the selected file 
into the root partition.  The best known solution so far is to 
expand the keymap file so that it becomes self-contained, and put 
it in the root partition.  That's what this tool does. 
.SH "FILES" 
.IP "\fB/etc/console/boottime.kmap.gz\fP" 10 
.PP 
Where the boot-time keymap is stored 
.SH "SEE ALSO" 
.PP 
loadkeys (8). 
.SH "AUTHOR" 
.PP 
This program and manual page were written by Yann Dirson 
dirson@debian.org for the \fBDebian GNU/Linux\fP system, but as 
it should not include any Debian-specific code, it may be used by 
others. 
.\" created by instant / docbook-to-man