> With multi-seat (ISTR the term originated at Redhat), people started
> to re-invent what a "user session" means. In a confusingly and quite
> irritatingly new manner, mind you. So you now (yay!) can have two Gnome
> sessions. But you pay the price that a Gnome session is quite a different
> beast from an X session, with an own DBUS thingy, an own Systemd
> thingy, yadda, yadda (same goes for KDE).
AFAIK this is orthogonal to multi-seat, e.g. the above issues already
arise with multiple concurrent logins on a single-seat setup, via
virtual-consoles.
Multi-seat issues have to do with the fact that monitors, keyboards,
mouses, etc... are connected "separately", so from a hardware point of
view there's no way for the machine to know which set of devices should
be used together and which set corresponds to a "new seat".
At least, not without extra manual configuration.
Contrast this to the old TTY days where all the devices connected to
a "seat" (monitor, keyboard, occasionally mouse, even sometimes
printers) where physically connected together via a single serial port.
[ Plus the fact that multiple monitors can be connected to the same
graphics card, but if you want to use them in a "multi-seat" setup,
they each want to run a separate Xorg server yet those servers need
to share the graphics card, as you mentioned. ]
Stefan
