Annotation of www/cvsync.html, Revision 1.11
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.11 ! jose 11: <meta name="copyright" content="This document copyright 2003-2004 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&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&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>
61: <b>CVSync</b> is intended to be both faster and flexible than
1.7 naddy 62: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=sup&sektion=1&format=html">sup(1)</a> and CVSup.
1.10 naddy 63: </p>
1.1 espie 64:
65: <p>
66: The OpenBSD Project currently has five main source repositories:
67: </p>
68:
69: <ul>
70: <li><b>src</b> - Houses all source code for the OpenBSD Operating System.</li>
71: <li><b>ports</b> - Houses the <a href="./ports.html">OpenBSD Ports</a>.</li>
1.10 naddy 72: <li><b>www</b> - Houses all OpenBSD web pages (including this one).</li>
1.1 espie 73: <li><b>x11</b> - Houses OpenBSD's adaptation of the
74: <a href="http://www.XFree86.org/">XFree86-3</a> software project.</li>
75: <li><b>xf4</b> - Houses OpenBSD's adaptation of the
76: <a href="http://www.XFree86.org/">XFree86-4</a> software project.</li>
77: </ul>
78:
79: <h3><a name="CVS"><font color="#0000e0">What Is CVS?</font></a></h3>
80:
81: <p>
82: CVS is the source code control system used to manage the OpenBSD source
83: tree. It is described in more detail <a href="anoncvs.html#CVS">here</a>.
84: Note that CVS and CVSync are entirely different programs. Although
85: CVS can be used for remote file access, it is not optimized for
86: wholesale source tree distribution over the net, and CVSync can be
87: easily an order of magnitude more efficient for this task.
88: </p>
89:
90: <h3>
91: <a name="starting"><font color="#0000e0">Getting Started Using CVSync</font></a>
92: </h3>
93:
94: <p>
95: If you only care about running CVSync, it is recommended that you
96: download the cvsync package from the <a href="ftp.html">ftp mirror
97: sites</a> instead of building your own from the <tt>net/cvsync</tt>
1.10 naddy 98: port.
1.1 espie 99: </p>
100:
101: <p>
102: For further information about CVSync, see the
103: <a href="http://www.cvsync.org/">project homepage</a>.
104: </p>
105:
106: <p>
107: In order to mirror the OpenBSD repository with CVSync,
108: the following configuration file might be used:
109: </p>
110:
111: <pre>
112: config {
113: hostname anoncvs.de.openbsd.org
1.5 naddy 114: # If your network link is a T1 or faster, comment out the following line.
1.1 espie 115: compress
1.4 espie 116: collection {
1.5 naddy 117: name openbsd release rcs
1.4 espie 118: prefix /cvs
1.5 naddy 119: umask 002
1.4 espie 120: }
1.1 espie 121: }
122: </pre>
123:
124: <p>
125: This directs cvsync to refresh all OpenBSD distributions from
126: <b>anoncvs.de.openbsd.org</b> with a <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=umask&sektion=2">umask(2)</a> that permits group write
127: permission to the local repository.
128: </p>
129:
130: <p>
131: Assuming this file is saved as <tt>cvs-syncfile</tt>, the
132: following command would be used to invoke cvsync
133: </p>
134: <pre>
135: cvsync -c cvs-syncfile
136: </pre>
137:
138: <h3><a name="using">
139: <font color="#0000e0">Using CVS to Update Your Source Tree</font>
140: </a></h3>
141:
142: <p>
143: It is now simple to check out any one of the CVSync'ed repositories.
144: For Korn/Bourne shells:
145: </p>
146: <pre>
147: # cd /usr
148: # CVSROOT=/cvs cvs checkout src
149: </pre>
150: <p>
151: For csh and its derivatives:
152: </p>
153: <pre>
154: # cd /usr
155: # setenv CVSROOT /cvs
156: # cvs checkout src
157: </pre>
158:
159: <p>
160: The above will check out the most current sources. Many of you will only
161: want the release sources, especially if you are patching your system. To
162: checkout release sources you must specify a tag along with your command.
163: For example:
164: </p>
165: <pre>
166: # cd /usr
1.10 naddy 167: # cvs checkout -rOPENBSD_3_4 src
1.1 espie 168: </pre>
169: <p>
1.10 naddy 170: Or <tt>OPENBSD_3_3</tt> for 3.3, etc.
1.1 espie 171: </p>
172:
173: <h3>
174: <a name="CVSROOT"><font color="#0000e0">Available CVSync Servers</font></a>
175: </h3>
176:
177: <p>The following CVSync servers are available:</p>
178:
1.3 naddy 179: <p>
1.6 naddy 180: <ul>
181: <li><strong>anoncvs.usa.openbsd.org</strong><br>
182: located at the University of Colorado, Boulder, western USA;<br>
1.3 naddy 183: maintained by <a href="mailto:millert@openbsd.org">Todd Miller</a>.<br>
1.6 naddy 184: Updated every 3 hours.<br>
1.3 naddy 185:
1.2 naddy 186: <p>
1.6 naddy 187: <li><a href="http://anoncvs.de.openbsd.org/"><strong>anoncvs.de.openbsd.org</strong></a><br>
188: Host also known as <strong>grappa.unix-ag.uni-kl.de</strong>,<br>
1.2 naddy 189: located at the University of Kaiserslautern, Germany;<br>
1.1 espie 190: maintained by <a href="mailto:naddy@openbsd.org">Christian Weisgerber</a>.<br>
1.6 naddy 191: Updated every 6 hours from anoncvs.usa.openbsd.org.<br>
1.3 naddy 192:
1.2 naddy 193: <p>
1.6 naddy 194: <li><a href="http://www.allbsd.org/"><strong>cvsync.allbsd.org</strong></a><br>
1.2 naddy 195: located in Tokyo, Japan;<br>
1.6 naddy 196: maintained by <a href="mailto:hrs@allbsd.org">Hiroki Sato</a>.<br>
1.3 naddy 197:
1.1 espie 198: <p>
1.6 naddy 199: <li><a href="http://csociety.org/cvsup.html"><strong>cvsync.csociety.org</strong></a><br>
1.2 naddy 200: located at Purdue University, Indiana, USA;<br>
1.6 naddy 201: maintained by <a href="mailto:will@csociety.purdue.edu">Will Andrews</a>.<br>
1.3 naddy 202:
203: <p>
1.9 naddy 204: <li><strong>cvsync.linux.org.tr</strong><br>
205: located at ULAKBIM, Ankara, Bilkent, Turkey;<br>
206: maintained by <a href="mailto:bdd@mindcast.org">Berk D. Demir</a>.<br>
207: Updated every 2 hours from anoncvs.usa.openbsd.org.<br>
208:
209: <p>
1.6 naddy 210: <li><a href="http://mirror.osn.de/"><strong>mirror.osn.de</strong></a><br>
1.3 naddy 211: located in Nürnberg, Germany;<br>
212: maintained by <a href="mailto:aw@osn.de">Armin Wolfermann</a>.<br>
1.6 naddy 213: Updated every 4 hours from cvsup.uk.openbsd.org.<br>
214: </ul>
1.1 espie 215:
216: <p>
1.2 naddy 217: <em>Note:</em> If your server is listed on here with inaccurate or
1.1 espie 218: unknown information, please contact <a
219: href="mailto:beck@openbsd.org"><tt>beck@openbsd.org</tt></a>
220: or <a href="mailto:naddy@openbsd.org"><tt>naddy@openbsd.org</tt></a>
221: </p>
222: <p>
223: You may want to use <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=traceroute&sektion=8">traceroute(8)</a>
224: to find out which server is nearest you.
225: Problems with a server should be reported to the <b>maintainer</b> of the
226: server in question.
227: </p>
228: <p>
229: Currently (as of December 17, 2003), the CVS repository sizes are
230: </p>
231: <table>
232: <tr><td width="20"></td>
233: <td><strong>openbsd-ports</strong></td>
234: <td>- <b>140</b>MB</td></tr>
235: <tr><td></td>
236: <td><strong>openbsd-src</strong></td>
237: <td>- <b>1140</b>MB</td></tr>
238: <tr><td></td>
239: <td><strong>openbsd-www</strong></td>
240: <td>- <b>104</b>MB</td></tr>
241: <tr><td></td>
242: <td><strong>openbsd-x11</strong></td>
243: <td>- <b>200</b>MB</td></tr>
244: <tr><td></td>
245: <td><strong>openbsd-xf4</strong></td>
246: <td>- <b>442</b>MB</td></tr>
247: <tr><td></td>
248: <td><strong>openbsd-cvsroot</strong></td>
249: <td>- <b>257</b>MB</td></tr>
250: </table>
251: <p>
252: The overall repository size currently increases at a rate
253: of about <b>225</b>MB per annum.
254: </p>
255: <p>
256: <strong>IMPORTANT NOTE:</strong>
257: There are a few issues relating to cryptographic software that everyone
258: should be aware of:
259: </p>
260: <ul>
261: <li>
262: <p>
263: The OpenBSD sources are from Canada. As
264: <a href="http://www.efc.ca/pages/doc/crypto-export.html">
265: researched by a Canadian individual</a> and as
266: <a href="http://axion.physics.ubc.ca/ECL.html">
267: described in the Export Control list of Canada</a>,
268: it is legal to export crypto software from Canada to the world.
269: </p>
270: </li>
271: <li>
272: <p>
273: However, if you are outside the USA or Canada, you should not
1.8 naddy 274: fetch the cryptographic sections of the OpenBSD sources from a
275: CVSync server located in the USA. The files in question are...
1.1 espie 276: </p>
277: <ul>
278: <li><tt>src/kerberosIV/*</tt></li>
279: <li><tt>src/kerberosV/*</tt></li>
280: <li><tt>src/lib/libdes/*</tt></li>
281: <li><tt>src/lib/libc/crypt/crypt.c</tt></li>
282: <li><tt>src/lib/libc/crypt/morecrypt.c</tt></li>
283: <li><tt>src/sys/crypto</tt></li>
284: <li><tt>src/sys/netinet</tt></li>
285: <li><tt>src/usr.sbin/afs/src/rxkad/*</tt></li>
286: <li><tt>XF4/xc-mit/lib/Xdmcp/Wraphelp.c</tt></li>
287: <li><tt>XF4/xc-old/lib/Xdmcp/Wraphelp.c</tt></li>
288: <li><tt>XF4/xc/lib/Xdmcp/Wraphelp.c</tt></li>
289: </ul>
290: <p>
291: Because of the USA ITAR munitions list,
292: crypto software may only be exported to Canada from the USA.
293: </p>
294: </li>
295: </ul>
296:
297: <p>
298: The OpenBSD project is looking for more CVSync servers -- if you are
299: interested, please contact <a href="mailto:naddy@openbsd.org">Christian Weisgerber</a>
300: for configuration details.
301: </p>
302:
303: <hr>
304: <a href="index.html"><img height="24" width="24" src="back.gif" border="0" alt="OpenBSD"></a>
305: <a href="mailto:www@openbsd.org">www@openbsd.org</a>
1.11 ! jose 306: <br><small>$OpenBSD: cvsync.html,v 1.10 2003/12/31 15:21:26 naddy Exp $</small>
1.1 espie 307:
308: </body>
309: </html>