From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 2 19:35:28 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C5C8116A4CE for ; Thu, 2 Sep 2004 19:35:28 +0000 (GMT) Received: from ds.netgate.net (ds.netgate.net [205.214.170.232]) by mx1.FreeBSD.org (Postfix) with ESMTP id 924CB43D5E for ; Thu, 2 Sep 2004 19:35:28 +0000 (GMT) (envelope-from ibrew@chrismiller.com) Received: (qmail 16600 invoked from network); 2 Sep 2004 19:35:28 -0000 Received: from vp4.netgate.net (ibrew@205.214.170.248) by ds.netgate.net with SMTP; 2 Sep 2004 19:35:28 -0000 Date: Thu, 2 Sep 2004 12:21:14 -0700 (PDT) From: ctodd@chrismiller.com X-X-Sender: ibrew@vp4.netgate.net To: freebsd-hackers@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII ReSent-Date: Thu, 2 Sep 2004 12:35:25 -0700 (PDT) Resent-From: Chris Miller Resent-To: freebsd-hackers@freebsd.org ReSent-Subject: How to customize a release? ReSent-Message-ID: Subject: How to customize a release? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Sep 2004 19:35:28 -0000 I'm looking for information on how to properly customize a FreeBSD distribution when using the "make release" framework. Specifically I need to modify some config files to default to serial console and fast baud rate, and use a custom kernel configuration (not just hack the GENERIC conf file). The documentation on the FreeBSD site covers how to build a release, but other than a few hints I'm not finding and references on the correct way to _customize_ the release. I did find a site that discusses building a release, mirroring the usr/src tree from that release directory, modifying the source, then creating a diff patch that's used on a subsequent "make release". If it works as advertised, this is somewhat helpful other than waiting an entire day for multiple release builds to finish. Is there a way to populate the build area with the source, then apply my own patches prior to running a full "make release"? I tried "make release.1" but this totally ignored my CHROOTDIR and tried to create "/R" in my root partition :-(. Also I noted that "make rerelease" updates the source from CVS which is undesirable in my case since I already have fresh source that was used to create patches, and if any of those original files changed my patches could fail. Can CVS updates be turned off for subsequent builds? Lastly, KERNCONF seems to have no relevance in "make release". How can I force a non generic kernel to be used when building the release? Chris