[BACK]Return to anoncvs.html CVS log [TXT][DIR] Up to [local] / www

Annotation of www/anoncvs.html, Revision 1.137

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">
                     10: <meta name="copyright" content="This document copyright 1996-1998 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.135     naddy      61:   <li><b>src</b> - Houses all source code for the OpenBSD Operating System.
                     62:   <li><b>ports</b> - Houses the <a href="./ports.html">OpenBSD Ports</a>.
                     63:   <li><b>www</b> - Houses all OpenBSD web pages. (Including this one).
                     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.135     naddy     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&amp;apropos=0&amp;sektion=8&amp;manpath=OpenBSD+Current&amp;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.135     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&amp;sektion=1&amp;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&amp;sektion=1&amp;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.
                    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>.
                    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.10      millert   229: located in California, western USA.<br>
1.135     naddy     230: maintained by <a href="mailto:millert@openbsd.org">Todd Miller</a>.<br>
1.83      millert   231: protocols: pserver only.<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.135     naddy     237: maintained by <a href="mailto:Todd.Miller@cs.colorado.edu">Todd Miller</a>.<br>
1.94      millert   238: protocols: rsh, ssh, ssh port 2022, pserver.<br>
1.1       deraadt   239: updated every 6 hours.<br>
                    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.118     beck      309: <li><strong>CVSROOT=anoncvs@anoncvs.calyx.nl:/cvs</strong><br>
                    310: located in Amsterdam, The Netherlands.<br>
1.127     jufi      311: maintained by <a href="mailto:nick@calyx.net">Nick Merrill</a>.<br>
1.118     beck      312: protocols: ssh.<br>
                    313: updated every 3 hours.<br>
                    314: <p>
1.69      deraadt   315: <li><strong>CVSROOT=anoncvs@anoncvs.jp.openbsd.org:/cvs</strong><br>
                    316: Host also known as <strong>kankoromochi.econ.nagasaki-u.ac.jp</strong>.<br>
                    317: located at Nagasaki Univ. Faculty of Economics, JAPAN.<br>
1.135     naddy     318: maintained by <a href="mailto:sigh@net.nagasaki-u.ac.jp">SUZUKI Hitoshi</a>.<br>
1.79      deraadt   319: protocols: ssh, pserver.<br>
                    320: updated every 3 hours.<br>
1.121     deraadt   321: <p>
1.73      deraadt   322: <li><strong>CVSROOT=anoncvs@anoncvs.cz.openbsd.org:/cvs</strong><br>
                    323: Host also known as <strong>com-os2.ms.mff.cuni.cz</strong>.<br>
1.98      rohee     324: located at Faculty Math &amp; Physics, Charles University, Prague, Czech republic.<br>
1.135     naddy     325: maintained by <a href="mailto:galambos@com-os2.ms.mff.cuni.cz">Leo Galambos</a>.<br>
1.73      deraadt   326: protocols: ssh, ssh port 2022.<br>
                    327: updated every 3 hours.<br>
1.121     deraadt   328: <p>
1.84      beck      329: <li><strong>CVSROOT=anoncvs@anoncvs1.au.openbsd.org:/cvs</strong><br>
                    330: Host also known as <strong>anoncvs.au.openbsd.org</strong>,
                    331: <strong>anoncvs.openbsd.aba.net.au</strong><br>
                    332: located in Carlton, Victoria, Australia.<br>
                    333: maintained by <A HREF="mailto:mwp@aba.net.au">Micheal Paddon</A><br>
                    334: protocols: ssh<br>
                    335: updated every 4 hours.<br>
1.121     deraadt   336: <p>
1.88      beck      337: <li><strong>CVSROOT=anoncvs@dolphin.mtmc.ru:/cvs</strong><br>
                    338: located in Moscow, Russia<br>
                    339: maintained by <A HREF="mailto:jc@mtmc.ru">John Chertihin</A><br>
                    340: protocols: rsh, ssh<br>
