X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=0.8 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KAM_THEBAT,KHOP_THREADED,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Date: Fri, 17 Aug 2012 17:05:16 +0400 From: Andrey Repin Reply-To: Andrey Repin Message-ID: <1911778469.20120817170516@mtu-net.ru> To: Corinna Vinschen Subject: Re: Options for getting mandatory locking in cygwin1.dll (was: Promote sqlite 3.7.13-1 from test status?) In-Reply-To: <20120817093737.GB26407@calimero.vinschen.de> References: <502C0B7D DOT 10909 AT etr-usa DOT com> <20120816085016 DOT GB5536 AT calimero DOT vinschen DOT de> <502CCBB1 DOT 2070600 AT etr-usa DOT com> <20120816105507 DOT GD17546 AT calimero DOT vinschen DOT de> <502CE120 DOT 4050900 AT etr-usa DOT com> <20120816122654 DOT GG17546 AT calimero DOT vinschen DOT de> <502D4F2F DOT 5080306 AT etr-usa DOT com> <20120817093737 DOT GB26407 AT calimero DOT vinschen DOT de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 Greetings, Corinna Vinschen! > A "mand" mount option sounds like a really interesting idea, together > with the special group permission settings as described in the Linux > fcntl(2) man page. Maybe we can even relax that by making the "mand" > option the default setting, so the correct file permissions would be > the only requirement by default. Ok, this also requires to use a > filesystem with real file permissions, so FAT or "noacl" mounted > filesystems are out of th question, but I can live with that just fine. Sorry byt I can't live with it. Setting "noacl" mounts aside from "mand" will force me to choose one or another. And it wouldn't be a choice in Cygwin's favor. Forced use of POSIX'ised permissions have higher probability of breaking existing Windows applications, than using POSIX "suggestive" locks instead of appropriate strict locks could harm Cygwin applications. > The problem with this approach is a non-technical one: In the next > couple of months I have probably no time to implement it. It's not > overly tricky to implement it, as far as I can see, but, as usual, > somebody has to do it. So if anybody would like to take a stab at > it... -- WBR, Andrey Repin (anrdaemon AT freemail DOT ru) 17.08.2012, <17:01> Sorry for my terrible english... -- 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