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