From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 3 09:47:49 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 C916616A4CE; Fri, 3 Sep 2004 09:47:49 +0000 (GMT) Received: from ms-dienst.rz.rwth-aachen.de (ms-2.rz.RWTH-Aachen.DE [134.130.3.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7BF4F43D55; Fri, 3 Sep 2004 09:47:49 +0000 (GMT) (envelope-from chris@unixpages.org) Received: from r220-1 (r220-1.rz.RWTH-Aachen.DE [134.130.3.31]) by ms-dienst.rz.rwth-aachen.de (iPlanet Messaging Server 5.2 HotFix 1.12 (built Feb 13 2003)) with ESMTP id <0I3G00ALYLVOGK@ms-dienst.rz.rwth-aachen.de>; Fri, 03 Sep 2004 11:47:48 +0200 (MEST) Received: from relay.rwth-aachen.de ([134.130.3.1]) by r220-1 (MailMonitor for SMTP v1.2.2 ) ; Fri, 03 Sep 2004 11:47:47 +0200 (MEST) Received: from haakonia.hitnet.rwth-aachen.de (haakonia.hitnet.RWTH-Aachen.DE [137.226.181.92])i839llRA018896; Fri, 03 Sep 2004 11:47:47 +0200 (MEST) Received: from gondor.middleearth (gondor.middleearth [192.168.1.42]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))(Postfix) with ESMTP id E323628442; Fri, 03 Sep 2004 11:47:41 +0200 (CEST) Received: by gondor.middleearth (Postfix, from userid 1001) id 7CC0C613A; Fri, 03 Sep 2004 11:47:41 +0200 (CEST) Date: Fri, 03 Sep 2004 11:47:41 +0200 From: Christian Brueffer In-reply-to: <20040902200131.GC2671@ip.net.ua> To: Ruslan Ermilov Message-id: <20040903094741.GE59319@unixpages.org> MIME-version: 1.0 Content-type: multipart/signed; boundary=FN+gV9K+162wdwwF; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-disposition: inline User-Agent: Mutt/1.5.5.1i X-Operating-System: FreeBSD 5.2-CURRENT X-PGP-Key: http://people.freebsd.org/~brueffer/brueffer.key.asc X-PGP-Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D References: <200409021538.26944.jhb@FreeBSD.org> <20040902200131.GC2671@ip.net.ua> cc: freebsd-hackers@freebsd.org cc: ctodd@chrismiller.com Subject: Re: 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: Fri, 03 Sep 2004 09:47:50 -0000 --FN+gV9K+162wdwwF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Sep 02, 2004 at 11:01:31PM +0300, Ruslan Ermilov wrote: > On Thu, Sep 02, 2004 at 03:38:26PM -0400, John Baldwin wrote: > > On Thursday 02 September 2004 03:21 pm, ctodd@chrismiller.com wrote: > > > 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, modi= fying > > > the source, then creating a diff patch that's used on a subsequent "m= ake > > > release". If it works as advertised, this is somewhat helpful other t= han > > > 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 patc= hes > > > could fail. Can CVS updates be turned off for subsequent builds? > > > > > > Lastly, KERNCONF seems to have no relevance in "make release". How ca= n I > > > force a non generic kernel to be used when building the release? > >=20 > > There is a 'KERNELS' variable that is helpful. Also, look at LOCAL_PAT= CHES=20 > > and LOCAL_SCRIPTS as far as how to patch a release build. Note that yo= u can=20 > > include patches to src/release/Makefile in LOCAL_PATCHES if need be. :) > >=20 > I'd say, please read the release(7) manpage. >=20 The FreeBSD from Scratch article might also be useful for you: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/fbsd-from-scratch/ - Christian --=20 Christian Brueffer chris@unixpages.org brueffer@FreeBSD.org GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D --FN+gV9K+162wdwwF Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFBOD29bHYXjKDtmC0RAmQ+AJ98CcHhWMAu9N7IS4Hi8SYTlX5DFgCeNWBB 5ZFRZe9V8R3HFIewtv2UkuU= =0oAq -----END PGP SIGNATURE----- --FN+gV9K+162wdwwF--