> On Wed, 24 Sep 1997, Christos Zoulas wrote:
> 
> > In article <XFMail.970924080356.root@garbled.futureone.com> root@garbled.futureone.com (Tim Rightnour) writes:
> > >I've had a number of problems with Solaris x86 compat and FreeBSD
> > >compatability..  I had access to a solaris machine for awhile, and grabbed the
> > >entire lib dir off it and installed it..  Normal bins ran just fine, however,
> > >Xwindows programs (for solaris) would not, because they expect a local socket
> > >while NetBSD XFree86 runs off a unix domain..  I never did figure out a way
> > >around this one..  The FreeBSD problem was similar, where it looked for some
> > >obscure library reference.. I think I could have overcome the FreeBSD problem
> > >by installing the xlibs for FreeBSD into the emul dir.. but the solaris problem
> > >was totally beyond me.
> > 
> > set your DISPLAY to be hostname:<screen>, so that you don't use the AF_UNIX
> > socket, but an AF_INET connection.
> 
> Would localhost:<screen> be any better?
> 
> At what point in the IP stack will hostname:<screen> transmissions get
> turned around? After they go out on the wire?
> 
> Take care,
> 
> Bill
> 

a possibility, possibly worth less than the bytes to write it:

I think I've heard rumors that some X servers are clever, and
"know" that localhost:0 really "should be" unix:0, and even that
local.domain.net:0 is really local...  Could this be an issue?

Dave