Gerhard Sittig wrote: > > On Wed, Oct 24, 2001 at 18:27 -0600, Warner Losh wrote: > > > > At timing solutions, we build all our products in a chroot jail. [...] > > > > We don't build RELEASES in the chroot. We build a system (make world > > DESTDIR=xxx outside of the chroot) that we then use to build the > > system (inside the chroot). > > What I've always been wondering since Kris first mentioned this > technique in the thread's course (building -STABLE in a jail on > a -RELEASE host or vice versa, IIUC) was the following: There's > the host's kernel serving a differing world's userland. We all > know what's the usual answer to "I just updated my kernel and > now -- insert whatever you please -- stopped working. :) What > did I miss? Or is it plain luck when things just work and one > shouldn't ask why they do? :>
I have a 10k shell script for doing this. It copies in all the stuff from the parent system which is important to match to the real kernel, including /kernel, the "ps" program, and basically all other programs that open /dev/kmem or link against libkvm. That means that the build environment works like the host system for all important commands, but acts like the target system for compilation, etc.. It can also copy in and install a list of packages. Basically, it operates off a tarball which is DISC 2. It also uses chroot (not jail, though I suspect he just meant chroot). -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
