svn: head/sys/i386/conf

Maxim Sobolev sobomax at
Tue Jan 6 16:37:17 PST 2009

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.


More information about the svn-src-head mailing list