Date: Fri, 03 Sep 2004 11:47:41 +0200 From: Christian Brueffer <chris@unixpages.org> To: Ruslan Ermilov <ru@freebsd.org> Cc: ctodd@chrismiller.com Subject: Re: How to customize a release? Message-ID: <20040903094741.GE59319@unixpages.org> In-Reply-To: <20040902200131.GC2671@ip.net.ua> References: <Pine.BSI.4.58L.0409021203480.12150@vp4.netgate.net> <200409021538.26944.jhb@FreeBSD.org> <20040902200131.GC2671@ip.net.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] 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, 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? > > > > There is a 'KERNELS' variable that is helpful. Also, look at LOCAL_PATCHES > > and LOCAL_SCRIPTS as far as how to patch a release build. Note that you can > > include patches to src/release/Makefile in LOCAL_PATCHES if need be. :) > > > I'd say, please read the release(7) manpage. > 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 -- 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 [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFBOD29bHYXjKDtmC0RAmQ+AJ98CcHhWMAu9N7IS4Hi8SYTlX5DFgCeNWBB 5ZFRZe9V8R3HFIewtv2UkuU= =0oAq -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040903094741.GE59319>