On Wednesday, August 2, 2017 3:17:37 AM EDT Lennart Poettering wrote: > On Di, 01.08.17 19:32, nerdopolis (bluescreen_aven...@verizon.net) wrote: > > > On Tuesday, August 1, 2017 3:00:25 AM EDT Lennart Poettering wrote: > > > On Mo, 31.07.17 21:24, nerdopolis (bluescreen_aven...@verizon.net) wrote: > > > > > > > > > First, when I attach a 2nd graphics card to seat1, it seems > > > > > > CanMultisession is > > > > > > set to 0. Is there a way to change that? or is that only supported > > > > > > on seat0, > > > > > > that supports the TTYs? > > > > > > > > > > Yes, this is only supported where VTs are supported, and that is > > > > > only seat0. > > > > > > > > Thanks, It's currently a kernel limitation I assume? I guess I'll worry > > > > about > > > > multiple sessions on non seat0 seats when it _is_ supported. > > > > > > Yeah the VCs are drawn by the kernel, hence doing multi-session on > > > other but the first seat would mean either updating the kernel or > > > doing something purely in userspace with a userspace terminal > > > renderer. David Hermann was working on something like this, but he > > > lost interest. > > > > > > Lennart > > > > > > > > Out of curiosity, what would the likes of Weston, X, and other Display > > Servers > > need on seats outside of seat0? A device to set KD_GRAPHICS on, like a > > special > > type of pty or something? > > Nah. Graphical display managers just need a set of DRM and input > devices to operate on, they require no VTs, ttys, ptys or anything. > > Lennart > >
Thanks, I was wondering what would be needed from the kernel, and/or user space to be able to run two Display Servers on seat1/seat-1, and switch between them though? _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel