From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5531 invoked by alias); 12 Aug 2012 09:07:23 -0000 Received: (qmail 5521 invoked by uid 22791); 12 Aug 2012 09:07:22 -0000 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 Received: from mail-ob0-f171.google.com (HELO mail-ob0-f171.google.com) (209.85.214.171) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 12 Aug 2012 09:07:01 +0000 Received: by obqv19 with SMTP id v19so5203125obq.2 for ; Sun, 12 Aug 2012 02:07:01 -0700 (PDT) MIME-Version: 1.0 Received: by 10.182.49.7 with SMTP id q7mr5760669obn.68.1344762421074; Sun, 12 Aug 2012 02:07:01 -0700 (PDT) Received: by 10.182.22.166 with HTTP; Sun, 12 Aug 2012 02:07:00 -0700 (PDT) In-Reply-To: <5025C431.7050201@cygwin.com> References: <5025C431.7050201@cygwin.com> Date: Sun, 12 Aug 2012 12:35:00 -0000 Message-ID: Subject: Re: Side-by-side configuration is incorrect reported as permission denied From: Pawel Jasinski To: cygwin@cygwin.com Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2012-08/txt/msg00251.txt.bz2 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