Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!gatech!psuvax1!psuhcx!wcf
From: wcf@psuhcx.psu.edu (Bill Fenner)
Newsgroups: comp.unix.wizards
Subject: Re: Ugly file name
Message-ID: <1230@psuhcx.psu.edu>
Date: 21 May 89 15:47:35 GMT
References: <105096@sun.Eng.Sun.COM> <9001@csli.Stanford.EDU> <672@marob.MASA.COM>
Reply-To: wcf@psuhcx.psu.edu (Bill Fenner)
Organization: Engineering Computer Lab, Penn State University
Lines: 21

In article <672@marob.MASA.COM> daveh@marob.masa.com (Dave Hammond) writes:
|>Several alternatives have been suggested to uniquely identify the file
|>to be removed. However, there are cases in which `rm' won't do the job
|>of deleting the file because the shell which is used to run `rm' may
|>strip the eighth bit off characters [some shells do]. In such cases, it
|
|I have found the `find' command quite useful in this respect.  Find's

How about using ls -i to find the inode of the file in question, then

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

or am I missing something?  It seems to me that that can handle any situation.
(As long as find can pass everything to rm.)

  Bill
-- 
   Bitnet: wcf@psuhcx.bitnet     Bill Fenner       | "Yesterday starts
  Internet: wcf@hcx.psu.edu                        |  tomorrow; tomorrow
 UUCP: {gatech,rutgers}!psuvax1!psuhcx!wcf         |  starts today"
Fido: Sysop at 1:129/87 (814/238 9633) \hogbbs!wcf |       -- Marillion