Talk:X display manager (program type)
|This is the talk page for discussing improvements to the X display manager (program type) article.|
|WikiProject Free Software / Software / Computing||(Rated Start-class, Low-importance)|
|WikiProject Computing||(Rated Start-class, Low-importance)|
Rename: Session Manager
I impudently suggest that this type of program be renamed: Session Manager, since that is what is does: it initiates and manages sessions of different users. And while we are at it, Display server could also get a better name (because it also handles the input from evdev and not just the ouput to framebuffer), but I haven't come up with one yet (UserInteractionCore and MainUserInterfaceThingy are not better names).
Now jokes aside, the X (version 11) (a.k.a. X11) - display server - protocol is about to be replaced with the Wayland - display server - protocol. Some existing (X) window managers, like KWin and Mutter are on the way in becoming wayland compositors. Since the session manager a.k.a. the X display manager will likely also have to be ported from X11 to Wayland (I am assuming that because of the "X" in the naming), should the article be renamed and should we create a different article? ScotXW (talk) 20:15, 22 August 2013 (UTC)
The session manager is started by the display manager. They are completely different. Also the window manager is not a display manager. None of these concepts directly translate to wayland.184.108.40.206 (talk) 23:56, 29 September 2015 (UTC)
I understand why the merge has been proposed: as the articles currently stand, XDM contains little that is not in X window manager. However, it seems that other window managers have their own articles, and that the XDM article could possibly be expanded. I therefore disagree with the merge. - Liberatore(T) 09:17, 21 December 2005 (UTC)
I also oppose merging as the display manager has nothing in common with the window manager. The biggest difference is that the window manager is a user task and the display manager is a system task. 220.127.116.11 (talk) 23:59, 29 September 2015 (UTC)
Move discussion in process
This article is confusing.
One cannot move from using the word "server" to "Xserver" in the description.
Servers must have clients. Roles of servers and clients can alternate, but they should be clear.
An Xserver is a daemon/service running on which machine? What other daemons are running and where? What other clients are running and where?
Connections across remote media, using TCP/IP for e.g. must be clear.
The only people who will understand this article are experts who already understand.
It needs to be clearly explained as it is both crucial and complex. How else can we get interactions with Operating Systems without GUI consoles? In the future Cloud Technologies, it will become absolutely essential to have good remote GUIs. —Preceding unsigned comment added by 18.104.22.168 (talk) 14:53, 20 July 2010 (UTC)
Some of the Negatives are Incorrect
Some of the negatives are either ancient news or due to xdm / xdmcp misconfiguration (and unix networking mis-configuration). Note for passwords XDM uses pam(1) or login(1) and it can't be intercepted locally - only if you use X to transport over a remote connection. XDM always uses a DES encryption for the key for X. Yea X is a standard unix networking app and like any should be either openssl secured or configured or ssh secured. But it's not a big deal for most people what XDM and X do is good enough without the extra site-specific security configuration headaches. —Preceding unsigned comment added by 22.214.171.124 (talk) 10:58, 28 February 2011 (UTC)