[BACK]Return to cvsync.html CVS log [TXT][DIR] Up to [local] / www

Annotation of www/cvsync.html, Revision 1.29

1.6       naddy       1: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
1.1       espie       2: <html>
                      3: <head>
                      4: <title>OpenBSD CVSync</title>
                      5: <link rev="made" href="mailto:www@openbsd.org">
                      6: <meta name="resource-type" content="document">
1.6       naddy       7: <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
1.1       espie       8: <meta name="description" content="How to get OpenBSD updates via Internet using CVSync">
                      9: <meta name="keywords" content="openbsd,cvsync,updates">
                     10: <meta name="distribution" content="global">
1.24      naddy      11: <meta name="copyright" content="This document copyright 2003-2005 by OpenBSD.">
1.1       espie      12: </head>
                     13:
                     14: <body bgcolor="#FFFFFF" text="#000000" link="#23238E">
                     15:
                     16: <a href="index.html"><img alt="[OpenBSD]" height="30" width="141" src="images/smalltitle.gif" border="0"></a>
                     17:
                     18: <h2><font color="#e00000">CVSync</font></h2>
                     19: <hr>
                     20:
                     21: <h3>Table of Contents</h3>
                     22: <ul>
                     23: <li><a href="#CVSync">What Is CVSync?</a></li>
1.10      naddy      24: <li><a href="#CVS">What Is CVS?</a></li>
1.1       espie      25: <li><a href="#starting">Getting Started Using CVSync</a></li>
                     26: <li><a href="#using">Using CVS to Update Your Source Tree</a></li>
                     27: <li><a href="#CVSROOT">Available CVSync Servers</a></li>
                     28: </ul>
                     29:
                     30: <hr>
                     31:
                     32:
                     33: <h3><a name="CVSync"><font color="#0000e0">What Is CVSync?</font></a></h3>
                     34:
                     35: <p>
                     36: <b>CVSync</b> is a software package for distributing and updating source
                     37: trees from a master <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=cvs&amp;sektion=1">cvs(1)</a> repository on a remote server host. The OpenBSD
                     38: sources are maintained in a CVS repository on a central development machine
                     39: in Canada.  With CVSync, OpenBSD users can easily keep their own source trees
1.10      naddy      40: up to date.
1.1       espie      41: </p>
                     42:
                     43: <p>
                     44: <b>CVSync</b> uses the so-called pull model of updating. Under the pull
                     45: model, each client asks the server for updates, if and when they are
                     46: wanted.  The server waits passively for update requests from its clients.
                     47: Thus all updates are instigated by the client.  The server never sends
                     48: unsolicited updates.  Users must either run the <b>CVSync</b> client
                     49: manually to get an update, or they must set up a <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=cron&amp;sektion=8">cron(8)</a> job to run it
1.10      naddy      50: automatically on a regular basis.
1.1       espie      51: </p>
                     52:
                     53: <p>
                     54: The term <b>CVSync</b>, capitalized just so, refers to the entire software
                     55: package. Its main components are the client <tt>cvsync</tt> which runs on
                     56: each user's machine, and the server <tt>cvsyncd</tt> which runs at each of
1.10      naddy      57: the OpenBSD CVSync mirror sites.
1.1       espie      58: </p>
                     59:
                     60: <p>
1.23      nick       61: <b>CVSync</b> is intended to be both faster and more flexible than
                     62: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=sup&amp;sektion=1&amp;format=html">sup(1)</a>
                     63: and <a href="cvsup.html">CVSup</a>.
1.10      naddy      64: </p>
1.1       espie      65:
                     66: <p>
                     67: The OpenBSD Project currently has five main source repositories:
                     68: </p>
                     69:
                     70: <ul>
                     71:   <li><b>src</b> - Houses all source code for the OpenBSD Operating System.</li>
                     72:   <li><b>ports</b> - Houses the <a href="./ports.html">OpenBSD Ports</a>.</li>
1.10      naddy      73:   <li><b>www</b> - Houses all OpenBSD web pages (including this one).</li>
1.26      matthieu   74:   <li><b>X11</b> - Houses OpenBSD's adaptation of the
                     75:       <a href="http://www.XFree86.org/">XFree86-3</a> software project.
                     76:       This is here just for historical purposes, most users will have no
                     77:       reason to use this tree, it is no longer being used.
                     78:   <li><b>XF4</b> - Houses OpenBSD's active X source tree.
