NavigationUser loginSpam?See spam posts on this site? If so, please don't reply to the spam! Instead, just report the URL to the webmaster. |
console keymap and console-setupHi, I'm a little confused as to how to set my console keymap. I've got a loadkeys /usr/share/keymaps/i386/qwerty/custom.kmap gets it installed and running just fine. I tried to modify Any help will be appreciated! Thanks, Tyler -- |
console keymap and console-setup
* Tyler Smith [070529 23:42]:
> Hi,
>
> I'm a little confused as to how to set my console keymap. I've got a
> custom keymap that suits me, and running
>
> loadkeys /usr/share/keymaps/i386/qwerty/custom.kmap
>
> gets it installed and running just fine. I tried to modify
> /etc/init.d/keymap.sh to load it automatically, but this fails. I
> think it's because I've got console-setup / setupcon loaded. I looked
> through the readme for console-setup, but it's not clear to me if I
> need to put my custom keymap somewhere special, or if I can just point
> to it from a config file. Google points to some conflicting advice,
> mostly on account of the switch from keymap.sh to console-setup I
> think.
Before "dvorak-classic" became a standard offering in Debian, the
approach which I used was to execute the command:
# install-keymap dvorak-classic.kmap.gz
sometime during installation and configuration of the system --
usually at the first opportunity.
Of course, if the keymapping file is on a floppy, a CD, or a flash
memory stick, you need to specify the path to the keymapping file.
It is not necessary to save a copy of custom.kmap.gz on your machine.
However, to make it easy to locate the file the next time you need to
configure another machine, you may wish to copy the file into:
/usr/share/keymaps/i386/qwerty/
and then execute:
# install-keymap /usr/share/keymaps/i386/qwerty/custom.kmap.gz
As soon as you install the new keymap, it becomes:
/etc/console/boottime.kmap.gz
after first copying the old keymap (typically QWERTY) to:
/etc/console/boottime.old.kmap.gz
Thereafter, when you boot the system, your custom keymap should be in
effect. No other configuration is required. See the man page for
install-keymap.
RLH
--
console keymap and console-setup
On 2007-05-30, Russell L. Harris wrote:
>
> Before "dvorak-classic" became a standard offering in Debian, the
> approach which I used was to execute the command:
>
> # install-keymap dvorak-classic.kmap.gz
>
> sometime during installation and configuration of the system --
> usually at the first opportunity.
>
Ok, so I ran
install-keymap /usr/share/keymaps/i386/qwerty/custom.kmap
and then rebooted.
The keymap was not installed, and I got the same problems as usual.
However, I then ran
loadkeys /usr/share/keymaps/i386/qwerty/custom.kmap
and got the proper keymap going. I took a look at
/etc/console/boottime.kmap.gz and it looks like the right file, so I'm
not sure what is wrong.
>
> Thereafter, when you boot the system, your custom keymap should be in
> effect. No other configuration is required. See the man page for
> install-keymap.
>
Maybe there should be see-also link to this from the loadkeys
manpage...
Thanks,
Tyler
--
console keymap and console-setup
* Tyler Smith [070530 08:28]:
> On 2007-05-30, Russell L. Harris wrote:
> >
> > Before "dvorak-classic" became a standard offering in Debian, the
> > approach which I used was to execute the command:
> >
> > # install-keymap dvorak-classic.kmap.gz
> >
> > sometime during installation and configuration of the system --
> > usually at the first opportunity.
> >
>
> Ok, so I ran
>
> install-keymap /usr/share/keymaps/i386/qwerty/custom.kmap
>
> and then rebooted.
>
> The keymap was not installed, and I got the same problems as usual.
> However, I then ran
>
> loadkeys /usr/share/keymaps/i386/qwerty/custom.kmap
>
> and got the proper keymap going. I took a look at
> /etc/console/boottime.kmap.gz and it looks like the right file, so I'm
> not sure what is wrong.
Perhaps install-keymap requires the keymap to be in gzip form?
RLH
--
console keymap and console-setup
I wrote:
+----------------------+
Ok, so I ran
install-keymap /usr/share/keymaps/i386/qwerty/custom.kmap
and then rebooted.
The keymap was not installed, and I got the same problems as usual.
However, I then ran
loadkeys /usr/share/keymaps/i386/qwerty/custom.kmap
and got the proper keymap going. I took a look at
/etc/console/boottime.kmap.gz and it looks like the right file, so I'm
not sure what is wrong.
+-----------------------+
As a quick update, I deterimined that running
loadkeys /etc/console/boottime.kmap.gz
sets the appropriate keymap, so whatever is going on during boot up,
/etc/console/boottime.kmap.gz is *not* getting loaded.
Tyler
--
console keymap and console-setup
On 2007-05-31, Florian Kulzer wrote:
>
> I think that in the end console-setup uses the definitions in
> /etc/default/console-setup, which have a syntax similar to the keyboard
> section in xorg.conf, e.g.
>
> XKBMODEL=""
> XKBLAYOUT="es"
> XKBVARIANT="nodeadkeys"
> XKBOPTIONS="lv3:ralt_switch"
>
> Can you achieve your custom keyboard layout like that? (The above works
> for me, but I never tried any fancy stuff with console-setup's keyboard
> layouts.)
>
The documentation for console-setup is very sketchy, and basically
just says use the same options you use for your xorg.conf. Well, I've
done that, and it still doesn't work. This is very frustrating.
Thanks for your suggestions though!
Tyler
--
[SOLVED] console keymap and console-setup
On 2007-05-31, Tyler Smith wrote:
> On 2007-05-31, Florian Kulzer wrote:
>>
>> I think that in the end console-setup uses the definitions in
>> /etc/default/console-setup, which have a syntax similar to the keyboard
>> section in xorg.conf, e.g.
>>
>> XKBMODEL=""
>> XKBLAYOUT="es"
>> XKBVARIANT="nodeadkeys"
>> XKBOPTIONS="lv3:ralt_switch"
>>
>> Can you achieve your custom keyboard layout like that? (The above works
>> for me, but I never tried any fancy stuff with console-setup's keyboard
>> layouts.)
>>
>
> The documentation for console-setup is very sketchy, and basically
> just says use the same options you use for your xorg.conf. Well, I've
> done that, and it still doesn't work. This is very frustrating.
>
> Thanks for your suggestions though!
>
> Tyler
>
Ok, I've got what I needed for the console sorted out. I couldn't
figure out the xorg-like options for console-setup. You'd think that
somewhere in the many man pages on xorg and console-setup and kbd and
keyboard and ... someone might have thought to explain what the
options actually do, beyond just listing what they are! It's all fine
and well to tell me how to control my keyboard groups, and how to get
to level 3, but I have no idea why I'd want to do either. At least
Wikipedia could tell me what a dead key was.
Anyways, I ended up purging console-setup. The only thing I liked
about it was the terminus font, and that was easy enough to manage on
my own, with a consolechars command added to .bash_profile. I put my
custom keymap somewhere, I'll probably never find it again, but I
changed the keymap.sh script to point to it, so I don't need to know.
Now I get my keymap loaded automatically during boot, and the font is
switched when I log on, and everything is just peachy. The keymap I'm
using is perfect for emacs, but it does alter the behaviour of a few
keys (arrows and page_{up|down}) when I use aptitude, mutt, and slrn,
but alternatives are available.
I have one more keyboard issue, but it's with xterm, so I'll leave
that until tomorrow.
Thanks for all the tips!
Tyler
--
console keymap and console-setup
On 2007-05-30, Florian Kulzer wrote:
>>
>> sets the appropriate keymap, so whatever is going on during boot up,
>> /etc/console/boottime.kmap.gz is *not* getting loaded.
>
> I never actually tried to play around with this myself, but I think the
> keymap should be loaded from
>
> /etc/console-setup/boottime.kmap.gz
> ^^^^^^
>
> and it should be possible to customize it; see the comments at the end
> of /etc/default/console-setup.
>
No dice. I copied the custom keymap to /etc/console-setup/ and
rebooted, but it still doesn't load. It works when I run
/etc/console-setup/boottime.kmap.gz, but I have to do that manually
for each boot.
Thanks,
Tyler
--
console keymap and console-setup
On 2007-05-30, Mumia W.. wrote:
> On 05/30/2007 11:26 AM, Tyler Smith wrote:
>>
>> [...] I copied the custom keymap to /etc/console-setup/ and
>> rebooted, but it still doesn't load. It works when I run
>> /etc/console-setup/boottime.kmap.gz, but I have to do that manually
>> for each boot.
>>
>
> Perhaps you could create a custom startup script in /etc/init.d/ that
> sets up your keyboard. Naturally, you'd also have to use update-rc.d to
> ensure that the script is run in the right run-levels.
>
I suppose I could, but I'm still confused as to how this is supposed
to work. The boot process must be loading a keymap at some point, but
it's clearly not getting it from console-setup, or keymaps.sh. Rather
than write a new script to over-ride the default keymap, there should
be a way to select a different default? The documentation for
console-select suggests this is true, but provides no details.
Tyler
--
console keymap and console-setup
Tyler Smith(tyler.smith@mail.mcgill.ca) is reported to have said:
> Hi,
>
> I'm a little confused as to how to set my console keymap. I've got a
> custom keymap that suits me, and running
>
> loadkeys /usr/share/keymaps/i386/qwerty/custom.kmap
>
> gets it installed and running just fine. I tried to modify
> /etc/init.d/keymap.sh to load it automatically, but this fails. I
> think it's because I've got console-setup / setupcon loaded. I looked
> through the readme for console-setup, but it's not clear to me if I
> need to put my custom keymap somewhere special, or if I can just point
> to it from a config file. Google points to some conflicting advice,
> mostly on account of the switch from keymap.sh to console-setup I
> think.
I have used a custom keymap for many years (based a very early issue of
a Linux Gazette article) and it works fine until console-tools gets
updated. Here's how I do it
in .bash_profile
echo Loading Custom Keys...
loadkeys ~/new-us.map > /dev/null 2>&1
As I use the Num keypad to switch consoles, and notice that they quit
working, after an upgrade, all I have to do to get my keypad back is
. .bash_profile. Note that I keep my custom keymap in /root so it
doesn't get corrupted when updating.
HTH=Hope This Helps, YMMV=Your Mileage May Vary, HAND=Have A Nice Day
Wayne
--
Those who can, do. Those who cannot, teach. Those who cannot teach,
HACK!
_______________________________________________________
--