From owner-freebsd-current@FreeBSD.ORG Thu Nov 29 22:32:36 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E342A16A41A; Thu, 29 Nov 2007 22:32:36 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from optimus.centralmiss.com (ns.centralmiss.com [206.156.254.79]) by mx1.freebsd.org (Postfix) with ESMTP id B0C1613C447; Thu, 29 Nov 2007 22:32:36 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (adsl-072-148-013-213.sip.jan.bellsouth.net [72.148.13.213]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by optimus.centralmiss.com (Postfix) with ESMTP id CB7C728BAC; Thu, 29 Nov 2007 16:07:53 -0600 (CST) Received: by draco.over-yonder.net (Postfix, from userid 100) id 5172E61C44; Thu, 29 Nov 2007 16:07:53 -0600 (CST) Date: Thu, 29 Nov 2007 16:07:53 -0600 From: "Matthew D. Fuller" To: Robert Watson Message-ID: <20071129220753.GB31891@over-yonder.net> References: <20071129140140.1f6bb021@Winter> <20071129145938.GA5751@mugin.localhost> <20071129215656.E7555@fledge.watson.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071129215656.E7555@fledge.watson.org> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.16-fullermd.4 (2007-06-09) Cc: freebsd-current@freebsd.org Subject: Kernel configging (was Re: -CURRENT buildkernel failure) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Nov 2007 22:32:37 -0000 On Thu, Nov 29, 2007 at 09:58:15PM +0000 I heard the voice of Robert Watson, and lo! it spake thus: > > I have to admit that, these days, I almost always create a new file, > include GENERIC, set a new ident, and then just add or trim options > and devices as needed. While I probably trim a little less from my > kernel than I used to, I find my upgrade path is much smoother since > I'm just maintaining my local variations in their own file. I fiddled with that a little bit when the include and no* got strong enough to pull it off, but I found it to be more trouble. Yanking out out non-present devices takes a LOT of no* lines, and keeping that up to date is harder than just dealing with the copy. What I do do these days, though, is use my choice of the current gen of distributed VCS's (though it's almost an insultingly simple use-case ;) to keep copies of GENERIC in one branch, and derive my config from that. So part of my pre-buildkernel process is copying in the new GENERIC to its branch, and merge that over into MYKERNEL. That makes keeping up with upstream changes easier, as well as giving me an easy history of what I've done with my config in the past. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.