Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!decwrl!labrea!aurora!eos!ames!pasteur!cory.Berkeley.EDU!leres
From: leres@cory.Berkeley.EDU (Craig Leres)
Newsgroups: comp.windows.x
Subject: Re: unix:0
Message-ID: <1061@pasteur.Berkeley.Edu>
Date: 27 Feb 88 04:32:35 GMT
References: <290@bacchus.DEC.COM> <5286@well.UUCP>
Sender: news@pasteur.Berkeley.Edu
Reply-To: leres@ucbarpa.Berkeley.EDU (Craig Leres)
Lines: 16

In the referenced message, pokey@well.UUCP (The Party Commander) wrote:
> works instead.  Of course, my reason was a little different -- I wanted to
> be able to use the same DISPLAY setting for both BSD and SysV systems.
> But it's not very likely that anyone would have a machine named "localhost",

You can certainly use "localhost:0" instead of "unix:0", but this will
cause you to use an internet domain socket instead of a Unix domain
socket to talk to the X server. And an internet socket to localhost
isn't always as fast as a Unix domain socket. A better solution is to
make "unix:0" mean "localhost:0" on systems that don't have Unix domain
sockets.

Also, "localhost" is the internet name of the current host. So anyone
with Unix system with internet code has a machine named "localhost".

		Craig