Bug 19225 - keytab-lilo is broken
Summary: keytab-lilo is broken
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: lilo
Version: 7.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Brock Organ
URL:
Whiteboard:
: 49233 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-10-17 03:14 UTC by apeacock
Modified: 2014-03-19 11:09 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-06-04 19:33:07 UTC
Embargoed:


Attachments (Terms of Use)

Description apeacock 2000-10-17 03:14:32 UTC
The keytab-lilo program does not work out of the box.  No matter what
parameters are passed, keytab-lilo reports:

findkeymap: No such file or directory
cannot open file us.map
keytab-lilo: Keymap is empty

Comment 1 LENHOF 2001-04-12 21:01:49 UTC
The only thing which could help is that :

[root@mylinux /root]# keytab-lilo /lib/kbd/keymaps/i386/qwerty/us.kmap.gz
/lib/kbd/keymaps/i386/azerty/fr-latin1.kmap.gz > /boot/fr-latin1.ktl 
Loading /lib/kbd/keymaps/i386/qwerty/us.kmap.gz
Loading /lib/kbd/keymaps/i386/azerty/fr-latin1.kmap.gz
[root@mylinux /root]#

But after running lilo -v and rebooting....my keyboard isn't more in French...

Perhaps it will give you some ideas ?

Thanks
Jean-Yves

Comment 2 eric gerbier 2001-06-06 09:40:06 UTC
I have the same problem with redhat 7.1.

I solve it with the original lilo.tar.gz : I extract the keytab-lilo.pl (perl
script), use it, reboot
ant it works well

the bug is in the packaged keytab-lilo (elf program)

Comment 3 Jeremy Katz 2002-06-04 06:29:45 UTC
*** Bug 49233 has been marked as a duplicate of this bug. ***

Comment 4 Jeremy Katz 2002-06-04 19:23:30 UTC
Reassigning

Comment 5 Jeremy Katz 2002-06-04 20:23:13 UTC
This should be fixed in rawhide since we're using kbd again instead of
console-tools (the perl version isn't used because we don't want to have a
dependency on perl for lilo)


Note You need to log in before you can comment on or make changes to this bug.