> is it a kernel level configuration or one in X that blocks using the alt-Fx
> to switch to a console?
Kind of both. First with the console you have different modes for the
keyboard. The first is cooked. Here your keypress are translated into
either key presses or some console function. For example you can do
echo -e '\033[?17;0;64c
and this will change the cursor to a red non blinking block. The other
mode is raw. Here what you press is what you get. The X server needs the
keyboard in raw mode. As you figure in this mode you can't see a VT
switch. Now what if the app want to VT switch anyways. Well their is a way
to do it. Once the app has the keyboard in raw mode it goes about it
business. Then you press the specific keys that tell X server you want to
VT switch. Remeber these are raw values. If you write a program like this
you can make up any key combo to VT switch all you want. Then it sends a
signal to the kernel to say hey I want to VT switch to another VC. Then
the app has to want until a signal back to let the app know when it is
okay to VT switch. You have to do things like change video hardware so you
don;t want to VT switch while doing this. Hope this answers your question.
Q: Why did they deprecate a.out support in linux?
A: Because a nasty coff is bad for your elf.
James Simmons [jsimmons@linux-fbdev.org] ____/|
fbdev/console/gfx developer \ o.O|
http://www.linux-fbdev.org =(_)=
http://linuxgfx.sourceforge.net U
http://linuxconsole.sourceforge.net
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Jun 23 2000 - 21:00:21 EST