From owner-freebsd-current Mon Jun 19 11:37:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.bastard.co.uk (node16292.a2000.nl [24.132.98.146]) by hub.freebsd.org (Postfix) with ESMTP id 2902C37BDBD; Mon, 19 Jun 2000 11:37:23 -0700 (PDT) (envelope-from adrian@bastard.co.uk) Received: from adrian by mail.bastard.co.uk with local (Exim 3.14 #1) id 1346QD-0004WJ-00; Mon, 19 Jun 2000 20:37:21 +0200 Date: Mon, 19 Jun 2000 20:37:21 +0200 From: Adrian Chadd To: David O'Brien Cc: freebsd-current@freebsd.org Subject: Re: fsck wrappers Message-ID: <20000619203721.R13112@zoe.bastard.co.uk> References: <20000619134233.O13112@zoe.bastard.co.uk> <20000619113434.A37336@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000619113434.A37336@dragon.nuxi.com>; from obrien@freebsd.org on Mon, Jun 19, 2000 at 11:34:34AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jun 19, 2000, David O'Brien wrote: > On Mon, Jun 19, 2000 at 01:42:33PM +0200, Adrian Chadd wrote: > > I've ported the NetBSD fsck wrapper to compile and run under FreeBSD. > > Can you summerize what this does, or does better than what we do today? The idea is the same as mount and its helpers - adding new fsck types doesn't require modifying the startup scripts or fsck. Think of a system where you have an FFS fs, an LFS fs, and perhaps an IFS fs. Each one requires a seperate fsck, but it would be stupid to have fsck_* -p in the rc scripts. Eventually FreeBSD systems will have more than just FFS based filesystems running the system, and users will want to fsck them just like a FFS filesystem. adrian -- Adrian Chadd Build a man a fire, and he's warm for the rest of the evening. Set a man on fire and he's warm for the rest of his life. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message