From owner-freebsd-stable@FreeBSD.ORG Sun Mar 14 10:19:28 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 05DAD16A4CE for ; Sun, 14 Mar 2004 10:19:28 -0800 (PST) Received: from smtp.omnis.com (smtp.omnis.com [216.239.128.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id E800643D31 for ; Sun, 14 Mar 2004 10:19:27 -0800 (PST) (envelope-from wes@softweyr.com) Received: from zaphod.softweyr.com (66-91-236-204.san.rr.com [66.91.236.204]) by smtp-relay.omnis.com (Postfix) with ESMTP id 7DE1F881D00; Sun, 14 Mar 2004 10:19:26 -0800 (PST) Date: Sun, 14 Mar 2004 10:19:27 -0800 From: Wes Peters To: Peter Jeremy Message-Id: <20040314101927.72f86abc.wes@softweyr.com> In-Reply-To: <20040311003115.GL10121@gsmx07.alcatel.com.au> References: <200403110014.LAA17110@lightning.itga.com.au> <20040311003115.GL10121@gsmx07.alcatel.com.au> Organization: Softweyr.com X-Mailer: Sylpheed version 0.9.8 (GTK+ 1.2.10; i386-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: gnb@itga.com.au cc: freebsd-stable@freebsd.org Subject: Re: unexpected softupdate inconsistency X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Mar 2004 18:19:28 -0000 On Thu, 11 Mar 2004 11:31:16 +1100 Peter Jeremy alleged: > On 2004-Mar-11 11:14:01 +1100, Gregory Bond wrote: > >The key phrase here is "What does vim do here _that rm doesn't_?" > > > >If vim is also just using unlink() then rm can (theoretically) do the job > >just as well. It seems like really odd advice to say "use vim because rm > >can't do the job." If this were in any way true, then I'd call that a > >serious bug in rm. > > If the filename to delete includes non-printing or magic-to-the-shell > characters (and especially ones with the top bit set), it can be > difficult to specify the filename as a command-line argument to rm(1). > In these cases, directory-editing modes in editors (or a scripting > language like perl) can be very helpful. Let us not forget 'rm -i *'... Tedious, perhaps, but it does get the job done. 'ls -B' may be helpful in identifying why 'rm foobar' doesn't work on a file apparently named 'foobar'. wes@zaphod$ touch foo^Bbar -- entered with ^V^B in bash wes@zaphod$ ls -lB foo* -rw-r--r-- 1 wes wes 0 Mar 14 10:18 foo\002bar -rw-r--r-- 1 wes wes 263 Jul 10 2003 foo.c wes@zaphod$ rm -i foo* remove foobar? y remove foo.c? n -- Where am I, and what am I doing in this handbasket? Wes Peters wes@softweyr.com