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