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 Message-ID: <4061FC16.7030102@scytek.de> Date: Wed, 24 Mar 2004 16:22:30 -0500 From: Volker Quetschke User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031205 Thunderbird/0.4 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: lstat on FAT - Was: Problem with find on FAT drives References: <4060B627 DOT 8000400 AT scytek DOT de> <20040324155332 DOT GF17229 AT cygbert DOT vinschen DOT de> <4061E702 DOT 1040705 AT scytek DOT de> <20040324205644 DOT GA4580 AT redhat DOT com> In-Reply-To: <20040324205644.GA4580@redhat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.39 X-IsSubscribed: yes Hi! Sorry, I just have to ask this, see below. >>>>So again, is this an expected/tolerated behaviour? >>> >>>Yes, it's by design. The answer is "don't use DOS paths". >> >>It's nice to be mean, isn't it? > > How about some clarification: "Don't use DOS paths if you want > consistent i-nodes?" > > You're welcome to use DOS paths if you want. You just can't expect > UNIX-style behavior from them. Did you read that mail to the end? It contained a full analysis of the problem and even a patch. It is just a small unconsistency that is easily fixable, I didn't fully check if my changing of isslash() does some harm, if it does the inode problem is still fixable. Again, see my ananlysis. Would you in principle preject a patch that fixes the inode behaviour on non NTFS drives? Volker -- PGP/GPG key (ID: 0x9F8A785D) available from wwwkeys.de.pgp.net key-fingerprint 550D F17E B082 A3E9 F913 9E53 3D35 C9BA 9F8A 785D -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/