Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!srcsip!nic.MR.NET!hal!ncoast!telotech!bsa
From: bsa@telotech.UUCP (Brandon S. Allbery)
Newsgroups: comp.unix.questions
Subject: Re: Filenames and Inode Numbers
Message-ID: <1989Jul31.194328.9707@telotech.uucp>
Date: 31 Jul 89 19:43:28 GMT
References: <20373@adm.BRL.MIL>
Sender: bsa@telotech.uucp (Brandon S. Allbery)
Reply-To: bsa@telotech.UUCP (Brandon S. Allbery)
Organization: _
	      telotech, inc. - Beachwood, OH
Lines: 23
In-reply-to: ritter@cs.msstate.edu (Thomas H. Ritter)

In article <20373@adm.BRL.MIL>, ritter@cs (Thomas H. Ritter) writes:
+---------------
| Rick Geymont <GU.GEYMONT%SCIENCE.UTAH.EDU@wasatch.utah.edu> writes:
| >The easiest way I have found to remove files with special characters in the
| >name is to do the following:
| >do an 'ls -i' and get the inode number
| >type 'find . -inum # -exec rm {} \;' where # is the inode number.
| 
| Well almost every time.  Our Suns have the -inum option but
| our Unisys 5000 SYSV3.1 does not.
| 
| BTW, I can do an ls -i and see the inode information but
| what other ways could I remove a file based on inode number?
+---------------

rm `/etc/ncheck -i ...`

++Brandon
-- 
-=> Brandon S. Allbery @ telotech, inc.   (I do not speak for telotech.) <=-
Any comp.sources.misc postings sent to this address will be DISCARDED -- use
allbery@uunet.UU.NET instead. My boss doesn't pay me to moderate newsgroups.
** allbery@NCoast.ORG ** uunet!hal.cwru.edu!ncoast!{allbery,telotech!bsa} **