=================================================================== RCS file: /cvsrepo/anoncvs/cvs/www/anoncvs.html,v retrieving revision 1.332 retrieving revision 1.333 diff -c -r1.332 -r1.333 *** www/anoncvs.html 2010/10/22 15:16:08 1.332 --- www/anoncvs.html 2010/11/02 11:54:08 1.333 *************** *** 11,17 **** ! --- 11,17 ---- ! *************** *** 33,38 **** --- 33,39 ----
  • Getting crypto sources through cvs(1)
  • Example usages for cvs(1)
  • Use rsh(1) or ssh(1)? +
  • Mirroring the CVS repository via sup(1)
  • Setting up an anoncvs mirror *************** *** 503,512 **** # cvs -qd anoncvs@anoncvs.ca.openbsd.org:/cvs get -P src !

    (If you are following the patch branch for 4.7): 

      	# cd /usr
! 	# cvs -qd anoncvs@anoncvs.ca.openbsd.org:/cvs get -rOPENBSD_4_7 -P src
  • Anytime afterwards, to `update' this tree: --- 504,513 ---- # cvs -qd anoncvs@anoncvs.ca.openbsd.org:/cvs get -P src !

    (If you are following the patch branch for 4.8): 

      	# cd /usr
! 	# cvs -qd anoncvs@anoncvs.ca.openbsd.org:/cvs get -rOPENBSD_4_8 -P src
  • Anytime afterwards, to `update' this tree: *************** *** 516,525 **** # cvs -q up -Pd !

    (If you are following the patch branch for 4.7): 

      	# cd /usr/src
! 	# cvs -q up -rOPENBSD_4_7 -Pd
    Every time you ran this it would synchronize your /usr/src tree. It would --- 517,526 ---- # cvs -q up -Pd !

    (If you are following the patch branch for 4.8): 

      	# cd /usr/src
! 	# cvs -q up -rOPENBSD_4_8 -Pd
    Every time you ran this it would synchronize your /usr/src tree. It would *************** *** 546,555 **** # cd /usr # cvs -qd anoncvs@anoncvs.ca.openbsd.org:/cvs get -P ports !

    (If you are following the patch branch for 4.7): 

      	# cd /usr
! 	# cvs -qd anoncvs@anoncvs.ca.openbsd.org:/cvs get -rOPENBSD_4_7 -P ports
  • Anytime afterwards, to `update' this tree:

    (If you are following current): --- 547,556 ---- # cd /usr # cvs -qd anoncvs@anoncvs.ca.openbsd.org:/cvs get -P ports !

    (If you are following the patch branch for 4.8): 

      	# cd /usr
! 	# cvs -qd anoncvs@anoncvs.ca.openbsd.org:/cvs get -rOPENBSD_4_8 -P ports
  • Anytime afterwards, to `update' this tree:

    (If you are following current): *************** *** 557,566 **** # cd /usr/ports # cvs -q up -Pd !

    (If you are following the patch branch for 4.7): 

      	# cd /usr/ports
! 	# cvs -q up -rOPENBSD_4_7 -Pd
    --- 558,567 ---- # cd /usr/ports # cvs -q up -Pd !

    (If you are following the patch branch for 4.8): 

      	# cd /usr/ports
! 	# cvs -q up -rOPENBSD_4_8 -Pd
    *************** *** 668,673 **** --- 669,695 ----

    +

    Mirroring the CVS repository via + sup(1)

    + +

    + Users wishing to mirror the OpenBSD CVS tree itself may now do so + from anoncvs.usa.openbsd.org or anoncvs3.usa.openbsd.org + (these are different machines). Note that this is the cvs tree, + not a checked out source tree. It is only useful if you + want to be able to do fast cvs operations (diff, annotate, etc) or + if you have multiple source trees and you only want to transfer new + data once (you can then checkout a tree from your local cvs mirror). +

    + A sample supfile would be: + 

    + 	cvs host=anoncvs.usa.openbsd.org hostbase=/ base=/home delete
+
    +

    + which would mirror the cvs tree into /home/cvs with the sup data + files ending up in /home/sup. The full OpenBSD cvs tree is currently + about 3.5GB in size, and will, of course continue to grow. +

    Setting up an anoncvs mirror

    *************** *** 679,685 **** and use up to 32MB of swap per anoncvs user (assuming the user does a large operation; while smaller operations use fewer resources, anoncvs still makes much more of an ! impact than ftp). Such anoncvs machines should have excellent network connectivity for the area they are expected to serve. A document which describes the setup of anoncvs servers is available. --- 701,707 ---- and use up to 32MB of swap per anoncvs user (assuming the user does a large operation; while smaller operations use fewer resources, anoncvs still makes much more of an ! impact than ftp or sup). Such anoncvs machines should have excellent network connectivity for the area they are expected to serve. A document which describes the setup of anoncvs servers is available. *************** *** 702,708 **** OpenBSD www@openbsd.org !
    $OpenBSD: anoncvs.html,v 1.332 2010/10/22 15:16:08 deraadt Exp $ --- 724,730 ---- OpenBSD www@openbsd.org !
    $OpenBSD: anoncvs.html,v 1.333 2010/11/02 11:54:08 sthen Exp $