Path: utzoo!utgpu!water!watmath!clyde!rutgers!mit-eddie!ll-xn!ames!ptsfa!pacbell!pbhyf!tlh
From: tlh@pbhyf.UUCP (Lee Hounshell)
Newsgroups: comp.sys.att
Subject: Re: Recommendation to mkdir /lost+f
Message-ID: <2700@pbhyf.UUCP>
Date: 21 Jan 88 15:55:55 GMT
References: <178@shlepper.ATT.COM> <144800017@occrsh.ATT.COM>
Reply-To: tlh@pbhyf.UUCP (Lee Hounshell)
Organization: Pacific * Bell, San Ramon, CA
Lines: 16

In article <144800017@occrsh.ATT.COM> rjd@occrsh.ATT.COM writes:
 >  On the same note: I was a little fuzzy why fsck required already-made
 >but empty directory entries or allocated blocks.  I seem to recall that
 >my lost+found directory was 32 characters (the minimum, just the . and ..
 >entries) prior to fsck being run and finding 5 disconnected files that
 >were reconnected just fine (I happened to have an ls -l output of the
 >/ filesystem before the crash which showed the 32 character lost+found
 >entry).  I will grant that Berkley unix may need the entries, but is this
 >really true for AT&T System V?

Yeah.. so was mine, and fsck reconnected about 10 files for me with no
problems about 3 weeks ago.  I suspect that the directory slot stuff is
only specific to Berkeley unix.. it certainly isn't needed for the 3B1.
comments?

Lee Hounshell