Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!killer!usource!frankb
From: frankb@usource.UUCP (Frank Bicknell)
Newsgroups: comp.unix.xenix
Subject: Re: Weird File Names (Removing them)
Summary: Watch out for mounted filesystems
Message-ID: <167@usource.UUCP>
Date: 21 Feb 89 16:38:20 GMT
References: <91@raider.MFEE.TN.US> <281@swusrgrp.UUCP>
Organization: UniSource, Inc., Sarasota, FL
Lines: 32

In article <281@swusrgrp.UUCP>, jeff@swusrgrp.UUCP (Jeff Tye sys adm) writes:
> In article <91@raider.MFEE.TN.US>, root@raider.MFEE.TN.US (Bob Reineri) writes:
> > One of them has a file in his home directory that I can't
> > get rid of to save my life. In a regular 'l' listing, it has
> > a filename of the greek letter 

> Try this:
... find the inode # ...
> 3)	Type this command (very carefully):
> 
> 		find . -inum inode -exec rm {} \;   (return)
> 
> 	(where inode is the number found in step 2)

> Voila'! It's gone.

BE CAREFUL that there are no other filesystems below '.', however.
Although Bob said the file was in his home directory and
filesystems are rarely mounted below home directories, if you
generalize this solution to, say '/', you could wipe out as many
files as you have filesystems mounted!  (ie there could be an
inode #x on each of those filesystems).

Safer would be:

 		find . -inum inode -exec rm -i {} \;

or use a fix program which does this only to the file in the
current filesystem (where _is_ that source code?).
-- 
Frank Bicknell; 1405 Main St, Ste 709; Sarasota, FL 34236-5701
killer!usource!frankb