From owner-freebsd-arch Sun Dec 2 2:23:35 2001 Delivered-To: freebsd-arch@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id B9A5337B405; Sun, 2 Dec 2001 02:23:33 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fB2ANMi91290; Sun, 2 Dec 2001 02:23:22 -0800 (PST) (envelope-from dillon) Date: Sun, 2 Dec 2001 02:23:22 -0800 (PST) From: Matthew Dillon Message-Id: <200112021023.fB2ANMi91290@apollo.backplane.com> To: Garance A Drosihn Cc: Robert Watson , arch@FreeBSD.ORG Subject: Re: Enabling Softupdates in default install on -CURRENT References: Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :At 11:27 PM -0500 12/1/01, Robert Watson wrote: :>I'm beginning to wonder if it isn't time to switch sysinstall to start :>configuring softupdates "by default" for file systems at install-time. :>We currently allow it to be selected, but don't enable it by default. :>I would propose it be turned on by default for all non-root file :>systems, or some other similar rule (file systems <64MB, ..). : :I expect it would be best to have it default 'off' for /, because the :user can get into strange-seeming failures when installing a new kernel. :I do like the idea of it being on for most other filesystems. : :I don't have much of an opinion as to whether it should also default :to off for other "small" file systems. I agree. / is still a problem - I have softupdates enabled on my 128M / partitions and if I 'make install' a kernel twice in a row the filesystem runs out of space and the second install fails. But that's the only time I've ever managed to run a softupdates filesystem out of space. If we incorporated a couple of 'sync's (like eight of them) at the beginning of a kernel or world install target it would probably be safe enough. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message