From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7655 invoked by alias); 19 Jun 2013 20:25:29 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 7645 invoked by uid 89); 19 Jun 2013 20:25:29 -0000 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 Received: from out4-smtp.messagingengine.com (HELO out4-smtp.messagingengine.com) (66.111.4.28) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Wed, 19 Jun 2013 20:25:27 +0000 Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 9FDE72093E for ; Wed, 19 Jun 2013 16:25:25 -0400 (EDT) Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute6.internal (MEProxy); Wed, 19 Jun 2013 16:25:25 -0400 Received: from [158.147.137.183] (unknown [158.147.137.183]) by mail.messagingengine.com (Postfix) with ESMTPA id 60A00C00E83; Wed, 19 Jun 2013 16:25:25 -0400 (EDT) Message-ID: <51C213B4.1030503@cwilson.fastmail.fm> Date: Thu, 20 Jun 2013 03:30:00 -0000 From: Charles Wilson 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 Subject: Re: Adding MSYS functionality to Cygwin References: <51C0B08E.8080900@etr-usa.com> <51C0D956.4090905@etr-usa.com> <20130619020234.GA3669@ednor.casa.cgf.cx> <51C1EAA3.6040307@etr-usa.com> <20130619174514.GA6071@ednor.casa.cgf.cx> In-Reply-To: <20130619174514.GA6071@ednor.casa.cgf.cx> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2013-06/txt/msg00520.txt.bz2 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 -- 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