1.135     naddy     341: updated every 24 hours (at 1 AM Moscow time).<br>
1.121     deraadt   342: <p>
1.103     beck      343: <li><strong>CVSROOT :pserver:anoncvs@cvs.bsdfr.org:/cvs</strong><br>
                    344: located at in France<br>
1.135     naddy     345: maintained by: <a href="mailto:jch@oleane.net">Jean-Claude Christophe</a><br>
1.103     beck      346: protocols: pserver<br>
                    347: updated every 24h <br>
1.121     deraadt   348: <p>
1.115     beck      349: <li><strong>CVSROOT=anoncvs@grappa.unix-ag.uni-kl.de:/cvs</strong><br>
                    350: located at the University of Kaiserslautern, Germany<br>
1.135     naddy     351: maintained by <A HREF="mailto:hgw@d1906.inka.de">Hans G&uuml;nter Weigand</A>
                    352: and <A HREF="mailto:naddy@openbsd.org">Christian Weisgerber</A><br>
1.115     beck      353: protocols: rsh, ssh, ssh port 2022, pserver<br>
1.135     naddy     354: updated every 6 hours from cvsup.uk.openbsd.org.<br>
1.121     deraadt   355: <p>
1.80      beck      356: <li><strong>CVSROOT=anoncvs@exokernel.lcs.mit.edu:/cvs</strong><br>
                    357: located at M.I.T, Eastern USA.<br>
                    358: maintained by ????<br>
                    359: protocols: ssh, ???<br>
                    360: updated every ? hours.<br>
1.121     deraadt   361: <p>
1.108     ho        362: <li><strong>CVSROOT=anoncvs@xyzzy.gsnig.org:/cvs</strong><br>
                    363: Located in G&ouml;teborg, Sweden<br>
1.80      beck      364: maintained by martin@openbsd.org<br>
1.108     ho        365: protocols: ssh port 2022<br>
                    366: updated every 4 hours.<br>
1.121     deraadt   367: <p>
1.80      beck      368: <li><strong>CVSROOT=anoncvs@stl-isaas.ey.com:/cvs</strong><br>
1.90      beck      369: Located in St. Louis, MO, Eastern USA<br>
1.81      beck      370: maintained by <A HREF="mailto:aaron11@sprynet.com">Aaron Miller</A><br>
                    371: protocols: ssh, ssh port 2022, pserver<br>
                    372: updated every 3 hours.<br>
1.121     deraadt   373: <p>
1.91      beck      374: <li><strong>CVSROOT=anoncvs@openbsd.groupbsd.org:/cvs</strong><br>
1.92      jason     375: Located in Hillsborough NC, Eastern USA<br>
                    376: maintained by <A HREF="mailto:jason@openbsd.org">Jason Wright</A><br>
1.91      beck      377: protocols: ssh<br>
                    378: updated every 4 hours.<br>
1.121     deraadt   379: <p>
1.120     beck      380: <li><strong>CVSROOT=anoncvs@anoncvs.mx.openbsd.org:/cvs</strong><br>
                    381: Located at Campus Iztacala, Universidad Autonoma de Mexico<br>
                    382: maintained by <A HREF="mailto:alex@iztacala.unam.mx">Alejandro Juarez</A><br>
                    383: protocols: ssh<br>
                    384: updated every 3 hours.<br>
1.121     deraadt   385: <p>
1.128     beck      386: <li><strong>CVSROOT=anoncvs@anoncvs.pl.openbsd.org:/cvs</strong><br>
                    387: Host also known as <strong>anoncvs1.pl.openbsd.org</strong>,
                    388: <strong>incredible.bmtmc.gda.pl</strong><br>
1.126     beck      389: Located at BMT Maritime Consultants, Gdansk, Poland<br>
1.122     beck      390: maintained by <A HREF="mailto:detergent@incredible.bmtmc.gda.pl">
                    391: Adam Naguszewski</A><br>
1.128     beck      392: protocols: ssh, pserver<br>
1.122     beck      393: updated every 3 hours.<br>
                    394: <p>
1.123     beck      395: <li><strong>CVSROOT=anoncvs@rt.fm:/cvs</strong><br>
1.136     miod      396: Located in Lake in the Hills, Illinois, USA<br>
1.123     beck      397: maintained by <A HREF="mailto:jcs@rt.fm">
                    398: Joshua Stein</A><br>
                    399: protocols: ssh<br>
1.124     beck      400: updated every 3 hours.<br>
1.131     beck      401: <P>
                    402: <li><strong>CVSROOT=anoncvs@shellhung.org:/cvs</strong><br>
                    403: Located in Hong Kong, China<br>
                    404: maintained by <A HREF="mailto:shell@shellhung.org">
                    405: Shell Hung</A><br>
                    406: protocols: pserver, ssh<br>
                    407: updated every 3 hours.<br>
1.123     beck      408: <p>
1.137   ! beck      409: <li><strong>CVSROOT=anoncvs@anoncvs.openbsd.ar:/cvs</strong><br>
        !           410: Located in Buenos Aires, Argentina<br>
        !           411: maintained by <A HREF="fgsch@openbsd.org">
        !           412: Alejo Sanchez, Caludio Castiglia, and Federico Schwindt</A><br>
        !           413: protocols: ssh<br>
        !           414: updated every 3 hours.<br>
        !           415: <p>
1.73      deraadt   416: </ul>
1.84      beck      417:
                    418:
1.73      deraadt   419: <p>
1.135     naddy     420: <em>Note:</em> If your server is listed on here with inaccurate or
1.104     ericj     421: unknown information, please contact
1.135     naddy     422: <a href="mailto:beck@openbsd.org"><tt>beck@openbsd.org</tt></a>
1.104     ericj     423: </p>
                    424:
1.80      beck      425: <p>
1.104     ericj     426: You may want to use
1.135     naddy     427: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=traceroute&amp;sektion=8&amp;format=html">traceroute(8)</a>
1.104     ericj     428: to find out which server is nearest you.
1.11      michaels  429: Problems with a server should be reported to the <b>maintainer</b> of the
                    430: server in question.
1.135     naddy     431: </dl>
1.104     ericj     432:
1.135     naddy     433: <h3><a name="CRYPTO"><font color="#0000e0">Getting crypto sources through cvs(1)</font></a></h3>
1.104     ericj     434:
1.1       deraadt   435: <p>
                    436: <strong>IMPORTANT NOTE:</strong>
                    437: There are a few issues relating to cryptographic software that everyone
                    438: should be aware of:
                    439: <ul>
                    440: <li>The OpenBSD sources are from Canada.
1.9       deraadt   441: As
1.135     naddy     442:        <a href="http://insight.mcmaster.ca/org/efc/pages/doc/crypto-export.html">
1.9       deraadt   443:        researched by a Canadian individual</a>
                    444: and as
1.135     naddy     445:        <a href="http://axion.physics.ubc.ca/ECL.html">
1.9       deraadt   446:        described in the Export Control list of Canada</a>
                    447: is legal to export crypto software from Canada to the world.
