From owner-cvs-all Wed Jan 23 8: 0:47 2002 Delivered-To: cvs-all@freebsd.org Received: from smtp.bsdhome.com (rdu25-2-113.nc.rr.com [24.25.2.113]) by hub.freebsd.org (Postfix) with ESMTP id 9066E37B416; Wed, 23 Jan 2002 08:00:40 -0800 (PST) Received: from neutrino.bsdhome.com (jupiter [192.168.220.13]) by smtp.bsdhome.com (8.11.3nb1/8.11.4) with ESMTP id g0NG0Y726522; Wed, 23 Jan 2002 11:00:34 -0500 (EST) Received: (from bsd@localhost) by neutrino.bsdhome.com (8.11.6/8.11.6) id g0NG0Ri57596; Wed, 23 Jan 2002 11:00:27 -0500 (EST) (envelope-from bsd) Date: Wed, 23 Jan 2002 11:00:27 -0500 From: Brian Dean To: Dag-Erling Smorgrav Cc: Michael Smith , Kris Kennaway , Benno Rice , Kirk McKusick , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/ufs/ffs ffs_alloc.c ffs_extern.h ffs_softdep.c Message-ID: <20020123110027.A57494@neutrino.bsdhome.com> References: <200201230314.g0N3Eud04579@mass.dis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from des@ofug.org on Wed, Jan 23, 2002 at 11:49:25AM +0100 Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Jan 23, 2002 at 11:49:25AM +0100, Dag-Erling Smorgrav wrote: > Michael Smith writes: > > Personally, I'd prefer to remove the option (always build the code) and > > default to enabling it on new filesystems. Kirk's recent commit removes > > the last major objection to this. > > My opinion as well, though it doesn't really bother me the way it is > now. I wonder, though, if there are code paths that could be removed > or simplified if softupdates is always compiled in. Please don't do this (force compiling the code). While I certainly encourage the use of softupdates (I use it myself almost everywhere), I also strongly encourage the ability to not build the code if that is desired. I can't really think of any good reason not use use softupdates in a general purpose Unix environment, but we need to remember that FreeBSD is used in many embedded or otherwise specialized environments where softupdates may offer minimal value and consumes precious code space (about 40K in this case). I certainly don't object to (and would strongly support) a "NOSOFTUPDATES" option, so that it has to be explicitly disabled as opposed to explicitly enabled. BTW, I'm not picking on softupdates, just the general philosophy of making it difficult to conditionally compile significant code-paths that are not globally applicable across FreeBSD's user-base. Whatever happend to "features, not policy"? -Brian -- Brian Dean bsd@FreeBSD.org bsd@bsdhome.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message