version 1, including all changes.
.
Rev |
Author |
# |
Line |
1 |
perry |
1 |
KEYTAB-LILO.PL |
|
|
2 |
!!!KEYTAB-LILO.PL |
|
|
3 |
NAME |
|
|
4 |
SYNOPSIS |
|
|
5 |
DESCRIPTION |
|
|
6 |
OPTIONS |
|
|
7 |
EXAMPLES |
|
|
8 |
AUTHOR |
|
|
9 |
SEE ALSO |
|
|
10 |
---- |
|
|
11 |
!!NAME |
|
|
12 |
|
|
|
13 |
|
|
|
14 |
keytab-lilo - compile keytables files for use with LILO |
|
|
15 |
!!SYNOPSIS |
|
|
16 |
|
|
|
17 |
|
|
|
18 |
__/usr/sbin/keytab-lilo__ [[__-p__ |
|
|
19 |
''old_code''=''new_code''] ... [[''default_layout''] |
|
|
20 |
''kbd_layout'' |
|
|
21 |
!!DESCRIPTION |
|
|
22 |
|
|
|
23 |
|
|
|
24 |
__keytab-lilo__ is a program which compiles keytable |
|
|
25 |
definitions (in the format specified in __keytables(5)__) |
|
|
26 |
into a format which can be used by __lilo(8)__ to set the |
|
|
27 |
keyboard type when booting [[using the __keytable__ |
|
|
28 |
parameter in __/etc/lilo.conf__]. |
|
|
29 |
|
|
|
30 |
|
|
|
31 |
''kbd_layout'' should be the name of a map file which |
|
|
32 |
specifies the desired keyboard layout. This file may be a |
|
|
33 |
__gzip(1)__ compressed map. If no file extension is |
|
|
34 |
given, __.map.gz__ is assumed. If the full pathname is |
|
|
35 |
not specified, __/usr/share/keymaps/__ is |
|
|
36 |
assumed. |
|
|
37 |
|
|
|
38 |
|
|
|
39 |
Since __lilo__ essentially needs to know the differences |
|
|
40 |
between the BIOS keyboard mapping and the one you require, |
|
|
41 |
the ''default_layout'' file should contain a |
|
|
42 |
__keytables(5)__ file for the BIOS default mapping. If no |
|
|
43 |
''default_layout'' file is specified, __us.map.gz__ is |
|
|
44 |
used. |
|
|
45 |
|
|
|
46 |
|
|
|
47 |
__keytab-lilo__ writes the output translation table as a |
|
|
48 |
binary string to standard output, so you should redirect it |
|
|
49 |
to a suitable file. __lilo__ has no particular |
|
|
50 |
restrictions on the name of keyboard translation files, but |
|
|
51 |
the suggested naming convention and location is |
|
|
52 |
__/boot/__''mapping''__.ktl__ (where __.ktl__ |
|
|
53 |
stands for |
|
|
54 |
__ |
|
|
55 |
!!OPTIONS |
|
|
56 |
|
|
|
57 |
|
|
|
58 |
__-p__ |
|
|
59 |
|
|
|
60 |
|
|
|
61 |
''old_code''=''new_code'' |
|
|
62 |
Specifies corrections ( |
|
|
63 |
!!EXAMPLES |
|
|
64 |
|
|
|
65 |
|
|
|
66 |
__keytab-lilo dvorak __ |
|
|
67 |
|
|
|
68 |
|
|
|
69 |
This is the most common form of invocation; it simply |
|
|
70 |
compiles the given map file (in this case dvorak) and puts |
|
|
71 |
the result in __/boot/dvorak.ktl__. |
|
|
72 |
!!AUTHOR |
|
|
73 |
|
|
|
74 |
|
|
|
75 |
Werner Almesberger (almesber@bernina.ethz.ch). |
|
|
76 |
Peter Maydell (pmaydell@chiark.greenend.org.uk) wrote this |
|
|
77 |
manual page. |
|
|
78 |
!!SEE ALSO |
|
|
79 |
|
|
|
80 |
|
|
|
81 |
lilo(8), keytables(5), |
|
|
82 |
gzip(1) |
|
|
83 |
|
|
|
84 |
|
|
|
85 |
__lilo__ comes with extensive documentation; this can be |
|
|
86 |
found in /usr/share/doc/lilo/ on Debian |
|
|
87 |
systems. |
|
|
88 |
---- |