Basically because of the knock on effects, which I view as
unnecessary if the
slight variation I described was chosen. A new DISPLAY format only
needed to be
defined because the chosen approached added a new socket, but the
new socket
provides nothing that could not be achieved with the existing socket.
One could argue about the knock one effects, i.e. that other
programs should
not be parsing DISPLAY outwith of the X trans library, but they
are. So now
there are patches for ssh to handle the new DISPLAY format, and
similarly
patches to xauth.
I _think_ it could all have been hidden within the trans library
without any
need for a new type/name of socket, and so no externally visible
change.
At worst it would have been specialised code in the Xserver, and
something wrt
launchd (i.e. does one just hardcode the "/tmp/.X11-unix/:%d"
pattern in
to it, or try to use some form of helper / decoupling?).
I'd certainly be willing to hack up how I think it should be done,
but then
I'm still on tiger. (I need to get the server compiling anyway), I
_believe_
the launchd source is public?
All you have to do is edit org.x.X11.plist. Where you see the line,
and you have it listening to the standard socket. I've already
mentioned this is possible. And can you identify a program that is
actually relying on the assumption that the socket is there?
--
Andrew J. Hesford <email@hidden>
Department of Electrical and Computer Engineering
University of Illinois at Urbana-Champaign
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/x11-users/email@hidden
