Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Injected-Via-Gmane: http://gmane.org/
To: cygwin AT cygwin DOT com
From: John Williams <jwilliams AT itee DOT uq DOT edu DOT au>
Subject: Re: Obtaining a pervious version
Date: Tue, 18 Feb 2003 13:43:27 +1000
Lines: 24
Message-ID: <3E51ABDF.4020707@itee.uq.edu.au>
References: <001401c2d6d0$6102a4a0$78d96f83 AT pomello> <3E5163E3 DOT 7000605 AT itee DOT uq DOT edu DOT au> <001701c2d6d6$403696e0$78d96f83 AT pomello> <20030217224649 DOT GA18908 AT redhat DOT com> <3E516C10 DOT 8050309 AT itee DOT uq DOT edu DOT au> <003101c2d6da$adc26cd0$78d96f83 AT pomello> <20030217233207 DOT GA18885 AT redhat DOT com> <20030217233946 DOT GB18885 AT redhat DOT com> <3E517569 DOT 1060800 AT itee DOT uq DOT edu DOT au> <002d01c2d6e1$2265d580$78d96f83 AT pomello> <20030218033542 DOT GE18885 AT redhat DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet AT main DOT gmane DOT org
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.9) Gecko/20020311
X-Accept-Language: en-us, en

Christopher Faylor wrote:
> The sources available for download are for 1.3.2.  The differences are
> below.  Basically, it seems like they made a few changes without really
> thinking too hard about what they did.  So, the cygwin mount table will
> be found in another registry entry but it will end up in the same shared
> memory region.
> 
> Reading further in the thread, I see that there was an accommodation of
> sorts.  I want to point out that it should be possible to build any
> of the tools that you're using under cygwin.  IMO, that's the best
> solution to this.
> 
> In fact, it should be possible to just binary edit the tools and change
> the 'xygwin1.dll' to 'cygwin1.dll'.  Then you can just get rid of the
> xygwin1.dll crap entirely.

Thanks for that - I'll pass it on to the developers.  I expect they'd 
probably rather focus on supporting their tools anyway, instead of a 
non-standard compatibility layer.

Cheers,

John



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/