From owner-cvs-src@FreeBSD.ORG Wed Sep 27 15:29:17 2006 Return-Path: X-Original-To: cvs-src@freebsd.org Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 443C416A535; Wed, 27 Sep 2006 15:29:17 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A98A43E3D; Wed, 27 Sep 2006 15:27:35 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.6/8.13.6) with ESMTP id k8RFROZN058728; Wed, 27 Sep 2006 11:27:34 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: Ceri Davies Date: Wed, 27 Sep 2006 11:24:59 -0400 User-Agent: KMail/1.9.1 References: <200609261959.k8QJxqkh068350@repoman.freebsd.org> <20060927041526.6b33a348.trhodes@FreeBSD.org> <20060927084514.GR54669@submonkey.net> In-Reply-To: <20060927084514.GR54669@submonkey.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200609271125.00138.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Wed, 27 Sep 2006 11:27:34 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/1947/Tue Sep 26 20:46:56 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Tom Rhodes , src-committers@freebsd.org, cvs-src@freebsd.org, cvs-all@freebsd.org, danger@freebsd.org, brueffer@freebsd.org Subject: Re: cvs commit: src/share/examples/mdoc example.4 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: Wed, 27 Sep 2006 15:29:17 -0000 On Wednesday 27 September 2006 04:45, Ceri Davies wrote: > On Wed, Sep 27, 2006 at 04:15:26AM -0400, Tom Rhodes wrote: > > On Wed, 27 Sep 2006 08:53:14 +0100 > > Ceri Davies wrote: > > > > > On Wed, Sep 27, 2006 at 03:41:24AM -0400, Tom Rhodes wrote: > > > > On Tue, 26 Sep 2006 22:23:39 +0200 > > > > Christian Brueffer wrote: > > > > > > > > > | @@ -33,11 +33,9 @@ > > > > > > | .Nm example > > > > > > | .Nd "example device driver manual page" > > > > > > | .Sh SYNOPSIS > > > > > > | -To compile the > > > > > > | -.Ns Nm > > > > > > | -driver into the kernel, > > > > > > | -place the following lines in the > > > > > > | -kernel configuration file: > > > > > > | +To enable support for > > > > > > | +.Ns Nm , > > > > > > | +place the following lines in the kernel configuration file: > > > > > > > > > > The formulation used before was much more accurate WRT the distinction > > > > > we make between compiling something into the kernel and loading it as a > > > > > module. If we load something as a module we also "enable support for > > > > > it". > > > > > > > > What about in cases where other hoops must be jumped before the > > > > driver/feature/whatever is really supported? > > > > > > They can be special cased in the real manual. In the wider sense, > > > kldload is the easiest way to enable support for something, and I know > > > that I'm personally well past encouraging users to recompile the kernel > > > just to get, for example, sound working when a simple kldload does the > > > job just as well in most cases. > > > > That is of course that "something" has a module. ;) > > Well yes, which is why the previous text explicitly said "to compile .Nm > into the kernel", because that's what the example does. > > > Seriously though, why handle one case any differently than > > another? > > Compiling something into the kernel and loading a module are different, > that's why, and we should be clear about the distinction (because, as > you state, some modules don't exist). And it's not the same as enabling the driver. You can kldload ipmi but still disable it via a hw.ipmi.on sysctl and then re-enable it later w/o unloading it by toggling the sysctl back on. Enable is a poor word choice and very vague. Since you are mentioning the specific details of adding lines to a kernel config file, you should be as specific in stating what that does (adds driver to kernel). -- John Baldwin