tinderbox on an oldish machine

xorquewasp at googlemail.com xorquewasp at googlemail.com
Sat Mar 28 16:37:11 EDT 2009


On 2009-03-28 16:31:29, Joe Marcus Clarke wrote:
> On Sat, 2009-03-28 at 20:20 +0000, xorquewasp at googlemail.com wrote:
> > 'Lo, again.
> > 
> > One small question: I'm running tinderbox on an old machine. How often
> > am I going to have to build world? Once per jail, on creation?
> 
> Depends on what you're tracking.  If you're tracking a RELEASE, you only
> need to build world on Jail creation.  If you're tracking a moving
> target like -STABLE, then it's a good idea to keep your Jail in sync
> with the head of the branch (at least every time __FreeBSD_version
> changes).

Yes, just RELEASE here. On i386 and amd64.

> > I'd ideally like to share a binary world between all my jails, possibly
> > keeping up-to-date with freebsd-update (and portsnap for the tree).
> 
> How can you share world between Jails?  If all the Jails use the same
> world, then you only need one Jail.

I may have misunderstood how tinderbox does things. I'm intending to build
sets of packages for some twenty or thirty hosts/jails on other machines.
I assume, now, from your comment that I don't use one jail per target
host (just one per arch/os version combination).

> > 
> > Is this doable?
> 
> Yes.  Just set your update command to NONE, build a tar file of a clean
> world which will live in ${pb}/jails/JAIL.  You can use the -m flag to
> createJail to specify a mount source for the Jail src.  This can be a
> nullfs mount.

Right. I do something very similar with 'ezjail'.

That clears a few things up.

xw


More information about the tinderbox-list mailing list