Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!ames!ptsfa!ssl
From: ssl@ptsfa.UUCP
Newsgroups: comp.unix.questions,comp.unix.wizards,comp.unix.xenix
Subject: Re: Confused file name in directory
Message-ID: <2136@ptsfa.UUCP>
Date: Wed, 25-Feb-87 10:25:56 EST
Article-I.D.: ptsfa.2136
Posted: Wed Feb 25 10:25:56 1987
Date-Received: Fri, 27-Feb-87 22:01:40 EST
References: <105@aob.UUCP> <563@aw.sei.cmu.edu.sei.cmu.edu>
Reply-To: ssl@ptsfa.UUCP (Sam Lok)
Organization: Pacific * Bell, San Ramon, CA
Lines: 23
Xref: utgpu comp.unix.questions:1179 comp.unix.wizards:1123 comp.unix.xenix:113

In article <563@aw.sei.cmu.edu.sei.cmu.edu> pdb@sei.cmu.edu (Patrick Barron) writes:
>
>As a last resort you could use 'clri' on the inode associated with that
>file (use 'ls -li' to find the inode numner).  fsck will certainly allow
>you to clear the directory entry once it realizes the inode's been zeroed.
>
>--Pat.

But as a last to the last resort, if you don't really want to get rid
of things, I'll try this before 'clri':
	1. make sure there's only one directory and/or filename start
	   with D
	2. then 'mv D* goodname'
Didn't try this with D\0a though, this might/might not work, but doesn't
hurt give it a try before earsing everything.  As long as D* expands into
one name, mv will work.


-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Sam Lok		San Francisco		{ihnp4,pyramid,qantel}!ptsfa!ssl
				|| To err is human, to really foul things
Disclaimer!?  WHAT disclaimer?	|| up requires super-user privilege!