X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	q=dns; s=default; b=DFhoCBpHATFa4RXAQWbucNZ+UOkgkiDMH4HztcgNKLE
	5IB3mW5gWKZs7rDMhMQJq/Vod9qZawJLdq8i4Mt2NNH/+X6RnwqnTkvvvZsN/6Sk
	TI819TzHw3CxcfgfYPqpDoovLm0Bb1vEeRftM5ULYoYDMI9CROYzWcUIDu2XSJQ8
	=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	s=default; bh=dNFWhNffhhHrd2OJvqXHvfD0cEI=; b=uzwJkioBTLqNamU17
	gfop8KQgF+MRfuCSyxt/5WGGxmf5jYT5Etb8dYzqZYm0l3oHvZqdS14TiTbkIm/0
	k82Wk5p7m15CbSgsQNph1+AnDGBdUR52zuhroBaPvx/ttO3JSNdXKLfDvht87/lp
	k+sGmmIehG189DEPpdsWR4g1og=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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-Spam-SWARE-Status:	No, score=-3.8 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_NO,RCVD_IN_HOSTKARMA_YE,SPF_PASS autolearn=ham version=3.3.1
Message-ID:	<51C213B4.1030503@cwilson.fastmail.fm>
Date:	Wed, 19 Jun 2013 16:25:24 -0400
From:	Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm>
User-Agent:	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version:	1.0
To:	The Cygwin Mailing List <cygwin AT cygwin DOT com>
Subject:	Re: Adding MSYS functionality to Cygwin
References:	<CABEPuQJDLjtbcLig1isTUJgb6RBCD8LNShbm9mTPcb9WM5S5fw AT mail DOT gmail DOT com> <51C0B08E DOT 8080900 AT etr-usa DOT com> <CABEPuQJJpRfPKSwZ7M0eTOdp1HxDcmvuy1=qXFHBw-8kLkZ1ZQ AT mail DOT gmail DOT com> <51C0D956 DOT 4090905 AT etr-usa DOT com> <20130619020234 DOT GA3669 AT ednor DOT casa DOT cgf DOT cx> <51C1EAA3 DOT 6040307 AT etr-usa DOT com> <20130619174514 DOT GA6071 AT ednor DOT casa DOT cgf DOT cx>
In-Reply-To:	<20130619174514.GA6071@ednor.casa.cgf.cx>

On 6/19/2013 1:45 PM, Christopher Faylor wrote:
> I'm talking about providing hooks so that an add-on MSYS dll could
> modify the windows command-line.  Then we wouldn't care what MSYS does
> with the command-line since it isn't a Cygwin DLL decision.  The goal is
> to allow a small DLL to hook into Cygwin and do whatever MSYS wants to
> do.
>
> Something like:
>
> callout (CO_EXEC, &command_line);
>
> Where it is expected that the command line could be modified.

Interesting. Obviously, there's more to a "complete" MSYS 
replacement/reimplementation, but cmd-line manipulation for exec'ing 
native apps is really the biggest MSYS-ism of the bunch.

I assume that, eventually and as-needed, a *small* number of additional 
"hooks" could be added to other code paths than exec/spawn/etc -- such 
as the aforementioned uname(3) thing. (One of the "deltas" between 
cygwin and msys was msys used a really stupid ownership/permission model 
-- pretend current user owns everything; check the DOS R/O bit for +w; 
check the file extension for +x; -- but this can be approximated with 
existing $CYGWIN entries or mount options. I think. So reimplementing 
that "feature" of MSYS would not require any additional hooks).

> The goal would be to collapse the fork back into Cygwin
> with minimal cost to the Cygwin DLL.

+1 <g>

--
Chuck



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -