From owner-svn-doc-all@FreeBSD.ORG Sat Nov 24 07:12:46 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 BC74FD78; Sat, 24 Nov 2012 07:12:46 +0000 (UTC) (envelope-from linimon@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 9F9678FC08; Sat, 24 Nov 2012 07:12:46 +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 qAO7Ck39092202; Sat, 24 Nov 2012 07:12:46 GMT (envelope-from linimon@svn.freebsd.org) Received: (from linimon@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id qAO7Ck3g092201; Sat, 24 Nov 2012 07:12:46 GMT (envelope-from linimon@svn.freebsd.org) Message-Id: <201211240712.qAO7Ck3g092201@svn.freebsd.org> From: Mark Linimon Date: Sat, 24 Nov 2012 07:12:46 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40147 - 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: Sat, 24 Nov 2012 07:12:46 -0000 Author: linimon Date: Sat Nov 24 07:12:46 2012 New Revision: 40147 URL: http://svnweb.freebsd.org/changeset/doc/40147 Log: Attempt to pacify igor. The few remaining complaints appear to be false positives. 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 Sat Nov 24 02:13:49 2012 (r40146) +++ head/en_US.ISO8859-1/articles/portbuild/article.xml Sat Nov 24 07:12:46 2012 (r40147) @@ -66,9 +66,9 @@ otherwise specified, all paths will be relative to this location. ${arch} will be used to specify one of the package architectures - (e.g. amd64, arm, &i386;, ia64, powerpc, &sparc64;), and + (e.g., amd64, arm, &i386;, ia64, powerpc, &sparc64;), and ${branch} will be used - to specify the build branch (e.g. 7, 7-exp, 8, 8-exp, 9, 9-exp, 10, 10-exp). + to specify the build branch (e.g., 7, 7-exp, 8, 8-exp, 9, 9-exp, 10, 10-exp). The set of branches that portmgr currently supports is the same as those that the &os; security team @@ -444,7 +444,7 @@ PKG_BIN=/usr/local/sbin/pkg-keep - Do not delete this build in the future, when it would be normally deleted as part of the latest - previous cycle. - Don't forget to clean it up manually when you no longer need it. + Do not forget to clean it up manually when you no longer need it. @@ -452,8 +452,8 @@ PKG_BIN=/usr/local/sbin/pkg-nofinish - 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, don't forget to cleanup - the clients when you don't need the build anymore. + once it finishes. If you use this option, do not forget to cleanup + the clients when you do not need the build any more. @@ -520,7 +520,7 @@ PKG_BIN=/usr/local/sbin/pkg -noduds - Do not rebuild the duds file (ports that are never - built, e.g. those marked IGNORE, + built, e.g., those marked IGNORE, NO_PACKAGE, etc.) during preprocessing. @@ -654,7 +654,7 @@ PKG_BIN=/usr/local/sbin/pkgThe actual package build itself occurs in two identical phases. The reason for this is that sometimes - transient problems (e.g. NFS failures, FTP sites being + transient problems (e.g., NFS failures, FTP sites being unreachable, etc.) may halt a build. Doing things in two phases is a workaround for these types of problems. @@ -742,7 +742,7 @@ PKG_BIN=/usr/local/sbin/pkgbuild srcupdate arch branch buildid - Replaces the src - tree with a new ZFS snapshot. Don't forget to use + tree with a new ZFS snapshot. Do not forget to use -nosrc flag to dopackages later! @@ -752,7 +752,7 @@ PKG_BIN=/usr/local/sbin/pkgbuild portsupdate arch branch buildid - Replaces the ports - tree with a new ZFS snapshot. Don't forget to use + tree with a new ZFS snapshot. Do not forget to use -noports flag to dopackages later! @@ -887,7 +887,7 @@ 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, @@ -925,8 +925,8 @@ PKG_BIN=/usr/local/sbin/pkgloads is refreshed every 2 minutes. If you do ps x | grep pdispatch - and it's less than the number of jobs that loads - thinks are in use, you're in trouble. + and it is less than the number of jobs that loads + thinks are in use, you are in trouble. You may have problem with the umount commands hanging. If so, you are going to have to use the @@ -1260,7 +1260,7 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 one of the symlinks that points to it. - If you are doing a completely new package set (e.g. for + If you are doing a completely new package set (e.g., for a new release), copy packages to the staging area on ftp-master with something like the following: @@ -1336,7 +1336,7 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 tested. Since the machine is shared, someone else may delete your - changes by mistake, so keep a copy of them in e.g. your home + changes by mistake, so keep a copy of them in e.g., your home directory on freefall. Do not use tmp/; since pointyhat itself runs some version of -CURRENT, you @@ -1417,7 +1417,7 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 - Port was broken due to a transient error (e.g. FTP site + Port was broken due to a transient error (e.g., FTP site down, package client error, etc.) @@ -1461,7 +1461,7 @@ 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. + (i.e., .tgz or .tbz) is optional. This will build only those packages listed as well as all of their dependencies. @@ -1579,7 +1579,7 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 /usr2/.) The filename chroot is a - a historical remnant. + historical remnant. @@ -1821,7 +1821,7 @@ squid_pidfile="/u > kern.maxfiles=40000 > kern.maxfilesperproc=30000 > -> # Since the NFS root is static we don't need to check frequently for file changes +> # Since the NFS root is static we do not need to check frequently for file changes > # This saves >75% of NFS traffic > vfs.nfs.access_cache_timeout=300 > debug.debugger_on_panic=1 @@ -2104,7 +2104,7 @@ MASTER_SITE_OVERRIDE= \ Hint: you will need one of these for each machine; however, if you have multiple machines at one site, you - should create a site-specific one (e.g. in + should create a site-specific one (e.g., in /var/portbuild/conf/clients/) and symlink to it. @@ -2855,7 +2855,7 @@ apache_pidfile="/var/run/httpd.pid" gmetad_enable="YES" gmond_enable="YES" inetd_enable="YES" -# XXX MCL these don't work! +# XXX MCL these do not work! #inetd_flags="-R 10000 -lw" mountd_enable="YES" nfs_server_enable="YES" @@ -3256,16 +3256,16 @@ ganglia:*:102:102::0:0:User &:/usr/l and is somewhat obsolete. - When a machine has a disk failure (e.g. panics due to read errors, + When a machine has a disk failure (e.g., panics due to read errors, etc), then we should do the following steps: - Note the time and failure mode (e.g. paste in the + Note the time and failure mode (e.g., paste in the relevant console output) in /var/portbuild/${arch}/reboots For i386 gohan clients, scrub the disk by touching - /SCRUB in the nfsroot (e.g. + /SCRUB in the nfsroot (e.g., /a/nfs/8.dir1/SCRUB) and rebooting. This will dd if=/dev/zero of=/dev/ad0 and force the drive to remap any bad sectors it finds, if it has enough spares left. This is @@ -3276,7 +3276,7 @@ ganglia:*:102:102::0:0:User &:/usr/l disk seems to be that the blade will completely hang and be unresponsive to either console break, or even NMI. - For other build systems that don't newfs their disk at boot (e.g. + For other build systems that do not newfs their disk at boot (e.g., amd64 systems) this step has to be skipped. If the problem recurs, then the disk is probably toast.