Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!decwrl!karlton
From: karlton@decwrl.dec.com (Philip Karlton)
Newsgroups: comp.windows.x
Subject: Re: unix:0
Message-ID: <302@bacchus.DEC.COM>
Date: 29 Feb 88 16:40:49 GMT
References: <2371@umd5.umd.edu> <5334@well.UUCP>
Reply-To: karlton@decwrl.UUCP (Philip Karlton)
Organization: DEC Western Software Lab, Palo Alto, CA
Lines: 13

In article <5334@well.UUCP> pokey@well.UUCP (Jef Poskanzer) writes:
>
>Yes, this solves Phil's problem of not being able to access a machine
>called unix.  But it does nothing for my problem of wanting to use the
>same DISPLAY string for local access on both SysV and BSD machines.
>I don't see how I can do that without hacking code.

I am confused. Why not just use ":0" to mean "use the most efficient means of
talking to the local host"? For BSD based systems, this will probably be a
UNIX domain socket. For those that have implemented a shared memory
communicaiton channel, that will be used.

PK