From owner-freebsd-current Thu Mar 21 08:18:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA16130 for current-outgoing; Thu, 21 Mar 1996 08:18:24 -0800 (PST) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id IAA16098 for ; Thu, 21 Mar 1996 08:18:15 -0800 (PST) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id KAA02561; Thu, 21 Mar 1996 10:13:51 -0600 From: Joe Greco Message-Id: <199603211613.KAA02561@brasil.moneng.mei.com> Subject: Re: lost+found ??? To: j@uriah.heep.sax.de (J Wunsch) Date: Thu, 21 Mar 1996 10:13:51 -0600 (CST) Cc: freebsd-current@FreeBSD.org In-Reply-To: <199603211259.NAA13192@uriah.heep.sax.de> from "J Wunsch" at Mar 21, 96 01:59:43 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > As Michael Smith wrote: > > > > What do I need to do? > > > > Nothing, fsck creates them as it needs them. > > ...thereby happily destroying arbitrary disk data if it has to extend > the root directory and fails to find free space to do so. > > newfs should create it. I gotta agree with this stand even though I hate lost+found directories cluttering up my directory hierarchies.... :-) oh, and Jordan, Suns create lost+found at mkfs time - I'm looking at the source that does the deed. They _will_ also create it at fsck time if it does not exist, but it looks like that's handled as an "unusual" condition. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Software Engineer, UNIX/Network Hacker, Etc. 414/362-3308 Marquette Electronics, Inc. - R&D - Milwaukee, WI jgreco@mei.com