Date: Wed, 21 Nov 2012 18:21:36 -0800 From: Devin Teske <devin.teske@fisglobal.com> To: Eitan Adler <lists@eitanadler.com> Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org>, Benjamin Kaduk <bjk@freebsd.org> Subject: Re: old style kernel configuration Message-ID: <CA3661C3-2DF7-40F3-8581-CCE994CC5689@fisglobal.com> In-Reply-To: <CAF6rxgmxiaA1twJf%2BKMv=ZpxCWp1MdL5GEEEFLwBuRqcGpctdQ@mail.gmail.com> References: <CAF6rxgmxiaA1twJf%2BKMv=ZpxCWp1MdL5GEEEFLwBuRqcGpctdQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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. >=20 I always build kernels with config(1) because it allows me to embed the _en= tire_ 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 comment= s are stripped from my config prior to embedding (and this is undesirable a= nd thus why we always configure our kernel by executing "config -C -g confi= gname"). > Is there any value in keeping this documented as an alternative to > "make buildkernel" or should it be treated as an implementation detail? >=20 Value: ability to embed entire config (comments and all) into the kernel Maybe this difference/value should be documented. --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA3661C3-2DF7-40F3-8581-CCE994CC5689>