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

Annotation of www/anoncvs.html, Revision 1.106

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