Info on "Can't open display"

[Christopher Faylor]

On Fri, Jun 15, 2001 at 09:34:22PM -0400, Suhaib Siddiqi wrote:
>
>> You will lose fork() support for sockets if you use winsock32 directly.
>
>
>I know.  What I want to see if this display problem goes away with it.
>I know it is not the best way.
>
>> I'm much more keen on identifying why the problem occurs - we can
>> probably solve it quickly inside cygwin1.dll once we know that.
>
>Can anyone build a debug version of Cygwin1.dll with the Egor Duda patch he
>posted this morning?  I do not have time to fool around with Cygwin code.

I'm sure everyone knows this, but Egor's patch was just a temporary
commenting out of some AF_UNIX security code.  It wasn't a real "fix".
So, don't get too excited if things start working for you after applying
the patch.

cgf