Talk:Features/ckremoval

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
Line 1: Line 1:
 
== Impact on other desktops ==
 
== Impact on other desktops ==
 
Lennart, can you tell us more about the impact on other desktops? You only mention Gnome and GDM but what is with KDE/KDM, LXDE/LXDM, Xfce other desktops? --[[User:Cwickert|Cwickert]] 21:21, 28 May 2011 (UTC)
 
Lennart, can you tell us more about the impact on other desktops? You only mention Gnome and GDM but what is with KDE/KDM, LXDE/LXDM, Xfce other desktops? --[[User:Cwickert|Cwickert]] 21:21, 28 May 2011 (UTC)
 +
 +
The new stuff and CK should be parallel installable and usable. Other desktops don't have to switch right-away, but if they did this would be good, of course. I will put up some docs eventually, explaining what to do. In most cases the code should get much simpler (since we probably can move session registration into PAM, and thus have no registration-specific CK code in the display managers anymore). The main reason why you might want to support the new stuff in your display manager natively is proper multi-seat support. --Lennart
  
 
== ZaphodHeads support ==
 
== ZaphodHeads support ==
 
In one of the Google docs linked to by this feature page, I read "gdm will spawn one X server for each video card found as they pop up, X itself should discover matching input devices."  Will this interfere with "ZaphodHeads" support?  In other words, will it still be easy to use two video cards in a single X session? --[[User:Amcnabb|Amcnabb]] 20:09, 1 June 2011 (UTC)
 
In one of the Google docs linked to by this feature page, I read "gdm will spawn one X server for each video card found as they pop up, X itself should discover matching input devices."  Will this interfere with "ZaphodHeads" support?  In other words, will it still be easy to use two video cards in a single X session? --[[User:Amcnabb|Amcnabb]] 20:09, 1 June 2011 (UTC)
 +
 +
Yes, you will if X supports that. By default all devices will be assigned to a magic "seat0" which is the implicit default seat. Only if you have special multi-seat hw any other automatic seat will be generated by default. Or you configure your seats manually. But either way, by default everything stays as it is and all hw is assigned to the main seat "seat0". --Lennart

Revision as of 07:53, 15 June 2011

Impact on other desktops

Lennart, can you tell us more about the impact on other desktops? You only mention Gnome and GDM but what is with KDE/KDM, LXDE/LXDM, Xfce other desktops? --Cwickert 21:21, 28 May 2011 (UTC)

The new stuff and CK should be parallel installable and usable. Other desktops don't have to switch right-away, but if they did this would be good, of course. I will put up some docs eventually, explaining what to do. In most cases the code should get much simpler (since we probably can move session registration into PAM, and thus have no registration-specific CK code in the display managers anymore). The main reason why you might want to support the new stuff in your display manager natively is proper multi-seat support. --Lennart

ZaphodHeads support

In one of the Google docs linked to by this feature page, I read "gdm will spawn one X server for each video card found as they pop up, X itself should discover matching input devices." Will this interfere with "ZaphodHeads" support? In other words, will it still be easy to use two video cards in a single X session? --Amcnabb 20:09, 1 June 2011 (UTC)

Yes, you will if X supports that. By default all devices will be assigned to a magic "seat0" which is the implicit default seat. Only if you have special multi-seat hw any other automatic seat will be generated by default. Or you configure your seats manually. But either way, by default everything stays as it is and all hw is assigned to the main seat "seat0". --Lennart