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