From owner-svn-doc-all@FreeBSD.ORG Mon Dec 24 09:02:51 2012 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5EA99E4F; Mon, 24 Dec 2012 09:02:51 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 40C708FC14; Mon, 24 Dec 2012 09:02:51 +0000 (UTC) Received: from svn.freebsd.org (localhost [127.0.0.1]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id qBO92pct073256; Mon, 24 Dec 2012 09:02:51 GMT (envelope-from hrs@svn.freebsd.org) Received: (from hrs@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id qBO92pi2073255; Mon, 24 Dec 2012 09:02:51 GMT (envelope-from hrs@svn.freebsd.org) Message-Id: <201212240902.qBO92pi2073255@svn.freebsd.org> From: Hiroki Sato Date: Mon, 24 Dec 2012 09:02:51 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40465 - head/en_US.ISO8859-1/articles/portbuild X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Dec 2012 09:02:51 -0000 Author: hrs Date: Mon Dec 24 09:02:50 2012 New Revision: 40465 URL: http://svnweb.freebsd.org/changeset/doc/40465 Log: DocBook markup fixes: - Replace literal with filename, makevar, option. - Make use of programlisting and screen consistent. - Use for footnote and for internal reference. - Add missing &prompt.root;. - Use instead of . Modified: head/en_US.ISO8859-1/articles/portbuild/article.xml Modified: head/en_US.ISO8859-1/articles/portbuild/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/portbuild/article.xml Mon Dec 24 00:09:26 2012 (r40464) +++ head/en_US.ISO8859-1/articles/portbuild/article.xml Mon Dec 24 09:02:50 2012 (r40465) @@ -54,7 +54,7 @@ Many of the details in this article will be of interest only to - those on the Ports Management + those on the Ports Management team. @@ -81,10 +81,10 @@ The scripts that control all of this live in - /var/portbuild/scripts/. + /var/portbuild/scripts/. These are the checked-out copies from the Subversion repository at - base/projects/portbuild/scripts/ + base/projects/portbuild/scripts/ . Typically, incremental builds are done that use previous @@ -344,7 +344,7 @@ PKG_BIN=/usr/local/sbin/pkgThe scripts/dopackages.wrapper script is used to perform the builds. - &prompt.root; dopackages.wrapper ${arch} ${branch} ${buildid} [-options] + &prompt.root; dopackages.wrapper ${arch} ${branch} ${buildid} Most often, you will be using latest for the value of buildid. @@ -354,7 +354,7 @@ PKG_BIN=/usr/local/sbin/pkg - -keep - Do not delete this build in the + - Do not delete this build in the future, when it would be normally deleted as part of the latest - previous cycle. Do not forget to clean it up manually when you no longer need it. @@ -362,7 +362,7 @@ PKG_BIN=/usr/local/sbin/pkg - -nofinish - Do not perform + - Do not perform post-processing once the build is complete. Useful if you expect that the build will need to be restarted once it finishes. If you use this option, do not forget to cleanup @@ -371,20 +371,20 @@ PKG_BIN=/usr/local/sbin/pkg - -finish - Perform + - Perform post-processing only. - -nocleanup - By default, when the - -finish stage of the build is complete, the build + - By default, when the + stage of the build is complete, the build data will be deleted from the clients. This option will prevent that. - -restart - Restart an interrupted + - Restart an interrupted (or non-finished) build from the beginning. Ports that failed on the previous build will be rebuilt. @@ -392,16 +392,16 @@ PKG_BIN=/usr/local/sbin/pkg - -continue - Restart an interrupted + - Restart an interrupted (or non-finished) build. Will not rebuild ports that failed on the previous build. - -incremental - Compare the + - Compare the interesting fields of the new - INDEX with the previous one, + INDEX with the previous one, remove packages and log files for the old ports that have changed, and rebuild the rest. This cuts down on build times substantially since @@ -410,126 +410,126 @@ PKG_BIN=/usr/local/sbin/pkg - -cdrom - This package build is + - This package build is intended to end up on a CD-ROM, so - NO_CDROM packages and distfiles + NO_CDROM packages and distfiles should be deleted in post-processing. - -nobuild - Perform all + - Perform all the preprocessing steps, but do not actually do the package build. - -noindex - Do not rebuild + - Do not rebuild INDEX during preprocessing. - -noduds - Do not rebuild the + - Do not rebuild the duds file (ports that are never built, e.g., those marked IGNORE, - NO_PACKAGE, etc.) during + NO_PACKAGE, etc.) during preprocessing. - -nochecksubdirs - Do not check the + - Do not check the SUBDIRS for ports that are not connected to the build. - -trybroken - Try to build - BROKEN ports (off by default + - Try to build + BROKEN ports (off by default because the amd64/&i386; clusters are fast enough now that when doing incremental builds, more time was spent rebuilding things that were going to fail anyway. Conversely, the other clusters are slow enough that it would be a waste of time - to try and build BROKEN ports). + to try and build BROKEN ports). - With -trybroken, you probably - also want to use -fetch-original + With , you probably + also want to use and - -unlimited-errors. + . - -nosrc - Do not update the - src tree from the ZFS snapshot, keep the tree from + - Do not update the + src tree from the ZFS snapshot, keep the tree from previous build instead. - -srcvcs - Do not update the - src tree from the ZFS snapshot, update it with + - Do not update the + src tree from the ZFS snapshot, update it with a fresh checkout instead. - -noports - Do not update the - ports tree from the ZFS snapshot, keep the tree from + - Do not update the + ports tree from the ZFS snapshot, keep the tree from previous build instead. - -portsvcs - Do not update the - ports tree from the ZFS snapshot, update it with + - Do not update the + ports tree from the ZFS snapshot, update it with a fresh checkout instead. - -norestr - Do not attempt to build - RESTRICTED ports. + - Do not attempt to build + RESTRICTED ports. - -noplistcheck - Do not make it fatal for + - Do not make it fatal for ports to leave behind files after deinstallation. - -nodistfiles - Do not collect distfiles + - Do not collect distfiles that pass make checksum for later uploading to ftp-master. - -fetch-original - Fetch the - distfile from the original MASTER_SITES + - Fetch the + distfile from the original MASTER_SITES rather than any cache such as on ftp-master. - -unlimited-errors + - defeat the "qmanager threshhold" check for runaway builds. You want this primarily when doing a - -restart of a build that you expect to mostly - fail, or perhaps a -trybroken run. By default, + of a build that you expect to mostly + fail, or perhaps a run. By default, the threshhold check is done. - Unless you specify -restart, - -continue, or -finish, + Unless you specify , + , or , the symlinks for the existing builds will be rotated. i.e, the existing symlink for previous will be deleted; the most recent build will have its symlink changed @@ -539,7 +539,7 @@ PKG_BIN=/usr/local/sbin/pkgIf the last build finished cleanly you do not need to delete anything. If it was interrupted, or you selected - -nocleanup, you need to clean up clients by running + , you need to clean up clients by running &prompt.user; build cleanup ${arch} ${branch} ${buildid} -full @@ -554,10 +554,10 @@ PKG_BIN=/usr/local/sbin/pkg dosetupnodes is supposed to be run from the dopackages script in the - -restart case, but it can be a good idea to + case, but it can be a good idea to run it by hand and then verify that the clients all have the expected job load. Sometimes, - dosetupnode cannot clean up a build and you + dosetupnode cannot clean up a build and you need to do it by hand. (This is a bug.) @@ -581,13 +581,13 @@ PKG_BIN=/usr/local/sbin/pkg${arch}/${branch}/journal: - don't know how to make dns-all(continuing) + don't know how to make dns-all(continuing) To correct this problem, simply comment out or remove - the SUBDIR entries that point to empty + the SUBDIR entries that point to empty subdirectories. After doing this, you can restart the build by running the proper dopackages command - with the -restart option. + with the option. @@ -691,77 +691,69 @@ PKG_BIN=/usr/local/sbin/pkg - An update of the current ports - tree from the ZFS snapshot [*] - + An update of the current ports + tree from the ZFS snapshot + Status of these steps can be found in + ${arch}/${branch}/build.log + as well as on stderr of the tty running the + dopackages command. An update of the running branch's - src tree from the ZFS snapshot [*] + src tree from the ZFS snapshot Checks which ports do not have a - SUBDIR entry in their respective - category's Makefile [*] + SUBDIR entry in their respective + category's Makefile Creates the duds file, which - is a list of ports not to build [*] [+] - + is a list of ports not to build + If any of these steps fail, the build will stop + cold in its tracks. Generates a fresh INDEX - file [*] [+] + file Sets up the nodes that will be used in the - build [*] [+] + build - Builds a list of restricted ports [*] [+] + Builds a list of restricted ports - Builds packages (phase 1) [++] + Builds packages (phase 1)Status of these steps can be found in + ${arch}/${branch}/journal. + Individual ports will write + their build logs to + ${arch}/${branch}/logs/ + and their error logs to + ${arch}/${branch}/errors/. + - Performs another node setup [+] + Performs another node setup - Builds packages (phase 2) [++] + Builds packages (phase 2) - - [*] Status of these steps can be found in - ${arch}/${branch}/build.log - as well as on stderr of the tty running the - dopackages command. - - [+] If any of these steps fail, the build will stop - cold in its tracks. - - [++] Status of these steps can be found in - ${arch}/${branch}/journal - . - Individual ports will write - their build logs to - ${arch}/${branch}/logs/ - and their error logs to - ${arch}/${branch}/errors/. - - @@ -794,11 +786,11 @@ PKG_BIN=/usr/local/sbin/pkgps x to identify it. You need to make sure that nothing else important - is running in this tty, e.g., ps -t p1 or whatever. + is running in this tty, e.g., ps -t p1 or whatever. If there is not, you can just kill off the whole term easily with - pkill -t pts/1; otherwise issue a - kill -HUP in there by, for example, -ps -t pts/1 -o pid= | xargs kill -HUP. Replace + pkill -t pts/1; otherwise issue a + kill -HUP in there by, for example, +ps -t pts/1 -o pid= | xargs kill -HUP. Replace p1 by whatever the tty is, of course. The @@ -827,11 +819,11 @@ PKG_BIN=/usr/local/sbin/pkgpointyhat thinks the job slot is still occupied. - To check, cat ~/loads/* to display the + To check, cat ~/loads/* to display the status of client machines; the first column is the number of jobs it thinks is running, and this should be roughly concordant with the load average. loads is refreshed - every 2 minutes. If you do ps x | grep pdispatch + every 2 minutes. If you do ps x | grep pdispatch and it is less than the number of jobs that loads thinks are in use, you are in trouble. @@ -909,14 +901,14 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 You can use qclient command to monitor the status of build nodes, and to list the currently scheduled jobs: - &prompt.user; python path/qmanager/qclient jobs -&prompt.user; python path/qmanager/qclient status + &prompt.user; python path/qmanager/qclient jobs +&prompt.user; python path/qmanager/qclient status The - scripts/stats ${branch} + scripts/stats ${branch} command shows the number of packages already built. - Running cat /var/portbuild/*/loads/* + Running cat /var/portbuild/*/loads/* shows the client loads and number of concurrent builds in progress. The files that have been recently updated are the clients that are online; the others are the offline clients. @@ -931,15 +923,15 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 idle node. - Running tail -f ${arch}/${branch}/build.log + Running tail -f ${arch}/${branch}/build.log shows the overall build progress. If a port build is failing, and it is not immediately obvious from the log as to why, you can preserve the - WRKDIR for further analysis. To do this, + WRKDIR for further analysis. To do this, touch a file called .keep in the port's directory. The next time the cluster tries to build this port, - it will tar, compress, and copy the WRKDIR + it will tar, compress, and copy the WRKDIR to ${arch}/${branch}/wrkdirs/. @@ -976,7 +968,7 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 - number of lines in INDEX + number of lines in INDEX @@ -1022,7 +1014,7 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 You can easily bounce the new ones to maintainers. After a port appears broken on every build combination - multiple times, it is time to mark it BROKEN. + multiple times, it is time to mark it BROKEN. Two weeks' notification for the maintainers seems fair. @@ -1039,20 +1031,20 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 When building packages for a release, it may be necessary to manually update the ports - and src trees to the release tag and use - -novcs and - -noportsvcs. + and src trees to the release tag and use + and + . To build package sets intended for use on a CD-ROM, - use the -cdrom option to + use the option to dopackages. If the disk space is not available on the cluster, use - -nodistfiles to avoid collecting distfiles. + to avoid collecting distfiles. After the initial build completes, restart the build with - -restart -fetch-original + to collect updated distfiles as well. Then, once the build is post-processed, take an inventory of the list of files fetched: @@ -1093,11 +1085,11 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 Once a build has completed, packages and/or distfiles can be transferred to ftp-master for propagation to the FTP mirror network. If the build was - run with -nofinish, then make sure to + run with , then make sure to follow up with dopackages -finish to post-process the - packages (removes RESTRICTED and - NO_CDROM packages where appropriate, + packages (removes RESTRICTED and + NO_CDROM packages where appropriate, prunes packages not listed in INDEX, removes from INDEX references to packages not built, and generates a @@ -1105,7 +1097,7 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 summary); and distfiles (moves them from the temporary distfiles/.pbtmp directory into distfiles/ and removes - RESTRICTED and NO_CDROM + RESTRICTED and NO_CDROM distfiles). It is usually a good idea to run the @@ -1118,28 +1110,28 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 the final package set for a release. The package subdirectories are named by whether they are for - release, stable, or - current. Examples: + release, stable, or + current. Examples: - packages-7.2-release + packages-7.2-release - packages-7-stable + packages-7-stable - packages-8-stable + packages-8-stable - packages-9-stable + packages-9-stable - packages-10-current + packages-10-current @@ -1148,11 +1140,11 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 - packages-stable + packages-stable - packages-current + packages-current @@ -1180,10 +1172,10 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 using rsync so we do not put too much strain on the mirrors. - ALWAYS use -n + ALWAYS use first with rsync and check the output to make sure it is sane. If it looks good, re-run the - rsync without the -n + rsync without the option. @@ -1272,8 +1264,8 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 If it has been a long time since one of the builds finished, the logs may have been automatically compressed with - bzip2. In that case, you must use sort | sed - 's,\.bz2,,g' instead. + bzip2. In that case, you must use sort | sed + 's,\.bz2,,g' instead. &prompt.user; comm -3 /tmp/8-errs /tmp/8-exp-errs | less @@ -1308,13 +1300,13 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 include: - - Port was broken by the experimental patches [1] + + Port was broken by the experimental patches - + Port was upgraded since the control build and has become - broken [2] + broken @@ -1327,7 +1319,7 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 Both columns should be investigated and the reason for the errors understood before committing the experimental patches set. - To differentiate between [1] and [2] above, you can do a rebuild + To differentiate between and above, you can do a rebuild of the affected packages under the control branch: &prompt.user; cd /var/portbuild/i386/8/ports @@ -1336,7 +1328,7 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 The following example is obsolete - Be sure to cvs update this tree to the same date as + Be sure to cvs update this tree to the same date as the experimental patches tree. @@ -1362,8 +1354,8 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 The list of packages to build should be a list of package names (including versions) as they appear in - INDEX. The PKGSUFFIX - (i.e., .tgz or .tbz) is optional. + INDEX. The PKGSUFFIX + (i.e., .tgz or .tbz) is optional. This will build only those packages listed as well as all of their dependencies. @@ -1489,7 +1481,7 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 - Configuring <literal>src</literal> + Configuring <filename>src</filename> @@ -1503,7 +1495,7 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 - If you are using pxeboot: create a + If you are using pxeboot: create a directory to contain the install bits. You will probably want to use a subdirectory of /pxeroot, e.g., @@ -1513,7 +1505,7 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 If you are cross-building, export - TARGET_ARCH=${arch}. + TARGET_ARCH=${arch}. The procedure for cross-building ports is not yet @@ -1523,8 +1515,8 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 Generate a kernel config file. Include - GENERIC (or, if you are using more than - 3.5G on &i386;, PAE). + GENERIC (or, if you are using more than + 3.5G on &i386;, PAE). Required options: @@ -1544,14 +1536,14 @@ options SEMMNU=120 options ALT_BREAK_TO_DEBUGGER - For PAE, it is not currently possible + For PAE, it is not currently possible to load modules. Therefore, if you are running an architecture that supports Linux emulation, you will need to add: options COMPAT_LINUX options LINPROCFS - Also for PAE, as of 20110912 you need + Also for PAE, as of 20110912 you need the following. This needs to be investigated: nooption NFSD # New Network Filesystem Server @@ -1573,9 +1565,9 @@ options NFSSERVER Customize files in etc/. Whether you do this on the client itself, or another machine, will depend on whether you are using - pxeboot. + pxeboot. - If you are using pxeboot: create + If you are using pxeboot: create a subdirectory of ${DESTDIR} called conf/. Create one subdirectory @@ -1648,7 +1640,7 @@ ganglia:*:102:102::0:0:User &:/usr/l different, machines, you will need to put those in the override directories.) - Recommended entries for physical nodes: + Recommended entries for physical nodes: hostname="${hostname}" inetd_enable="YES" linux_enable="YES" @@ -1662,16 +1654,16 @@ gmond_enable="YES" squid_enable="YES" squid_chdir="/usr2/squid/logs" squid_pidfile="/usr2/squid/logs/squid.pid" - + - Required entries for VMWare-based nodes: + Required entries for VMWare-based nodes: vmware_guest_vmmemctl_enable="YES" vmware_guest_guestd_enable="YES" - + - Recommended entries for VMWare-based nodes: + Recommended entries for VMWare-based nodes: hostname="" ifconfig_em0="DHCP" fsck_y_enable="YES" @@ -1687,7 +1679,7 @@ gmond_enable="YES" squid_enable="YES" squid_chdir="/usr2/squid/logs" squid_pidfile="/usr2/squid/logs/squid.pid" - + &man.ntpd.8; should not @@ -1749,7 +1741,7 @@ squid_pidfile="/u - Configuring <literal>ports</literal> + Configuring <filename>ports</filename> @@ -1770,7 +1762,7 @@ www/squid (with SQUID_AUFS on) Customize files in usr/local/etc/. Whether you do this on the client itself, or another machine, will depend on whether you are using - pxeboot. + pxeboot. The trick of using conf @@ -1809,7 +1801,7 @@ www/squid (with SQUID_AUFS on) Create usr/local/etc/rc.d/portbuild.sh, using the appropriate value for - scratchdir: + scratchdir: #!/bin/sh # # Configure a package build system post-boot @@ -1827,7 +1819,7 @@ for i in */builds/*; do done # Flag that we are ready to accept jobs -touch /tmp/.boot_finished +touch /tmp/.boot_finished @@ -1908,14 +1900,14 @@ ports-${arch} As root: -mkdir portbuild -chown ports-${arch}:ports-${arch} portbuild -mkdir pkgbuild -chown ports-${arch}:ports-${arch} pkgbuild -mkdir squid -mkdir squid/cache -mkdir squid/logs -chown -R squid:squid squid +&prompt.root; mkdir portbuild +&prompt.root; chown ports-${arch}:ports-${arch} portbuild +&prompt.root; mkdir pkgbuild +&prompt.root; chown ports-${arch}:ports-${arch} pkgbuild +&prompt.root; mkdir squid +&prompt.root; mkdir squid/cache +&prompt.root; mkdir squid/logs +&prompt.root; chown -R squid:squid squid @@ -1988,14 +1980,14 @@ ports-${arch} of MASTER_SITE_BACKUP must be common to all nodes, but the first entry in MASTER_SITE_OVERRIDE should be the - nearest local FTP mirror. Example: + nearest local FTP mirror. Example: .if defined(FETCH_ORIGINAL) MASTER_SITE_BACKUP= .else MASTER_SITE_OVERRIDE= \ ftp://friendly-local-ftp-mirror/pub/FreeBSD/ports/distfiles/${DIST_SUBDIR}/ \ ftp://${BACKUP_FTP_SITE}/pub/FreeBSD/distfiles/${DIST_SUBDIR}/ -.endif +.endif @@ -2018,7 +2010,7 @@ MASTER_SITE_OVERRIDE= \ file contains overrides to /var/portbuild/${arch}/portbuild.conf. - Suggested values: + Suggested values: disconnected=1 http_proxy="http://localhost:3128/" squid_dir=/usr2/squid @@ -2028,16 +2020,16 @@ sudo_cmd="sudo -H" rsync_gzip=-z infoseek_host=localhost -infoseek_port=${tunelled-tcp-port} +infoseek_port=${tunelled-tcp-port} - Possible other values: + Possible other values: use_md_swap=1 md_size=9g use_zfs=1 scp_cmd="/usr/local/bin/scp" ssh_cmd="/usr/local/bin/ssh" - + @@ -2056,9 +2048,8 @@ ssh_cmd="/usr/local/bin/ssh" Add an appropriate data_source entry to /usr/local/etc/gmetad.conf: - - data_source "arch/location Package Build Cluster" 30 hostname - + + data_source "arch/location Package Build Cluster" 30 hostname You will need to restart gmetad. @@ -2078,7 +2069,7 @@ ssh_cmd="/usr/local/bin/ssh" Ensure that ssh to the client is working by executing - ssh hostname uname -a. + ssh hostname uname -a. The actual command is not important; what is important is to confirm the setup, and also add an entry into known_hosts, once you have confirmed the @@ -2089,14 +2080,14 @@ ssh_cmd="/usr/local/bin/ssh" Populate the client's copy of /var/portbuild/scripts/ by something like - /var/portbuild/scripts/dosetupnode arch major latest hostname. + /var/portbuild/scripts/dosetupnode arch major latest hostname. Verify that you now have files in that directory. Test the other TCP ports by executing - telnet hostname portnumber. + telnet hostname portnumber. 414 (or its tunnel) should give you a few lines of status information including arch and osversion; 8649 should @@ -2114,7 +2105,7 @@ ssh_cmd="/usr/local/bin/ssh" Tell qmanager about the node. Example: - python path/qmanager/qclient add + python path/qmanager/qclient add name=uniquename arch=arch osversion=osversion @@ -2125,7 +2116,7 @@ ssh_cmd="/usr/local/bin/ssh" primarypool=package pools="package all" maxjobs=1 acl="ports-arch,deny_all" - + @@ -2382,15 +2373,15 @@ dopackages without -n Create a new zfs filesystem: - zfs create -o mountpoint=/a/portbuild/arch a/portbuild/arch + &prompt.root; zfs create -o mountpoint=/a/portbuild/arch a/portbuild/arch -chown ports-arch:portbuild /var/portbuild/arch; -chmod 775 /var/portbuild/arch; -cd /var/portbuild/arch +&prompt.root; chown ports-arch:portbuild /var/portbuild/arch; +&prompt.root; chmod 775 /var/portbuild/arch; +&prompt.root; cd /var/portbuild/arch @@ -2416,7 +2407,7 @@ cd /var/portbuild/arch Kick-start the build for the branch with - build create arch branch + &prompt.root; build create arch branch @@ -2432,8 +2423,8 @@ cd /var/portbuild/arch Creating and linking an external archive directory - mkdir /dumpster/pointyhat/arch/archive - ln -s /dumpster/pointyhat/arch/archive archive + &prompt.root; mkdir /dumpster/pointyhat/arch/archive +&prompt.root; ln -s /dumpster/pointyhat/arch/archive archive @@ -2465,7 +2456,7 @@ cd /var/portbuild/arch - cd .ssh && ssh-keygen + &prompt.root; cd .ssh && ssh-keygen @@ -2479,9 +2470,9 @@ cd /var/portbuild/arch - Make a private configuration directory: - mkdir /var/portbuild/conf/arch - + Make a private configuration directory: + + &prompt.root; mkdir /var/portbuild/conf/arch @@ -2585,13 +2576,13 @@ cd /var/portbuild/arch Export that value for a later initialization step: - &prompt.root; export PORTBUILD_USER=portbuild + &prompt.root; export PORTBUILD_USER=portbuild - Add the following to /boot/loader.conf: -console="vidconsole,comconsole" + Add the following to /boot/loader.conf: +console="vidconsole,comconsole" *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***