On Mon, Nov 19, 2007 at 08:48:59AM -0600, Andrew J. Hesford wrote:
> On Nov 19, 2007, at 6:05 AM, Derek Fawcus wrote:
>
> All you have to do is edit org.x.X11.plist. Where you see the line,
> <dict><key>SecureSocketWithKey</key><string>DISPLAY</string></dict>
> just change it to
>
> <dict><key>SockPathName</key><string>/tmp/.X11-unix/:0</string></dict>
> and you have it listening to the standard socket.
(well I can't since I don't have 10.5 yet :-)
> 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?
Off the top of my head no. But code is relying upon being able to parse DISPLAY.
But if the above edit achieves the same startup behaviour as that shipped with 10.5,
one has to ask _why_ did 10.5 use a new socket?
What is _gained_ my using an alternate socket, that could not have been achieved
without it. Similarly what is _gained_ by defining a new interpretation for DISPLAY,
that could not have been hidden in the x11 transport library?
So far all I can see is that two other programs (xauth, ssh) had to be updated
to cope with the new DISPLAY contents.
DF
_______________________________________________
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
This email sent to email@hidden
