Date: Mon, 22 Aug 2005 13:57:03 -0400 From: John Baldwin <jhb@FreeBSD.org> To: Colin Percival <cperciva@FreeBSD.org> Cc: cvs-src@FreeBSD.org, Doug Barton <dougb@FreeBSD.org>, cvs-all@FreeBSD.org, src-committers@FreeBSD.org Subject: Re: cvs commit: src/sys/conf newvers.sh Message-ID: <200508221357.05742.jhb@FreeBSD.org> In-Reply-To: <43079814.8030107@freebsd.org> References: <200508190356.j7J3uj5D095435@repoman.freebsd.org> <200508201437.36296.jhb@FreeBSD.org> <43079814.8030107@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday 20 August 2005 04:52 pm, Colin Percival wrote:
> John Baldwin wrote:
> > On Friday 19 August 2005 11:40 am, Colin Percival wrote:
> >>When running
> >>FreeBSD Update builds, I'll typically have a RELEASE-pX tree checked out
> >>and a security patch (which is going to get committed to the tree later);
> >>I want to be able to build tree + patch with a label of RELEASE-p{X + 1}.
> >
> > If you used 'make release' to build your custom release (like a lot of
> > other folks do) you would have had all this for free. :)
>
> I'm not building a release; I'm building and installing a new world and
> kernel. For FreeBSD Update, I need the actual files which people will have
> installed on their systems, not the ISO images and FTP install tree.
You can extract the dists to build the trees as well. I did this recently to
update ~1200 boxes over a one-way satellite link. :) This would also let you
not require that people install a fixed-set of distributions but let them
subscribe to multiple distribution sets if desired since you can recreate any
configuration by extracting the appropriate set of dists into a work area.
--
John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve" = http://www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200508221357.05742.jhb>