X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-3.7 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,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: <5025C431.7050201@cygwin.com> References: <5025C431 DOT 7050201 AT cygwin DOT com> Date: Sun, 12 Aug 2012 11:07:00 +0200 Message-ID: Subject: Re: Side-by-side configuration is incorrect reported as permission denied From: Pawel Jasinski To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com 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. 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. Cheers, Pawel -- 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