Mail Archives: cygwin/2001/02/24/16:52:51
You may choose to igmore the problem, as you have, and hope it goes
away, but it hasnt. cygwin is unusable with sockscap, while it was
before: because of changes to the code. I would apprecciate it if you
could keep quietif you have nothing of value to add to the discussion,
and random rants.
Thanks
Regards
madhu
|Date: Sat, 24 Feb 2001 16:40:02 -0500
|From: Chris Faylor <cgf AT redhat DOT com>
|On Thu, Feb 22, 2001 at 12:41:20PM -0800, MADHU wrote:
|>helu,
|>that is just your opinion, I was seeking a little more technical
|>explanation, and as I pointed out in my post, and my privatre response
|>to ernie boyd, ALL evidence points to a cygwin problem.
|
|It is more than an opinion. It is cold hard fact. Sorry.
|
|cgf
|
--
This is the mail archive of the cygwin AT sources DOT redhat DOT com mailing list
for the Cygwin project.
Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Re: cygwin with sockscap32
To: "'Earnie Boyd'" <cygwin at cygwin dot com>
Subject: Re: cygwin with sockscap32
From: Christopher Faylor <cgf at redhat dot com>
Date: Thu, 22 Feb 2001 13:04:55 -0500
References: <878B7E94C206D511895800A0C9F4871CD5BB19 AT xcup01 DOT cup DOT hp DOT com>
<3A954C6E DOT FF247549 AT ece DOT gatech DOT edu>
Reply-To: cygwin at cygwin dot com
On Thu, Feb 22, 2001 at 12:29:18PM -0500, Charles S. Wilson wrote:
>"MADHU,SURESH (HP-Cupertino,ex1)" wrote:
>> >> I think its a cygnus issue. Because the sockscap code has not
changed, but
>> the cygwin code has - and the sockscap source code is not as open
source as
>> the cygnus code,
>
>Yes. It is and must be -- but perhaps the sockscap owners don't
>understand that. By linking to the cygwin1.dll, the sockscap code is
>required to be open source. If you cannot obtain the source from
>them,
>then it is because the owners are VIOLATING cygwin's license.
>
>They MUST release the code -- if they don't, I'm sure Red Hat's
>lawyers
>would love to talk with them.
Yup.
Also the fact that something "worked" before and "doesn't work" after
upgrading
cygwin does *not* automatically mean that "it's a cygwin problem".
cgf
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
References:
RE: cygwin with sockscap32
From: MADHU,SURESH (HP-Cupertino,ex1)
Re: cygwin with sockscap32
From: Charles S. Wilson
Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
- Raw text -