Feb. 3, 2015
5:50 p.m.
On Tue, 03 Feb 2015 09:34:31 -0600, riya khanna said:
(e.g. evdev) and mediate accesses in user space through ioctl. For example, if a container is in the background (i.e. user not interacting with it), then all inputs should be blocked to it, but if it becomes active again inputs must be redirected to its virtual devices.
That's actually nowhere near as obviously true as you might think, and depends *heavily* on what the definition and exact semantics of "background" is. Do you mean 'process &' type of background, or "user ctl-Z'ed the process" background, or "screensaver has kicked in" background? Those all have very different semantics....