X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-5.4 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE
X-Spam-Check-By:	sourceware.org
MIME-Version:	1.0
In-Reply-To:	<CA+7conm=AXUX9Xfj67tGRgMbrgC47W9QHuQ2L3V2p_=7Cf81GQ@mail.gmail.com>
References:	<k045k2$gvk$1 AT dough DOT gmane DOT org> <5025C431 DOT 7050201 AT cygwin DOT com> <CA+7connXxSSkw-fhHvqbVanEvX7YHOVVdLndmqmd07xRvFT49Q AT mail DOT gmail DOT com> <20120812170641 DOT GC32748 AT ednor DOT casa DOT cgf DOT cx> <CA+7conm=AXUX9Xfj67tGRgMbrgC47W9QHuQ2L3V2p_=7Cf81GQ AT mail DOT gmail DOT com>
Date:	Sun, 12 Aug 2012 16:35:23 -0400
Message-ID:	<CA+sc5m=myjskB4zG0HARWHvZMQGz-k=j7jT=q1Gny4XpNgMfCg@mail.gmail.com>
Subject:	Re: Side-by-side configuration is incorrect reported as permission denied
From:	Earnie Boyd <earnie AT users DOT sourceforge DOT net>
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

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.

-- 
Earnie
-- https://sites.google.com/site/earnieboyd

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