Date: Thu, 2 Sep 2004 23:01:31 +0300 From: Ruslan Ermilov <ru@freebsd.org> To: John Baldwin <jhb@freebsd.org> Cc: ctodd@chrismiller.com Subject: Re: How to customize a release? Message-ID: <20040902200131.GC2671@ip.net.ua> In-Reply-To: <200409021538.26944.jhb@FreeBSD.org> References: <Pine.BSI.4.58L.0409021203480.12150@vp4.netgate.net> <200409021538.26944.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--adJ1OR3c6QgCpb/j Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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 ne= ed > > 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, modify= ing > > 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? >=20 > There is a 'KERNELS' variable that is helpful. Also, look at LOCAL_PATCH= ES=20 > and LOCAL_SCRIPTS as far as how to patch a release build. Note that you = can=20 > include patches to src/release/Makefile in LOCAL_PATCHES if need be. :) >=20 I'd say, please read the release(7) manpage. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --adJ1OR3c6QgCpb/j Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (FreeBSD) iD8DBQFBN3waqRfpzJluFF4RAvHSAJ4xuaDzCTkwz2YEq/TSLeqDOWP6GQCcC5Ed HUWxLN7wMsPYgtQC5W9ps6g= =AlOC -----END PGP SIGNATURE----- --adJ1OR3c6QgCpb/j--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040902200131.GC2671>