Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Sat, 24 Feb 2001 13:49:54 -0800 Message-Id: <200102242149.f1OLns802613@quickmonkey.com> From: MADHU To: cgf AT redhat DOT com CC: cygwin AT cygwin DOT com In-reply-to: <20010224164002.B6385@redhat.com> (message from Chris Faylor on Sat, 24 Feb 2001 16:40:02 -0500) Subject: Re: cygwin with sockscap32 X-Url: http://www.meer.net/~enometh/ Reply-to: madhu AT quickmonkey DOT com X-Attribution: Madhu References: <200102222041 DOT f1MKfKj29110 AT quickmonkey DOT com> <20010224164002 DOT B6385 AT redhat DOT com> MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII 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 |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'" Subject: Re: cygwin with sockscap32 From: Christopher Faylor 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