From owner-freebsd-current Thu Jan 7 10:15:11 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA16610 for freebsd-current-outgoing; Thu, 7 Jan 1999 10:15:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rt2.synx.com (tech.boostworks.com [194.167.81.239]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA16601 for ; Thu, 7 Jan 1999 10:15:08 -0800 (PST) (envelope-from root@synx.com) Received: from synx.com (rn.synx.com [192.1.1.241]) by rt2.synx.com (8.9.1/8.9.1) with ESMTP id TAA00741; Thu, 7 Jan 1999 19:19:56 +0100 (CET) Message-Id: <199901071819.TAA00741@rt2.synx.com> Date: Thu, 7 Jan 1999 19:13:28 +0100 (CET) From: Remy Nonnenmacher Reply-To: remy@synx.com Subject: Re: Kernel configurator To: culverk@wam.umd.edu cc: Freebsd-current@FreeBSD.ORG In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 7 Jan, Kenneth Wayne Culver wrote: >> >> This sounds like a very good idea, to me. >> > It would be a pain. Every time a new kernel option or device got added, > the program would have to be changed. It would seem to me that this is > just another thing to remember to update. > And what about having the device or option surrounded with special comments in the LINT file. The configurator would be able to extract informations/constraints/values from there !. (Just a though, as the LINT file serves me as a reference for parameters). RN. IhM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message