delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT 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 AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) |
X-MHO-User: | U2FsdGVkX1+WDF1Bc3vBifKRMQ784Ps4 |
Date: | Sun, 12 Aug 2012 13:06:41 -0400 |
From: | Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com> |
To: | cygwin AT cygwin DOT com |
Subject: | Re: Side-by-side configuration is incorrect reported as permission denied |
Message-ID: | <20120812170641.GC32748@ednor.casa.cgf.cx> |
Reply-To: | cygwin AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT 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> |
MIME-Version: | 1.0 |
In-Reply-To: | <CA+7connXxSSkw-fhHvqbVanEvX7YHOVVdLndmqmd07xRvFT49Q@mail.gmail.com> |
User-Agent: | Mutt/1.5.20 (2009-06-14) |
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 11:07:00AM +0200, Pawel Jasinski wrote: >Hi, > >> >> Cygwin doesn't report Windows error codes. It reports POSIX ones. I >> have no idea why there would be a POSIX error code for side-by-side >> errors but if there were, then reporting that is more appropriate. >> > >out of curiosity I have poked into errno.h (as well as man page) on >linux and linux is easier on its users. >It uses values defined by POSIX as well as values which make sense in >context of Linux. >Would you consider relaxing your policy in respect of error codes and >POSIX where would it be a benefit for the user? > >In this particular case, all situation where errno (or a message) is >simply reported back to the user would be fine. >Only code which does errno specific attempts to recover or be clever >about it would be affected. Yes, and, what do we do with these "clever" apps? Tell them that they are out of luck because we've just pulled the rug out from under them? >At the moment I my internet access is weak, but once I am at home this >would be a grep through cygwin packages to find out such a use. Windows has 15999 error codes. Linux has ~133. Some UNIX apps which recognize errnos rely on being able to index into the "sys_errlist" array. This would mean that we would need to set up a sys_errlist array with all of these error codes, and since we already map a lot of them, come up with some way to deal with that. 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. Otherwise, no, I'm not going to worry about this issue. 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
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |