diff options
Diffstat (limited to 'handbook/kernelopts.sgml')
| -rw-r--r-- | handbook/kernelopts.sgml | 22 |
1 files changed, 11 insertions, 11 deletions
diff --git a/handbook/kernelopts.sgml b/handbook/kernelopts.sgml index 8351d59a4e..fff4f9d3c6 100644 --- a/handbook/kernelopts.sgml +++ b/handbook/kernelopts.sgml @@ -1,4 +1,4 @@ -<!-- $Id: kernelopts.sgml,v 1.8 1997-08-12 09:18:03 asami Exp $ --> +<!-- $Id: kernelopts.sgml,v 1.9 1997-10-19 13:32:10 jraynard Exp $ --> <!-- The FreeBSD Documentation Project --> <!-- <!DOCTYPE linuxdoc PUBLIC '-//FreeBSD//DTD linuxdoc//EN'> --> @@ -13,7 +13,7 @@ id="kernelconfig" name="kernel configuration"> before reading here. <p>The use of kernel options is basically described in the <ref id="kernelconfig:options" name="kernel configuration"> section. - There's also an explanation about ``historic'' and ``new-style'' + There's also an explanation of ``historic'' and ``new-style'' options. The ultimate goal is to eventually turn all the supported options in the kernel into new-style ones, so for people who correctly did a <tt/make depend/ in their kernel compile directory @@ -36,7 +36,7 @@ id="kernelconfig" name="kernel configuration"> before reading here. </verb> <p>This way, an administrator mentioning another value for the option in his config file will take the default out of effect, and - replace it with his new value. Apparently, the new value will be + replace it with his new value. Clearly, the new value will be substituted into the source code during the preprocessor run, so it must be a valid C expression in whatever context the default value would have been used. @@ -57,16 +57,16 @@ id="kernelconfig" name="kernel configuration"> before reading here. <p>People familiar with the C language will immediately recognize that everything could be counted as a ``config option'' where - there is at least a single <tt/#ifdef/ referencing it... Now only - few people probably would try to say + there is at least a single <tt/#ifdef/ referencing it... However, + it's unlikely that many people would put <verb> options notyet,notdef </verb> - <p>in their config file however, and watch the kernel compilation - fall over. :-) + <p>in their config file, and then wonder why the kernel compilation + falls over. :-) - <p>Apparently, using arbitrary names for the options makes it very + <p>Clearly, using arbitrary names for the options makes it very hard to track their usage throughout the kernel source tree. That is the rationale behind the <em/new-style/ option scheme, where each option goes into a separate <tt/.h/ file in the kernel compile @@ -129,9 +129,9 @@ id="kernelconfig" name="kernel configuration"> before reading here. #include "opt_foo.h" </verb> <p><em>on top</em>, before all the <tt/#include <xxx.h>/ - stuff. The sequence is most important in case the options will - override some defaults from the regular include files, where the - defaults are protected by + stuff. This sequence is most important as the options could + override defaults from the regular include files, if the + defaults are of the form <verb> #ifndef NEW_OPTION |