Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!rutgers!usc!elroy.jpl.nasa.gov!ames!pacbell.com!pacbell!att!dptg!ulysses!andante!alice!andrew
From: andrew@alice.UUCP (Andrew Hume)
Newsgroups: comp.unix.questions
Subject: Re: Tip about lost+found
Summary: don't blame mkfs
Message-ID: <10854@alice.UUCP>
Date: 23 May 90 03:39:10 GMT
References: <836@zeusa.UUCP> <418@mtndew.UUCP>
Organization: AT&T Bell Laboratories, Murray Hill NJ
Lines: 8



independent of steve's program (which looks quite formal yet useful),
don't blame mkfs for not making a lost+found. it seems fairly clear
that the responsibility for l+f is solely with the only program
that uses it, fsck (and its cousins). there is no technical reason
for fsck not creating a lost+found dir unless the file system is completely
out of space.