From owner-freebsd-hackers@FreeBSD.ORG Thu Mar 12 19:07:42 2015 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 400A771E for ; Thu, 12 Mar 2015 19:07:42 +0000 (UTC) Received: from udns.ultimatedns.net (unknown [IPv6:2602:d1:b4d6:e600:4261:86ff:fef6:aa2a]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1473DA86 for ; Thu, 12 Mar 2015 19:07:41 +0000 (UTC) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id t2CJ9Lpa046493; Thu, 12 Mar 2015 12:09:21 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: Matt Tagg , "Julian H. Stacey" In-Reply-To: <201503121754.t2CHscnQ092956@fire.js.berklix.net> References: <201503121754.t2CHscnQ092956@fire.js.berklix.net> From: "Chris H" Subject: Re: find with -delete option on absolute paths Date: Thu, 12 Mar 2015 12:09:21 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <3b90cd87b96ea11ed03d5125a897949e@ultimatedns.net> Content-Transfer-Encoding: 8bit Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Mar 2015 19:07:42 -0000 On Thu, 12 Mar 2015 18:54:38 +0100 "Julian H. Stacey" wrote > Matt Tagg wrote: > > Hey BSD folks > > > > I believe this was discussed previously (2013), though I could not > > find a resolution. > > > > To recap, suppose we try deleting files on an absolute path: > > > > matt@mtbook:/% find /tmp/foo/* -delete > > find: -delete: /tmp/foo/bar.txt: relative path potentially not safe > > > > As you can see it gives an error and quits. However if we instead try this: > > > > matt@mtbook:/% gfind /tmp/foo/* -delete > > > > GNU Find throws no error and works as expected ('bar.txt is deleted') > > > > So as an end user, I find this rather confusing. How can I get the > > same behavior with BSD Find out of the box? > > Off on a tangent: > Last millenia (1987 :-) when I was using find & needed an rm to reduce > near duplicate trees on DOS & Unix, I wrote my own C > http://berklix.com/~jhs/src/bsd/jhs/bin/public/cmpd/ > I've never since worried about getting syntax of test conditions > wrong & deleting good stuff by mistake. Thanks for sharing that, Julian. :-) I don't see an entry for this in the ports tree. :-/ Thanks, again. --Chris > > Cheers, > Julian > -- > Julian Stacey, BSD Linux Unix C Sys Eng Consultant Munich http://berklix.com > Indent previous with "> ". Reply Below as a play script. > Send plain text, Not quoted-printable, HTML, or base64. > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"