Then there's the people that were running multiple keyboards, mice and monitors for a couple of people on the same box well over a decade back. What is it with Wayland fanboys not having a clue about the system that they are supposed to be improving on?
I setup such a system a year and a half ago (4 stations off one computer, totaling > 10mpx of desktop space).
Allowing me to be abundantly clear: I wish Wayland was production ready a year ago. Multiseat-X sucks for these reasons:
- You either need a separate graphics card per session, or use framebuffered Xephyr windows to run your desktop (I chose the latter, as performance wasn't a concern, but adding more graphics cards was)
- Dynamically assigning keyboards/mice to different screens based on a common USB host... sucks. SystemD manages sessions and integrates with udev so a hotplugged USB devices can be limited to it's associated session. Seriously awesome.
- The above is doubly a problem as when a usb peripheral disconnects momentarily, an X session forgets about it and never sees it again... Fixed by following what was happening with GDB, putting together an awful hack, and nuking X updates from the package system.
- All users sessions run on the same virtual terminal. I'd often ssh into the system to maintain it rather than my usual ctrl+alt+F1
- Documentation is erratic and frequently wrong.
- What I have works, but I would not deploy it to someone else's work environment
All that badness aside, I do appreciate only having to maintain one machine for software updates etc, not having to setup network shares, or worry about users logging in with NFS + LDAP. It made it quite easy for 4 people to share a powerful machine that they only needed the speed from on occasion, and collaboration was super simple.
I look forward to rebuilding this setup with pure SystemD + Wayland in the next 18-24 months.