Date: Thu, 15 May 2003 09:58:44 -0700 From: "David O'Brien" <obrien@freebsd.org> To: John Hay <jhay@icomtek.csir.co.za> Cc: freebsd-bugs@freebsd.org Subject: Re: misc/52122: make release does not use proper binar Message-ID: <20030515165844.GA20271@dragon.nuxi.com> In-Reply-To: <20030515163142.GA75538@zibbi.icomtek.csir.co.za> References: <200305151600.h4FG0Uwt088142@freefall.freebsd.org> <20030515163142.GA75538@zibbi.icomtek.csir.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, May 15, 2003 at 06:31:42PM +0200, John Hay wrote:
> One reason why it isn't that useful inside the chroot area, is that
> if your running kernel and the newly built bits gets too much out of
> sync you will need to update the machine in any case, so you will
> end up with "new" binaries and a kernel on the machine and so it
> is a "waste" to recompile world inside the chroot area.
In this case the release died near the end (release.9 target). It was
easy to update the running kernel and reboot. Now we wanted to restart
the release w/o starting from scratch. This release build included ports
README's and Docs, and thus takes a very long time to build. To not have
to start from scratch, I did "chroot ${CHROOT} /bin/sh" and then ran "rm
/tmp/.world_done ; /mk" which should have restarted the release build and
done the mimimum work to finish the release. It didn't because of the
cross-release commit that removed the installworld w/in the ${CHROOT}.
This bit not only me, but another person also building an Alpha snapshot.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030515165844.GA20271>