Date: Sat, 24 Nov 2012 07:12:46 +0000 (UTC) From: Mark Linimon <linimon@FreeBSD.org> 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 Message-ID: <201211240712.qAO7Ck3g092201@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
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. <replaceable>${arch}</replaceable> 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 <replaceable>${branch}</replaceable> 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 <username>portmgr</username> currently supports is the same as those that the &os; <ulink url="http://www.freebsd.org/security/index.html#supported-branches">security team</ulink> @@ -444,7 +444,7 @@ PKG_BIN=/usr/local/sbin/pkg</programlist <para><literal>-keep</literal> - Do not delete this build in the future, when it would be normally deleted as part of the <literal>latest</literal> - <literal>previous</literal> 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. </para> </listitem> @@ -452,8 +452,8 @@ PKG_BIN=/usr/local/sbin/pkg</programlist <para><literal>-nofinish</literal> - 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. </para> </listitem> @@ -520,7 +520,7 @@ PKG_BIN=/usr/local/sbin/pkg</programlist <listitem> <para><literal>-noduds</literal> - Do not rebuild the <filename>duds</filename> file (ports that are never - built, e.g. those marked <literal>IGNORE</literal>, + built, e.g., those marked <literal>IGNORE</literal>, <literal>NO_PACKAGE</literal>, etc.) during preprocessing. </para> @@ -654,7 +654,7 @@ PKG_BIN=/usr/local/sbin/pkg</programlist <note><para>The 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.</para></note> @@ -742,7 +742,7 @@ PKG_BIN=/usr/local/sbin/pkg</programlist <para><literal>build srcupdate <replaceable>arch</replaceable> <replaceable>branch</replaceable> <replaceable>buildid</replaceable></literal> - 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 <literal>-nosrc</literal> flag to <command>dopackages</command> later! </para> @@ -752,7 +752,7 @@ PKG_BIN=/usr/local/sbin/pkg</programlist <para><literal>build portsupdate <replaceable>arch</replaceable> <replaceable>branch</replaceable> <replaceable>buildid</replaceable></literal> - 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 <literal>-noports</literal> flag to <command>dopackages</command> later! </para> @@ -887,7 +887,7 @@ PKG_BIN=/usr/local/sbin/pkg</programlist identify the tty in which it's running (either record the output of &man.tty.1; when you start the build, or use <command>ps x</command> to identify it. You need to make sure that nothing else important - is running in this tty, e.g. <command>ps -t p1</command> or whatever. + is running in this tty, e.g., <command>ps -t p1</command> or whatever. If there is not, you can just kill off the whole term easily with <command>pkill -t pts/1</command>; otherwise issue a <command>kill -HUP</command> in there by, for example, @@ -925,8 +925,8 @@ PKG_BIN=/usr/local/sbin/pkg</programlist it thinks is running, and this should be roughly concordant with the load average. <literal>loads</literal> is refreshed every 2 minutes. If you do <command>ps x | grep pdispatch</command> - and it's less than the number of jobs that <literal>loads</literal> - thinks are in use, you're in trouble.</para> + and it is less than the number of jobs that <literal>loads</literal> + thinks are in use, you are in trouble.</para> <para>You may have problem with the <command>umount</command> 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.</para> </note> - <para>If you are doing a completely new package set (e.g. for + <para>If you are doing a completely new package set (e.g., for a new release), copy packages to the staging area on <hostid>ftp-master</hostid> with something like the following:</para> @@ -1336,7 +1336,7 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 tested.</para> <para>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 <hostid>freefall</hostid>. Do not use <filename>tmp/</filename>; since <hostid>pointyhat</hostid> itself runs some version of <literal>-CURRENT</literal>, you @@ -1417,7 +1417,7 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 </listitem> <listitem> - <para>Port was broken due to a transient error (e.g. FTP site + <para>Port was broken due to a transient error (e.g., FTP site down, package client error, etc.) </para> </listitem> @@ -1461,7 +1461,7 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 <para>The list of packages to build should be a list of package names (including versions) as they appear in <filename>INDEX</filename>. The <literal>PKGSUFFIX</literal> - (i.e. .tgz or .tbz) is optional.</para></note> + (i.e., .tgz or .tbz) is optional.</para></note> <para>This will build only those packages listed as well as all of their dependencies.</para> @@ -1579,7 +1579,7 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 <filename>/usr2/</filename>.)</para> <note> <para>The filename <filename>chroot</filename> is a - a historical remnant.</para> + historical remnant.</para> </note> </step> </procedure> @@ -1821,7 +1821,7 @@ squid_pidfile="<filename>/<replaceable>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= \ <para>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 <filename>/var/portbuild/conf/clients/</filename>) and symlink to it.</para> </step> @@ -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.</para> </note> - <para>When a machine has a disk failure (e.g. panics due to read errors, + <para>When a machine has a disk failure (e.g., panics due to read errors, etc), then we should do the following steps:</para> <itemizedlist> - <listitem><para>Note the time and failure mode (e.g. paste in the + <listitem><para>Note the time and failure mode (e.g., paste in the relevant console output) in <filename>/var/portbuild/<replaceable>${arch}</replaceable>/reboots</filename></para></listitem> <listitem><para>For i386 gohan clients, scrub the disk by touching - <filename>/SCRUB</filename> in the nfsroot (e.g. + <filename>/SCRUB</filename> in the nfsroot (e.g., <filename>/a/nfs/8.dir1/SCRUB</filename>) and rebooting. This will <command>dd if=/dev/zero of=/dev/ad0</command> 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.</para></note> - <para>For other build systems that don't newfs their disk at boot (e.g. + <para>For other build systems that do not newfs their disk at boot (e.g., amd64 systems) this step has to be skipped.</para></listitem> <listitem><para>If the problem recurs, then the disk is probably toast.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201211240712.qAO7Ck3g092201>