Annotation of www/cvsup.html, Revision 1.5
1.1 brian 1: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML Strict//EN">
2: <html>
3: <head>
4: <title>OpenBSD CVSup</title>
5: <link rev=made href=mailto:www@openbsd.org>
6: <meta name="resource-type" content="document">
7: <meta name="description" content="How to get OpenBSD updates via Internet using CVSup">
8: <meta name="keywords" content="openbsd,cvsup,updates">
9: <meta name="distribution" content="global">
10: <meta name="copyright" content="This document copyright 2000 by OpenBSD.">
11: </head>
12:
13: <BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#23238E">
14:
15: <img alt="[OpenBSD]" height=30 width=141 SRC="images/smalltitle.gif">
16: <p>
17: <h2><font color=#e00000>CVSup</font><hr></h2>
18:
19: <p>
20: <ul><h3>Table Of Contents</h3>
21: <li><a href="#cvsup">What is CVSup?</a>
22: <li><a href="#starting">Getting Started Using CVSup.</a>
23: <li><a href="#using">Using CVS to Update your Source Tree.</a>
24: <li><a href="#CVSROOT">Available CVSup Servers.</a>
25: </ul>
26: </p>
27: <hr>
28:
29:
1.2 brian 30: <h3><a name="cvsup"><font color=#0000e0>What is CVSup?</font></a></h3>
1.1 brian 31:
32: <p>
33: <b>CVSup</b> is a software package for distributing and updating source
34: trees from a master CVS repository on a remote server host. The OpenBSD
35: sources are maintained in a CVS repository on a central development machine
36: in Canada. With CVSup, OpenBSD users can easily keep their own source trees
37: up to date.
38: </p>
39:
40: <p>
41: <b>CVSup</b> uses the so-called pull model of updating. Under the pull
42: model, each client asks the server for updates, if and when they are
43: wanted. The server waits passively for update requests from its clients.
44: Thus all updates are instigated by the client. The server never sends
45: unsolicited updates. Users must either run the <b>CVSup</b> client
46: manually to get an update, or they must set up a cron job to run it
47: automatically on a regular basis.
48: </p>
49:
50: <p>
51: The term <b>CVSup</b>, capitalized just so, refers to the entire software
52: package. Its main components are the client <tt>cvsup</tt> which runs on
53: each user's machine, and the server <tt>cvsupd</tt> which runs at each of
54: the OpenBSD CVSup mirror sites.
55: </p>
56:
57: <p>
58: <b>CVSup</b> is intended to be both faster and more flexible than
59: <b>sup</b>, CVSup's predecessor.
60: </p>
61:
62: <p>
63: The OpenBSD Project currently has four main source repositories:
64: </p>
65:
66: <ul>
67: <li><b>src</b> - Houses all source code for the OpenBSD Operating System.
68: <li><b>ports</b> - Houses the <a href="./ports.html">OpenBSD Ports</a>.
69: <li><b>www</b> - Houses all OpenBSD web pages. (Including this one).
70: <li><b>x11</b> - Houses OpenBSD's adaptation of the
71: <a href="http://www.XFree86.org/">XFree86</a> software project.
72: </ul>
73:
1.2 brian 74: <h3><a name="CVS"><font color=#0000e0>What is CVS?</font></a></h3>
1.1 brian 75:
76: <p>
77: CVS is the source code control system used to manage the OpenBSD source
78: tree.</a> It is described in more detail <a href=anoncvs.html#CVS>here</a>.
79:
1.2 brian 80: <h3>
81: <a name="starting"><font color=#0000e0>Getting Started Using CVSup.</font></a>
82: </h3>
1.1 brian 83:
84: <p>
85: The latest version of CVSup is available at
86: <a href=http://www.polstra.com/projects/freeware/CVSup/>
87: http://www.polstra.com/projects/freeware/CVSup/</a>.
88: </p>
89:
90: <p>
91: The following configuration file might be used:
92: </p>
93:
94: <pre>
95: # Defaults that apply to all the collections
96: *default release=cvs
97: *default delete use-rel-suffix
98: *default umask=002
99: *default host=cvsup.uk.OpenBSD.org
100: *default base=/cvs
101: *default prefix=/cvs
102:
103: # If your network link is a T1 or faster, comment out the following line.
104: *default compress
105:
106: OpenBSD-all
107: #OpenBSD-src
108: #OpenBSD-www
109: #OpenBSD-ports
110: #OpenBSD-x11
111: </pre>
112:
113: <p>
114: This directs cvsup to refresh all OpenBSD distributions from
115: <b>cvsup.uk.OpenBSD.org</b> with a umask that permits group write
116: permission to the local repository.
117: </p>
118:
119: <p>
120: Assuming this file is saved as <tt>cvs-supfile</tt>, the
121: following command would be used to envoke the cvsup GUI:
122: <pre>
123: cvsup cvs-supfile
124: </pre>
125: whereas for batch mode, the following might be used:
126: <pre>
127: cvsup -g -L 2 cvs-supfile
128: </pre>
129:
1.2 brian 130: <h3><a name="using">
131: <font color=#0000e0>Using CVS(1) to update your source tree.</font>
132: </a></h3>
1.1 brian 133:
134: <p>
135: It is now simple to checkout any one of the CVSup'd repositories:
136:
137: <ul>
138: <li> For Korn/Bourne shells.
139: <ul><pre>
140: # <b>cd /usr</b>
141: # <b>CVSROOT=/cvs cvs checkout src</b>
142: </pre></ul>
143: <li> For CSH based shells.
144: <ul><pre>
145: # <b>cd /usr</b>
146: # <b>setenv CVSROOT /cvs</b>
147: # <b>cvs checkout src</b>
148: </pre></ul>
149: </ul>
150:
151: <p>
152: The above will checkout the most current sources. Many of you will only
153: want the release sources, especially if you are patching your system. To
154: checkout release sources you must specify a tag along with your command.
155: For example:
156: </p>
157:
158: <p>
159: <ul><pre>
160: # <b>cd /usr</b>
161: # <b>cvs checkout -rOPENBSD_2_6 src</b>
162: </pre></ul>
163: Or OPENBSD_2_5 for 2.5, etc.
164: </p>
165:
1.2 brian 166: <h3>
167: <a name="CVSROOT"><font color=#0000e0>Available CVSup Servers.</font></a>
168: </h3>
1.1 brian 169:
170: <dl>
171: <dt><strong>The following CVSup servers are available:</strong>
172: <dd>
173:
174: <p>
175: <li><strong>cvsup.uk.OpenBSD.org</strong><br>
176: located in Brighton, UK.<br>
177: maintained by <a href=mailto:brian@OpenBSD.org>Brian Somers</a>.<br>
178: updated every 2 hours.<br>
179: <p>
180: <b>Available collections</b>:
181: <table>
182: <tr><td width=20><td><strong>OpenBSD-src</strong><td>- The <b>src</b> repository
183: <tr><td><td><strong>OpenBSD-ports</strong><td>- The <b>ports</b> repository
184: <tr><td><td><strong>OpenBSD-www</strong><td>- The <b>www</b> repository
185: <tr><td><td><strong>OpenBSD-x11</strong><td>- The <b>x11</b> repository
186: <tr><td><td><strong>OpenBSD-all</strong><td>- All OpenBSD repositories
187: </table>
188: </p>
189:
1.3 brian 190: <p>
191: <li><strong>cvsup.de.OpenBSD.org</strong><br>
192: located near Frankfurt am Main.<br>
193: maintained by <a href=mailto:wosch@FreeBSD.org>Wolfram Schneider</a>.<br>
194: updated by CTM.<br>
195: <p>
196: <b>Available collections</b>:
197: <table>
198: <tr><td width=20><td><strong>openbsd-src-all</strong><td>- The <b>src</b> repository
199: <tr><td><td><strong>openbsd-ports-all</strong><td>- The <b>ports</b> repository
200: <tr><td><td><strong>openbsd-www-all</strong><td>- The <b>www</b> repository
201: <tr><td><td><strong>openbsd-cvs-all</strong><td>- All OpenBSD repositories except for x11
202: </table>
203: </p>
204:
1.5 ! ericj 205: <p>
! 206: <li><strong>openbsd.ik.bme.hu</strong><br>
! 207: located in Hungary.<br>
! 208: maintained by <a href=mailto:mohacsi@hera.ik.bme.hu>Mohacsi Janos</a>.<br>
! 209: Updated every 4 hours.<br>
! 210: <p>
! 211: <b>Available collections</b>:
! 212: <table>
! 213: <tr><td width=20><td><strong>OpenBSD-src</strong><td>- The <b>src</b> repository
! 214: <tr><td><td><strong>OpenBSD-ports</strong><td>- The <b>ports</b> repository
! 215: <tr><td><td><strong>OpenBSD-www</strong><td>- The <b>www</b> repository
! 216: <tr><td><td><strong>OpenBSD-x11</strong><td>- The <b>x11</b> repository
! 217: <tr><td><td><strong>OpenBSD-all</strong><td>- All OpenBSD repositories
! 218: </table>
! 219: </p>
1.1 brian 220: </ul>
221:
222:
1.5 ! ericj 223:
1.1 brian 224: <p>
225: <EM>Note:</EM>, If your server is listed on here with inaccurate or
226: unknown information, please contact <A
227: HREF="mailto:beck@openbsd.org"><tt>beck@openbsd.org</tt></A>
228: <p>
229: You may want to use `traceroute' to find out which server is nearest you.
230: Problems with a server should be reported to the <b>maintainer</b> of the
231: server in question.
232: </dl>
233: <p>
1.4 brian 234: Currently (as of April 11, 2000), the cvs repository sizes are
235: <table>
236: <tr><td width=20><td><strong>ports</strong><td>- <b>30</b>Mb
237: <tr><td><td><strong>src</strong><td>- <b>657</b>Mb
238: <tr><td><td><strong>www</strong><td>- <b>19</b>Mb
239: <tr><td><td><strong>x11</strong><td>- <b>195</b>Mb
240: </table>
241: <p>
242: There is an additional overhead of <b>25</b>Mb for the CVSROOT and sup
243: directories
244: <p>
1.1 brian 245: <strong>IMPORTANT NOTE:</strong>
246: There are a few issues relating to cryptographic software that everyone
247: should be aware of:
248: <ul>
249: <li>The OpenBSD sources are from Canada.
250: As
251: <a href=http://insight.mcmaster.ca/org/efc/pages/doc/crypto-export.html>
252: researched by a Canadian individual</a>
253: and as
254: <a href=http://axion.physics.ubc.ca/ECL.html>
255: described in the Export Control list of Canada</a>
256: is legal to export crypto software from Canada to the world.
257: <p>
258: <li>However, if you are outside the USA or Canada, you should not
259: fetch the cryptographic sections of the OpenBSD sources from an
260: anoncvs server located in the USA. The files in question are...
261: <ul>
262: <li>src/kerberosIV/*
263: <li>src/lib/libdes/*
264: <li>src/lib/libc/crypt/crypt.c
265: <li>src/lib/libc/crypt/morecrypt.c
266: <li>src/sys/netinet
267: <li>src/usr.sbin/afs/src/rxkad/*
268: <li>X11/xc/lib/Xdmcp/Wraphelp.c
269: </ul>
270: Because of the USA ITAR munitions list,
271: crypto software may only be exported to Canada from the USA.
272: </ul>
273:
274: <p>
275: The OpenBSD project is looking for more CVSup servers -- if you are
276: interested, please contact <a href=mailto:brian@OpenBSD.org>Brian Somers</a>
277: for configuration details.
278: </p>
279:
280: <hr>
281: <a href=index.html><img height=24 width=24 src=back.gif border=0 alt=OpenBSD></a>
282: <a href=mailto:www@openbsd.org>www@openbsd.org</a>
1.5 ! ericj 283: <br><small>$OpenBSD: cvsup.html,v 1.4 2000/04/11 10:02:39 brian Exp $</small>
1.1 brian 284:
285: </body>
286: </html>