X-Spam-Check-By: sourceware.org Date: Tue, 25 Apr 2006 09:50:35 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Call for testing Cygwin snapshot Message-ID: <20060425075035.GJ28583@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20060424181242 DOT GA5783 AT calimero DOT vinschen DOT de> <444DA8C5 DOT 6030105 AT cwilson DOT fastmail DOT fm> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <444DA8C5.6030105@cwilson.fastmail.fm> User-Agent: Mutt/1.4.2i Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk 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 On Apr 25 00:42, Charles Wilson wrote: > Corinna Vinschen wrote: > > >- Reintroducing the dirent member d_ino. 1.5.20 tries hard to return a > > useful d_ino value, which is supposed to be also the same as st_ino as > > returned by stat(2) in all cases, regardless of the obstacles to do > > this on Windows. Do you have strange file systems like HPFS or > > ClearCase? > > I'll take a look at this w.r.t clearcase. How exactly should I test -- > what am I looking for? Just a little app that compares dirent.d_ino and > stat.st_ino for a specified file on the strange filesystem? Thanks for the offer. Can you please send the output of the tiny tool I mailed in http://sourceware.org/ml/cygwin/2006-01/msg00818.html? Other than that, yes, a bit of comparison between d_ino and st_ino of would be helpful. You could use the tool I posted in http://sourceware.org/ml/cygwin/2006-04/msg00314.html. Just keep in mind that it has to be build using the sys/dirent.h header from the snapshots. Another important factor is, if the underlying filesystem tends to change the inode number between subsequent calls. You can either compare the inode numbers using the above tool, or you can see if you encounter the dreaded "cp: skipping file 'foo', as it was replaced while being copied" problem. > Do I only care about the lower 32 bits, or all 64? The whole 64 bit inode number is important. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/