From owner-svn-src-head@FreeBSD.ORG Wed Jan 7 00:43:20 2009 Return-Path: Delivered-To: svn-src-head@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9E921106566B; Wed, 7 Jan 2009 00:43:20 +0000 (UTC) (envelope-from sobomax@FreeBSD.org) Received: from sippysoft.com (gk1.360sip.com [72.236.70.240]) by mx1.freebsd.org (Postfix) with ESMTP id 4743C8FC08; Wed, 7 Jan 2009 00:43:20 +0000 (UTC) (envelope-from sobomax@FreeBSD.org) Received: from [192.168.1.38] (S0106001372fd1e07.vs.shawcable.net [70.71.171.106]) (authenticated bits=0) by sippysoft.com (8.13.8/8.13.8) with ESMTP id n070hIxM059920 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 6 Jan 2009 16:43:19 -0800 (PST) (envelope-from sobomax@FreeBSD.org) Message-ID: <4963FA9A.8030208@FreeBSD.org> Date: Tue, 06 Jan 2009 16:43:06 -0800 From: Maxim Sobolev Organization: Sippy Software, Inc. User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 References: <200901061510.n06FAQ0g034585@svn.freebsd.org> <4963D4E9.707@FreeBSD.org> <20090106224658.GB3130@onelab2.iet.unipi.it> <4963F29B.4070001@FreeBSD.org> <20090107003033.GA5795@onelab2.iet.unipi.it> <4963F92E.1040708@FreeBSD.org> In-Reply-To: <4963F92E.1040708@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: svn-src-head@FreeBSD.org, Luigi Rizzo , src-committers@FreeBSD.org, Luigi Rizzo , svn-src-all@FreeBSD.org Subject: Re: svn: head/sys/i386/conf X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jan 2009 00:43:21 -0000 Maxim Sobolev wrote: > Luigi Rizzo wrote: >> On Tue, Jan 06, 2009 at 04:08:59PM -0800, Maxim Sobolev wrote: >>> Luigi Rizzo wrote: >>>> On Tue, Jan 06, 2009 at 02:02:17PM -0800, Maxim Sobolev wrote: >>>>> Luigi Rizzo wrote: >>>>>> +# through getenv() (or kenv(1) in userland). The format of the file >>>>>> +# is 'variable=value' , same as for hints files. >>>>> What do you think about extending comment with the following: >>>>> >>>>> "hints files" -> "hints or loader.conf(5) files". >>>> i don't know -- in fact, I have a curiosity here: >>>> loader.conf is processed by some code in loader.4th which in turn >>>> is interpreted by loader.conf, and this chain does some magic >>>> on certain variable names (and can also do $variable expansion). >>>> >>>> Instead, I believe that 'hints' (and presumably 'env' values) are >>>> passed directly to the kernel, so there are no special manipulation >>>> of variable names or values. Is that correct ? >>> That's true, however if loader doesn't have any handling logic for a >>> certain valuable it simply sets kenv (aka kernel tunable). Take a >>> look at the loader.conf(5) for example. >> >> ok, but all we need to say is the following: >> >> The file can contain lines of the form >> >> name = "value" # this is a coment >> >> where whitespace around name and '=' is ignored, and so is >> everything after a '#' character. Almost any printable >> character except '=' is acceptable as part of a name. Quotes >> are optional and necessary only if the value contains >> whitespace. >> >> so why don't we just say that in the kenv(1) manpage (and refer to >> that) instead of referring to loader.conf which contains a lot of >> stuff that does not apply in this case ? > > My main point is that usually people set those tunables not in "hints > files" but in loader.conf, so that if you refer to hints you should also > need to mention loader.conf. In fact I guess that many people may not > even know about what "hints files" are. Forgot to mention that IMHO another reason why loader.conf(5) is a good reference is that it describes purpose of many of the commonly used tunables. -Maxim