Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: $Revision: 1.6.2.16 $; site haddock.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!haddock!bill
From: bill@haddock.UUCP
Newsgroups: net.sources
Subject: Re: rm-damnit.1
Message-ID: <59700001@haddock.UUCP>
Date: Thu, 25-Apr-85 06:54:00 EDT
Article-I.D.: haddock.59700001
Posted: Thu Apr 25 06:54:00 1985
Date-Received: Wed, 1-May-85 04:09:16 EDT
References: <174@geowhiz.UUCP>
Lines: 10
Nf-ID: #R:geowhiz:-17400:haddock:59700001:000:255
Nf-From: haddock!bill    Apr 25 09:54:00 1985




  And then there is always

	 find . <some criteria> -exec rm {} \;

  You can use crude but effective tools like "od -bch ." to see what the
true name of a file is.  I think the problem with funny names is getting
them past the shell; rm doesn't care.