From owner-cvs-src@FreeBSD.ORG Tue Jan 23 21:43:07 2007 Return-Path: X-Original-To: cvs-src@freebsd.org Delivered-To: cvs-src@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9824416A404; Tue, 23 Jan 2007 21:43:07 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 6C87D13C45A; Tue, 23 Jan 2007 21:43:07 +0000 (UTC) (envelope-from sam@errno.com) Received: from [10.0.0.248] (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id l0NLh6VH030879 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 23 Jan 2007 13:43:06 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <45B68169.1060207@errno.com> Date: Tue, 23 Jan 2007 13:43:05 -0800 From: Sam Leffler User-Agent: Thunderbird 1.5.0.8 (X11/20061115) MIME-Version: 1.0 To: mjacob@freebsd.org References: <20070123173026.E692416A4CD@hub.freebsd.org> <45B65710.4060607@root.org> <20070123105009.G41619@ns1.feral.com> <45B65E4C.2050306@errno.com> <20070123112723.P43982@ns1.feral.com> <45B66458.9030406@errno.com> <20070123125236.U51690@ns1.feral.com> In-Reply-To: <20070123125236.U51690@ns1.feral.com> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: cvs-src@freebsd.org, src-committers@freebsd.org, cvs-all@freebsd.org, Nate Lawson Subject: Re: cvs commit: src/sys/cam/scsi scsi_da.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jan 2007 21:43:07 -0000 mjacob@freebsd.org wrote: >>> If you just do a module, all you're doing is moving compiled code from >>> one place to another. IMO. >> >> My thought was if it's split into a module then you can have alternative >> modules available at the loader prompt/menu to fallback to. Also if >> it's split out we can probably auto-generate it. > > umm, yes. > > So, what's wrong with an ascii sysctl/hint definition? Nothing. I just thought I was suggesting something in-between what we have now and a pure ascii mechanism like hints that requires in-kernel parsing. Sam