From owner-svn-doc-projects@FreeBSD.ORG Mon Feb 18 15:29:08 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id C4E5CD49; Mon, 18 Feb 2013 15:29:08 +0000 (UTC) (envelope-from gabor@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 AF24035D; Mon, 18 Feb 2013 15:29:08 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1IFT8lN013554; Mon, 18 Feb 2013 15:29:08 GMT (envelope-from gabor@svn.freebsd.org) Received: (from gabor@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1IFT7la013541; Mon, 18 Feb 2013 15:29:07 GMT (envelope-from gabor@svn.freebsd.org) Message-Id: <201302181529.r1IFT7la013541@svn.freebsd.org> From: Gabor Kovesdan Date: Mon, 18 Feb 2013 15:29:07 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41007 - in projects/xml-tools: bn_BD.ISO10646-1/articles/explaining-bsd bn_BD.ISO10646-1/articles/new-users de_DE.ISO8859-1/htdocs de_DE.ISO8859-1/share/xml en_US.ISO8859-1/articles/co... X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Feb 2013 15:29:08 -0000 Author: gabor Date: Mon Feb 18 15:29:06 2013 New Revision: 41007 URL: http://svnweb.freebsd.org/changeset/doc/41007 Log: - MFH Added: projects/xml-tools/share/pgpkeys/achim.key - copied unchanged from r41006, head/share/pgpkeys/achim.key projects/xml-tools/share/pgpkeys/pclin.key - copied unchanged from r41006, head/share/pgpkeys/pclin.key Deleted: projects/xml-tools/en_US.ISO8859-1/htdocs/FAQ/ Modified: projects/xml-tools/bn_BD.ISO10646-1/articles/explaining-bsd/article.xml projects/xml-tools/bn_BD.ISO10646-1/articles/new-users/article.xml projects/xml-tools/de_DE.ISO8859-1/htdocs/about.xml projects/xml-tools/de_DE.ISO8859-1/share/xml/news.xml projects/xml-tools/de_DE.ISO8859-1/share/xml/press.xml projects/xml-tools/en_US.ISO8859-1/articles/committers-guide/article.xml projects/xml-tools/en_US.ISO8859-1/articles/contributors/contrib.additional.xml projects/xml-tools/en_US.ISO8859-1/articles/contributors/contrib.committers.xml projects/xml-tools/en_US.ISO8859-1/articles/portbuild/article.xml projects/xml-tools/en_US.ISO8859-1/books/arch-handbook/book.xml projects/xml-tools/en_US.ISO8859-1/books/arch-handbook/boot/chapter.xml projects/xml-tools/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml projects/xml-tools/en_US.ISO8859-1/books/arch-handbook/isa/chapter.xml projects/xml-tools/en_US.ISO8859-1/books/arch-handbook/jail/chapter.xml projects/xml-tools/en_US.ISO8859-1/books/arch-handbook/kobj/chapter.xml projects/xml-tools/en_US.ISO8859-1/books/arch-handbook/mac/chapter.xml projects/xml-tools/en_US.ISO8859-1/books/arch-handbook/newbus/chapter.xml projects/xml-tools/en_US.ISO8859-1/books/arch-handbook/pccard/chapter.xml projects/xml-tools/en_US.ISO8859-1/books/arch-handbook/scsi/chapter.xml projects/xml-tools/en_US.ISO8859-1/books/arch-handbook/smp/chapter.xml projects/xml-tools/en_US.ISO8859-1/books/arch-handbook/sound/chapter.xml projects/xml-tools/en_US.ISO8859-1/books/arch-handbook/usb/chapter.xml projects/xml-tools/en_US.ISO8859-1/books/arch-handbook/vm/chapter.xml projects/xml-tools/en_US.ISO8859-1/books/developers-handbook/testing/chapter.xml projects/xml-tools/en_US.ISO8859-1/books/developers-handbook/tools/chapter.xml projects/xml-tools/en_US.ISO8859-1/books/faq/book.xml projects/xml-tools/en_US.ISO8859-1/books/fdp-primer/book.xml projects/xml-tools/en_US.ISO8859-1/books/handbook/book.xml projects/xml-tools/en_US.ISO8859-1/books/handbook/boot/chapter.xml projects/xml-tools/en_US.ISO8859-1/books/handbook/config/chapter.xml projects/xml-tools/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml projects/xml-tools/en_US.ISO8859-1/books/handbook/desktop/chapter.xml projects/xml-tools/en_US.ISO8859-1/books/handbook/disks/chapter.xml projects/xml-tools/en_US.ISO8859-1/books/handbook/filesystems/chapter.xml projects/xml-tools/en_US.ISO8859-1/books/handbook/firewalls/chapter.xml projects/xml-tools/en_US.ISO8859-1/books/handbook/geom/chapter.xml projects/xml-tools/en_US.ISO8859-1/books/handbook/introduction/chapter.xml projects/xml-tools/en_US.ISO8859-1/books/handbook/jails/chapter.xml projects/xml-tools/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.xml projects/xml-tools/en_US.ISO8859-1/books/handbook/l10n/chapter.xml projects/xml-tools/en_US.ISO8859-1/books/handbook/linuxemu/chapter.xml projects/xml-tools/en_US.ISO8859-1/books/handbook/mac/chapter.xml projects/xml-tools/en_US.ISO8859-1/books/handbook/mail/chapter.xml projects/xml-tools/en_US.ISO8859-1/books/handbook/mirrors/chapter.xml projects/xml-tools/en_US.ISO8859-1/books/handbook/printing/chapter.xml projects/xml-tools/en_US.ISO8859-1/books/porters-handbook/book.xml (contents, props changed) projects/xml-tools/en_US.ISO8859-1/htdocs/Makefile projects/xml-tools/en_US.ISO8859-1/htdocs/donations/wantlist.xml projects/xml-tools/en_US.ISO8859-1/htdocs/features.xml projects/xml-tools/en_US.ISO8859-1/htdocs/internal/internal.xml projects/xml-tools/en_US.ISO8859-1/htdocs/layout/css/layout.css projects/xml-tools/en_US.ISO8859-1/htdocs/mailto.xml projects/xml-tools/en_US.ISO8859-1/htdocs/projects/newbies.xml projects/xml-tools/en_US.ISO8859-1/htdocs/releng/index.xml projects/xml-tools/ja_JP.eucJP/books/handbook/advanced-networking/chapter.xml projects/xml-tools/ja_JP.eucJP/books/handbook/cutting-edge/chapter.xml projects/xml-tools/ja_JP.eucJP/books/handbook/mirrors/chapter.xml projects/xml-tools/ja_JP.eucJP/books/handbook/ports/chapter.xml projects/xml-tools/ja_JP.eucJP/htdocs/internal/internal.xml projects/xml-tools/ja_JP.eucJP/htdocs/mailto.xml projects/xml-tools/ja_JP.eucJP/share/xml/news.xml projects/xml-tools/nl_NL.ISO8859-1/articles/contributing/article.xml projects/xml-tools/nl_NL.ISO8859-1/books/handbook/audit/chapter.xml projects/xml-tools/nl_NL.ISO8859-1/books/handbook/disks/chapter.xml projects/xml-tools/nl_NL.ISO8859-1/books/handbook/filesystems/chapter.xml projects/xml-tools/nl_NL.ISO8859-1/books/handbook/firewalls/chapter.xml projects/xml-tools/nl_NL.ISO8859-1/books/handbook/jails/chapter.xml projects/xml-tools/nl_NL.ISO8859-1/books/handbook/linuxemu/chapter.xml projects/xml-tools/nl_NL.ISO8859-1/books/handbook/mail/chapter.xml projects/xml-tools/nl_NL.ISO8859-1/books/handbook/multimedia/chapter.xml projects/xml-tools/nl_NL.ISO8859-1/books/handbook/network-servers/chapter.xml projects/xml-tools/nl_NL.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml projects/xml-tools/nl_NL.ISO8859-1/books/handbook/security/chapter.xml projects/xml-tools/nl_NL.ISO8859-1/books/handbook/virtualization/chapter.xml projects/xml-tools/share/pgpkeys/des.key projects/xml-tools/share/pgpkeys/pgpkeys-developers.xml projects/xml-tools/share/pgpkeys/pgpkeys.ent projects/xml-tools/share/xml/authors.ent projects/xml-tools/share/xml/developers.ent projects/xml-tools/share/xml/mirrors.xml projects/xml-tools/share/xml/news.xml projects/xml-tools/share/xml/press.xml Directory Properties: projects/xml-tools/ (props changed) projects/xml-tools/de_DE.ISO8859-1/ (props changed) projects/xml-tools/en_US.ISO8859-1/ (props changed) projects/xml-tools/ja_JP.eucJP/ (props changed) projects/xml-tools/nl_NL.ISO8859-1/ (props changed) projects/xml-tools/share/ (props changed) Modified: projects/xml-tools/bn_BD.ISO10646-1/articles/explaining-bsd/article.xml ============================================================================== --- projects/xml-tools/bn_BD.ISO10646-1/articles/explaining-bsd/article.xml Mon Feb 18 13:03:19 2013 (r41006) +++ projects/xml-tools/bn_BD.ISO10646-1/articles/explaining-bsd/article.xml Mon Feb 18 15:29:06 2013 (r41007) @@ -1,3 +1,4 @@ + @@ -16,6 +16,26 @@ + 2013 + + + 1 + + + A Decade of OS Access-control Extensibility + https://queue.acm.org/detail.cfm?id=2430732 + ACM Queue + https://queue.acm.org/ + 18. Januar 2013 + Robert N. M. Watson +

Wer sich näher mit der Absicherung von Betriebssystemen + beschäftigt, ist erstaunt über die zahlreichen in der + Praxis eingesetzten Modelle zur Zugangskontrolle.

+ + + + + 2012 Modified: projects/xml-tools/en_US.ISO8859-1/articles/committers-guide/article.xml ============================================================================== --- projects/xml-tools/en_US.ISO8859-1/articles/committers-guide/article.xml Mon Feb 18 13:03:19 2013 (r41006) +++ projects/xml-tools/en_US.ISO8859-1/articles/committers-guide/article.xml Mon Feb 18 15:29:06 2013 (r41007) @@ -4156,24 +4156,6 @@ bak/packages packages from last complet there are at least some perks: - - - Direct access to cvsup-master - - - As a committer, you may apply to &a.kuriyama; for direct access - to cvsup-master.FreeBSD.org, - providing the public key output from cvpasswd - yourusername@FreeBSD.org - freefall.FreeBSD.org. Please note: you must - specify freefall.FreeBSD.org on the - cvpasswd command line even though the - actual server is cvsup-master. Access to - cvsup-master should not be overused as it is - a busy machine. - - - Free 4-CD and DVD Sets Modified: projects/xml-tools/en_US.ISO8859-1/articles/contributors/contrib.additional.xml ============================================================================== --- projects/xml-tools/en_US.ISO8859-1/articles/contributors/contrib.additional.xml Mon Feb 18 13:03:19 2013 (r41006) +++ projects/xml-tools/en_US.ISO8859-1/articles/contributors/contrib.additional.xml Mon Feb 18 15:29:06 2013 (r41007) @@ -2603,6 +2603,11 @@ + Dmitry Kazarov + d.y.kazarov@mail.ru + + + Dmitry Khrustalev dima@xyzzy.machaon.ru @@ -3366,7 +3371,7 @@ Gary Hayers - gary@hayers.net + gary@hayers.org @@ -6835,6 +6840,11 @@ + Michael Sanders + mike@topcat.hypermart.net + + + Michael Sardo jaeger16@yahoo.com @@ -8380,11 +8390,6 @@ - Po-Chien Lin - linpc@cs.nctu.edu.tw - - - Pomegranate daver@flag.blackened.net @@ -8792,6 +8797,11 @@ + Dr. Rolf Jansen + cyclaero@gmail.com + + + Roman Neuhauser neuhauser@chello.cz Modified: projects/xml-tools/en_US.ISO8859-1/articles/contributors/contrib.committers.xml ============================================================================== --- projects/xml-tools/en_US.ISO8859-1/articles/contributors/contrib.committers.xml Mon Feb 18 13:03:19 2013 (r41006) +++ projects/xml-tools/en_US.ISO8859-1/articles/contributors/contrib.committers.xml Mon Feb 18 15:29:06 2013 (r41007) @@ -524,6 +524,10 @@ + &a.smh; + + + &a.ehaupt; @@ -820,6 +824,10 @@ + &a.achim; + + + &a.truckman; @@ -840,6 +848,10 @@ + &a.pclin; + + + &a.yzlin; Modified: projects/xml-tools/en_US.ISO8859-1/articles/portbuild/article.xml ============================================================================== --- projects/xml-tools/en_US.ISO8859-1/articles/portbuild/article.xml Mon Feb 18 13:03:19 2013 (r41006) +++ projects/xml-tools/en_US.ISO8859-1/articles/portbuild/article.xml Mon Feb 18 15:29:06 2013 (r41007) @@ -60,7 +60,7 @@ The codebase Most of the package building magic occurs under the - /var/portbuild directory. Unless + /a/portbuild directory. Unless otherwise specified, all paths will be relative to this location. ${arch} will be used to specify one of the package architectures @@ -74,15 +74,16 @@ - Packages are no longer built for branches 4, 5, or 6, nor + FreeBSD no longer builds packages for branches 4, 5, or 6, nor for the alpha architecture. - The scripts that control all of this live in - /var/portbuild/scripts/. + The scripts that control all of this live in either + /a/portbuild/scripts/ or. + /a/portbuild/admin/scripts/. These are the checked-out copies from the Subversion repository at - - base/projects/portbuild/scripts/ + + base/projects/portbuild/ . Typically, incremental builds are done that use previous @@ -109,7 +110,7 @@ - Notes on the codebase + Historical notes on the codebase Until mid-2010, the scripts were completely specific to pointyhat.FreeBSD.org as the head (dispatch) node. During @@ -145,18 +146,6 @@ - This document was originally written before these changes - were made. Where things such as script invocations have changed, - they were denoted as new codebase: as opposed - to old codebase:. - - - Up until November 2012, pointyhat had still - been running the old codebase. That installation has now been - permanently offlined. Therefore, all the instructions having - to do with the old codebase have been removed. - - Also during this process, the codebase was migrated to the @@ -166,16 +155,61 @@ found in CVS. + + + Notes on privilege separation + + As of January 2013, a rewrite is in progress to further separate + privileges. The following concepts are introduced: + + + + Server-side user portbuild assumes all + responsiblity for operations involving builds and communicating + with the clients. This user no longer has access to + sudo. + + + + Server-side user srcbuild is created + and given responsiblity for operations involving both VCS + operations and anything involving src builds for the clients. + This user does not have access to + sudo. + + + + The server-side + ports-arch + users go away. + + + + None of the above server-side users have + ssh keys. Individual + portmgr will accomplish all those + tasks using ksu. (This is + still work-in-progress.) + + + + The only client-side user is also named + portbuild and still has access to + sudo for the purpose of managing + jails. + + + Build Client Management - The &i386; clients co-located with pointyhat - netboot from it (connected nodes); all - other clients (disconnected nodes) - are either self-hosted or netboot from some other - pxe host. + You may set up clients to either netboot from the master + (connected nodes) + or have them either self-hosted or netboot from some other + pxe host + (disconnected nodes). In all cases they set themselves up at boot-time to prepare to build packages. @@ -200,29 +234,31 @@ Jail Build Environment Setup - Package builds are performed in a + Package builds are performed by the clients in a jail populated by the portbuild script using the ${arch}/${branch}/builds/${buildid}/bindist.tar file. - The makeworld command builds a world from the + On the server, use the + makeworld command to build a world from the ${arch}/${branch}/builds/${buildid}/src/ - tree and installs it into + tree and install it into ${arch}/${branch}/builds/${buildid}/bindist.tar. The tree will be updated first unless -novcs is - specified. It should be run as root: + specified. - &prompt.root; /var/portbuild/scripts/makeworld ${arch} ${branch} ${buildid} [-novcs] + &prompt.root; /a/portbuild/admin/scripts/makeworld ${arch} ${branch} ${buildid} [-novcs] - The bindist.tar tarball is created from the + Similiarly on the server, the + bindist.tar tarball is created from the previously installed world by the mkbindist - script. It should be also be run as root: + script. - &prompt.root; /var/portbuild/scripts/mkbindist ${arch} ${branch} ${buildid} + &prompt.root; /a/portbuild/admin/scripts/mkbindist ${arch} ${branch} ${buildid} - The per-machine tarballs are located in + The per-machine tarballs are located on the server in ${arch}/clients. The bindist.tar file is extracted @@ -233,6 +269,16 @@ For both commands above, if ${buildid} is latest, it may be omitted. + + + Currently the above two scripts must be run as + root; otherwise, the install scripts + lack sufficient permissions. This is undesirable for + security reasons. Work is in progress in -HEAD to allow + users to do installations; once that is committed, the + intention is to use that and run these two commands as + srcbuild. + @@ -782,7 +828,7 @@ PKG_BIN=/usr/local/sbin/pkgTo free up resources, you will need to clean up client machines by running build cleanup command. For example: - &prompt.user; /var/portbuild/scripts/build cleanup i386 8-exp 20080714120411 -full + &prompt.user; /a/portbuild/scripts/build cleanup i386 8-exp 20080714120411 -full If you forget to do this, then the old build jails will not be cleaned up for 24 hours, and no @@ -797,6 +843,11 @@ PKG_BIN=/usr/local/sbin/pkgloads thinks are in use, you are in trouble. + + The following notes about mounting only apply to + connected nodes. + + You may have problem with the umount commands hanging. If so, you are going to have to use the allgohans script to run an &man.ssh.1; @@ -826,6 +877,11 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 You may also see messages about procfs. + + The above is the end of the notes that apply only to + connected nodes. + + After you have done all the above, remove the ${arch}/lock file before trying to restart the build. If you do not, @@ -872,7 +928,7 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 scripts/stats ${branch} command shows the number of packages already built. - Running cat /var/portbuild/*/loads/* + Running cat /a/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. @@ -909,7 +965,7 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 it if not. Keep an eye on &man.df.1; output. If the - /var/portbuild file system becomes full + /a/portbuild file system becomes full then Bad Things happen. The status of all current builds is generated periodically @@ -1014,12 +1070,7 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 &prompt.user; cd ${arch}/${branch} &prompt.user; find distfiles > distfiles-${release} - - This inventory file typically lives in - i386/${branch} - on the cluster master. - - This is useful to aid in periodically cleaning out + You should use that output to periodically clean out the distfiles from ftp-master. When space gets tight, distfiles from recent releases can be kept while others can be thrown away. @@ -1043,6 +1094,16 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 Uploading Packages + + For FreeBSD.org as of 2013, the instructions + about uploading to ftp-master are obsolete. + In the future, ftp-master will pull + from pointyhat, using a mechanism yet + to be implemented. However, the instructions about + RESTRICTED and NO_CDROM + must still be carefully followed. + + 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 @@ -1120,7 +1181,7 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 a new release), copy packages to the staging area on ftp-master with something like the following: - &prompt.root; cd /var/portbuild/${arch}/${branch} + &prompt.root; cd /a/portbuild/${arch}/${branch} &prompt.root; tar cfv - packages/ | ssh portmgr@ftp-master tar xfC - w/ports/${arch}/tmp/${subdir} Then log into ftp-master, verify that @@ -1148,7 +1209,7 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 Distfiles should be transferred with the cpdistfiles script: - &prompt.root; /var/portbuild/scripts/cpdistfiles ${arch} ${branch} ${buildid} [-yesreally] | tee log2 + &prompt.root; /a/portbuild/scripts/cpdistfiles ${arch} ${branch} ${buildid} [-yesreally] | tee log2 Doing it by hand is deprecated. @@ -1156,6 +1217,11 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 Experimental Patches Builds + + Most of the information in this section is obsolete + as of 2013 and needs to be rewritten. + + Experimental patches builds are run from time to time to new features or bugfixes to the ports infrastructure (i.e. bsd.port.mk), or to test large sweeping @@ -1206,21 +1272,15 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 build. This will ensure an apples-to-apples comparison later. - - Once the build finishes, compare the control build failures to those of the experimental patches build. Use the following commands to facilitate this (this assumes the 8 branch is the control branch, and the 8-exp branch is the experimental patches branch): - &prompt.user; cd /var/portbuild/i386/8-exp/errors + &prompt.user; cd /a/portbuild/i386/8-exp/errors &prompt.user; find . -name \*.log\* | sort > /tmp/8-exp-errs -&prompt.user; cd /var/portbuild/i386/8/errors +&prompt.user; cd /a/portbuild/i386/8/errors &prompt.user; find . -name \*.log\* | sort > /tmp/8-errs @@ -1283,7 +1343,7 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 rebuild of the affected packages under the control branch: - &prompt.user; cd /var/portbuild/i386/8/ports + &prompt.user; cd /a/portbuild/i386/8/ports The following example is obsolete @@ -1296,9 +1356,9 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 The following command will set up the control branch for - the partial build (old codebase): + the partial build: - &prompt.user; /var/portbuild/scripts/dopackages.8 -noportsvcs -nobuild -novcs -nofinish + &prompt.user; /a/portbuild/scripts/dopackages.wrapper i386 8 -noportsvcs -nobuild -novcs -nofinish The builds must be performed from the @@ -1306,14 +1366,14 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 initially be empty except for the Makefile symlink. If this symlink does not exist, it must be created: - &prompt.user; cd /var/portbuild/i386/8/packages/All + &prompt.user; cd /a/portbuild/i386/8/packages/All &prompt.user; ln -sf ../../Makefile . &prompt.user; make -k -j<#> <list of packages to build> <#> is the concurrency of the build to attempt. It is usually the sum of the weights listed in - /var/portbuild/i386/mlist unless you have a + /a/portbuild/i386/mlist unless you have a reason to run a heavier or lighter build. The list of packages to build should be a list of package @@ -1346,17 +1406,15 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 Before following these steps, please coordinate with portmgr. - - Due to some generous donations, portmgr is - no longer looking for the loan of &i386; or amd64 - systems. However, we are still interested in borrowing tier-2 - systems. - - Node requirements - portmgr is still working on characterizing + + This section is only of interest when considering + tier-2 architectures. + + + Here are the requirement for what a node needs to be generally useful. @@ -1436,7 +1494,8 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 /usr2/.) The filename chroot is a - historical remnant. + historical remnant. The chroot + command is no longer used. @@ -1477,8 +1536,9 @@ 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 on &i386;, and + you are using more than + 3.5G, PAE). Required options: @@ -1493,9 +1553,14 @@ options SHMMAXPGS=65536 options SEMMNI=40 options SEMMNS=240 options SEMUME=40 -options SEMMNU=120 +options SEMMNU=120 + + If you are interested in debugging general + problems, you may wish to use the following. + However, for unattended operations, it is best + to leave it out: -options ALT_BREAK_TO_DEBUGGER + options ALT_BREAK_TO_DEBUGGER For PAE, it is not currently possible to load modules. Therefore, if you are running an architecture @@ -1912,7 +1977,7 @@ portbuild ALL=(ALL) NOPASSWD: ALL

Create - /var/portbuild/${arch}/clients/bindist-${hostname}.tar. + /a/portbuild/${arch}/clients/bindist-${hostname}.tar. @@ -1951,16 +2016,16 @@ 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 - /var/portbuild/conf/clients/) + /a/portbuild/conf/clients/) and symlink to it. Create -/var/portbuild/${arch}/portbuild-${hostname} +/a/portbuild/${arch}/portbuild-${hostname} using one of the existing ones as a guide. This file contains overrides to -/var/portbuild/${arch}/portbuild.conf. +/a/portbuild/${arch}/portbuild.conf. Suggested values: @@ -2026,7 +2091,7 @@ 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. + /a/portbuild/scripts/dosetupnode arch major latest hostname. Verify that you now have files in that directory. @@ -2071,7 +2136,7 @@ ssh_cmd="/usr/local/bin/ssh"Once you are sure that the client is working, tell pollmachine about it by adding it to - /var/portbuild/${arch}/mlist. + /a/portbuild/${arch}/mlist. @@ -2087,10 +2152,15 @@ ssh_cmd="/usr/local/bin/ssh"HEAD. + + As + srcbuild: + + - Edit /var/portbuild/conf/server.conf + Edit /a/portbuild/conf/admin/admin.conf with the following changes: @@ -2115,7 +2185,7 @@ ssh_cmd="/usr/local/bin/ssh" - Run /var/portbuild/updatesnap manually. + Run /a/portbuild/admin/scripts/updatesnap manually. @@ -2123,24 +2193,21 @@ ssh_cmd="/usr/local/bin/ssh" Steps necessary after <application>qmanager</application> is started - - Again, as - portbuild: - - For each branch that will be supported, do the following: - Kick-start the build for the branch with: + As portbuild, + kick-start the build for the branch with: build create arch branch - Create + As srcbuild, + create bindist.tar. @@ -2157,7 +2224,7 @@ ssh_cmd="/usr/local/bin/ssh" - Edit /var/portbuild/conf/server.conf + Edit /a/portbuild/admin/conf/admin.conf with the following changes: @@ -2184,7 +2251,7 @@ zfs destroy -r a/snap/src-o You will probably find that the following files and - symlinks in /var/portbuild/errorlogs/ + symlinks in /a/portbuild/errorlogs/ can be removed: @@ -2229,7 +2296,7 @@ zfs destroy -r a/snap/src-o - Edit /var/portbuild/conf/server.conf + Edit /a/portbuild/admin/conf/admin.conf with the following changes: @@ -2244,7 +2311,7 @@ zfs destroy -r a/snap/src-o - Run /var/portbuild/updatesnap manually. + Run /a/portbuild/admin/scripts/updatesnap manually. @@ -2268,49 +2335,24 @@ zfs destroy -r a/snap/src-o Steps necessary before <application>qmanager</application> is started - The initial steps need to be done as - root. + The next steps are most easily done as user + portbuild. - - - If it has not already been done, create the - portbuild - user and group. - - - - mkdir /var/portbuild/arch - - - - Create a new zfs filesystem: - - &prompt.root; zfs create -o mountpoint=/a/portbuild/arch a/portbuild/arch - - - - &prompt.root; chown portbuild:portbuild /var/portbuild/arch; -&prompt.root; chmod 775 /var/portbuild/arch; -&prompt.root; cd /var/portbuild/arch - - - - Create the .ssh directory. - - - - The next steps are most easily done as user - portbuild. + The following assumes you have already run + mkportbuild. - Create an archive directory for buildlogs and errorlogs - under archive/. + As the portbuild user, run + + &prompt.user; /a/portbuild/admin/tools/addarch arch + + For each branch that will be supported, do the following: @@ -2354,8 +2396,10 @@ zfs destroy -r a/snap/src-o - Create a fresh portbuild.conf file - from one of the ones for another architecture. + Edit portbuild.conf + from one of the ones for another architecture. + addarch will have created a default + one for you. @@ -2365,23 +2409,13 @@ zfs destroy -r a/snap/src-o - &prompt.root; cd .ssh && ssh-keygen - - - - If desired, - edit the .ssh/config file for - convenience in using ssh. - - - If you need to create any tunnels: Make a private configuration directory: - &prompt.root; mkdir /var/portbuild/conf/arch + &prompt.root; mkdir /a/portbuild/conf/arch @@ -2393,26 +2427,26 @@ zfs destroy -r a/snap/src-o - Once again as root: + As srcbuild: Add arch to SUPPORTED_ARCHS in - /var/portbuild/conf/server.conf. + /a/portbuild/admin/conf/admin.conf. Add the arch directory to - /var/portbuild/scripts/zbackup and - /var/portbuild/scripts/zexpire. + /a/portbuild/admin/scripts/zbackup. + (This is a hack and should go away.) - Add an appropriate arch entry for - /var/portbuild/scripts/dologs to the portbuild + Enable the appropriate arch entry for + /a/portbuild/scripts/dologs to the portbuild crontab. (This is a hack and should go away.) @@ -2422,17 +2456,11 @@ zfs destroy -r a/snap/src-o Steps necessary after <application>qmanager</application> is started - Again as root: + Again as srcbuild: - Tell qmanager about the arch: - - python path/qmanager/qclient add_acl name=ports-arch uidlist=ports-arch gidlist=portbuild sense=1 - - - For each branch that will be supported, do the following: @@ -2452,54 +2480,6 @@ zfs destroy -r a/snap/src-o Please talk to Mark Linimon before making any changes to this section. - - Notes on privilege separation - - As of January 2013, a rewrite is in progress to further separate - privileges. The following concepts are introduced: - - - - Server-side user portbuild assumes all - responsiblity for operations involving builds and communicating - with the clients. This user no longer has access to - sudo. - - *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***