Annotation of www/anoncvs.html, Revision 1.108
1.1 deraadt 1: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML Strict//EN">
2: <html>
3: <head>
1.93 deraadt 4: <title>OpenBSD AnonCVS</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 Anonymous CVS">
8: <meta name="keywords" content="openbsd,anoncvs,updates">
9: <meta name="distribution" content="global">
10: <meta name="copyright" content="This document copyright 1996-1998 by OpenBSD.">
1.1 deraadt 11: </head>
12:
1.14 downsj 13: <BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#23238E">
1.1 deraadt 14:
1.58 pauls 15: <img alt="[OpenBSD]" height=30 width=141 SRC="images/smalltitle.gif">
1.93 deraadt 16: <p>
17: <h2><font color=#e00000>Anonymous CVS</font><hr></h2>
1.14 downsj 18:
1.100 ericj 19: <p>
20: <ul><h3>Table Of Contents</h3>
21: <li><a href="#anoncvs">What is Anonymous CVS?</a>
22: <li><a href="#CVS">What is CVS?</a>
23: <li><a href="#starting">Getting Started Using Anonymous CVS.</a>
24: <li><a href="#using">Using CVS to Get and Update your Source Tree.</a>
25: <li><a href="#CVSROOT">Available Anonymous CVS Servers.</a>
1.104 ericj 26: <li><a href="#CRYPTO">Getting crypto sources through CVS(1).</a>
27: <li><a href="#EXAMPLE">Example usages for CVS(1).</a>
28: <li><a href="#WHICH">Use rsh(1) or ssh(1)?</a>
1.107 millert 29: <li><a href="#SUP">Mirroring the CVS repository via sup(1).</a>
1.105 ericj 30: <li><a href="#MIRROR">Setting up an anoncvs mirror.</a>
1.100 ericj 31: </ul>
32: </p>
33: <hr>
34:
35:
36: <a name="anoncvs"></a>
37: <h3><font color=#0000e0>What is Anonymous CVS?</font></h3>
1.99 ericj 38:
1.15 grr 39: <p>
40: Anonymous CVS is a method of keeping your local copy of the OpenBSD source
41: tree up to date with respect to changes made to current OpenBSD sources.
1.99 ericj 42: </p>
43:
1.14 downsj 44: <p>
1.15 grr 45: The major advantage of Anonymous CVS over other source code update
46: techniques is that it works directly against a central source code
47: repository or mirror. This means that you have the full set of CVS
48: commands available to control merging and updating your changes with
49: other source changes and for performing diff's, change histories
50: and other queries against the central repository.
1.99 ericj 51: </p>
52:
1.36 deraadt 53: <p>
1.99 ericj 54: The OpenBSD Project currently has three main source repositories:
55: </p>
56:
57: <ul>
58: <li><b>src</b> - Houses all source code for the OpenBSD Operating System.
59: <li><b>ports</b> - Houses the <a href="./ports.html">OpenBSD Ports</a>.
60: <li><b>www</b> - Houses all OpenBSD web pages. (Including this one).
61: </ul>
62:
1.100 ericj 63: <p>
64: To summarize, the real strength of using Anonymous CVS is that it is
65: a "tolerant" source code control system - it <strong>respects</strong>
66: changes that you have made to your local sources and makes <strong>
67: "best efforts"</strong> to update your entire source tree, rather than
68: leaving you a list of arcane problems that have to be resolved before
69: continuing.
70: </p>
71:
72: <a name="CVS"></a>
73: <h3><font color=#0000e0>What is CVS?</font></h3>
1.99 ericj 74:
1.36 deraadt 75: <p>
76: <a href=why-cvs.html>
77: CVS is the source code control system used to manage the OpenBSD source tree.</a>
1.16 deraadt 78: It implements a central repository for all officially released source code
1.15 grr 79: and changes, while permitting developers to maintain local copies of the
1.99 ericj 80: source code with their working changes. Developers with "<b>write access</b>"
1.15 grr 81: can commit changes directly to the OpenBSD source tree, while "Anonymous
1.99 ericj 82: CVS" users have "<b>read access</b>" and can keep their local copies of the source
1.15 grr 83: up to date and issue queries against the central depository.
1.99 ericj 84: </p>
85:
1.15 grr 86: <p>
1.22 niklas 87: The major strength of CVS is that it has the ability to perform intelligent
1.15 grr 88: merges of changes to the central repository with changes that you make to
89: your local copy. This means that if you make a change to a module and
90: perform an update, your changes are not "blown away", rather CVS makes
91: best efforts to merge the changes made to the central sources with changes
92: you've made to your local copy.
1.99 ericj 93: </p>
94:
1.15 grr 95: <p>
96: In the event that the changes can't be completely merged, CVS provides a
97: "soft fallback", in terms of providing you with annotated changes to your
1.39 todd 98: local copy, preserving an unmodified copy of your version and continuing
1.15 grr 99: to update any other source modules you requested.
1.99 ericj 100: </p>
101:
1.100 ericj 102: <a name="starting"></a>
103: <h3><font color=#0000e0>Getting Started Using Anonymous CVS.</font></h3>
104:
105: <p>
106: The latest version of CVS is available at
107: <a href=http://download.cyclic.com/pub/>Cyclic</a>.
108: Versions earlier than 1.6 are not recommended, and may not work.
109: If you already have OpenBSD installed, CVS is included.
110: </p>
111:
1.22 niklas 112: <p>
1.99 ericj 113: People who own an OpenBSD CD may have seen the <i>CVS/</i> dirs on it.
114: Actually there is a reason, the CD has a checkout of the OpenBSD <b>src</b> module
1.95 millert 115: usable to continue updating from. Using this tree will result in a much
1.23 mickey 116: faster initial CVS update than a fresh checkout of the full OpenBSD
117: source tree. There are two ways of using the CD:
1.99 ericj 118: </p>
119:
1.23 mickey 120: <ul>
1.99 ericj 121: <li>To copy the CVS tree from the CD to <i>/usr/src</i> (assuming the CD is mounted on /mnt):
1.22 niklas 122: <pre>
1.99 ericj 123: # <b>cd /mnt; pax -rw CVS Makefile [a-z]* /usr/src</b>
1.22 niklas 124: </pre>
1.99 ericj 125: <li>Use a union mount with the CD below a writable directory. (This can be used when only compiling from the tree.)
1.22 niklas 126: <pre>
1.99 ericj 127: # <b>mount -t union -o -b /mnt /usr/src</b>
1.22 niklas 128: </pre>
1.23 mickey 129: </ul>
1.100 ericj 130:
131: <p>
132: For people who don't have a CD on hand, you can use <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=cvs&sektion=1&format=html">cvs(1)</a> to "<b>checkout</b>" the source repository for you. This is discussed in the <a href="#using">next section</a>.
133: </p>
134:
135: <p>
1.99 ericj 136: After this, <i>/usr/src</i> will be a nice checkout area where all <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=cvs&sektion=1&format=html">cvs(1)</a> commands will work OK.
1.100 ericj 137: </p>
138:
139: <a name="using"></a>
140: <h3><font color=#0000e0>Using CVS(1) to get and update your source tree.</font></h3>
141:
142: <p>
143: CVS was designed to be a simple way to retrive and update your sources, therefore there
144: isn't much involved at all in doing so. To start off you must know which Anonymous CVS server you are going to use. A list of these servers is <a href="#CVSROOT">below</a>.
145: Do, however, notice that there are only 3 ways to access these servers.
146: </p>
1.99 ericj 147:
1.100 ericj 148: <ul>
149: <li><b>ssh</b> - Secure Shell can be used to access the anonymous CVS servers. This is the <b>recommended</b> way of doing so, as it is encrypted. As of 2.6 OpenBSD has included OpenSSH in its standard distribution.
150: <li><b>rsh</b> - Remote Shell can be used on some of the servers for users who don't have access to <a href="http://www.openssh.com">ssh</a>
151: <li><b>pserver</b> - pserver is primarily useful for users who are behind firewalls that block the other two connections.
152: </ul>
153:
154: <p>
155: <b>NOTE:</b> - For users wishing to use ssh, you must first set the <i>CVS_RSH</i> variable to ssh.
156:
157: <ul>
158: <li> For Korn/Bourne shells.
159: <pre>
160: $ <b>export CVS_RSH="/usr/bin/ssh"</b>
161: </pre>
162: <li> For CSH based shells.
163: <pre>
164: $ <b>setenv CVS_RSH /usr/bin/ssh</b>
165: </pre>
166: </ul>
167:
168: <p>
169: Once you have chosen which <a href="#CVSROOT">Anonymous CVS Server</a> you will use, and which method you will use, you can start using cvs. For those of you who have CD's you can start with the CVS checkout that is on the CD by using the method <a href="#starting">above</a> to get the sources onto your system. If you don't have a CD handy, use the method below to checkout the sources. This method puts the OpenBSD source tree into <i>/usr/src</i>.
170: </p>
171:
172: <p>
173: <ul><pre>
174: # <b>cd /usr; cvs checkout src</b>
175: </ul></pre>
176: </p>
1.99 ericj 177:
1.1 deraadt 178: <p>
1.100 ericj 179: The above will checkout the most current sources. Many of you will only want the release sources, especially if you are patching your system. To checkout release sources you must specify a tag along with your command. Example:
180: </p>
1.1 deraadt 181:
182: <p>
1.100 ericj 183: <ul><pre>
184: # <b>cd /usr; cvs checkout -rOPENBSD_2_6 src</b>
185: </ul></pre>
186: Or OPENBSD_2_5 for 2.5, etc.
187: </p>
188:
189:
190: <a name="CVSROOT"></a>
191: <h3><font color=#0000e0>Available Anonymous CVS Servers.</font></h3>
1.1 deraadt 192:
193: <p>
194: There are two levels of source tree access:
195:
196: <dl>
197: <dt><strong>Read-write access for developers:</strong>
198: <dd>Developers who need to commit changes to the source tree must have
199: an account on the OpenBSD machines. Getting this access will be a
200: natural result of working on the sources with other OpenBSD developers.
201: If someone does some good work and shows they can work with the team,
202: they will get an account.
203: </dl>
204:
205: <dl>
206: <dt><strong>Read-only access for everyone:</strong>
207: <dd>Anyone can access the read-only CVS repositories. These copies
208: of the read-write CVS repository are mirrored often. To use one,
209: set your <strong>CVSROOT</strong> environment variable to one of
210: the following values:
1.12 grr 211: <p>
212: <strong>Please see the note about using ssh vs. rsh below!</strong>
213: <p>
1.1 deraadt 214: <ul>
215: <p>
1.83 millert 216: <li><strong>CVSROOT=anoncvs@anoncvs1.usa.openbsd.org:/cvs</strong><br>
217: Host also known as <strong>anoncvs@anoncvs4.usa.openbsd.org</strong>.<br>
1.10 millert 218: located in California, western USA.<br>
1.46 millert 219: maintained by <a href=mailto:millert@openbsd.org>Todd Miller</a>.<br>
1.83 millert 220: protocols: pserver only.<br>
1.1 deraadt 221: updated every 4 hours.<br>
222: <p>
1.83 millert 223: <li><strong>CVSROOT=anoncvs@anoncvs.usa.openbsd.org:/cvs</strong><br>
224: Host also known as <strong>anoncvs3.usa.openbsd.org</strong>.<br>
1.1 deraadt 225: located at the University of Colorado, Boulder, western USA.<br>
226: maintained by <a href=mailto:Todd.Miller@cs.colorado.edu>Todd Miller</a>.<br>
1.94 millert 227: protocols: rsh, ssh, ssh port 2022, pserver.<br>
1.1 deraadt 228: updated every 6 hours.<br>
229: <p>
1.76 deraadt 230: <li><strong>CVSROOT=anoncvs@anoncvs5.usa.openbsd.org:/cvs</strong><br>
231: Host also known as <strong>squid.nas.nasa.gov</strong>.<br>
232: located at Ames Research Center, Moffett Field, California, USA.<br>
1.78 deraadt 233: maintained by <a href=mailto:allison@mail.arc.nasa.gov>Tyler Allison</a>.<br>
1.77 deraadt 234: protocols: ssh only.<br>
235: updated every 3 hours.<br>
1.84 beck 236: <li><strong>CVSROOT=anoncvs@mirror.arc.nasa.gov:/cvs</strong><br>
237: located at Ames Research Center, Moffett Field, California, USA.<br>
238: maintained by <a href=mailto:allison@mail.arc.nasa.gov>Tyler Allison</a>.<br>
239: protocols: ssh only.<br>
240: updated every 3 hours.<br>
1.76 deraadt 241: <p>
1.31 deraadt 242: <li><strong>CVSROOT=anoncvs@anoncvs6.usa.openbsd.org:/cvs</strong><br>
243: Host also known as <strong>openbsd.citi.umich.edu</strong>.<br>
244: located at the University of Michigan, central USA.<br>
245: maintained by <a href=mailto:rees@umich.edu>Jim Rees</a>.<br>
246: protocols: ssh, ssh port 2022.<br>
247: updated every 12 hours.<br>
248: <p>
1.24 deraadt 249: <li><strong>CVSROOT=anoncvs@anoncvs1.ca.openbsd.org:/cvs</strong><br>
1.40 beck 250: Host also known as <strong>anoncvs.ca.openbsd.org</strong>,
1.74 beck 251: <strong>openbsd.sunsite.ualberta.ca</strong><br>
1.24 deraadt 252: located in Edmonton, Alberta, Canada.<br>
1.80 beck 253: maintained by <A HREF="mailto:beck@ualberta.ca">Bob Beck</A><br>
1.53 beck 254: protocols: ssh, rsh, ssh port 2022, pserver<br>
1.45 beck 255: updated every 2 hours.<br>
1.24 deraadt 256: <p>
1.106 beck 257: <li><strong>CVSROOT=anoncvs@valkyrie.secureops.com:/cvs</strong><br>
258: located in Montreal, Quebec, Canada.<br>
259: maintained by <A HREF="mailto:drbones@darkelves.com">Patrick Ethier</A><br>
260: protocols: ssh<br>
261: updated every 24 hours at 3 AM EST<br>
262: <p>
1.1 deraadt 263: <li><strong>CVSROOT=anoncvs@anoncvs.uk.openbsd.org:/cvs</strong><br>
264: Host also known as <strong>dumpty.wonderland.org</strong>.<br>
265: located in London, UK.<br>
266: maintained by <a href=mailto:peter@wonderland.org>Peter Galbavy</a>.<br>
267: protocols: rsh.<br>
268: updated every 12 hours.<br>
269: <p>
270: <li><strong>CVSROOT=anoncvs@anoncvs.tw.openbsd.org:/cvs</strong><br>
1.64 deraadt 271: Host also known as <strong>OpenBSD.csie.NCTU.edu.tw</strong>.<br>
1.1 deraadt 272: located in Taipei, Taiwan.<br>
1.63 deraadt 273: maintained by <a href=mailto:lkchu@OpenBSD.csie.NCTU.edu.tw>Liang-Kai Chu</a>.<br>
1.1 deraadt 274: protocols: rsh, ssh, ssh port 2022.<br>
275: updated every 12 hours.<br>
276: <p>
277: <li><strong>CVSROOT=anoncvs@anoncvs.no.openbsd.org:/cvs</strong><br>
1.64 deraadt 278: Host also known as <strong>cvs.inet.no</strong>.<br>
1.1 deraadt 279: located in Norway.<br>
1.64 deraadt 280: maintained by <a href=mailto:cvsadmin@inet.no>Michael Shuldman</a>.<br>
1.1 deraadt 281: protocols: rsh, ssh, ssh port 2022.<br>
282: updated every 4 hours.<br>
283: <p>
1.33 deraadt 284: <li><strong>CVSROOT=anoncvs@anoncvs.se.openbsd.org:/cvs</strong><br>
1.54 art 285: Host also known as <strong>anoncvs.stacken.kth.se</strong>.<br>
1.33 deraadt 286: located in Sweden.<br>
287: maintained by <a href=mailto:anoncvs@stacken.kth.se>Magnus Holmberg</a>.<br>
288: protocols: rsh, ssh, ssh port 2022.<br>
1.57 art 289: updated every 3 hours.<br>
1.68 wvdputte 290: <p>
291: <li><strong>CVSROOT=anoncvs@anoncvs.be.openbsd.org:/cvs</strong><br>
292: Host also known as <strong>badlands.rug.ac.be</strong>.<br>
293: located in Belgium.<br>
294: maintained by <a href=mailto:wvdputte@reptile.rug.ac.be>Wim Vandeputte</a>.<br>
295: protocols: ssh, ssh port 2022.<br>
296: updated every 3 hours.<br>
1.69 deraadt 297: <p>
298: <li><strong>CVSROOT=anoncvs@anoncvs.jp.openbsd.org:/cvs</strong><br>
299: Host also known as <strong>kankoromochi.econ.nagasaki-u.ac.jp</strong>.<br>
300: located at Nagasaki Univ. Faculty of Economics, JAPAN.<br>
301: maintained by <a href=mailto:sigh@net.nagasaki-u.ac.jp>SUZUKI Hitoshi</a>.<br>
1.79 deraadt 302: protocols: ssh, pserver.<br>
303: updated every 3 hours.<br>
1.73 deraadt 304: <li><strong>CVSROOT=anoncvs@anoncvs.cz.openbsd.org:/cvs</strong><br>
305: Host also known as <strong>com-os2.ms.mff.cuni.cz</strong>.<br>
1.98 rohee 306: located at Faculty Math & Physics, Charles University, Prague, Czech republic.<br>
1.73 deraadt 307: maintained by <a href=mailto:galambos@com-os2.ms.mff.cuni.cz>Leo Galambos</a>.<br>
308: protocols: ssh, ssh port 2022.<br>
309: updated every 3 hours.<br>
1.84 beck 310: <li><strong>CVSROOT=anoncvs@anoncvs1.au.openbsd.org:/cvs</strong><br>
311: Host also known as <strong>anoncvs.au.openbsd.org</strong>,
312: <strong>anoncvs.openbsd.aba.net.au</strong><br>
313: located in Carlton, Victoria, Australia.<br>
314: maintained by <A HREF="mailto:mwp@aba.net.au">Micheal Paddon</A><br>
315: protocols: ssh<br>
316: updated every 4 hours.<br>
1.88 beck 317: <li><strong>CVSROOT=anoncvs@dolphin.mtmc.ru:/cvs</strong><br>
318: located in Moscow, Russia<br>
319: maintained by <A HREF="mailto:jc@mtmc.ru">John Chertihin</A><br>
320: protocols: rsh, ssh<br>
1.89 beck 321: updated every 24 hours (at 1 AM Moscow time)<br>
1.86 beck 322: <li><strong>CVSROOT :pserver:anoncvs@gloup.linuxfr.org:/cvs</strong><br>
1.87 beck 323: Host also known as <strong>gloup.linuxfr.org</strong><br>
1.96 beck 324: located at Paris (Claranet), FRANCE<br>
1.87 beck 325: maintained by: <A HREF=mailto:seisen@linuxfr.org>Fabien Seisen</A><br>
1.96 beck 326: protocols: pserver, ssh<br>
1.86 beck 327: updated every 24h ( at 2h GMT )<br>
1.103 beck 328: <li><strong>CVSROOT :pserver:anoncvs@cvs.bsdfr.org:/cvs</strong><br>
329: located at in France<br>
330: maintained by: <A HREF=mailto:jch@oleane.net>Jean-Claude Christophe</A><br>
331: protocols: pserver<br>
332: updated every 24h <br>
1.80 beck 333: <li><strong>CVSROOT=anoncvs@exokernel.lcs.mit.edu:/cvs</strong><br>
334: located at M.I.T, Eastern USA.<br>
335: maintained by ????<br>
336: protocols: ssh, ???<br>
337: updated every ? hours.<br>
1.108 ! ho 338: <li><strong>CVSROOT=anoncvs@xyzzy.gsnig.org:/cvs</strong><br>
! 339: Located in Göteborg, Sweden<br>
1.80 beck 340: maintained by martin@openbsd.org<br>
1.108 ! ho 341: protocols: ssh port 2022<br>
! 342: updated every 4 hours.<br>
1.80 beck 343: <li><strong>CVSROOT=anoncvs@stl-isaas.ey.com:/cvs</strong><br>
1.90 beck 344: Located in St. Louis, MO, Eastern USA<br>
1.81 beck 345: maintained by <A HREF="mailto:aaron11@sprynet.com">Aaron Miller</A><br>
346: protocols: ssh, ssh port 2022, pserver<br>
347: updated every 3 hours.<br>
1.91 beck 348: <li><strong>CVSROOT=anoncvs@openbsd.groupbsd.org:/cvs</strong><br>
1.92 jason 349: Located in Hillsborough NC, Eastern USA<br>
350: maintained by <A HREF="mailto:jason@openbsd.org">Jason Wright</A><br>
1.91 beck 351: protocols: ssh<br>
352: updated every 4 hours.<br>
1.80 beck 353: <li><strong>CVSROOT=anoncvs@headend-vlan1-cm19.fibertel.com.ar:/cvs</strong><br>
354: Located in Buenos Aires, Argentina<br>
355: maintained by ????<br>
356: protocols: ssh?, ???<br>
357: updated every ? hours.<br>
1.73 deraadt 358: </ul>
1.84 beck 359:
360:
1.73 deraadt 361: <p>
1.80 beck 362: <EM>Note:</EM>, If your server is listed on here with inaccurate or
1.104 ericj 363: unknown information, please contact
364: <A HREF="mailto:beck@openbsd.org"><tt>beck@openbsd.org</tt></A>
365: </p>
366:
1.80 beck 367: <p>
1.104 ericj 368: You may want to use
369: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=traceroute&sektion=8&format=html">traceroute(8)</a>
370: to find out which server is nearest you.
1.11 michaels 371: Problems with a server should be reported to the <b>maintainer</b> of the
372: server in question.
1.104 ericj 373: </dl></p>
374:
375: <a name="CRYPTO"></a>
376: <h3><font color=#0000e0>Getting crypto sources through CVS(1)</font></h3>
377:
1.1 deraadt 378: <p>
379: <strong>IMPORTANT NOTE:</strong>
380: There are a few issues relating to cryptographic software that everyone
381: should be aware of:
382: <ul>
383: <li>The OpenBSD sources are from Canada.
1.9 deraadt 384: As
385: <a href=http://insight.mcmaster.ca/org/efc/pages/doc/crypto-export.html>
386: researched by a Canadian individual</a>
387: and as
388: <a href=http://axion.physics.ubc.ca/ECL.html>
389: described in the Export Control list of Canada</a>
390: is legal to export crypto software from Canada to the world.
1.1 deraadt 391: <p>
392: <li>However, if you are outside the USA or Canada, you should not
393: fetch the cryptographic sections of the OpenBSD sources from an
394: anoncvs server located in the USA. The files in question are...
395: <ul>
396: <li>src/kerberosIV/*
1.57 art 397: <li>src/lib/libdes/*
1.1 deraadt 398: <li>src/lib/libc/crypt/crypt.c
399: <li>src/lib/libc/crypt/morecrypt.c
1.36 deraadt 400: <li>src/sys/netinet
1.67 art 401: <li>src/usr.sbin/afs/src/rxkad/*
1.56 matthieu 402: <li>X11/xc/lib/Xdmcp/Wraphelp.c
1.1 deraadt 403: </ul>
404: Because of the USA ITAR munitions list,
405: crypto software may only be exported to Canada from the USA.
406: <p>
407: <li>The OpenBSD project is looking for more anoncvs servers -- read
408: on to find out how you can help.
409: </ul>
410:
1.104 ericj 411: <a name="EXAMPLE"></a>
412: <h3><font color=#0000e0>Example usages for CVS(1).</font></h3>
413:
1.1 deraadt 414: <p>
415: A sample use of an anoncvs CVS server would be:
1.104 ericj 416: <ul><pre>
417: % <strong>setenv CVSROOT anoncvs@anoncvs.ca.openbsd.org:/cvs</strong>
418: % <strong>cd /tmp</strong>
419: % <strong>cvs get src/sys/arch/sparc</strong>
1.12 grr 420: [copies the files from the repository to your machine]
1.104 ericj 421: % <strong>cvs log src/sys/arch/sparc/sparc/locore.s</strong>
1.12 grr 422: [shows the commit log for the chosen file ]
1.104 ericj 423: % <strong>cvs diff -bc -r1.1 -r1.5 src/sys/arch/sparc/sparc/locore.s</strong>
1.12 grr 424: [shows the changes between revisions 1.1 and rev 1.5]
1.104 ericj 425: </pre></ul>
1.1 deraadt 426:
427: <p>
1.18 todd 428: <a name=pserver>In order to use a cvs ``pserver'' (a direct tcp connection instead of using ssh or rsh) you must login once:</a>
1.104 ericj 429:
430: <ul><pre>
1.18 todd 431: [ *NOTE* You must be using cvs version 1.8 or higher to do this ]
1.104 ericj 432: % <strong>setenv CVSROOT :pserver:anoncvs@anoncvs.ca.openbsd.org:/cvs</strong>
433: % <strong>cvs login</strong>
1.59 beck 434: (Logging in to anoncvs@anoncvs1.ca.openbsd.org)
1.104 ericj 435: CVS password: <strong>anoncvs</strong>
1.18 todd 436: [this writes a line to ~/.cvspass (filename over-ridden by CVS_PASSFILE).]
437: [An example line from my ~/.cvspass after typing 'blah' for the above ]
438: [password is: ]
439: [:pserver:anoncvs@anoncvs5.usa.openbsd.org:/cvs Au'yc ]
440: [...after logging in ONCE every other use of the above CVSROOT will work ]
1.104 ericj 441: % <strong>cvs get ksrc-i386 ksrc-common</strong>
1.18 todd 442: [allows you to retrieve ONLY that necessary to rebuild an i386 kernel ]
1.104 ericj 443: </pre></ul>
1.18 todd 444:
445: <p>
1.39 todd 446: Here is how someone using anoncvs regularly would update his
1.1 deraadt 447: source tree:
1.60 millert 448: <ul><li>First, start out by `get'-ing an initial tree:
1.27 todd 449:
1.104 ericj 450: <ul><pre>
451: # <strong>setenv CVSROOT anoncvs@anoncvs.ca.openbsd.org:/cvs</strong>
452: # <strong>cd /usr</strong>
453: # <strong>cvs -q get -PA src</strong>
454: </pre></ul>
1.27 todd 455: </li>
1.37 todd 456:
1.27 todd 457: <li> Anytime afterwards, to `update' this tree:
1.104 ericj 458: <ul><pre>
459: # <strong>cd /usr/src</strong>
460: # <strong>cvs -q up -PAd</strong>
461: </pre></ul>
1.27 todd 462:
1.39 todd 463: Everytime you ran this it would synchronize your /usr/src tree. It would
1.1 deraadt 464: not destroy any of your local changes, rather it would attempt to merge
465: changes in. If you use obj directories (not obj symbolic links) you may
466: wish to append "-I obj" to the cvs command line, this will keep cvs from
467: spitting out a warning about all the obj directories it is going to
468: encounter which are not in the repository.
1.72 millert 469:
470: <p>
471: <li> NOTE: if you are updating a source tree that you initially fetched
472: from a different server, or from a CD, you <strong>must</strong>
473: add the <em>-d $CVSROOT</em> options to cvs. You must also set the
474: <em>CVS_IGNORE_REMOTE_ROOT</em> environment variable.
475:
1.104 ericj 476: <ul><pre>
477: # <strong>cd /usr/src</strong>
478: # <strong>cvs -d $CVSROOT -q up -PAd</strong>
479: </pre></ul>
1.72 millert 480:
1.27 todd 481: </li>
482: </ul>
483:
1.37 todd 484: <p>
485: To <a name=ports>use</a> <a href=ports.html>ports</a>, it is similar to src:
486: <ul><li>
487: <pre>
1.104 ericj 488: # <strong>setenv CVSROOT anoncvs@anoncvs.ca.openbsd.org:/cvs</strong>
489: # <strong>cd /usr</strong>
490: # <strong>cvs -q get -PA ports</strong>
1.38 deraadt 491: </pre>
1.37 todd 492: </li>
493: <li> Anytime afterwards, to `update' this tree:
494: <pre>
1.104 ericj 495: # <strong>cd /usr</strong>
496: # <strong>cvs -q up -PAd ports</strong>
1.37 todd 497: </pre>
498: </li>
499: </p>
500: </ul>
501:
1.104 ericj 502: In the above example, <i>-q</i> is optional, only intended to minimize
1.27 todd 503: cvs's output. For those who like to see screenfulls of output, it
504: can be omitted.
1.1 deraadt 505:
506: <p>
1.104 ericj 507: or to make a diff of a locally patched module (here <i>cd.c</i>) to include with
1.12 grr 508: a bug report:
1.104 ericj 509: <ul><pre>
510: # <strong>cd /usr</strong>
511: # <strong>cvs diff -u src/sys/scsi/cd.c > /tmp/patch</strong>
512: </pre></ul>
1.37 todd 513: </p>
1.12 grr 514:
515: <p>
1.104 ericj 516: The <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=cvs&sektion=1&format=html">CVS(1) man page</a>
517: (included with the CVS sources) has much more
1.1 deraadt 518: information about how CVS can be used.
519:
520: <p>
1.105 ericj 521: <strong>X11 Source tree</strong>
522: <br>
523: Anoncvs mirrors also carry the OpenBSD X11 source tree. You can adapt
524: the recipe above to update your X11 source tree from the second CD.
525: Either copy or use a union mount to get the X11 sources in <i>/usr/X11</i>:
526:
527: <ul>
528: <li>copy the tree off it (assuming the 2nd CD is mounted on /mnt):
529: <pre>
530: # <strong>cd /mnt; cp -Rp X11 /usr</strong>
531: </pre>
532: <li>use a union mount with the CD below a writable directory.
533: <pre>
534: # <strong>mount -t union -o -b /mnt/X11 /usr/X11</strong>
535: </pre></ul>
536:
537: After this, <i>/usr/X11</i> will be ready to be used by cvs. You can for
538: example update it to -current source (assuming you've already set
539: the <b>CVSROOT</b> environment variable):
540:
541: <ul><pre>
542: # <strong>cd /usr/X11</strong>
543: # <strong>cvs -q update -PAd</strong>
544: </pre></ul>
545:
546: <p>
1.12 grr 547: <strong>Warning:</strong>
548: When using cvs you should take care that your current directory is either
549: the root of the tree you're referencing or in a separate place such as /tmp.
550: Some commands such as "get" can create an arbitrary sub-tree in the current
551: directory, and a subsequent update will recursively flesh out this sub-tree.
552:
553: <p>
1.1 deraadt 554: The anoncvs service gives fledgling developers a chance to learn CVS
555: operation and get thoroughly involved in the development process
556: before getting "commit" access -- as a result of showing useful
557: skills and high quality results they will naturally later be given
558: developer access. As well, people providing patches can create
559: their "diff"s relative to the CVS tree, which will ease integration.
560:
1.104 ericj 561:
562: <a name="WHICH"></a>
563: <h3><font color=#0000e0>Use rsh(1) or ssh(1)?</font></h3>
564:
1.1 deraadt 565: <p>
1.15 grr 566: <strong>Anoncvs: rsh vs. ssh</strong>
1.12 grr 567: <br>
568: By default, the CVS client uses rsh to talk to the CVS server. Many
1.39 todd 569: of the CVS sites no longer support rsh for security reasons or a local
1.12 grr 570: problem like a firewall or imperfect protocol emulator such as slirp
571: may prevent you from using rsh.
1.97 deraadt 572: The alternative is a to use a "secure shell" connection using either
573: <a href=http://www.openssh.com>OpenSSH (*FREE*)</a> or
574: <a href=http://www.cs.hut.fi/ssh/>ssh (non-commercial and commercial)</a>.
1.68 wvdputte 575:
576: <p>
1.97 deraadt 577: The OpenBSD anoncvs repositries support the SSH1 protocol, not the SSH2
578: protocol due to the use of a "strict non-commercial use licensing policy".
1.28 beck 579:
1.75 millert 580: <p>
581: Once ssh is installed, one sets the environment variable
1.28 beck 582: <strong>CVS_RSH</strong> to point to ssh (typically
583: <strong>/usr/local/bin/ssh</strong>). If your local site prevents you
584: from connecting out to port 22 (which ssh defaults to using) use port
585: 2022.
1.1 deraadt 586:
587: <p>
588: Do not be tempted to turn on compression since CVS already compresses.
589: Use something like the following in your <strong>$HOME/.ssh/config</strong>
1.10 millert 590: file. Note that not all anoncvs servers allow ssh connections on
1.21 millert 591: port 2022. Also note that most anoncvs servers no longer accept
592: the <strong>none</strong> cipher as it is disabled in recent
593: versions of ssh for security reasons.
1.1 deraadt 594: <pre>
1.59 beck 595: Host anoncvs.ca.openbsd.org
1.1 deraadt 596: Port 2022
597: </pre>
598:
599: <p>
600: CVS is a little noisy starting up; to quiet it a bit you may want to
601: do this:
1.105 ericj 602:
603: <ul><pre>
604: <strong>setenv CVS_CLIENT_PORT -1</strong>
605: </pre></ul>
1.1 deraadt 606:
607: <p>
1.8 deraadt 608: If you wish to change from one CVS server to another (say your normal one is
609: down, or for any other reason), the environment variable which will let you
610: do this is
1.105 ericj 611:
612: <ul><pre>
613: <strong>setenv CVS_IGNORE_REMOTE_ROOT</strong>
614: </pre></ul>
615:
1.72 millert 616: Note that you will also need to use the <strong>-d</strong> flag
617: as mentioned above.
1.8 deraadt 618:
1.107 millert 619: <a name="SUP"></a>
620: <h3><font color=#0000e0>Mirroring the CVS repository via sup(1).</font></h3>
621:
622: <p>
623: Users wishing to mirror the OpenBSD CVS tree itself may now do so
624: from <em>anoncvs.usa.openbsd.org</em>. Note that this is the cvs
625: tree, <b>not</b> a checked out source tree. It is only useful if
626: you want to be able to do fast cvs operations (diff, annotate, etc)
627: or if you have multiple source trees and you only want to transfer
628: new data once (you can then checkout a tree from your local cvs
629: mirror).
630: <p>
631: A sample supfile would be:
632: <pre>
633: cvs host=anoncvs.usa.openbsd.org hostbase=/ base=/home delete
634: </pre>
635: <p>
636: which would mirror the cvs tree into /home/cvs with the sup data
637: files ending up in /home/sup. The full OpenBSD cvs tree is just
638: under a gigabyte in size.
1.65 matthieu 639:
1.105 ericj 640: <a name="MIRROR"></a>
641: <h3><font color=#0000e0>Setting up an anoncvs mirror.</font></h3>
642:
1.107 millert 643: <p>
1.1 deraadt 644: If you wish to be a new anoncvs mirror site, please contact the anoncvs
1.102 deraadt 645: <a href=mailto:sup@openbsd.org>maintainer</a>.
1.107 millert 646: Anoncvs mirrors require about 1GB of disk, and use up to 4MB of swap
1.1 deraadt 647: per anoncvs user (assuming the user does a large operation; while smaller
648: operations use fewer resources, anoncvs still makes much more of an
649: impact than ftp or sup). Such anoncvs machines should have excellent
650: network connectivity for the area they are expected to serve. A
651: <a href=anoncvs.shar>document</a>
652: which describes the setup of anoncvs servers is available.
653:
1.60 millert 654: <h3><font color=#0000e0>Final notes:</font></h3>
655: After upgrading your source tree, you should read the comments
656: at the top of <KBD>/usr/src/Makefile</KBD> before attemping
657: a build. Also, you should build a new kernel <strong>before</strong>
1.101 ericj 658: doing a <KBD>make build</KBD> if possible. In some cases it may be
1.60 millert 659: necessary to rebuild and install the <KBD>config</KBD> utility before
660: you can build the kernel. If <KBD>config GENERIC</KBD> fails this
661: is probably the case.
662: <p>
663: It is important to note that upgrading from a release to the current tree
664: by rebuilding the sources can be rather difficult due to dependencies
665: that are often not obvious. Therefore, it is suggested that you first
666: install the latest snapshot before attemping a tree build from source.
1.1 deraadt 667:
668: <hr>
1.58 pauls 669: <a href=index.html><img height=24 width=24 src=back.gif border=0 alt=OpenBSD></a>
1.1 deraadt 670: <a href=mailto:www@openbsd.org>www@openbsd.org</a>
1.108 ! ho 671: <br><small>$OpenBSD: anoncvs.html,v 1.107 2000/04/20 14:59:01 millert Exp $</small>
1.1 deraadt 672:
673: </body>
674: </html>
![[BACK]](/icons/back.gif){kind=icon}
Return to anoncvs.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www