Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
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 17:51:37 -0500
From: Chris Faylor <cgf AT redhat DOT com>
To: MADHU <madhu AT quickmonkey DOT com>
Cc: cygwin AT cygwin DOT com
Subject: Re: cygwin with sockscap32
Message-ID: <20010224175137.A6846@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: MADHU <madhu AT quickmonkey DOT com>, cygwin AT cygwin DOT com
References: <200102222041 DOT f1MKfKj29110 AT quickmonkey DOT com> <20010224164002 DOT B6385 AT redhat DOT com> <200102242149 DOT f1OLns802613 AT quickmonkey DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.11i
In-Reply-To: <200102242149.f1OLns802613@quickmonkey.com>; from madhu@quickmonkey.com on Sat, Feb 24, 2001 at 01:49:54PM -0800

On Sat, Feb 24, 2001 at 01:49:54PM -0800, MADHU wrote:
>You may choose to igmore the problem, as you have, and hope it goes
yaway, 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.

I am sorry but I'm not going to honor your appreciation, especially since
you saw fit to forward private email to the public cygwin list.

What I sent was not a rant.  It was an observation.  If something stops
working between B20 and 1.1.x it does not necessarily indicate that there
is a bug in 1.1.x.

However, the only way the problem is going to be narrowed down is if
you, or someone, debugs sockscap.  The sources *must* be available given
Cygwin's licensing agreement.

If they are not available then this is certainly off-topic for this
mailing list and moreover, is actually illegal.

In my opinion, the facts that you have provided so far do not offer
enough details to allow anyone to debug your problem.  That leaves the
burden on you to either provide more facts or debug the problem yourself.
Given that I haven't seen any sockscap experts stepping forward to offer
in-depth insight, I fear that the burden of debugging this problem may
be yours.

Christopher Faylor
Cygwin Engineering Manager
Red Hat, Inc.

>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]
>

-- 
cgf AT cygnus DOT com                        Red Hat, Inc.
http://sources.redhat.com/            http://www.redhat.com/

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple