From: Helge Hafting <[EMAIL PROTECTED]> > The keyboard is very much the issue - your typing either goes into
No, it isn't. I have the keyboard under control. Forget that keyboards even exist ;-) Trust me. I know the ruby patch, but I'm trying to make this work with an unpatched kernel. And the VT switching is the only remaining problem. At the end I will run 2 X servers ( yes, I am doing a multi-head (or is it multi-seat ?) system). Currently when I start the second one, it will perform a VT switch and thereby "turn off" the first one (it is still running, just not visible). What if I recompile the kernel with no VT support ? (that is my next try anyway) > the VT on the primary card - or into the X session. There is no other way > the computer can know what you mean. I guess you're going to > run an X session that won't use kbd input at all, given the question you > ask? > > The stock 2.6.x can't do it, but take a look at the ruby patch. > Ruby is really meant for hooking up several keybaords, so you can have one > keboard for the VT's on your first card and another kbd for the X session. > This lets several users work at the same time, using only one pc. > > If you don't need the scondary keyboard - don't plug one in. Ruby can still > give you a dummy VT where no input or output happens, and X can use that VT. > > Boot the ruby-patched 2.6.x kernel with the "dumbcon=1" parameter to get one > dummy console, and let X use VT17 which will be that dummy. > > Helge Hafting - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
