Annotation of www/cvsync.html, Revision 1.137
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>
1.125 tj 6: <title>OpenBSD: CVSync</title>
1.6 naddy 7: <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
1.133 tj 8: <meta name="copyright" content="This document copyright 2003-2017 by OpenBSD.">
1.121 tb 9: <meta name="viewport" content="width=device-width, initial-scale=1">
10: <link rel="stylesheet" type="text/css" href="openbsd.css">
1.128 tb 11: <link rel="canonical" href="https://www.openbsd.org/cvsync.html">
1.131 tb 12: <style type="text/css">
13: h3 { color: #0000e0; }
14: </style>
1.1 espie 15: </head>
16:
17: <body bgcolor="#FFFFFF" text="#000000" link="#23238E">
18:
1.121 tb 19: <h2>
1.122 tb 20: <a href="index.html">
1.121 tb 21: <font color="#0000ff"><i>Open</i></font><font color="#000084">BSD</font></a>
22: <font color="#e00000">CVSync</font>
23: </h2>
1.1 espie 24: <hr>
1.121 tb 25: <p>
1.1 espie 26:
1.131 tb 27: <h3 id="CVSync">What Is CVSync?</h3>
1.1 espie 28:
29: <b>CVSync</b> is a software package for distributing and updating source
1.137 ! tb 30: trees from a master <a href="https://man.openbsd.org/cvs">cvs(1)</a>
1.124 tb 31: repository on a remote server host.
32: The OpenBSD sources are maintained in a CVS repository on a central
33: development machine in Canada.
34: With CVSync, OpenBSD users can easily keep their own source trees up to date.
1.1 espie 35:
36: <p>
37: <b>CVSync</b> uses the so-called pull model of updating. Under the pull
38: model, each client asks the server for updates, if and when they are
39: wanted. The server waits passively for update requests from its clients.
40: Thus all updates are instigated by the client. The server never sends
41: unsolicited updates. Users must either run the <b>CVSync</b> client
1.124 tb 42: manually to get an update, or they must set up a
1.137 ! tb 43: <a href="https://man.openbsd.org/cron">cron(8)</a> job to run it
1.10 naddy 44: automatically on a regular basis.
1.1 espie 45:
46: <p>
47: The term <b>CVSync</b>, capitalized just so, refers to the entire software
48: package. Its main components are the client <tt>cvsync</tt> which runs on
49: each user's machine, and the server <tt>cvsyncd</tt> which runs at each of
1.10 naddy 50: the OpenBSD CVSync mirror sites.
1.1 espie 51:
52: <p>
1.134 tj 53: The OpenBSD Project currently has four main source repositories:
1.1 espie 54:
55: <ul>
56: <li><b>src</b> - Houses all source code for the OpenBSD Operating System.</li>
1.78 steven 57: <li><b>ports</b> - Houses the <a href="faq/ports/index.html">OpenBSD Ports</a>.</li>
1.10 naddy 58: <li><b>www</b> - Houses all OpenBSD web pages (including this one).</li>
1.51 deraadt 59: <li><b>xenocara</b> - Houses OpenBSD's active X.org v7 source tree.
1.1 espie 60: </ul>
61:
1.131 tb 62: <h3 id="CVS">What Is CVS?</h3>
1.1 espie 63:
64: CVS is the source code control system used to manage the OpenBSD source
65: tree. It is described in more detail <a href="anoncvs.html#CVS">here</a>.
66: Note that CVS and CVSync are entirely different programs. Although
67: CVS can be used for remote file access, it is not optimized for
68: wholesale source tree distribution over the net, and CVSync can be
69: easily an order of magnitude more efficient for this task.
70:
1.131 tb 71: <h3 id="starting">Getting Started Using CVSync</h3>
1.1 espie 72:
73: If you only care about running CVSync, it is recommended that you
74: download the cvsync package from the <a href="ftp.html">ftp mirror
75: sites</a> instead of building your own from the <tt>net/cvsync</tt>
1.10 naddy 76: port.
1.1 espie 77:
78: <p>
79: For further information about CVSync, see the
80: <a href="http://www.cvsync.org/">project homepage</a>.
1.116 sthen 81: However, don't build your own copy from unmodified upstream source -
82: the port/package has been modified to support commitid which is now
83: used in the OpenBSD repository.
1.1 espie 84:
85: <p>
86: In order to mirror the OpenBSD repository with CVSync,
87: the following configuration file might be used:
88:
89: <pre>
90: config {
1.103 mpi 91: hostname anoncvs.eu.openbsd.org
1.5 naddy 92: # If your network link is a T1 or faster, comment out the following line.
1.1 espie 93: compress
1.4 espie 94: collection {
1.5 naddy 95: name openbsd release rcs
1.4 espie 96: prefix /cvs
1.5 naddy 97: umask 002
1.4 espie 98: }
1.1 espie 99: }
100: </pre>
101:
102: <p>
103: This directs cvsync to refresh all OpenBSD distributions from
1.124 tb 104: <b>anoncvs.eu.openbsd.org</b> with a
1.137 ! tb 105: <a href="https://man.openbsd.org/umask">umask(2)</a> that permits group write
1.1 espie 106: permission to the local repository.
107:
108: <p>
109: Assuming this file is saved as <tt>cvs-syncfile</tt>, the
110: following command would be used to invoke cvsync
1.124 tb 111:
1.1 espie 112: <pre>
1.91 nick 113: <b>cvsync -c cvs-syncfile</b>
1.1 espie 114: </pre>
115:
1.131 tb 116: <h3 id="using">Using CVS to Work With Your Repository</h3>
1.1 espie 117:
1.48 nick 118: Now that you have a local copy of the CVS repository, it is now simple
119: to check out, update, or do any of the other CVS operations you would
120: normally do against a remote repository, locally.
1.50 nick 121: For example:
1.1 espie 122: <pre>
1.91 nick 123: <b>cvs -d/cvs checkout -P src</b>
124: <b>cvs -d/cvs up -Pd</b>
125: <b>cvs -d/cvs diff -u file.c</b>
1.1 espie 126: </pre>
1.48 nick 127: More details on CVS operation can be found in
128: <a href="faq/faq5.html#BldGetSrc">FAQ5, Fetching appropriate source
129: code</a> and in the
1.137 ! tb 130: <a href="https://man.openbsd.org/cvs">cvs(1)</a>
1.48 nick 131: man page.
1.1 espie 132:
1.131 tb 133: <h3 id="CVSROOT">Available CVSync Servers</h3>
1.1 espie 134:
1.124 tb 135: The following CVSync servers are available:
1.1 espie 136:
1.6 naddy 137: <ul>
1.107 brad 138: <li><strong>anoncvs.comstyle.com</strong><br>
139: Location: Toronto, Canada.<br>
140: Maintained by <a href="mailto:brad@comstyle.com">Brad Smith</a>.<br>
141: Updated hourly.<br>
142: <p>
1.136 krw 143: <li><strong>obsdacvs.cs.toronto.edu</strong><br>
1.110 nick 144: Location: University of Toronto, Toronto, ON, Canada.<br>
145: Maintained by <a href="mailto:nick@holland-consulting.net">Nick Holland</a>.<br>
146: Updated every 2 hours.<br>
147: <p>
1.88 sthen 148: <li><strong>anoncvs.fr.openbsd.org</strong><br>
149: Location: Paris, France.<br>
1.117 sthen 150: Maintained by <a href="mailto:openbsd-mirror@bsdfrog.org">Landry Breuil, Antoine Jacoutot</a>.<br>
1.88 sthen 151: Updated every 2 hours from anoncvs1.ca.openbsd.org.<br>
152: <p>
1.90 sthen 153: <li><a href="http://mirror.osn.de/"><strong>mirror.osn.de</strong></a><br>
1.37 steven 154: Location: Nürnberg, Germany.<br>
155: Maintained by <a href="mailto:aw@osn.de">Armin Wolfermann</a>.<br>
1.62 sthen 156: Updated every 3 hours.<br>
1.1 espie 157: <p>
1.112 florian 158: <li><strong>ftp.hostserver.de</strong><br>
159: Location: Frankfurt, Germany.<br>
1.130 tb 160: Maintained by <a href="mailto:mirror@hostserver.de">Sebastian Benoit, Peter Hessler</a>.<br>
1.112 florian 161: Updated hourly from anoncvs1.ca.openbsd.org.<br>
162: <p>
1.90 sthen 163: <li><a href="http://www.allbsd.org/"><strong>cvsync.allbsd.org</strong></a><br>
1.37 steven 164: Location: Tokyo, Japan.<br>
165: Maintained by <a href="mailto:hrs@allbsd.org">Hiroki Sato</a>.<br>
1.69 sthen 166: <p>
1.77 sthen 167: <li><strong>anoncvs.eu.openbsd.org</strong><br>
168: Location: Stockholm University, Stockholm, Sweden.<br>
1.93 sthen 169: Maintained by <a href="mailto:jj@openbsd.org, ftp@it.su.se">Janne Johansson</a>.<br>
1.77 sthen 170: Updated every 2 hours.<br>
171: <p>
172: <li><strong>anoncvs.spacehopper.org</strong><br>
173: Location: London, United Kingdom.<br>
174: Maintained by <a href="mailto:sthen@openbsd.org">Stuart Henderson</a>.<br>
175: Updated hourly from anoncvs.ca.openbsd.org.<br>
176: <p>
1.118 sthen 177: <li><strong>anoncvs3.usa.openbsd.org</strong><br>
178: Location: National Center for Atmospheric Research, Boulder, CO, USA.<br>
179: Maintained by <a href="mailto:millert@openbsd.org">Todd C. Miller</a>.<br>
180: Updated hourly.<br>
181: <p>
1.127 millert 182: <li><strong>anoncvs4.usa.openbsd.org</strong><br>
183: Host also known as <strong>anoncvs4.usa.openbsd.org</strong>.<br>
184: Location: New York Internet, New York, NY, USA.<br>
185: Maintained by <a href="mailto:millert@openbsd.org">Todd C. Miller</a>.<br>
186: Updated hourly.<br>
187: <p>
1.118 sthen 188: <li><strong>anoncvs2.usa.openbsd.org</strong><br>
1.129 tj 189: Host also known as <strong>anoncvs2.usa.openbsd.org, openbsd.se.rit.edu</strong>.<br>
1.118 sthen 190: Location: Rochester Institute of Technology, Rochester, NY, USA.<br>
191: Maintained by <a href="mailto:millert@openbsd.org">Todd C. Miller</a>.<br>
192: Updated hourly.<br>
193: <p>
1.77 sthen 194: <li><strong>anoncvs1.usa.openbsd.org</strong><br>
1.127 millert 195: Host also known as <strong>anoncvs.usa.openbsd.org, anoncvs1.usa.openbsd.org</strong>.<br>
1.118 sthen 196: Location: Network Media, LLC, Bend, OR, USA.<br>
1.77 sthen 197: Maintained by <a href="mailto:millert@openbsd.org">Todd C. Miller</a>.<br>
1.118 sthen 198: Updated hourly.<br>
1.77 sthen 199: <p>
1.29 grunk 200:
1.12 sturm 201: </ul>
202:
1.2 naddy 203: <em>Note:</em> If your server is listed on here with inaccurate or
1.1 espie 204: unknown information, please contact <a
205: href="mailto:beck@openbsd.org"><tt>beck@openbsd.org</tt></a>
1.124 tb 206:
1.1 espie 207: <p>
1.137 ! tb 208: You may want to use <a href="https://man.openbsd.org/traceroute">traceroute(8)</a>
1.1 espie 209: to find out which server is nearest you.
210: Problems with a server should be reported to the <b>maintainer</b> of the
211: server in question.
1.124 tb 212:
1.1 espie 213: <p>
1.123 sthen 214: As of March 2016, the CVS repository sizes are
1.124 tb 215:
216: <p>
1.1 espie 217: <table>
218: <tr><td width="20"></td>
219: <td><strong>openbsd-ports</strong></td>
1.123 sthen 220: <td>- <b>857</b>MB</td></tr>
1.1 espie 221: <tr><td></td>
222: <td><strong>openbsd-src</strong></td>
1.123 sthen 223: <td>- <b>2201</b>MB</td></tr>
1.1 espie 224: <tr><td></td>
225: <td><strong>openbsd-www</strong></td>
1.123 sthen 226: <td>- <b>598</b>MB</td></tr>
1.48 nick 227: <tr><td></td>
228: <td><strong>openbsd-xenocara</strong></td>
1.123 sthen 229: <td>- <b>1426</b>MB</td></tr>
1.1 espie 230: <tr><td></td>
231: <td><strong>openbsd-cvsroot</strong></td>
1.123 sthen 232: <td>- <b>1248</b>MB</td></tr>
1.1 espie 233: </table>
1.124 tb 234:
1.1 espie 235: <p>
236: The overall repository size currently increases at a rate
1.95 tedu 237: of about <b>400</b>MB per annum. The src repository increases by about
238: <b>150</b>MB.
1.124 tb 239:
1.1 espie 240: <p>
241: <strong>IMPORTANT NOTE:</strong>
242: There are a few issues relating to cryptographic software that everyone
243: should be aware of:
1.124 tb 244:
1.1 espie 245: <ul>
246: <li>
247: <p>
248: The OpenBSD sources are from Canada. As
249: <a href="http://www.efc.ca/pages/doc/crypto-export.html">
250: researched by a Canadian individual</a> and as
251: <a href="http://axion.physics.ubc.ca/ECL.html">
252: described in the Export Control list of Canada</a>,
253: it is legal to export crypto software from Canada to the world.
254: </li>
255: <li>
256: <p>
257: However, if you are outside the USA or Canada, you should not
1.8 naddy 258: fetch the cryptographic sections of the OpenBSD sources from a
259: CVSync server located in the USA. The files in question are...
1.1 espie 260: <ul>
261: <li><tt>src/kerberosIV/*</tt></li>
262: <li><tt>src/kerberosV/*</tt></li>
263: <li><tt>src/lib/libdes/*</tt></li>
264: <li><tt>src/lib/libc/crypt/crypt.c</tt></li>
265: <li><tt>src/lib/libc/crypt/morecrypt.c</tt></li>
266: <li><tt>src/sys/crypto</tt></li>
267: <li><tt>src/sys/netinet</tt></li>
268: <li><tt>src/usr.sbin/afs/src/rxkad/*</tt></li>
269: </ul>
270: <p>
271: Because of the USA ITAR munitions list,
272: crypto software may only be exported to Canada from the USA.
273: </li>
274: </ul>
275:
276: </body>
277: </html>
![[BACK]](/icons/back.gif){kind=icon}
Return to cvsync.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www