From owner-freebsd-fs Sat Oct 30 15:41:52 1999 Delivered-To: freebsd-fs@freebsd.org Received: from calis.blacksun.org (Calis.blacksun.org [168.100.186.40]) by hub.freebsd.org (Postfix) with ESMTP id 70DAD14D7D for ; Sat, 30 Oct 1999 15:41:35 -0700 (PDT) (envelope-from don@calis.blacksun.org) Received: from localhost (don@localhost) by calis.blacksun.org (8.9.3/8.9.2) with ESMTP id SAA44033; Sat, 30 Oct 1999 18:42:04 -0400 (EDT) (envelope-from don@calis.blacksun.org) Date: Sat, 30 Oct 1999 18:42:04 -0400 (EDT) From: Don To: Chang Song Cc: freebsd-fs@FreeBSD.ORG Subject: Re: journaling UFS and LFS In-Reply-To: <381B728F.82963E1A@zk3.dec.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Could you let me know what SoftUpdate does not address? > Thank you. Growing and shriking the file system, access control lists, the softupdates license issue, and the ability ot easily extend the capabilites of the file system without having to rewrite utilities such as fsck. > Is jornaling only solution to removal of fsck at boot time? > Softupdate not only address required boot time fsck on crash and but also > addresses tighter consistency of UFS. You want to avoid a UFS fsck at boot time. fsck for lfs or softupdates is very fast as opposed to fsck'ing a large UFS partition. -Don To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message