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