Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Mon, 17 Jun 2002 13:00:00 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: [Fwd: Re: Newbie: How to get permissions working with 'ntsec'] Message-ID: <20020617130000.X30892@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <3D0C8E93 DOT 2020601 AT scytek DOT de> <002801c2154e$cb5876c0$a300a8c0 AT nhv> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <002801c2154e$cb5876c0$a300a8c0@nhv> User-Agent: Mutt/1.3.22.1i On Sun, Jun 16, 2002 at 11:59:26AM -0400, Norman Vine wrote: > >> CYGWIN = `ntsec ntea check_case:strict' > > can ntsec and ntea be used together ?? ntsec overrides ntea on NTFS, ntea will still work on FAT, though. I suggest to switch ntea off. It creates a special file on FAT filesystems which grows more and more and which can't be deleted with simple operations. I suggest not to use check_case:strict, too. We created it for a customer. Case checking is only implemented inside of the path evalutaion routines in Cygwin. The underlying filesystems are still only case preserving. You will run into problems which are pretty hard to track down as a user. If you like checking the case, at least switch to check_case:adjust which is somewhat less nitpicking. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/