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

Annotation of www/cvsync.html, Revision 1.108

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