Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU

BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

filesystem limits

Subject: filesystem limits
From: jrvz at comcast.net (James R. Van Zandt)
Date: Sun, 30 Jan 2005 11:33:07 -0500
In-reply-to: <Pine.LNX.4.61.0501111842220.31215@buddha.badbelly.com> (message from Gregory Boyce on Tue, 11 Jan 2005 18:46:51 -0500 (EST))
References: <W760241372214231105476068@webmail4> <Pine.LNX.4.61.0501111842220.31215@buddha.badbelly.com>

Gregory Boyce <gboyce at badbelly.com> wrote:
>On Tue, 11 Jan 2005, Bill Holt wrote:
>
>> woops...
>> find . -name '*' | xargs rm
>
>I would normally do:
>
>find . -name '*' -exec rm {} \;

Both of these would fail if filenames have spaces.  I suggest

   find . -name '*' -exec rm "{}" \;

	  - Jim Van Zandt

Follow-Ups:
- filesystem limits
  - From: david at thekramers.net (David Kramer)

References:
- filesystem limits
  - From: william_holt at speakeasy.net (Bill Holt)
- filesystem limits
  - From: gboyce at badbelly.com (Gregory Boyce)

Prev by Date: about /tmp
Next by Date: filesystem limits
Previous by thread: filesystem limits
Next by thread: filesystem limits
Index(es):
- Date
- Thread

Boston Linux & Unix / webmaster@blu.org