Date: Tue, 06 Jan 2009 16:08:59 -0800 From: Maxim Sobolev <sobomax@FreeBSD.org> To: Luigi Rizzo <rizzo@iet.unipi.it> Cc: svn-src-head@FreeBSD.org, Luigi Rizzo <luigi@FreeBSD.org>, src-committers@FreeBSD.org, svn-src-all@FreeBSD.org Subject: Re: svn: head/sys/i386/conf Message-ID: <4963F29B.4070001@FreeBSD.org> In-Reply-To: <20090106224658.GB3130@onelab2.iet.unipi.it> References: <200901061510.n06FAQ0g034585@svn.freebsd.org> <4963D4E9.707@FreeBSD.org> <20090106224658.GB3130@onelab2.iet.unipi.it>
next in thread | previous in thread | raw e-mail | index | archive | help
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. -Maxim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4963F29B.4070001>