1.1       espie      79: </ul>
                     80:
                     81: <h3><a name="CVS"><font color="#0000e0">What Is CVS?</font></a></h3>
                     82:
                     83: <p>
                     84: CVS is the source code control system used to manage the OpenBSD source
                     85: tree.  It is described in more detail <a href="anoncvs.html#CVS">here</a>.
                     86: Note that CVS and CVSync are entirely different programs.  Although
                     87: CVS can be used for remote file access, it is not optimized for
                     88: wholesale source tree distribution over the net, and CVSync can be
                     89: easily an order of magnitude more efficient for this task.
                     90: </p>
                     91:
                     92: <h3>
                     93: <a name="starting"><font color="#0000e0">Getting Started Using CVSync</font></a>
                     94: </h3>
                     95:
                     96: <p>
                     97: If you only care about running CVSync, it is recommended that you
                     98: download the cvsync package from the <a href="ftp.html">ftp mirror
                     99: sites</a> instead of building your own from the <tt>net/cvsync</tt>
1.10      naddy     100: port.
1.1       espie     101: </p>
                    102:
                    103: <p>
                    104: For further information about CVSync, see the
                    105: <a href="http://www.cvsync.org/">project homepage</a>.
                    106: </p>
                    107:
                    108: <p>
                    109: In order to mirror the OpenBSD repository with CVSync,
                    110: the following configuration file might be used:
                    111: </p>
                    112:
                    113: <pre>
                    114:        config {
                    115:            hostname anoncvs.de.openbsd.org
1.5       naddy     116:            # If your network link is a T1 or faster, comment out the following line.
1.1       espie     117:            compress
1.4       espie     118:            collection {
1.5       naddy     119:                name openbsd release rcs
1.4       espie     120:                prefix /cvs
1.5       naddy     121:                umask 002
1.4       espie     122:            }
1.1       espie     123:        }
                    124: </pre>
                    125:
                    126: <p>
                    127: This directs cvsync to refresh all OpenBSD distributions from
                    128: <b>anoncvs.de.openbsd.org</b> with a <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=umask&amp;sektion=2">umask(2)</a> that permits group write
                    129: permission to the local repository.
                    130: </p>
                    131:
                    132: <p>
                    133: Assuming this file is saved as <tt>cvs-syncfile</tt>, the
                    134: following command would be used to invoke cvsync
                    135: </p>
                    136: <pre>
                    137:         cvsync -c cvs-syncfile
                    138: </pre>
                    139:
                    140: <h3><a name="using">
                    141: <font color="#0000e0">Using CVS to Update Your Source Tree</font>
                    142: </a></h3>
                    143:
                    144: <p>
                    145: It is now simple to check out any one of the CVSync'ed repositories.
                    146: For Korn/Bourne shells:
                    147: </p>
                    148: <pre>
                    149:         # cd /usr
                    150:         # CVSROOT=/cvs cvs checkout src
                    151: </pre>
                    152: <p>
                    153: For csh and its derivatives:
                    154: </p>
                    155: <pre>
                    156:         # cd /usr
                    157:         # setenv CVSROOT /cvs
                    158:         # cvs checkout src
                    159: </pre>
                    160:
                    161: <p>
                    162: The above will check out the most current sources. Many of you will only
                    163: want the release sources, especially if you are patching your system.  To
                    164: checkout release sources you must specify a tag along with your command.
                    165: For example:
                    166: </p>
                    167: <pre>
                    168:         # cd /usr
1.17      david     169:         # cvs checkout -rOPENBSD_3_5 src
1.1       espie     170: </pre>
                    171: <p>
1.17      david     172: Or <tt>OPENBSD_3_4</tt> for 3.4, etc.
1.1       espie     173: </p>
                    174:
                    175: <h3>
                    176: <a name="CVSROOT"><font color="#0000e0">Available CVSync Servers</font></a>
                    177: </h3>
                    178:
                    179: <p>The following CVSync servers are available:</p>
                    180:
1.3       naddy     181: <p>
1.6       naddy     182: <ul>
1.14      millert   183: <li><strong>anoncvs1.usa.openbsd.org</strong><br>
1.15      millert   184: located in Redwood City, California, western USA;<br>
1.14      millert   185: maintained by <a href="mailto:millert@openbsd.org">Todd Miller</a>.<br>
                    186: Updated every 2 hours.<br>
                    187:
                    188: <p>
1.15      millert   189: <li><strong>anoncvs3.usa.openbsd.org</strong><br>
                    190: located at the University of Colorado, Boulder, western USA;<br>
1.3       naddy     191: maintained by <a href="mailto:millert@openbsd.org">Todd Miller</a>.<br>
1.14      millert   192: Updated every 2 hours.<br>
1.3       naddy     193:
1.2       naddy     194: <p>
1.6       naddy     195: <li><a href="http://anoncvs.de.openbsd.org/"><strong>anoncvs.de.openbsd.org</strong></a><br>
                    196: Host also known as <strong>grappa.unix-ag.uni-kl.de</strong>,<br>
