Re: I sometimes lose 'q' key in profit of 'a' using mac-fr3 keymap... (fwd)
Since I have no Mac this belongs here...
---------- Forwarded message ----------
Date: Wed, 2 May 2001 12:55:36 +0200
From: Duncan Sands <sands@topo.math.u-psud.fr>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: I sometimes lose 'q' key in profit of 'a' using mac-fr3 keymap...
On Wed, May 02, 2001 at 10:54:50AM +0200, Geert Uytterhoeven wrote:
> On Wed, 2 May 2001, Michael Schmitz wrote:
> > > I had the same problem. If I remember right, the keyboard configuration
> > > script loads the keymap from /usr/share/keymaps, then regenerates it
> > > in /etc/console-tools. The problem is that it is regenerated wrong: the
> > > setting for the q key is not written. Note the suspicious fact that q has
> > > keycode 0. This is clearly a bug in one of the console tools, one that
> >
> > keycode 0 is illegal on x86 (you'll find a long flame war on this topic in
> > the l-k archives). You could change the kernel to remap keycode 0 to some
> > spare keycode, and adjust the keymap to match. Or you could continue the
> > 'keycode 0 is a valid keycode on some architectures so please fix
> > console-tools' argument.
> > Seeing how common sense (WRT to making incompatible changes and all) often
> > loses, I'd go for the first option.
>
> According to Andriew Brouwer there is a severe security problem with using
> keycode 0, since it's reserved to mean something special somewhere in the
> keyboard ioctls.
>
> Note that Amiga still uses keycode 0. It's hard to break backwards
> compatibility here...
>
> Don't know how `keycode 0' is related to the new input subsystem though.
> Perhaps that would solve the whole problem completely.
>
> Gr{oetje,eeting}s,
>
> Geert
>
> P.S. Sorry, can't find Andries mail right now, so you have to ask him
> yourself if you can't find out.
Let's try to fix this 'q' -> 'a' problem. It was a real pain for me
when I first installed Debian on a mac with a French keyboard: you need
to be able to hit 'q' to get out of the fdisk program, and maybe it comes
up in other parts of the installation too. This hassle already came up on
the mailing list by the way.
Duncan.
Reply to: