Newsgroups: comp.unix.sysv386
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!uunet!mtxinu!ed
From: ed@mtxinu.COM (Ed Gould)
Subject: Re: fsck Recovery From Crashes
Message-ID: <1991Jun4.054004.8896@mtxinu.COM>
Keywords: inode file directory lost+found
Reply-To: ed@mtxinu.COM (Ed Gould)
Organization: mt Xinu, Berkeley
References: <35@metran.UUCP> <1991Jun02.184143.15566@virtech.uucp> <1074@camco.Celestial.COM>
Date: Tue, 4 Jun 91 05:40:04 GMT

>This brings to mind a utility I've been meaning to write.  It
>would run daily and make an index by inode number of each
>filesystem to make it easier to figure out what was what in a
>lost+found directory after a crash.

>Before I reinvent another wheel, has anyone already done this?

The ncheck program - if it exists in your version of UNIX - does
exactly this.  It was a standard part of the system through at
least V7 and is still part of BSD.

-- 
Ed Gould			No longer formally affiliated with,
ed@mtxinu.COM			and certainly not speaking for, mt Xinu.

"I'll fight them as a woman, not a lady.  I'll fight them as an engineer."
