X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-1.9 required=5.0	tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE
X-Spam-Check-By: sourceware.org
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX1+5Gh3cVC8tv0wr7M0AM5oD
Date: Sun, 12 Aug 2012 16:54:07 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Side-by-side configuration is incorrect reported as permission denied
Message-ID: <20120812205407.GA7337@ednor.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <k045k2$gvk$1@dough.gmane.org> <5025C431.7050201@cygwin.com> <CA+7connXxSSkw-fhHvqbVanEvX7YHOVVdLndmqmd07xRvFT49Q@mail.gmail.com> <20120812170641.GC32748@ednor.casa.cgf.cx> <CA+7conm=AXUX9Xfj67tGRgMbrgC47W9QHuQ2L3V2p_=7Cf81GQ@mail.gmail.com> <CA+sc5m=myjskB4zG0HARWHvZMQGz-k=j7jT=q1Gny4XpNgMfCg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CA+sc5m=myjskB4zG0HARWHvZMQGz-k=j7jT=q1Gny4XpNgMfCg@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@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

On Sun, Aug 12, 2012 at 04:35:23PM -0400, Earnie Boyd wrote:
>On Sun, Aug 12, 2012 at 1:56 PM, Pawel Jasinski wrote:
>>>If you can find a nice Linux errno which maps from
>>>ERROR_SXS_CANT_GEN_ACTCTX to something other than EACCES I'd be happy
>>>to change Cygwin.
>>
>>Sorry I was not clear.  The point was not to use linux error code.
>>what I was trying to say is linux does not follow POSIX only error
>>codes policy.  Such a policy is impractical.  Your point was POSIX
>>only, wasn't it?  You can add cygwin specific error codes.
>
>Cygwin doesn't have the access required to execute the process because
>of some reason.  It is up to you to examine the reason.  Why should we
>be bothered with anything other than EACCESS?  When you reported the
>issue the first action you took was to determine why you couldn't
>execute a Windows program.  That was the correct action, hammering this
>list with your wishes isn't gaining you sympathy from those that use
>and support it.

Actually, it was Andrew Defaria who wanted it but, yeah, I think I've
personally devoted more time to this than the issue warrants.

I've asked Corinna privately if she has any ideas or concerns but I
would be surprised if this was something that she thought important
to address.

If someone has a patch they want to propose they should send it to
cygwin-patches, bearing in mind that we don't want to break any
existing applications.

cgf

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

