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

Annotation of www/anoncvs.html, Revision 1.11

1.1       deraadt     1: <!DOCTYPE HTML PUBLIC  "-//IETF//DTD HTML Strict//EN">
                      2: <html>
                      3: <head>
1.2       deraadt     4: <title>OpenBSD AnonCVS</title>
1.1       deraadt     5: <link rev=made href=mailto:www@openbsd.org>
                      6: <meta name="resource-type" content="document">
                      7: <meta name="description" content="the main OpenBSD page">
                      8: <meta name="keywords" content="openbsd,main">
                      9: <meta name="distribution" content="global">
                     10: <meta name="copyright" content="This document copyright 1996 by OpenBSD, Inc.">
                     11: </head>
                     12:
                     13: <body>
                     14:
                     15: <h1>OpenBSD</h1>
1.6       jkatz      16: <hr>
1.1       deraadt    17: <h3>CVS Access:</h3>
                     18: CVS is used to manage the OpenBSD source tree. This allows
                     19: developers to work on a local source tree and commit their changes when
                     20: ready.  Also <strong>anyone</strong> can edit source files on their
                     21: local machines, and automatically track and merge in any changes made
                     22: in the OpenBSD CVS repository. Additionally they can easily see the
                     23: logs of, check out, or "diff" the source files in the OpenBSD source
                     24: tree.
                     25: </p>
                     26:
                     27: <p>
                     28: Most importantly, the <strong>anoncvs</strong> service does NOT
                     29: delete the changes you make in your local copy of the source tree --
                     30: read on for more details!
                     31: </p>
                     32:
                     33: <p>
                     34: The latest version of CVS is available at
                     35: <a href=ftp://ftp.cyclic.com/pub/cvs/>Cyclic</a>.
                     36: Versions earlier than 1.6 are not recommended, and may not work.
                     37: If you already have OpenBSD installed, CVS is included.
                     38: </p>
                     39:
                     40: <p>
                     41: There are two levels of source tree access:
                     42: </p>
                     43:
                     44: <dl>
                     45: <dt><strong>Read-write access for developers:</strong>
                     46: <dd>Developers who need to commit changes to the source tree must have
                     47: an account on the OpenBSD machines.  Getting this access will be a
                     48: natural result of working on the sources with other OpenBSD developers.
                     49: If someone does some good work and shows they can work with the team,
                     50: they will get an account.
                     51: </dl>
                     52:
                     53: <dl>
                     54: <dt><strong>Read-only access for everyone:</strong>
                     55: <dd>Anyone can access the read-only CVS repositories. These copies
                     56: of the read-write CVS repository are mirrored often. To use one,
                     57: set your <strong>CVSROOT</strong> environment variable to one of
                     58: the following values:
                     59: <ul>
                     60: <p>
                     61: <li><strong>CVSROOT=anoncvs@anoncvs.usa.openbsd.org:/cvs</strong><br>
1.10      millert    62: Host also known as <strong>anoncvs.openbsd.org</strong>,
                     63: <strong>anoncvs@anoncvs1.usa.openbsd.org</strong>,
                     64: <strong>anoncvs@anoncvs4.usa.openbsd.org</strong> and
                     65: <strong>anoncvs2.isc.org</strong>.<br>
                     66: located in California, western USA.<br>
                     67: maintained by <a href=mailto:niklas@openbsd.org>Niklas Hallqvist</a>.<br>
                     68: protocols: ssh only.<br>
1.1       deraadt    69: updated every 4 hours.<br>
                     70: <p>
                     71: <li><strong>CVSROOT=anoncvs@anoncvs2.usa.openbsd.org:/cvs</strong><br>
