It's really alerting that you don't see what the "frickeln" part is.
On a single monitor you can do it your "frickel" way.
1) it is not a clean solution and locked into Xephyr, what about Mir,
wayland? - why don't you whine here about lock-in to X for your
solution
2) no serious company will let the employees stare at one monitor for
two seats, it is unhealthy and is not compatible with EU ergonomics
and health requirement at workplaces and also for 99.999% of the
companies a security break (one employee see what the other does)
3) no imagine ignoring a&b what about not 2 users but 16, will you
split your monitor into 16 xephyr sessions?
4) wikipedia: multiseat is about *independent sessions* which is
already violated by *1* monitor
system-logind in combination with udev offers an incredible amount of
hotplug possibilities:
1) already marked by udev hardware: like plugable multiseat stations:
plug keyboard,mouse, monitor into the station - a new seat appears.
2) mark hardware as seat e.g usb hub: connect usb hub, connect
monitor, mouse, keyboard to usb hub: now either
a) loginctl attach $id_of_usb_hub seat2
b) have a udev rule which contains the usb device id / vendor id
(now if you wish any usb hub from that manufactor(that model) will be
recognized as a multiseat device - but all this is configurable
as you wish)
c) add the devices via loginctl attach $monitor2 $monitor3 (if you
wish) $kb2 $mouse2 (you can also add them permanently or until reboot)
2014-06-08 15:20 GMT+02:00 Ruediger Meier
On Sunday 08 June 2014, Damian Ivanov wrote:
Sounds already like lots of "frickeln" your approach. systemd does it hotplug and clean.
LOL, where exactly is the "frickeln" part? I start a second seat by typing just one command. How would you do this with systemd?
What kind of hotplug could be used? Second user appears in front of the desk and is automatically logged in or what? How would it know which keyboard is placed in front of the left monitor? Or what if you still want to use one of three keyboards for both monitors?
How would systemd automatically decide how many montors should be used for the one or the other user? Does it run on single monitor at all?
2014-06-08 13:42 GMT+02:00 Ruediger Meier
: On Sunday 08 June 2014, Damian Ivanov wrote:
http://en.wikipedia.org/wiki/Multiseat_configuration sure it can be on one monitor if you manage to split the monitor so 2 X servers can run (and be active) at the same time and both users have their independent session.
That's very easy if you run each "seat X-server" within (borderless) Xephyr windows. You can resize and place the windows across half, one or x monitors dynamically as needed. if one user is away for a coffee then the other one can resize his Xephyr to the full available underlying real X-Server.
This solution is completely independent of how many GPUs or monitors you want to use.
Simplified I start such second seat but this script: ------------ disp=":11"
# as root MOUSE="/dev/input/by-id/usb-Logitech_USB_Optical_Mouse-event-mouse" KBD="/dev/input/by-id/usb-Dell_Dell_USB_Keyboard-event-kbd"
export DISPLAY=:0 Xephyr \ "${disp}" \ -ac \ -screen 1280x1024 \ -dpms \ -keybd "evdev,,device=${KBD},xkbrules=evdev,xkbmodel=evdev,xkblayout=de,xk bvariant=nodeadkeys,xkboptions=compose:rwin" \ -mouse "evdev,,device=${MOUSE}" \ & sleep 2
# as user export DISPLAY="${disp}" startkde # or whatever -----------
Since systemd, logind, new udev, dbus deps or whatever I got several kind of problems. As workaround now I run Xephyr as root and "startkde" as the user which wants to use the new session.
cu, Rudi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org