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 From: Jim Meyering To: bug-coreutils AT gnu DOT org Cc: Luke Kendall , cygwin AT cygwin DOT com Subject: Re: Path confusion In-Reply-To: <424D4BA9.2010507@byu.net> (Eric Blake's message of "Fri, 01 Apr 2005 06:24:57 -0700") References: <20050401071130 DOT 2051685080 AT pessard DOT research DOT canon DOT com DOT au> <424D4BA9 DOT 2010507 AT byu DOT net> Date: Fri, 01 Apr 2005 23:31:44 +0200 Message-ID: <85wtrm18vz.fsf@pi.meyering.net> Lines: 11 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Eric Blake wrote: > How about it - does it make sense to add an --xdev option to all of the > recursive descent tools (chown, chmod, ls, ...) to force the recursion to > stop at mount points, or is find/xargs the only supported idiom for this? It's seductive, but I don't think we can justify it. You've probably noticed that du has the --one-file-system (-x) option. That's justifiable because du couldn't do parts of its job if invoked through e.g., find+xargs. On the other hand, programs like chown, chmod, chgrp work just fine when invoked through find+xargs. -- 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/