From owner-freebsd-arch Tue Oct 24 3:45:50 2000 Delivered-To: freebsd-arch@freebsd.org Received: from mail-relay.eunet.no (mail-relay.eunet.no [193.71.71.242]) by hub.freebsd.org (Postfix) with ESMTP id ED5AA37B479 for ; Tue, 24 Oct 2000 03:45:47 -0700 (PDT) Received: from login-1.eunet.no (login-1.eunet.no [193.75.110.2]) by mail-relay.eunet.no (8.9.3/8.9.3/GN) with ESMTP id MAA02164; Tue, 24 Oct 2000 12:45:42 +0200 (CEST) (envelope-from mbendiks@eunet.no) Received: from localhost (mbendiks@localhost) by login-1.eunet.no (8.9.3/8.8.8) with ESMTP id MAA44964; Tue, 24 Oct 2000 12:45:41 +0200 (CEST) (envelope-from mbendiks@eunet.no) X-Authentication-Warning: login-1.eunet.no: mbendiks owned process doing -bs Date: Tue, 24 Oct 2000 12:45:35 +0200 (CEST) From: Marius Bendiksen To: Dag-Erling Smorgrav Cc: arch@FreeBSD.ORG Subject: Re: Ideas concerning fsck In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Doing anything at all before you know you can trust your root > > > partition (where fsck itself is stored) is not a very good idea. > > And using /etc/fstab, stored on the same partition, is a better idea? > No. However, we can't get around the need for fstab, but we can get > around the need for some kind of fscktab which contains static > information which practically noone will ever need to change. We can get around the need for fstab by using the bootfs idea that AIX and others use (Poul-Henning has suggested this also in connection with DEVFS) to get less magic in the boot sequence. Also, if noone ever needs to change it, then it's even less likely to change, and thus be in an inconsistant state, than /etc/fstab. Hence, it is no real point of failure. While being able to employ a dynamic fsck would be a good thing, I am still concerned about removing the static version. I'd suggest adding a pass -1, like Kirk said, or somesuch. Marius To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message