Sun Aug 26 10:34:20 2012 UTC ()
Update path to mksandbox.


(wiz)
diff -r1.9 -r1.10 pkgsrc/doc/guide/files/bulk.xml

cvs diff -r1.9 -r1.10 pkgsrc/doc/guide/files/bulk.xml (expand / switch to unified diff)

--- pkgsrc/doc/guide/files/bulk.xml 2011/07/31 08:48:22 1.9
+++ pkgsrc/doc/guide/files/bulk.xml 2012/08/26 10:34:20 1.10
@@ -1,14 +1,14 @@ @@ -1,14 +1,14 @@
1<!-- $NetBSD: bulk.xml,v 1.9 2011/07/31 08:48:22 spz Exp $ --> 1<!-- $NetBSD: bulk.xml,v 1.10 2012/08/26 10:34:20 wiz Exp $ -->
2 2
3<chapter id="bulk"> 3<chapter id="bulk">
4<title>Creating binary packages for everything in pkgsrc (bulk 4<title>Creating binary packages for everything in pkgsrc (bulk
5builds)</title> 5builds)</title>
6 6
7<para>When you have multiple machines that should run the same packages, 7<para>When you have multiple machines that should run the same packages,
8it is wasted time if they all build their packages themselves from 8it is wasted time if they all build their packages themselves from
9source. There are two ways of getting a set of binary packages: The old 9source. There are two ways of getting a set of binary packages: The old
10bulk build system, or the new (as of 2007) parallel bulk build (pbulk) 10bulk build system, or the new (as of 2007) parallel bulk build (pbulk)
11system. This chapter describes how to set them up so that the packages 11system. This chapter describes how to set them up so that the packages
12are most likely to be usable later.</para> 12are most likely to be usable later.</para>
13 13
14<sect1 id="bulk.pre"> 14<sect1 id="bulk.pre">
@@ -356,27 +356,28 @@ fi @@ -356,27 +356,28 @@ fi
356 <sect2 id="setting-up-a-sandbox"> 356 <sect2 id="setting-up-a-sandbox">
357 <title>Setting up a sandbox for chrooted builds</title> 357 <title>Setting up a sandbox for chrooted builds</title>
358 358
359 <para>If you don't want all the packages nuked from a machine 359 <para>If you don't want all the packages nuked from a machine
360 (rendering it useless for anything but pkg compiling), there 360 (rendering it useless for anything but pkg compiling), there
361 is the possibility of doing the package bulk build inside a 361 is the possibility of doing the package bulk build inside a
362 chroot environment.</para> 362 chroot environment.</para>
363 363
364 <para>The first step is to set up a chroot sandbox, 364 <para>The first step is to set up a chroot sandbox,
365 e.g. <filename>/usr/sandbox</filename>. This can be done by 365 e.g. <filename>/usr/sandbox</filename>. This can be done by
366 using null mounts, or manually.</para> 366 using null mounts, or manually.</para>
367 367
368 <para>There is a shell script called 368 <para>There is a shell script called
369 <filename>pkgsrc/mk/bulk/mksandbox</filename> which will set 369 <filename>mksandbox</filename> installed by the <filename
 370 role="pkg">pkgtools/mksandbox</filename> package, which will set
370 up the sandbox environment using null mounts. It will also 371 up the sandbox environment using null mounts. It will also
371 create a script called <filename>sandbox</filename> in the 372 create a script called <filename>sandbox</filename> in the
372 root of the sandbox environment, which will allow the null 373 root of the sandbox environment, which will allow the null
373 mounts to be activated using the <command>sandbox 374 mounts to be activated using the <command>sandbox
374 mount</command> command and deactivated using the 375 mount</command> command and deactivated using the
375 <command>sandbox umount</command> command.</para> 376 <command>sandbox umount</command> command.</para>
376 377
377 <para>To set up a sandbox environment by hand, after extracting all 378 <para>To set up a sandbox environment by hand, after extracting all
378 the sets from a &os; installation or doing a <command>make 379 the sets from a &os; installation or doing a <command>make
379 distribution DESTDIR=/usr/sandbox</command> in 380 distribution DESTDIR=/usr/sandbox</command> in
380 <filename>/usr/src/etc</filename>, be sure the following items 381 <filename>/usr/src/etc</filename>, be sure the following items
381 are present and properly configured:</para> 382 are present and properly configured:</para>
382 383