From owner-freebsd-current Sat Mar 23 18:15:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA15028 for current-outgoing; Sat, 23 Mar 1996 18:15:51 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA15017 for ; Sat, 23 Mar 1996 18:15:49 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id TAA08681; Sat, 23 Mar 1996 19:08:37 -0700 From: Terry Lambert Message-Id: <199603240208.TAA08681@phaeton.artisoft.com> Subject: Re: lost+found ??? To: adam@veda.is (Adam David) Date: Sat, 23 Mar 1996 19:08:36 -0700 (MST) Cc: freebsd-current@freefall.freebsd.org In-Reply-To: <199603240048.AAA00428@veda.is> from "Adam David" at Mar 24, 96 00:48:08 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >> What do I need to do? > > >Nothing, fsck creates them as it needs them. > > Does it still happily create lost+found as inode #2 if ".." is missing? > Would it use inode #1 in the absence of the "." entry? Tee hee hee. Inode 1 is not use because historically it was used to chain the bad blocks and some archive programs know this and refuse to back it up. Inode #2 is the root inode. Inode #3 is the traditional lost+found inode. And no, fsck creates the lost+found as a normal directory, so it gets whatever inode it gets (if you precreate it with newfs, it will get inode 3). Consider: you might rename lost+found. The old fsck would still put entries in it; the new one would make another lost+found. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.