On 11/21/2012 8:21 PM, Devin Teske wrote: > > On Nov 21, 2012, at 5:58 PM, Eitan Adler wrote: > >> I've been working on removing obsolete information various documents. >> While going through older articles I noticed a few references to the >> "old style" kernel configuration involving running config(1) manually. >> > > I always build kernels with config(1) because it allows me to embed the > _entire_ kernel config into the kernel (by using the "-C" option to > config(1)). > > Otherwise, if I rely only on the INCLUDE_CONFIG_FILE parameter, the comments > are stripped from my config prior to embedding (and this is undesirable and > thus why we always configure our kernel by executing "config -C -g > configname"). > > >> Is there any value in keeping this documented as an alternative to >> "make buildkernel" or should it be treated as an implementation detail? >> > > Value: ability to embed entire config (comments and all) into the kernel > > Maybe this difference/value should be documented. >
Maybe it makes sense to add INCLUDE_ENTIRE_CONFIG_FILE? Bryan _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
