On Thursday, 30 March 2006, at 14:59:21 (+1000), David Seikel wrote: > That's actually what triggers the keyboard locking problem in the > first place. If you don't let X know which VT to run on, it tries > to autodetect the VT, but it gets into a race condition with init or > a getty which is also allocating VTs at the same time. The end > result is that X gets confused, and sometimes ends up with the > display on one VT, but the keyboard redirected to some other VT, and > with VT switching disabled for some reason.
Any distribution which tries to start a getty on the same VT as X is flawed. Furthermore, Linux has standardized on X being on tty7. That should always be the default on Linux. Michael -- Michael Jennings (a.k.a. KainX) http://www.kainx.org/ <[EMAIL PROTECTED]> n + 1, Inc., http://www.nplus1.net/ Author, Eterm (www.eterm.org) ----------------------------------------------------------------------- "It's been awhile since I've seen the way the candles light your face. And it's been awhile, but I can still remember just the way you taste." -- Staind, "It's Been Awhile" ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
