There's also 
	rm -i *
This will go through each file in the directory and ask if you want to
remove it. It's nice if you happen to get a file with unprintables in it.
I had a bug in tin on another account that would create 100k files
(nearly 1/10th of my quota!!!) named \133\133 or something like that
(where \133 is the octal representation of the ASCII code of the chars in
question). Anyway, that was the only way I could get rid of them.

Dan Bongert                | Hire the Morally Handicapped--It's More Fun
dbongert@students.wisc.edu | National Institute for the Morally Handicapped
herkimer@upL.cs.wisc.edu   | http://www.upl.cs.wisc.edu/~herkimer

On Thu, 20 Feb 1997, Dan Bell wrote:

> On Thu, 20 Feb 1997, Henry B. Hotz wrote:
> 
> > 1) rm Unix\\    (character escape)
> > 
> > 2) rm Unix?     (wild card matching)
> > 
> > 3) rm Unix*     (brute force wild card matching)
> > 
> > 4) rm 'Unix\'   (probably, not so sure of this one)
> 
> <kludge mode>
> 
> If your machine allows incoming ftp, ftp in under a uid that has
> permissions to change the un-removable file, and do the following:
> 
> ftp>cd /
> ftp>del "weirdfile"
> ftp>quit
> 
> </kludge mode>
> 
> Not exactly the approved way, but a decent brute-force approach. 
> 
> 
> 
> 
> Daniel Bell
> JHU CS
> 
>