1.5       johns      72: Host also known as <strong>hydra.heuris.com</strong>.<br>
1.4       deraadt    73: located in St. Louis, Missouri, mid-western USA.<br>
1.1       deraadt    74: maintained by <a href=mailto:johns@heuris.com>John Stone</a>.<br>
                     75: protocols: rsh, ssh, ssh port 2022.<br>
                     76: updated every 12 hours.<br>
                     77: <p>
                     78: <li><strong>CVSROOT=anoncvs@anoncvs3.usa.openbsd.org:/cvs</strong><br>
                     79: Host also known as <strong>freestuff.cs.colorado.edu</strong>.<br>
                     80: located at the University of Colorado, Boulder, western USA.<br>
                     81: maintained by <a href=mailto:Todd.Miller@cs.colorado.edu>Todd Miller</a>.<br>
                     82: protocols: ssh, ssh port 2022.<br>
                     83: updated every 6 hours.<br>
                     84: <p>
                     85: <li><strong>CVSROOT=anoncvs@anoncvs.uk.openbsd.org:/cvs</strong><br>
                     86: Host also known as <strong>dumpty.wonderland.org</strong>.<br>
                     87: located in London, UK.<br>
                     88: maintained by <a href=mailto:peter@wonderland.org>Peter Galbavy</a>.<br>
                     89: protocols: rsh.<br>
                     90: updated every 12 hours.<br>
                     91: <p>
                     92: <li><strong>CVSROOT=anoncvs@anoncvs.tw.openbsd.org:/cvs</strong><br>
                     93: Host also known as <strong>hercules.secc.fju.edu.tw</strong>.<br>
                     94: located in Taipei, Taiwan.<br>
                     95: maintained by <a href=mailto:shawn@openbsd.org>Shawn Hsiao</a>.<br>
                     96: protocols: rsh, ssh, ssh port 2022.<br>
                     97: updated every 12 hours.<br>
                     98: <p>
                     99: <li><strong>CVSROOT=anoncvs@anoncvs.no.openbsd.org:/cvs</strong><br>
                    100: located in Norway.<br>
                    101: maintained by <a href=mailto:micheals@openbsd.org>Michael Shuldman</a>.<br>
                    102: protocols: rsh, ssh, ssh port 2022.<br>
                    103: updated every 4 hours.<br>
                    104: </ul>
                    105: <p>
                    106: You may want to use `traceroute' to find out which server is nearest you.
1.11    ! michaels  107: Problems with a server should be reported to the <b>maintainer</b> of the
        !           108: server in question.
1.1       deraadt   109: </dl>
                    110: </p>
                    111: <p>
                    112: <strong>IMPORTANT NOTE:</strong>
                    113: There are a few issues relating to cryptographic software that everyone
                    114: should be aware of:
                    115: <ul>
                    116: <li>The OpenBSD sources are from Canada.
1.9       deraadt   117: As
                    118:        <a href=http://insight.mcmaster.ca/org/efc/pages/doc/crypto-export.html>
                    119:        researched by a Canadian individual</a>
                    120: and as
                    121:        <a href=http://axion.physics.ubc.ca/ECL.html>
                    122:        described in the Export Control list of Canada</a>
                    123: is legal to export crypto software from Canada to the world.
1.1       deraadt   124: <p>
                    125: <li>However, if you are outside the USA or Canada, you should not
                    126: fetch the cryptographic sections of the OpenBSD sources from an
                    127: anoncvs server located in the USA. The files in question are...
                    128: <ul>
                    129: <li>src/kerberosIV/*
                    130: <li>src/lib/libc/crypt/crypt.c
                    131: <li>src/lib/libc/crypt/morecrypt.c
                    132: </ul>
                    133: Because of the USA ITAR munitions list,
                    134: crypto software may only be exported to Canada from the USA.
                    135: <p>
                    136: <li>The OpenBSD project is looking for more anoncvs servers -- read
                    137: on to find out how you can help.
                    138: </ul>
                    139: </p>
                    140:
                    141: <p>
                    142: A sample use of an anoncvs CVS server would be:
                    143: <pre>
                    144: % setenv CVSROOT anoncvs@anoncvs.usa.openbsd.org:/cvs
                    145: % cd /tmp
                    146: % cvs get src/sys/arch/sparc
                    147: [copies the files from the repository to your machine]
                    148: % cvs log src/sys/arch/sparc/sparc/locore.s
                    149: [shows the commit log for the chosen file ]
                    150: % cvs diff -bc -r1.1 -r1.5 src/sys/arch/sparc/sparc/locore.s
                    151: [shows the changes between revisions 1.1 and rev 1.5]
                    152: </pre>
                    153: </p>
                    154:
                    155: <p>
                    156: Here is how someone using anoncvs regularily would update his
                    157: source tree:
                    158: <pre>
                    159: # setenv CVSROOT anoncvs@anoncvs.usa.openbsd.org:/cvs
                    160: # cd /usr
                    161: # cvs -q get -PA src
                    162: </pre>
                    163: or similarily later on he might try
                    164: <pre>
                    165: # cd /usr/src
                    166: # cvs -q up -PAd
                    167: </pre>
                    168: Everytime you ran this it would syncronize your /usr/src tree. It would
                    169: not destroy any of your local changes, rather it would attempt to merge
                    170: changes in. If you use obj directories (not obj symbolic links) you may
                    171: wish to append "-I obj" to the cvs command line, this will keep cvs from
                    172: spitting out a warning about all the obj directories it is going to
                    173: encounter which are not in the repository.
                    174: </p>
                    175:
                    176: <p>
                    177: The CVS man page (included with the CVS sources) has much more
                    178: information about how CVS can be used.
                    179: </p>
                    180:
                    181: <p>
                    182: The anoncvs service gives fledgling developers a chance to learn CVS
                    183: operation and get thoroughly involved in the development process
                    184: before getting "commit" access -- as a result of showing useful
                    185: skills and high quality results they will naturally later be given
                    186: developer access.  As well, people providing patches can create
                    187: their "diff"s relative to the CVS tree, which will ease integration.
                    188: </p>
                    189:
                    190: <p>
                    191: The CVS client uses rsh to talk to the CVS server.  If some local
                    192: security measure like a firewall (or imperfect protocol emulators
                    193: like slirp) prevents you from using rsh, you may be able to use
                    194: <a href=http://www.cs.hut.fi/ssh>ssh</a> instead.  In this case,
                    195: one sets the environment variable <strong>CVS_RSH</strong> to point
                    196: to ssh (typically <strong>/usr/local/bin/ssh</strong>). To reduce the
                    197: performance hit the anoncvs server would take it is recommended (and
                    198: requested) that you disable encryption.  If your local site prevents
                    199: you from connecting out to port 22 (which ssh defaults to using) use
                    200: port 2022.
                    201: </p>
                    202:
                    203: <p>
                    204: Do not be tempted to turn on compression since CVS already compresses.
                    205: Use something like the following in your <strong>$HOME/.ssh/config</strong>
1.10      millert   206: file.  Note that not all anoncvs servers allow ssh connections on
                    207: port 2022.
1.1       deraadt   208: </p>
                    209: <pre>
                    210:        Host anoncvs.usa.openbsd.org
                    211:            Cipher none
                    212:            Port 2022
                    213: </pre>
                    214:
                    215: <p>
                    216: CVS is a little noisy starting up; to quiet it a bit you may want to
                    217: do this:
                    218: <pre>
                    219: setenv CVS_CLIENT_PORT -1
                    220: </pre>
                    221: </p>
                    222:
                    223: <p>
1.8       deraadt   224: If you wish to change from one CVS server to another (say your normal one is
                    225: down, or for any other reason), the environment variable which will let you
                    226: do this is
                    227: <pre>
                    228: setenv CVS_IGNORE_REMOTE_ROOT
                    229: </pre>
                    230: </p>
                    231:
                    232: <p>
1.1       deraadt   233: If you wish to be a new anoncvs mirror site, please contact the anoncvs
                    234: <a href=mailto:deraadt@theos.com>maintainer</a>.
                    235: Anoncvs mirrors require about 300MB of disk, and use up to 4MB of swap
                    236: per anoncvs user (assuming the user does a large operation; while smaller
                    237: operations use fewer resources, anoncvs still makes much more of an
                    238: impact than ftp or sup).  Such anoncvs machines should have excellent
                    239: network connectivity for the area they are expected to serve.  A
                    240: <a href=anoncvs.shar>document</a>
                    241: which describes the setup of anoncvs servers is available.
                    242: </p>
                    243:
                    244: </dl>
                    245:
                    246: <hr>
1.3       deraadt   247: <a href=index.html><img src=back.gif border=0 alt=OpenBSD></a>
1.1       deraadt   248: <a href=mailto:www@openbsd.org>www@openbsd.org</a>
1.11    ! michaels  249: <br><small>$OpenBSD: anoncvs.html,v 1.10 1997/04/07 07:43:59 millert Exp $</small>
1.1       deraadt   250:
                    251: </body>
                    252: </html>