1.1       deraadt   448: <p>
                    449: <li>However, if you are outside the USA or Canada, you should not
                    450: fetch the cryptographic sections of the OpenBSD sources from an
                    451: anoncvs server located in the USA. The files in question are...
                    452: <ul>
                    453: <li>src/kerberosIV/*
1.57      art       454: <li>src/lib/libdes/*
1.1       deraadt   455: <li>src/lib/libc/crypt/crypt.c
                    456: <li>src/lib/libc/crypt/morecrypt.c
1.36      deraadt   457: <li>src/sys/netinet
1.67      art       458: <li>src/usr.sbin/afs/src/rxkad/*
1.56      matthieu  459: <li>X11/xc/lib/Xdmcp/Wraphelp.c
1.1       deraadt   460: </ul>
                    461: Because of the USA ITAR munitions list,
                    462: crypto software may only be exported to Canada from the USA.
                    463: <p>
                    464: <li>The OpenBSD project is looking for more anoncvs servers -- read
                    465: on to find out how you can help.
                    466: </ul>
                    467:
1.135     naddy     468: <h3><a name="EXAMPLE"><font color="#0000e0">Example usages for cvs(1)</font></a></h3>
1.104     ericj     469:
1.1       deraadt   470: <p>
1.135     naddy     471: A sample use of an anoncvs server would be:
                    472: <pre>
1.104     ericj     473: % <strong>setenv CVSROOT anoncvs@anoncvs.ca.openbsd.org:/cvs</strong>
                    474: % <strong>cd /tmp</strong>
                    475: % <strong>cvs get src/sys/arch/sparc</strong>
1.12      grr       476:     [copies the files from the repository to your machine]
1.104     ericj     477: % <strong>cvs log src/sys/arch/sparc/sparc/locore.s</strong>
1.135     naddy     478:     [shows the commit log for the chosen file]
1.104     ericj     479: % <strong>cvs diff -bc -r1.1 -r1.5 src/sys/arch/sparc/sparc/locore.s</strong>
1.12      grr       480:     [shows the changes between revisions 1.1 and rev 1.5]
1.135     naddy     481: </pre>
1.1       deraadt   482:
                    483: <p>
1.135     naddy     484: <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     485:
1.135     naddy     486: <pre>
1.104     ericj     487: % <strong>setenv CVSROOT :pserver:anoncvs@anoncvs.ca.openbsd.org:/cvs</strong>
                    488: % <strong>cvs login</strong>
1.59      beck      489: (Logging in to anoncvs@anoncvs1.ca.openbsd.org)
1.104     ericj     490: CVS password: <strong>anoncvs</strong>
1.135     naddy     491:     [This writes a line to ~/.cvspass (filename over-ridden by CVS_PASSFILE).]
1.18      todd      492:     [An example line from my ~/.cvspass after typing 'blah' for the above    ]
                    493:     [password is:                                                            ]
                    494:     [:pserver:anoncvs@anoncvs5.usa.openbsd.org:/cvs Au'yc                    ]
1.135     naddy     495:     [After logging in ONCE every other use of the above CVSROOT will work.   ]
1.104     ericj     496: % <strong>cvs get ksrc-i386 ksrc-common</strong>
1.135     naddy     497:     [Allows you to retrieve ONLY that necessary to rebuild an i386 kernel.   ]
                    498: </pre>
1.18      todd      499:
                    500: <p>
1.39      todd      501: Here is how someone using anoncvs regularly would update his
1.1       deraadt   502: source tree:
1.60      millert   503: <ul><li>First, start out by `get'-ing an initial tree:
1.27      todd      504:
1.109     jason     505: <p> (If you are following <i>current</i>):
1.135     naddy     506: <pre>
                    507:        # <strong>setenv CVSROOT anoncvs@anoncvs.ca.openbsd.org:/cvs</strong>
                    508:        # <strong>cd /usr</strong>
                    509:        # <strong>cvs -q get -PA src</strong>
                    510: </pre>
1.109     jason     511:
1.129     millert   512: <p> (If you are following the patch branch for 2.8):
1.135     naddy     513: <pre>
                    514:        # <strong>setenv CVSROOT anoncvs@anoncvs.ca.openbsd.org:/cvs</strong>
                    515:        # <strong>cd /usr</strong>
                    516:        # <strong>cvs -q get -rOPENBSD_2_8 -P src</strong>
                    517: </pre>
1.27      todd      518: </li>
1.37      todd      519:
1.27      todd      520: <li> Anytime afterwards, to `update' this tree:
1.109     jason     521: <p> (If you are following <i>current</i>):
1.135     naddy     522: <pre>
                    523:        # <strong>cd /usr/src</strong>
                    524:        # <strong>cvs -q up -PAd</strong>
                    525: </pre>
1.27      todd      526:
1.129     millert   527: <p> (If you are following the patch branch for 2.8):
1.135     naddy     528: <pre>
                    529:        # <strong>cd /usr/src</strong>
                    530:        # <strong>cvs -q up -rOPENBSD_2_8 -Pd</strong>
                    531: </pre>
1.109     jason     532:
1.39      todd      533: Everytime you ran this it would synchronize your /usr/src tree. It would
1.1       deraadt   534: not destroy any of your local changes, rather it would attempt to merge
                    535: changes in. If you use obj directories (not obj symbolic links) you may
                    536: wish to append "-I obj" to the cvs command line, this will keep cvs from
                    537: spitting out a warning about all the obj directories it is going to
                    538: encounter which are not in the repository.
1.72      millert   539:
                    540: <p>
1.109     jason     541: <li> NOTES: if you are updating a source tree that you initially fetched
1.72      millert   542: from a different server, or from a CD, you <strong>must</strong>
                    543: add the <em>-d $CVSROOT</em> options to cvs.  You must also set the
1.109     jason     544: <em>CVS_IGNORE_REMOTE_ROOT</em> environment variable.  If you are following
                    545: a patch branch, be sure to always <strong>omit</strong> the <code>-A</code>
                    546: flag to cvs, or you may find yourself tracking <i>current</i> instead.
1.72      millert   547:
1.109     jason     548: <p> (If you are following <i>current</i>):
1.135     naddy     549: <pre>
                    550:        # <strong>cd /usr/src</strong>
                    551:        # <strong>cvs -d $CVSROOT -q up -PAd</strong>
                    552: </pre>
1.72      millert   553:
1.109     jason     554: <p> (If you are following a patch branch):
1.135     naddy     555: <pre>
                    556:        # <strong>cd /usr/src</strong>
                    557:        # <strong>cvs -d $CVSROOT -q up -Pd</strong>
                    558: </pre>
1.109     jason     559:
1.27      todd      560: </li>
                    561: </ul>
                    562:
1.37      todd      563: <p>
1.135     naddy     564: To <a name="ports">use</a> <a href="ports.html">ports</a>, it is similar to src:
1.37      todd      565: <ul><li>
                    566: <pre>
1.135     naddy     567:        # <strong>setenv CVSROOT anoncvs@anoncvs.ca.openbsd.org:/cvs</strong>
                    568:        # <strong>cd /usr</strong>
                    569:        # <strong>cvs -q get -PA ports</strong>
1.38      deraadt   570: </pre>
1.37      todd      571: </li>
                    572: <li> Anytime afterwards, to `update' this tree:
                    573: <pre>
1.135     naddy     574:        # <strong>cd /usr</strong>
                    575:        # <strong>cvs -q up -PAd ports</strong>
1.37      todd      576: </pre>
                    577: </li>
1.127     jufi      578: </ul>
1.37      todd      579:
1.104     ericj     580: In the above example, <i>-q</i> is optional, only intended to minimize
1.27      todd      581: cvs's output.  For those who like to see screenfulls of output, it
                    582: can be omitted.
1.1       deraadt   583:
                    584: <p>
1.104     ericj     585: or to make a diff of a locally patched module (here <i>cd.c</i>) to include with
1.12      grr       586: a bug report:
1.135     naddy     587: <pre>
                    588:        # <strong>cd /usr</strong>
                    589:        # <strong>cvs diff -u src/sys/scsi/cd.c &gt; /tmp/patch</strong>
                    590: </pre>
1.12      grr       591:
                    592: <p>
1.135     naddy     593: The <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=cvs&amp;sektion=1&amp;format=html">cvs(1) man page</a>
1.104     ericj     594: (included with the CVS sources) has much more
1.1       deraadt   595: information about how CVS can be used.
                    596:
1.135     naddy     597: <h4>X11 Source tree</h4>
                    598:
1.1       deraadt   599: <p>
1.105     ericj     600: Anoncvs mirrors also carry the OpenBSD X11 source tree. You can adapt
                    601: the recipe above to update your X11 source tree from the second CD.
                    602: Either copy or use a union mount to get the X11 sources in <i>/usr/X11</i>:
                    603:
                    604: <ul>
                    605: <li>copy the tree off it (assuming the 2nd CD is mounted on /mnt):
                    606: <pre>
                    607:         # <strong>cd /mnt; cp -Rp X11 /usr</strong>
                    608: </pre>
                    609: <li>use a union mount with the CD below a writable directory.
                    610: <pre>
                    611:         # <strong>mount -t union -o -b /mnt/X11 /usr/X11</strong>
1.135     naddy     612: </pre>
                    613: </ul>
1.105     ericj     614:
                    615: After this, <i>/usr/X11</i> will be ready to be used by cvs. You can for
                    616: example update it to -current source (assuming you've already set
                    617: the <b>CVSROOT</b> environment variable):
                    618:
1.135     naddy     619: <pre>
1.105     ericj     620:         # <strong>cd /usr/X11</strong>
                    621:         # <strong>cvs -q update -PAd</strong>
1.135     naddy     622: </pre>
1.105     ericj     623:
                    624: <p>
1.12      grr       625: <strong>Warning:</strong>
                    626: When using cvs you should take care that your current directory is either
1.109     jason     627: the root of the tree you are referencing or in a separate place such as /tmp.
1.12      grr       628: Some commands such as "get" can create an arbitrary sub-tree in the current
                    629: directory, and a subsequent update will recursively flesh out this sub-tree.
                    630:
                    631: <p>
1.1       deraadt   632: The anoncvs service gives fledgling developers a chance to learn CVS
                    633: operation and get thoroughly involved in the development process
                    634: before getting "commit" access -- as a result of showing useful
                    635: skills and high quality results they will naturally later be given
                    636: developer access.  As well, people providing patches can create
                    637: their "diff"s relative to the CVS tree, which will ease integration.
                    638:
1.104     ericj     639:
1.135     naddy     640: <h3><a name="WHICH"><font color="#0000e0">Use rsh(1) or ssh(1)?</font></a></h3>
1.104     ericj     641:
1.1       deraadt   642: <p>
1.15      grr       643: <strong>Anoncvs: rsh vs. ssh</strong>
1.12      grr       644: <br>
                    645: By default, the CVS client uses rsh to talk to the CVS server.  Many
1.39      todd      646: of the CVS sites no longer support rsh for security reasons or a local
1.12      grr       647: problem like a firewall or imperfect protocol emulator such as slirp
                    648: may prevent you from using rsh.
1.135     naddy     649: The alternative is a to use a "secure shell" connection using
                    650: <a href="http://www.openssh.com">OpenSSH</a>.
1.28      beck      651:
1.75      millert   652: <p>
                    653: Once ssh is installed, one sets the environment variable
1.135     naddy     654: <var>CVS_RSH</var> to point to ssh (typically
1.113     brad      655: <strong>/usr/bin/ssh</strong>).  If your local site prevents you
1.28      beck      656: from connecting out to port 22 (which ssh defaults to using) use port
                    657: 2022.
1.1       deraadt   658:
                    659: <p>
                    660: Do not be tempted to turn on compression since CVS already compresses.
                    661: Use something like the following in your <strong>$HOME/.ssh/config</strong>
1.10      millert   662: file.  Note that not all anoncvs servers allow ssh connections on
1.21      millert   663: port 2022.  Also note that most anoncvs servers no longer accept
                    664: the <strong>none</strong> cipher as it is disabled in recent
                    665: versions of ssh for security reasons.
1.1       deraadt   666: <pre>
1.59      beck      667:        Host anoncvs.ca.openbsd.org
1.1       deraadt   668:            Port 2022
                    669: </pre>
                    670:
                    671: <p>
                    672: CVS is a little noisy starting up; to quiet it a bit you may want to
                    673: do this:
1.105     ericj     674:
1.135     naddy     675: <pre>
                    676:        <strong>% setenv CVS_CLIENT_PORT -1</strong>
                    677: </pre>
1.1       deraadt   678:
                    679: <p>
1.8       deraadt   680: If you wish to change from one CVS server to another (say your normal one is
                    681: down, or for any other reason), the environment variable which will let you
                    682: do this is
1.105     ericj     683:
1.135     naddy     684: <pre>
                    685:        <strong>% setenv CVS_IGNORE_REMOTE_ROOT</strong>
                    686: </pre>
1.105     ericj     687:
1.135     naddy     688: <p>
1.72      millert   689: Note that you will also need to use the <strong>-d</strong> flag
                    690: as mentioned above.
1.8       deraadt   691:
1.135     naddy     692: <h3><a name="SUP"><font color="#0000e0">Mirroring the CVS repository via sup(1)</font></a></h3>
1.107     millert   693:
                    694: <p>
                    695: Users wishing to mirror the OpenBSD CVS tree itself may now do so
                    696: from <em>anoncvs.usa.openbsd.org</em>.  Note that this is the cvs
                    697: tree, <b>not</b> a checked out source tree.  It is only useful if
                    698: you want to be able to do fast cvs operations (diff, annotate, etc)
                    699: or if you have multiple source trees and you only want to transfer
                    700: new data once (you can then checkout a tree from your local cvs
                    701: mirror).
                    702: <p>
                    703: A sample supfile would be:
                    704: <pre>
                    705:        cvs host=anoncvs.usa.openbsd.org hostbase=/ base=/home delete
                    706: </pre>
                    707: <p>
                    708: which would mirror the cvs tree into /home/cvs with the sup data
1.133     millert   709: files ending up in /home/sup.  The full OpenBSD cvs tree is currently
                    710: about 1.3 gigabytes in size.
1.65      matthieu  711:
1.135     naddy     712: <h3><a name="MIRROR"><font color="#0000e0">Setting up an anoncvs mirror</font></a></h3>
1.105     ericj     713:
1.107     millert   714: <p>
1.1       deraadt   715: If you wish to be a new anoncvs mirror site, please contact the anoncvs
1.135     naddy     716: <a href="mailto:sup@openbsd.org">maintainer</a>.
1.134     millert   717: Anoncvs mirrors require about 1.2GB of disk, and use up to 32MB of swap
1.1       deraadt   718: per anoncvs user (assuming the user does a large operation; while smaller
                    719: operations use fewer resources, anoncvs still makes much more of an
                    720: impact than ftp or sup).  Such anoncvs machines should have excellent
                    721: network connectivity for the area they are expected to serve.  A
1.135     naddy     722: <a href="anoncvs.shar">document</a>
1.1       deraadt   723: which describes the setup of anoncvs servers is available.
                    724:
1.135     naddy     725: <h3><font color="#0000e0">Final notes</font></h3>
1.60      millert   726: After upgrading your source tree, you should read the comments
                    727: at the top of <KBD>/usr/src/Makefile</KBD> before attemping
                    728: a build.  Also, you should build a new kernel <strong>before</strong>
1.101     ericj     729: doing a <KBD>make build</KBD> if possible.  In some cases it may be
1.60      millert   730: necessary to rebuild and install the <KBD>config</KBD> utility before
                    731: you can build the kernel.  If <KBD>config GENERIC</KBD> fails this
                    732: is probably the case.
                    733: <p>
                    734: It is important to note that upgrading from a release to the current tree
                    735: by rebuilding the sources can be rather difficult due to dependencies
                    736: that are often not obvious.  Therefore, it is suggested that you first
                    737: install the latest snapshot before attemping a tree build from source.
1.1       deraadt   738:
                    739: <hr>
1.135     naddy     740: <a href="index.html"><img height="24" width="24" src="back.gif" border="0" alt="OpenBSD"></a>
                    741: <a href="mailto:www@openbsd.org">www@openbsd.org</a>
1.137   ! beck      742: <br><small>$OpenBSD: anoncvs.html,v 1.136 2001/02/22 23:21:53 miod Exp $</small>
1.1       deraadt   743:
                    744: </body>
                    745: </html>