| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Mon, 09 Jan 2012 16:11:36 -0500 From: Phillip Susi <psusi@....rr.com> To: Greg KH <gregkh@...e.de> CC: linux-kernel@...r.kernel.org Subject: Multiple consoles I was considering some questions I read about setting up a multi-seat system where you have two separate sets of displays, keyboards, mice, and X servers. The problem someone noticed is that if you run the second X server on tty8, then you have to switch the console to tty8 to activate it, which disables the primary X server. It occurred to me that there ought to be an entirely separate set of virtual consoles bound to the second seat, and the second X server ought to run on one of those vcs. Or of course, you could choose to log into the console and not bother with X. Looking at drivers/tty/vt/vt.c, it appears that it was written assuming that there is just one linux console. It appears to use global variables for keeping track of which vc is active, etc, rather than creating one or more console devices, and store the vc multiplexing information in those devices. So to fix this, vt.c and keyboard.c would need significantly refactored to remove the global variables and create a console device to bind vcs, keyboards, and displays to, and then you could create a second one if you wanted. Does this make sense or am I missing something? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists