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

Annotation of www/cvsync.html, Revision 1.114

1.58      sthen       1: <!-- DO NOT EDIT MANUALLY! See comments in www/build/mirrors.dat for details -->
1.37      steven      2:
1.6       naddy       3: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
1.1       espie       4: <html>
                      5: <head>
                      6: <title>OpenBSD CVSync</title>
                      7: <meta name="resource-type" content="document">
1.6       naddy       8: <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
1.1       espie       9: <meta name="description" content="How to get OpenBSD updates via Internet using CVSync">
                     10: <meta name="keywords" content="openbsd,cvsync,updates">
                     11: <meta name="distribution" content="global">
1.109     sthen      12: <meta name="copyright" content="This document copyright 2003-2014 by OpenBSD.">
1.114   ! sthen      13: <link rel="canonical" href="http://www.openbsd.org/cvsync.html">
1.1       espie      14: </head>
                     15:
                     16: <body bgcolor="#FFFFFF" text="#000000" link="#23238E">
                     17:
                     18: <a href="index.html"><img alt="[OpenBSD]" height="30" width="141" src="images/smalltitle.gif" border="0"></a>
                     19:
                     20: <h2><font color="#e00000">CVSync</font></h2>
                     21: <hr>
                     22:
                     23: <h3><a name="CVSync"><font color="#0000e0">What Is CVSync?</font></a></h3>
                     24:
                     25: <p>
                     26: <b>CVSync</b> is a software package for distributing and updating source
                     27: 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
                     28: sources are maintained in a CVS repository on a central development machine
                     29: in Canada.  With CVSync, OpenBSD users can easily keep their own source trees
1.10      naddy      30: up to date.
1.1       espie      31: </p>
                     32:
                     33: <p>
                     34: <b>CVSync</b> uses the so-called pull model of updating. Under the pull
                     35: model, each client asks the server for updates, if and when they are
                     36: wanted.  The server waits passively for update requests from its clients.
                     37: Thus all updates are instigated by the client.  The server never sends
                     38: unsolicited updates.  Users must either run the <b>CVSync</b> client
                     39: 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      40: automatically on a regular basis.
1.1       espie      41: </p>
                     42:
                     43: <p>
                     44: The term <b>CVSync</b>, capitalized just so, refers to the entire software
                     45: package. Its main components are the client <tt>cvsync</tt> which runs on
                     46: each user's machine, and the server <tt>cvsyncd</tt> which runs at each of
1.10      naddy      47: the OpenBSD CVSync mirror sites.
1.1       espie      48: </p>
                     49:
                     50: <p>
1.23      nick       51: <b>CVSync</b> is intended to be both faster and more flexible than
1.97      tedu       52: sup and CVSup.
1.10      naddy      53: </p>
1.1       espie      54:
                     55: <p>
1.42      nick       56: The OpenBSD Project currently has six main source repositories:
1.1       espie      57: </p>
                     58:
                     59: <ul>
                     60:   <li><b>src</b> - Houses all source code for the OpenBSD Operating System.</li>
1.78      steven     61:   <li><b>ports</b> - Houses the <a href="faq/ports/index.html">OpenBSD Ports</a>.</li>
1.10      naddy      62:   <li><b>www</b> - Houses all OpenBSD web pages (including this one).</li>
1.26      matthieu   63:   <li><b>X11</b> - Houses OpenBSD's adaptation of the
                     64:       <a href="http://www.XFree86.org/">XFree86-3</a> software project.
1.51      deraadt    65:   <li><b>XF4</b> - Houses OpenBSD's adaptation of the XFree86-4 source tree.
                     66:   <li><b>xenocara</b> - Houses OpenBSD's active X.org v7 source tree.
1.1       espie      67: </ul>
                     68:
1.84      jasper     69: The <b>X11</b> and <b>XF4</b> repositories are here just for historical
1.97      tedu       70: purposes, most users will have no reason to use those trees, they are no longer
1.84      jasper     71: being used.
                     72:
1.1       espie      73: <h3><a name="CVS"><font color="#0000e0">What Is CVS?</font></a></h3>
                     74:
                     75: <p>
                     76: CVS is the source code control system used to manage the OpenBSD source
                     77: tree.  It is described in more detail <a href="anoncvs.html#CVS">here</a>.
                     78: Note that CVS and CVSync are entirely different programs.  Although
                     79: CVS can be used for remote file access, it is not optimized for
                     80: wholesale source tree distribution over the net, and CVSync can be
                     81: easily an order of magnitude more efficient for this task.
                     82: </p>
                     83:
                     84: <h3>
                     85: <a name="starting"><font color="#0000e0">Getting Started Using CVSync</font></a>
                     86: </h3>
                     87:
                     88: <p>
                     89: If you only care about running CVSync, it is recommended that you
                     90: download the cvsync package from the <a href="ftp.html">ftp mirror
                     91: sites</a> instead of building your own from the <tt>net/cvsync</tt>
1.10      naddy      92: port.
1.1       espie      93: </p>
                     94:
                     95: <p>
                     96: For further information about CVSync, see the
                     97: <a href="http://www.cvsync.org/">project homepage</a>.
                     98: </p>
                     99:
                    100: <p>
                    101: In order to mirror the OpenBSD repository with CVSync,
                    102: the following configuration file might be used:
                    103: </p>
                    104:
                    105: <pre>
                    106:        config {
1.103     mpi       107:            hostname anoncvs.eu.openbsd.org
1.5       naddy     108:            # If your network link is a T1 or faster, comment out the following line.
1.1       espie     109:            compress
1.4       espie     110:            collection {
1.5       naddy     111:                name openbsd release rcs
1.4       espie     112:                prefix /cvs
1.5       naddy     113:                umask 002
1.4       espie     114:            }
1.1       espie     115:        }
                    116: </pre>
                    117:
                    118: <p>
                    119: This directs cvsync to refresh all OpenBSD distributions from
1.103     mpi       120: <b>anoncvs.eu.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
1.1       espie     121: permission to the local repository.
                    122: </p>
                    123:
                    124: <p>
                    125: Assuming this file is saved as <tt>cvs-syncfile</tt>, the
                    126: following command would be used to invoke cvsync
                    127: </p>
                    128: <pre>
1.91      nick      129:         <b>cvsync -c cvs-syncfile</b>
1.1       espie     130: </pre>
                    131:
                    132: <h3><a name="using">
1.48      nick      133: <font color="#0000e0">Using CVS to Work With Your Repository</font>
1.1       espie     134: </a></h3>
                    135:
                    136: <p>
1.48      nick      137: Now that you have a local copy of the CVS repository, it is now simple
                    138: to check out, update, or do any of the other CVS operations you would
                    139: normally do against a remote repository, locally.
1.50      nick      140: For example:
1.1       espie     141: <pre>
1.91      nick      142:         <b>cvs -d/cvs checkout -P src</b>
                    143:         <b>cvs -d/cvs up -Pd</b>
                    144:         <b>cvs -d/cvs diff -u file.c</b>
1.1       espie     145: </pre>
1.48      nick      146: More details on CVS operation can be found in
                    147: <a href="faq/faq5.html#BldGetSrc">FAQ5, Fetching appropriate source
                    148: code</a> and in the
                    149: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=cvs&amp;sektion=1">cvs(1)</a>
                    150: man page.
1.1       espie     151:
                    152: <h3>
                    153: <a name="CVSROOT"><font color="#0000e0">Available CVSync Servers</font></a>
                    154: </h3>
                    155:
                    156: <p>The following CVSync servers are available:</p>
                    157:
1.3       naddy     158: <p>
1.6       naddy     159: <ul>
1.72      sthen     160: <li><strong>ftp5.eu.openbsd.org</strong><br>
                    161: Host also known as <strong>anga.funkfeuer.at</strong>.<br>
1.44      martin    162: Location: Vienna, Austria.<br>
1.104     naddy     163: Maintained by <a href="mailto:martin@catai.org">Martin Reindl</a>.<br>
                    164: Updated hourly.<br>
1.44      martin    165: <p>
1.107     brad      166: <li><strong>anoncvs.comstyle.com</strong><br>
                    167: Location: Toronto, Canada.<br>
                    168: Maintained by <a href="mailto:brad@comstyle.com">Brad Smith</a>.<br>
                    169: Updated hourly.<br>
                    170: <p>
1.110     nick      171: <li><strong>openbsd.cs.toronto.edu</strong><br>
                    172: Location: University of Toronto, Toronto, ON, Canada.<br>
                    173: Maintained by <a href="mailto:nick@holland-consulting.net">Nick Holland</a>.<br>
                    174: Updated every 2 hours.<br>
                    175: <p>
1.88      sthen     176: <li><strong>anoncvs.fr.openbsd.org</strong><br>
                    177: Location: Paris, France.<br>
                    178: Maintained by <a href="mailto:landry@openbsd.org">Landry Breuil</a>.<br>
                    179: Updated every 2 hours from anoncvs1.ca.openbsd.org.<br>
                    180: <p>
1.90      sthen     181: <li><a href="http://mirror.osn.de/"><strong>mirror.osn.de</strong></a><br>
1.37      steven    182: Location: N&uuml;rnberg, Germany.<br>
                    183: Maintained by <a href="mailto:aw@osn.de">Armin Wolfermann</a>.<br>
1.62      sthen     184: Updated every 3 hours.<br>
1.1       espie     185: <p>
1.112     florian   186: <li><strong>ftp.hostserver.de</strong><br>
                    187: Location: Frankfurt, Germany.<br>
                    188: Maintained by <a href="mailto:mirror@hostserver.de">Sebastian Benoit, Florian Obser</a>.<br>
                    189: Updated hourly from anoncvs1.ca.openbsd.org.<br>
                    190: <p>
1.90      sthen     191: <li><a href="http://www.allbsd.org/"><strong>cvsync.allbsd.org</strong></a><br>
1.37      steven    192: Location: Tokyo, Japan.<br>
                    193: Maintained by <a href="mailto:hrs@allbsd.org">Hiroki Sato</a>.<br>
1.69      sthen     194: <p>
1.77      sthen     195: <li><strong>anoncvs.eu.openbsd.org</strong><br>
                    196: Location: Stockholm University, Stockholm, Sweden.<br>
1.93      sthen     197: Maintained by <a href="mailto:jj@openbsd.org, ftp@it.su.se">Janne Johansson</a>.<br>
1.77      sthen     198: Updated every 2 hours.<br>
                    199: <p>
                    200: <li><strong>anoncvs.spacehopper.org</strong><br>
                    201: Location: London, United Kingdom.<br>
                    202: Maintained by <a href="mailto:sthen@openbsd.org">Stuart Henderson</a>.<br>
                    203: Updated hourly from anoncvs.ca.openbsd.org.<br>
                    204: <p>
                    205: <li><strong>anoncvs1.usa.openbsd.org</strong><br>
                    206: Host also known as <strong>anoncvs.usa.openbsd.org, anoncvs4.usa.openbsd.org</strong>.<br>
1.88      sthen     207: Location: Internet Systems Consortium, Redwood City, CA, USA.<br>
1.77      sthen     208: Maintained by <a href="mailto:millert@openbsd.org">Todd C. Miller</a>.<br>
                    209: Updated every 2 hours.<br>
                    210: <p>
                    211: <li><strong>anoncvs3.usa.openbsd.org</strong><br>
                    212: Location: National Center for Atmospheric Research, Boulder, CO, USA.<br>
                    213: Maintained by <a href="mailto:millert@openbsd.org">Todd C. Miller</a>.<br>
                    214: Updated every 2 hours.<br>
                    215: <p>
1.29      grunk     216:
1.12      sturm     217: </ul>
                    218:
                    219: <p>
1.2       naddy     220: <em>Note:</em> If your server is listed on here with inaccurate or
1.1       espie     221: unknown information, please contact <a
                    222: href="mailto:beck@openbsd.org"><tt>beck@openbsd.org</tt></a>
                    223: </p>
                    224: <p>
                    225: You may want to use <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=traceroute&amp;sektion=8">traceroute(8)</a>
                    226: to find out which server is nearest you.
                    227: Problems with a server should be reported to the <b>maintainer</b> of the
                    228: server in question.
                    229: </p>
                    230: <p>
