Naveed Hasan wrote:
Editing the XWin.exe 6.8.2.0-4 binary for fun and profit.
http://www.cs.columbia.edu/~naveed/CygwinX
While I can appreciate that building X11 from source might be difficult
and painful, this is really not a good solution at all.
Most importantly, this won't fix the bug in
Brian Dessent wrote:
Additionally, you are violating the GPL because you offer binaries with
Er, sorry... X11 isn't GPL, my fault. I fired off without thinking...
like I said, it's a pretty common occurance.
Brian
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem
On Wed, 17 May 2006, Brian Dessent wrote:
Brian Dessent wrote:
Additionally, you are violating the GPL because you offer binaries with
Er, sorry... X11 isn't GPL, my fault. I fired off without thinking...
like I said, it's a pretty common occurance.
otoh, some people on this list choose
Editing the XWin.exe 6.8.2.0-4 binary for fun and profit.
http://www.cs.columbia.edu/~naveed/CygwinX
Naveed
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:
Brian Willis wrote:
Corinna Vinschen wrote:
On May 18 10:35, Brian Willis wrote:
Is there any way to make the X server listen on loopback but not on
the outside interface? The firewall software does all interfaces,
not just the outside.
That would be a surprise. Are you using the XP SP2
On Thu, 19 May 2005, Brian Willis wrote:
Is there any way to get Cygwin to listen on only localhost?
No.
I thought the -nolisten tcp was supposed to do this.
-nolisten tcp disables tcp completely
bye
ago
--
[EMAIL PROTECTED]
http://www.gotti.org ICQ: 126018723
On Wed, 18 May 2005, Brian Willis wrote:
I'm trying to turn off the tcp port for Cygwin/X. I would like to just
close it down on the outside interface and still have it listen on the
loopback device. I have not been able to find a way to do that. The
closest thing I could find is to
Alexander Gottwald wrote:
On Wed, 18 May 2005, Brian Willis wrote:
I'm trying to turn off the tcp port for Cygwin/X. I would like to just
close it down on the outside interface and still have it listen on the
loopback device. I have not been able to find a way to do that. The
closest thing
Corinna Vinschen wrote:
On May 18 10:35, Brian Willis wrote:
Is there any way to make the X server listen on loopback but not on the
outside interface? The firewall software does all interfaces, not just
the outside.
That would be a surprise. Are you using the XP SP2 firewall by any
chance?
