Instead of making a "console" to own a VC, I'd suggest that
(a) each input device have one "associated" VC where inputs would be sent,
(b) each VC have a list of screen to output to.
(c) each VC have a list of input devices currently attached to it to allow
saving keyboard/button state.
I think this is more flexible than the "binding into console" idea, as we
can have e.g. headless setups or inputless (monitor only) VCs. It also
allows for new kinds of input devices.
Stephen
-
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/