Xref: utzoo comp.sys.att:6499 comp.unix.questions:13735
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!purdue!haven!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.sys.att,comp.unix.questions
Subject: Re: Reattach inode to lost&found / what file is it?
Keywords: fsck lost&found inode
Message-ID: <17612@mimsy.UUCP>
Date: 19 May 89 14:37:02 GMT
References: <1099@adds.newyork.NCR.COM>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 15

In article <1099@adds.newyork.NCR.COM> tanya@adds.newyork.NCR.COM
(Tanya Katz) writes:
>After fsck reattaches a file to directory lost&found,
>it names it with the inode.  Is there a nice neat way
>of determining what file this was originally?

Which of its up-to-32000 possible names would you prefer?  Consider,
e.g., vi, which is also known as edit, ex, e, and view.

There is never any guaranteed way to turn an inode into a single
pathname, because an inode may have anywhere from zero to (some large
number that varies with the implementation) names.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris@mimsy.umd.edu	Path:	uunet!mimsy!chris