From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 22 02:21:46 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E66F9362; Thu, 22 Nov 2012 02:21:46 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id A22C48FC08; Thu, 22 Nov 2012 02:21:46 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.17]) by ltcfislmsgpa07.fnfis.com (8.14.5/8.14.5) with ESMTP id qAM2Lc0E029904 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 21 Nov 2012 20:21:38 -0600 Received: from [10.0.0.100] (10.14.152.61) by smtp.fisglobal.com (10.132.206.17) with Microsoft SMTP Server (TLS) id 14.2.309.2; Wed, 21 Nov 2012 20:21:37 -0600 Subject: Re: old style kernel configuration MIME-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset="us-ascii" From: Devin Teske In-Reply-To: Date: Wed, 21 Nov 2012 18:21:36 -0800 Content-Transfer-Encoding: quoted-printable Message-ID: References: To: Eitan Adler X-Mailer: Apple Mail (2.1283) X-Originating-IP: [10.14.152.61] X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.9.8185, 1.0.431, 0.0.0000 definitions=2012-11-21_04:2012-11-21,2012-11-21,1970-01-01 signatures=0 Cc: FreeBSD Hackers , Benjamin Kaduk X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Devin Teske List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Nov 2012 02:21:47 -0000 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.