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