Xref: utzoo comp.sys.att:6495 comp.unix.questions:13724
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!haven!umbc3!wolf.umbc.edu!alex
From: alex@wolf.umbc.edu (Alex Crain)
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: <2060@umbc3.UMBC.EDU>
Date: 19 May 89 16:29:23 GMT
References: <1099@adds.newyork.NCR.COM>
Sender: newspost@umbc3.UMBC.EDU
Lines: 21

In article <1099@adds.newyork.NCR.COM>, tanya@adds.newyork.NCR.COM (Tanya Katz) writes:

> But if it's an object file, I usually search the string 
> table (if it has one) or the symbol table, to try to
> figure out what it is...
> 
> Isn't there a more sophistocated method to identify
> an object?

	Try "what <filename>".

	In my experiance, however, binarys (or anything else) that go to
lost+found usually have some trash in them, so their probably no good. Most
of the files that I find in lost+found are intermediate files from the 
compiler, representing changes in the inode table that never got flushed to 
disk.

					:alex
Alex Crain
Systems Programmer			alex@umbc3.umbc.edu
Univ Md Baltimore County		umbc3.umbc.edu!nerwin!alex