X-Spam-Check-By: sourceware.org X-IronPort-AV: i="4.04,158,1144040400"; d="scan'208"; a="48399289:sNHT449680776" From: "Ross, George - DOA" To: "Eric Blake" , "cygwin AT cygwin DOT com" Subject: RE: "rm -rf ./foo/" safe to use? Date: Wed, 26 Apr 2006 10:26:23 -0500 Message-ID: <20060426102623316.00000003124@DOA56811> In-Reply-To: X-Mailer: Oracle Connector for Outlook 10.1.2.0.6 80309 (11.0.6568) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id k3QFR9LR031491 A few years ago, I came across a "rm -rf" problem with NFSv2 and NFSv3 clients. NFS clients on Solaris 8 and 9, AIX 4.3, and the Hummingbird on Windows all had a problem with "rm -rf", against a certain NFS server. The problem was an NFS protocol implementation short-cut. When reported, one of the vendors fixed the problem, others did not. I do not know if the problem still exists (but can check to see if does). I have never tested the cygwin NFS client against the above-mentioned NFS server. -----Original Message----- From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com] On Behalf Of Eric Blake Sent: Wednesday, April 26, 2006 10:02 AM To: cygwin AT cygwin DOT com Subject: Re: "rm -rf ./foo/" safe to use? Tom Rodman trodman.com> writes: > > I think I had read something years back about cygwin's inode > simulation (sorry to munge up the terminology), being imperfect; so > that may have convinced me to not use "rm -rf DIRXXX". And how would imperfect inode simulation mess up rm? Seriously - I would like to know what gave you the impression that inode behavior could interfere with rm. > > So is "rm -rf ./foo/" safe to use? Is there any danger that anything > other than ./foo/ will be deleted? I use recursive rm all the time, both on FAT drives (where cygwin must do inode simulation) and on NTFS drives (where cygwin uses NTFS inodes). The only danger in deleting more than you intended is if you type the command wrong, but that same danger holds true for 'cmd /c rmdir'. IMO, if you are going to use cygwin, then use cygwin's rm (but maybe I'm biased, since I happen to be the rm maintainer). -- Eric Blake volunteer cygwin coreutils maintainer -- 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/ -- 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/