1.2       naddy     197: located at the University of Kaiserslautern, Germany;<br>
1.1       espie     198: maintained by <a href="mailto:naddy@openbsd.org">Christian Weisgerber</a>.<br>
1.19      naddy     199: Updated every 6 hours.<br>
1.3       naddy     200:
1.2       naddy     201: <p>
1.6       naddy     202: <li><a href="http://www.allbsd.org/"><strong>cvsync.allbsd.org</strong></a><br>
1.2       naddy     203: located in Tokyo, Japan;<br>
1.6       naddy     204: maintained by <a href="mailto:hrs@allbsd.org">Hiroki Sato</a>.<br>
1.3       naddy     205:
1.1       espie     206: <p>
1.6       naddy     207: <li><a href="http://csociety.org/cvsup.html"><strong>cvsync.csociety.org</strong></a><br>
1.2       naddy     208: located at Purdue University, Indiana, USA;<br>
1.6       naddy     209: maintained by <a href="mailto:will@csociety.purdue.edu">Will Andrews</a>.<br>
1.3       naddy     210:
                    211: <p>
1.9       naddy     212: <li><strong>cvsync.linux.org.tr</strong><br>
                    213: located at ULAKBIM, Ankara, Bilkent, Turkey;<br>
                    214: maintained by <a href="mailto:bdd@mindcast.org">Berk D. Demir</a>.<br>
                    215: Updated every 2 hours from anoncvs.usa.openbsd.org.<br>
                    216:
                    217: <p>
1.6       naddy     218: <li><a href="http://mirror.osn.de/"><strong>mirror.osn.de</strong></a><br>
1.3       naddy     219: located in N&uuml;rnberg, Germany;<br>
                    220: maintained by <a href="mailto:aw@osn.de">Armin Wolfermann</a>.<br>
1.20      naddy     221: Updated every 4 hours from anoncvs1.usa.openbsd.org.<br>
1.1       espie     222:
                    223: <p>
1.12      sturm     224: <li><a href="http://anoncvs.erisiandiscord.de/"><strong>anoncvs.erisiandiscord.de</strong></a><br>
                    225: located in Darmstadt, Germany;<br>
                    226: maintained by <a href="mailto:sturm@openbsd.org">Nikolay Sturm</a>.<br>
                    227: Updated every 3 hours from cvsup.uk.openbsd.org.<br>
1.18      naddy     228:
                    229: <p>
1.25      nick      230: <li><strong>cvsync.de.openbsd.org</strong><br>
1.18      naddy     231: located in Erlangen, Germany;<br>
1.27      grunk     232: maintained by <a href="mailto:grunk@openbsd.org">Alexander von Gernler</a>
                    233: and <a href="mailto:stuka@pestilenz.org">Christian Kollee</a>.<br>
1.18      naddy     234: Updated every 2 hours.<br>
1.21      naddy     235:
                    236: <p>
                    237: <li><strong>openbsd.cc.ntu.edu.tw</strong><br>
                    238: located at National Taiwan University, Taiwan;<br>
                    239: maintained by <a href="mailto:lkchu@ntuee.net">Liang-Kai Chu</a>.<br>
                    240: Updated every 2 hours.<br>
1.24      naddy     241:
                    242: <p>
                    243: <li><a href="http://mirror.sg.depaul.edu/"><strong>mirror.sg.depaul.edu</strong></a><br>
                    244: located at DePaul University in Chicago, Illinois, USA;<br>
                    245: maintained by <a href="mailto:mirror-admin@sg.depaul.edu">Eric Pancer</a>.<br>
                    246: Updated every 2 hours.<br>
1.25      nick      247:
                    248: <p>
                    249: <li><strong>cvsync.openbsd.se</strong><br>
                    250: located in Uppsala, Sweden;<br>
                    251: maintained by <a href="mailto:admin@openbsd.se">Peter Laur</a>.<br>
                    252: Updated every 2 hours.<br>
1.28      grunk     253:
                    254: <p>
                    255: <li><strong>cvsync.catai.net</strong><br>
                    256: located in Vienna, Austria;<br>
                    257: maintained by <a href="mailto:martin@openbsd.org">Martin Reindl</a>.<br>
                    258: Updated every 2 hours from cvsync.de.openbsd.org.<br>
1.29    ! grunk     259:
        !           260: <p>
        !           261: <li><strong>cvsup.openbsd.nu</strong><br>
        !           262: located in Stockholm, Sweden;<br>
        !           263: maintained by <a href="mailto:kent@openbsd.nu">Kent Riboe</a>.<br>
        !           264: Updated every 3 hours from cvsync.de.openbsd.org.<br>
1.12      sturm     265: </ul>
                    266:
                    267: <p>