1.105     naddy     231: As of August 2013, the CVS repository sizes are
1.1       espie     232: </p>
                    233: <table>
                    234: <tr><td width="20"></td>
                    235:     <td><strong>openbsd-ports</strong></td>
1.105     naddy     236:     <td>- <b>679</b>MB</td></tr>
1.1       espie     237: <tr><td></td>
                    238:     <td><strong>openbsd-src</strong></td>
1.105     naddy     239:     <td>- <b>2044</b>MB</td></tr>
1.1       espie     240: <tr><td></td>
                    241:     <td><strong>openbsd-www</strong></td>
1.105     naddy     242:     <td>- <b>467</b>MB</td></tr>
1.48      nick      243: <tr><td></td>
                    244:     <td><strong>openbsd-xenocara</strong></td>
1.105     naddy     245:     <td>- <b>1140</b>MB</td></tr>
1.1       espie     246: <tr><td></td>
                    247:     <td><strong>openbsd-x11</strong></td>
                    248:     <td>- <b>200</b>MB</td></tr>
                    249: <tr><td></td>
                    250:     <td><strong>openbsd-xf4</strong></td>
1.48      nick      251:     <td>- <b>564</b>MB</td></tr>
1.1       espie     252: <tr><td></td>
                    253:     <td><strong>openbsd-cvsroot</strong></td>
1.105     naddy     254:     <td>- <b>1027</b>MB</td></tr>
1.1       espie     255: </table>
                    256: <p>
                    257: The overall repository size currently increases at a rate
1.95      tedu      258: of about <b>400</b>MB per annum. The src repository increases by about
                    259: <b>150</b>MB.
1.1       espie     260: </p>
                    261: <p>
                    262: <strong>IMPORTANT NOTE:</strong>
                    263: There are a few issues relating to cryptographic software that everyone
                    264: should be aware of:
                    265: </p>
                    266: <ul>
                    267:   <li>
                    268:     <p>
                    269:     The OpenBSD sources are from Canada. As
                    270:     <a href="http://www.efc.ca/pages/doc/crypto-export.html">
                    271:     researched by a Canadian individual</a> and as
                    272:     <a href="http://axion.physics.ubc.ca/ECL.html">
                    273:     described in the Export Control list of Canada</a>,
                    274:     it is legal to export crypto software from Canada to the world.
                    275:     </p>
                    276:   </li>
                    277:   <li>
                    278:     <p>
                    279:     However, if you are outside the USA or Canada, you should not
1.8       naddy     280:     fetch the cryptographic sections of the OpenBSD sources from a
                    281:     CVSync server located in the USA. The files in question are...
1.1       espie     282:     </p>
                    283:     <ul>
                    284:       <li><tt>src/kerberosIV/*</tt></li>
                    285:       <li><tt>src/kerberosV/*</tt></li>
                    286:       <li><tt>src/lib/libdes/*</tt></li>
                    287:       <li><tt>src/lib/libc/crypt/crypt.c</tt></li>
                    288:       <li><tt>src/lib/libc/crypt/morecrypt.c</tt></li>
                    289:       <li><tt>src/sys/crypto</tt></li>
                    290:       <li><tt>src/sys/netinet</tt></li>
                    291:       <li><tt>src/usr.sbin/afs/src/rxkad/*</tt></li>
                    292:       <li><tt>XF4/xc-mit/lib/Xdmcp/Wraphelp.c</tt></li>
                    293:       <li><tt>XF4/xc-old/lib/Xdmcp/Wraphelp.c</tt></li>
                    294:       <li><tt>XF4/xc/lib/Xdmcp/Wraphelp.c</tt></li>
                    295:     </ul>
                    296:     <p>
                    297:     Because of the USA ITAR munitions list,
                    298:     crypto software may only be exported to Canada from the USA.
                    299:     </p>
                    300:   </li>
                    301: </ul>
                    302:
                    303: </body>
                    304: </html>