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