From: "Andrew Cottrell" To: Cc: "Richard Dawe" Subject: RE: Program to stat . before and after a chdir Date: Sun, 24 Aug 2003 10:21:49 +1000 Message-ID: <000101c369d5$b9984320$0101a8c0@acp42g> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id h7O0M5P08709 Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > Could someone try the following program on Windows 2000/XP > and post the results, please? I'm wondering if our stat is > totally broken on Windows 2000/XP with respect to reporting > inode numbers. > > If this program doesn't PASS, then I don't see how we can > expect fileutils's rm to function correctly. > > I'm trying to understand the inode messages on Windows > 2000/XP. I don't have either OS, so I can't try to reproduce > it. I've never seen that error on my Windows '98 SE box. My results pass. I am using XP SP1 with all MS patches (as of last night). Here are the results:- DJ204 D:\dj204\test\inode>inode PASS DJ204 D:\dj204\contrib>..\test\inode\inode PASS As I spotted the last weekend a simple directory tree works fine, but a complex direcory tree traversal fails when performing a rm -rf. I suspect that the example may not show the problem up, but if you traverse the gnu or contrib directories (if you have some contrib programs installed) then the stat . could possible show up. Andrew