Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site uwmacc.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!seismo!uwvax!uwmacc!jwp
From: jwp@uwmacc.UUCP (Jeffrey W Percival)
Newsgroups: net.unix
Subject: Re: more on strange file names
Message-ID: <1358@uwmacc.UUCP>
Date: Sun, 4-Aug-85 15:18:02 EDT
Article-I.D.: uwmacc.1358
Posted: Sun Aug  4 15:18:02 1985
Date-Received: Tue, 6-Aug-85 20:10:49 EDT
References: <137@lmef.UUCP>
Reply-To: jwp@uwmacc.UUCP (Jeffrey W Percival)
Distribution: net
Organization: UWisconsin-Madison Academic Comp Center
Lines: 14

In article <137@lmef.UUCP> damon@lmef.UUCP (Damon Scaggs) writes:
>A while back there was considerable discussion about how to delete files
>
>	find . -inum (inode # of file) -exec /bin/rm {} \;
>
>Certainly this is better than clri followed by a fsck...

Nope.  The original posting concerned 2.8BSD, and *nothing* using "rm"
worked.  Nothing whose performance ultimately relied on "unlink(2)" did
the job.  I received many suggestions, and tried them all, but my file
names were such that only the clri method was successful.

-- 
	Jeff Percival ...!uwvax!uwmacc!jwp