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