1.2       naddy     268: <em>Note:</em> If your server is listed on here with inaccurate or
1.1       espie     269: unknown information, please contact <a
                    270: href="mailto:beck@openbsd.org"><tt>beck@openbsd.org</tt></a>
                    271: or <a href="mailto:naddy@openbsd.org"><tt>naddy@openbsd.org</tt></a>
                    272: </p>
                    273: <p>
                    274: You may want to use <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=traceroute&amp;sektion=8">traceroute(8)</a>
                    275: to find out which server is nearest you.
                    276: Problems with a server should be reported to the <b>maintainer</b> of the
                    277: server in question.
                    278: </p>
                    279: <p>
1.29    ! grunk     280: As of December 12, 2005, the CVS repository sizes are
1.1       espie     281: </p>
                    282: <table>
                    283: <tr><td width="20"></td>
                    284:     <td><strong>openbsd-ports</strong></td>
1.29    ! grunk     285:     <td>- <b>204</b>MB</td></tr>
1.1       espie     286: <tr><td></td>
                    287:     <td><strong>openbsd-src</strong></td>
1.29    ! grunk     288:     <td>- <b>1369</b>MB</td></tr>
1.1       espie     289: <tr><td></td>
                    290:     <td><strong>openbsd-www</strong></td>
1.29    ! grunk     291:     <td>- <b>236</b>MB</td></tr>
1.1       espie     292: <tr><td></td>
                    293:     <td><strong>openbsd-x11</strong></td>
                    294:     <td>- <b>200</b>MB</td></tr>
                    295: <tr><td></td>
                    296:     <td><strong>openbsd-xf4</strong></td>
1.29    ! grunk     297:     <td>- <b>531</b>MB</td></tr>
1.1       espie     298: <tr><td></td>
                    299:     <td><strong>openbsd-cvsroot</strong></td>
1.29    ! grunk     300:     <td>- <b>301</b>MB</td></tr>
1.1       espie     301: </table>
                    302: <p>
                    303: The overall repository size currently increases at a rate
1.22      nick      304: of about <b>400</b>MB per annum.
1.1       espie     305: </p>
                    306: <p>
                    307: <strong>IMPORTANT NOTE:</strong>
                    308: There are a few issues relating to cryptographic software that everyone
                    309: should be aware of:
                    310: </p>
                    311: <ul>
                    312:   <li>
                    313:     <p>
                    314:     The OpenBSD sources are from Canada. As
                    315:     <a href="http://www.efc.ca/pages/doc/crypto-export.html">
                    316:     researched by a Canadian individual</a> and as
                    317:     <a href="http://axion.physics.ubc.ca/ECL.html">
                    318:     described in the Export Control list of Canada</a>,
                    319:     it is legal to export crypto software from Canada to the world.
                    320:     </p>
                    321:   </li>
                    322:   <li>
                    323:     <p>
                    324:     However, if you are outside the USA or Canada, you should not
1.8       naddy     325:     fetch the cryptographic sections of the OpenBSD sources from a
                    326:     CVSync server located in the USA. The files in question are...
1.1       espie     327:     </p>
                    328:     <ul>
                    329:       <li><tt>src/kerberosIV/*</tt></li>
                    330:       <li><tt>src/kerberosV/*</tt></li>
                    331:       <li><tt>src/lib/libdes/*</tt></li>
                    332:       <li><tt>src/lib/libc/crypt/crypt.c</tt></li>
                    333:       <li><tt>src/lib/libc/crypt/morecrypt.c</tt></li>
                    334:       <li><tt>src/sys/crypto</tt></li>
                    335:       <li><tt>src/sys/netinet</tt></li>
                    336:       <li><tt>src/usr.sbin/afs/src/rxkad/*</tt></li>
                    337:       <li><tt>XF4/xc-mit/lib/Xdmcp/Wraphelp.c</tt></li>
                    338:       <li><tt>XF4/xc-old/lib/Xdmcp/Wraphelp.c</tt></li>
                    339:       <li><tt>XF4/xc/lib/Xdmcp/Wraphelp.c</tt></li>
                    340:     </ul>
                    341:     <p>
                    342:     Because of the USA ITAR munitions list,
                    343:     crypto software may only be exported to Canada from the USA.
                    344:     </p>
                    345:   </li>
                    346: </ul>
                    347:
                    348: <p>
                    349: The OpenBSD project is looking for more CVSync servers -- if you are
                    350: interested, please contact <a href="mailto:naddy@openbsd.org">Christian Weisgerber</a>
                    351: for configuration details.
                    352: </p>
                    353:
                    354: <hr>
                    355: <a href="index.html"><img height="24" width="24" src="back.gif" border="0" alt="OpenBSD"></a>
                    356: <a href="mailto:www@openbsd.org">www@openbsd.org</a>
1.29    ! grunk     357: <br><small>$OpenBSD: cvsync.html,v 1.28 2005/11/07 12:26:02 grunk Exp $</small>
1.1       espie     358:
                    359: </body>
                    360: </html>