X-Recipient: archive-cygwin@delorie.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=ioqlKnOnEBZjsEnisiODaWr7HxHz3GNOJjXpZAWP/fX
	ZxDw8ebNe5wb5lLNpnMxdXIi06CV/HLHxQXwJy6GplHaUoTZBu2YwLjkxVqzLxRV
	zeflSk2DpvtNcOxdJzZb5ugCR8AXIqF1zYVcOsqba1SrFntI1IRmbpksKjIULsXE
	=
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=IDDYj7Y8qQDhMP3yiHf1Hp1Tu+I=; b=ceAGAy46YwVLNeSki
	DVJnW1MfR4ArGV6PCOuQoByp6i7AD4c9I6sUtHiNV3XkdywBHDtNXGSMsKj/sNfP
	KqFVHl9yfqWy1wVcOZfZsK35BUO7YYA9n11vh3zpKuxqxsRbwCXcyEFk3KZHtlys
	kytxL14LsKWAu6CJxv4eSj0F/8=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2
X-HELO: vms173025pub.verizon.net
Message-id: <540A600A.6090201@verizon.net>
Date: Fri, 05 Sep 2014 21:14:50 -0400
From: Gerry Reno <greno@verizon.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7
MIME-version: 1.0
To: cygwin@cygwin.com
Subject: Re: latest cygwin: 'run' problem
References: <5405C013.7030503@verizon.net> <87a96hrki4.fsf@Rainer.invalid> <54060378.2070108@gmail.com> <5406680D.4030105@verizon.net> <540761FA.1040902@verizon.net> <87ppfcqyc7.fsf@Rainer.invalid>
In-reply-to: <87ppfcqyc7.fsf@Rainer.invalid>
Content-type: text/plain; charset=UTF-8
Content-transfer-encoding: 7bit
X-IsSubscribed: yes

On 09/03/2014 03:48 PM, Achim Gratz wrote:
> Gerry Reno writes:
>> On the 32-bit system cygwin installs that haven't been updated yet 'run.exe' shows:
>>
>>     $ ls -l /usr/bin/run.exe
>>     -rwxr-xr-x 1 Administrator None 65053 Jul 24  2013 /usr/bin/run.exe
>>
>> On a 32-bit system with this latest cygwin 'run.exe' shows:
>>
>>     $ ls -l /usr/bin/run.exe
>>     -rwxr-xr-x 1 SYSTEM SYSTEM 66077 Jun  9 13:16 /usr/bin/run.exe
>>
>> Filesize is different so something has changed there.
> A "cygcheck -f /usr/bin/run.exe" would be more enlightening, although I
> think the two versions of run should be 1.3.0 and 1.3.1.  If so then the
> reason for mstsc not recognizing the options would be the patch by Max
> Polk that quotes all the arguments (the change description said it'd
> quote only arguments with spaces in them, but the code actually quotes
> all of them anyway).  This also means that mstsc seems to implement its
> own version of options processing or argument quoting (probably the
> former since options to mstsc need not be quoted).  The quoting function
> in the current version of run is too naive anyway, so I'll have to
> update it with something more sensible.  It'll be a few days, sorry for
> the inconvenience.
>
>
> Regards,
> Achim.

Can run-1.3.0-1 be added back into the Setup as an alternate choice until 'run' can be fixed?

Gerry


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

